I used the Kingo root method, went well was even able to install TIBackup and a few other applications.
However, I've looked and there are posts that "show" the Knox status in startup mode but where do I find it? IF I didn't flash a custom recovery to NOT trip knox, how do I verify that Knox is still 0x0?
I am hoping I am not asking a repetitive question because I did do a search on the Q&A forum first and found lots of posts "about" Knox and various other posts about this but, and PLEASE FORGIVE ME IF I DIDN'T FIND IT AND AM ASKING A REDUNDANT QUESTION, how do I confirm I haven't tripped Knox?
Thank you in advance.
Look up how to put phone in download mode and u will see it
TWEAKED 1.0 NOTE 3
BACARDILIMON said:
Look up how to put phone in download mode and u will see it
TWEAKED 1.0 NOTE 3
Click to expand...
Click to collapse
Thank you, much obliged. I swear this was driving me nuts.
FYI, in case anyone else is wondering, Kingo works great on the T-Mobile Note 3 root and no Knox trip.
Now to remove bloatware...
sanjsrik said:
Thank you, much obliged. I swear this was driving me nuts.
FYI, in case anyone else is wondering, Kingo works great on the T-Mobile Note 3 root and no Knox trip.
Now to remove bloatware...
Click to expand...
Click to collapse
i read on another thread that they worked out the security issues with kingo. i used it to root and it was quick and easy. havent experienced any side effects. it doesn't trip KNOX
I hate knox!!!
I just do not understand WHY they felt the need to put this Knox crap in the software. IJS
sanjsrik said:
Thank you, much obliged. I swear this was driving me nuts.
FYI, in case anyone else is wondering, Kingo works great on the T-Mobile Note 3 root and no Knox trip.
Now to remove bloatware...
Click to expand...
Click to collapse
Be careful. I just used the kingo app on my stock note3 and it tripped my knox warranty. So be very careful. Just proves you can't believe everything that you read.
Sent from my SM-N900T using Tapatalk
Edit: The kingo program installed clockwork mod recovery on my phone during the rooting process.
Troy1 said:
Be careful. I just used the kingo app on my stock note3 and it tripped my knox warranty. So be very careful. Just proves you can't believe everything that you read.
Sent from my SM-N900T using Tapatalk
Edit: The kingo program installed clockwork mod recovery on my phone during the rooting process.
Click to expand...
Click to collapse
The Kingo program installed supersu on my device and that's it. I still have 0x0 Knox. So, no idea what happened with yours. I don't even think CWM is included in Kingo.
Troy1 said:
Be careful. I just used the kingo app on my stock note3 and it tripped my knox warranty. So be very careful. Just proves you can't believe everything that you read.
Sent from my SM-N900T using Tapatalk
Edit: The kingo program installed clockwork mod recovery on my phone during the rooting process.
Click to expand...
Click to collapse
Kingo does not load a recovery, just a copy of supersu to provide root access. You did something to cause cwm to be installed. Perhaps a different process or you loaded cwm afterwards yourself?
I can confirm Kingo does not trip Knox, unless you did something afterwards or maybe you do not have original T-mo phone, I think the new bootloaders are locked and will trip flag, but I think T-mo should still be on MI7.
pete4k said:
I can confirm Kingo does not trip Knox, unless you did something afterwards or maybe you do not have original T-mo phone, I think the new bootloaders are locked and will trip flag, but I think T-mo should still be on MI7.
Click to expand...
Click to collapse
I thought it was weird also. But the only thing I did was verify the bootloader version at MI7 and ran the program. I watched the program run and freaked out when I saw the cyanogen robot. I didn't even have that recovery anywhere on the phone where the program could access it. I'm not sure how our why it happened. I'm new to that program and this phone but not new to flashing. I was trying to preserve all warranties and remain stock. Just wanted root. Hopefully someone will figure out how to revert knox one day.
Sent from my SM-N900T using Tapatalk
---------- Post added at 08:28 PM ---------- Previous post was at 07:52 PM ----------
I just read the kingo changelog and as of version 1.1.7 there are scripts added to use a custom recovery to inject root. On their Facebook page it even says to be aware of the risks involved in flashing a custom recovery. I used version 1.1.8 and at no time did it say it was going to install a recovery nor did it give me the option to choose not to. I am trying to get sold off the people that developed the app but cannot find an email address on the website. I'm glad that the program has worked for so many. Sad that it didn't for me. If anyone could tell me if I did something wrong it would be appreciated. Seems like I am the only one this has happened to.
Sent from my SM-N900T using Tapatalk
Sorry to hear that, when I get home tonight I'll verify which version I used, but I just double checked and my Knox flag is not tripped yet. To be fair there was at least one huge warning in red letters saying I will loose my warranty and brick my phone by using this program, so I was actually sort of expecting to trip the flag. Also it seems T-mo does not check Knox flag, or at least I have not seen one T-mo customer claiming his warranty was refused yet, due to that.
It would be nice to figure out why it didn't work for you, when it worked for many others, so we can post warning.
pete4k said:
Sorry to hear that, when I get home tonight I'll verify which version I used, but I just double checked and my Knox flag is not tripped yet. To be fair there was at least one huge warning in red letters saying I will loose my warranty and brick my phone by using this program, so I was actually sort of expecting to trip the flag. Also it seems T-mo does not check Knox flag, or at least I have not seen one T-mo customer claiming his warranty was refused yet, due to that.
It would be nice to figure out why it didn't work for you, when it worked for many others, so we can post warning.
Click to expand...
Click to collapse
I agree. And thank you for the info regarding tmobile. I just can't figure out what I would have done wrong. The warranty could be an issue but I'll deal with that if it ever arises. I was just trying to keep the phone as stock as possible. Thank you for your assistance.
Sent from my SM-N900T using Tapatalk
I used Kingo 1.1.8.1835, no problems, what's your version? And how do I check if they installed CF recovery?
pete4k said:
I used Kingo 1.1.8.1835, no problems, what's your version? And how do I check if they installed CF recovery?
Click to expand...
Click to collapse
I used 1.1.8. I just powered down and then used volume+,power and home to bit into recovery. The cool thing out of this if there is anything, is that the cwm recovery is the touch version. I had never used that version before.
Sent from my SM-N900T using Tapatalk
Stock recovery on mine and we used same version, strange
Worked PERFECTLY!
Just completed the process of rooting my new GN3...FLAWLESS! Now on to some custom ROMs!!! :victory:
Is there a way to undo root of in use kingo. I will probably want to take the kitkat ota when it released, but want to root to use some xposed mods till then.
Sent from my SM-N900T using Tapatalk
I think you just hook your phone up, start up Kingo and press unroot. I have not tried it myself but the option should be there. As a matter of fact there is nothing I read so far to want me upgrade and many to not.
sanjsrik said:
I used the Kingo root method, went well was even able to install TIBackup and a few other applications.
However, I've looked and there are posts that "show" the Knox status in startup mode but where do I find it? IF I didn't flash a custom recovery to NOT trip knox, how do I verify that Knox is still 0x0?
I am hoping I am not asking a repetitive question because I did do a search on the Q&A forum first and found lots of posts "about" Knox and various other posts about this but, and PLEASE FORGIVE ME IF I DIDN'T FIND IT AND AM ASKING A REDUNDANT QUESTION, how do I confirm I haven't tripped Knox?
Thank you in advance.
Click to expand...
Click to collapse
boot into download mode holding home+power down button+power
Related
Hello all. Can anyone tell me which is the easy way for rooting my T Mobile note 3? Sorry but I'm newbie in this phone!
Thank you, and I'll be waiting for your reply guys.
MCASTILLO said:
Hello all. Can anyone tell me which is the easy way for rooting my T Mobile note 3? Sorry but I'm newbie in this phone!
Thank you, and I'll be waiting for your reply guys.
Click to expand...
Click to collapse
There are 2 choices:
Root dela Vega - Will NOT trip the KNOX. it will remain 0x0.
http://forum.xda-developers.com/showthread.php?t=2484223
Chainfire - Will trip the KNOX to 0x1. Will void your warranty with Samsung.
http://forum.xda-developers.com/showthread.php?t=2466423
Make sure to read carefully and follow the step by step process to make your rooting a pleasant one...
kuroy301 said:
There are 2 choices:
Root dela Vega - Will NOT trip the KNOX. it will remain 0x0.
http://forum.xda-developers.com/showthread.php?t=2484223
Chainfire - Will trip the KNOX to 0x1. Will void your warranty with Samsung.
http://forum.xda-developers.com/showthread.php?t=2466423
Make sure to read carefully and follow the step by step process to make your rooting a pleasant one...
Click to expand...
Click to collapse
Thank you for your answer.
Which is better. With root dela Vega I don't loose my warranty? Sorry my friend. I don't understand very well this! But I going to read all.
If you call T-Mobile and tell them you rooted your device and now have a hardware problem.... you might have a problem.
If you leave out the root part and just describe the problems you are having most likely you will be fine.
If the device won't even turn on, etc... they can't see that it was rooted.
That said, you should really... REALLY read up on what rooting method you choose and the followup messages that are posted by those who use it so that you are aware of what issues you may run into.
If you do this fully informed, you should be both successfully rooted and able to deal with any issues you run into because you already read about it.
Also read up on what you can do with Root once you get it. Deleting a bunch of files is not a good idea if you are not really familiar with what you are doing.
Thank you for your answers.
This is my problem. When I turn on the wifi appears this notice...
I don't know what happen! But I received three replacements. And all they is the same problem! I really like the root cell phone. At the moment I have note 2 rooting. And it working very good!
But. Can anyone help with this notice. Please? By the way. The phone doesn't have any application, only of factory.
If you do a simple google search for prevention information samsung, you will find a ton of messages in many forums about this. It is a bug that many samsung devices are currently experiencing.
Hard to imagine you have gotten three replacement phones for this issue AND didn't makes this the topic of your question instead of rooting.
If you are rooted, you can freeze the KNOX apps and you most likely won't see these errors. I don't.
krelvinaz said:
If you do a simple google search for prevention information samsung, you will find a ton of messages in many forums about this. It is a bug that many samsung devices are currently experiencing.
Hard to imagine you have gotten three replacement phones for this issue AND didn't makes this the topic of your question instead of rooting.
If you are rooted, you can freeze the KNOX apps and you most likely won't see these errors. I don't.
Click to expand...
Click to collapse
Then.. Is this normal. My phone will continue with this bug?
One more thing. I'm interesting in root. And the issue with my phone. This is the right place. Q&A. Help. Troubleshooting. Doesn't it?
And thank you.
Do you have any issue with your phone. Any bug. If your phone is root at the moment, right now you have any bug. Or you have issue with KNOX?
MCASTILLO said:
Then.. Is this normal. My phone will continue with this bug?
One more thing. I'm interesting in root. And the issue with my phone. This is the right place. Q&A. Help. Troubleshooting. Doesn't it?
And thank you.
Do you have any issue with your phone. Any bug. If your phone is root at the moment, right now you have any bug. Or you have issue with KNOX?
Click to expand...
Click to collapse
It is a bug, ie should not be happening.
It affects more than the Note 3 and is known. Assumption is that Samsung is fixing it. Don't know if the fix will come from them or T-Mobile.
I am rooted, used the De La Vega Root method when I got the phone.
As a rooted device, I can use Titanium Backup to Freeze the Knox apps and as a result the "bug" does not show.
I have not use for Knox nor plan to. Knox flag is 0x0 though.
Below shows the frozen KNOX apps.
Any one click apk or mac options? I dont have a pc and money is tight!
Sent from my GT-N5110 using XDA Premium HD app
I just bought a T-Mobile Note 3 (N-900T) with 4.4.2 out of the box and have been looking through a billion posts trying to figure out how to root it. Some of the things I read suggest that something else might have been done first, because I'm joining in the middle of the ball game. So far I think I've found four ways to root:
1. Root de la Vega (for 4.4.2?).
2. Install TWRP (Installs Recovery and su?).
3. CF Auto Root (trips Knox?).
See how confused I am? I lost the fourth way. I can't figure out if any actually work on a new 4.4.2.
My desire is root and Recovery, no custom ROM and no Kingo/Vroot.
Comments please.
Frank
I agree with you. I have been researching this subject and still not sure what to use to ROOT. I rooted my Note 2 using Kingo Android Root and that was so simple.
Don't really know if I can use Kingo Android Root for 4.4.2?
Frank Westlake said:
I just bought a T-Mobile Note 3 (N-900T) with 4.4.2 out of the box and have been looking through a billion posts trying to figure out how to root it. Some of the things I read suggest that something else might have been done first, because I'm joining in the middle of the ball game. So far I think I've found four ways to root:
1. Root de la Vega (for 4.4.2?).
2. Install TWRP (Installs Recovery and su?).
3. CF Auto Root (trips Knox?).
See how confused I am? I lost the fourth way. I can't figure out if any actually work on a new 4.4.2.
My desire is root and Recovery, no custom ROM and no Kingo/Vroot.
Comments please.
Frank
Click to expand...
Click to collapse
I used CF auto root. look into something called triangle away.
I plan to keep my phone regardless, and I take care of it. There's always odin if you screw up so...
I built this tread just because I have answered this question about 4 times in the last two days. It is a work in progress but I hope to help others with their rooting questions. Hope this helps and if you have questions please ask it in my thread so I can make updates. Thanks.
http://forum.xda-developers.com/showthread.php?t=2704340
To OP - why don't you want to use Kingosoft?
I use Kingosoft, no KNOX trip, work just fine for almost 1 month now. Also, I can unroot easily if I want to. In my past experience with Samsung phones, unrooting can be as complex as rooting it in the first place, so I appreciate the ability to unroot easily with Kingosoft.
lanwarrior said:
To OP - why don't you want to use Kingosoft?
I use Kingosoft, no KNOX trip, work just fine for almost 1 month now. Also, I can unroot easily if I want to. In my past experience with Samsung phones, unrooting can be as complex as rooting it in the first place, so I appreciate the ability to unroot easily with Kingosoft.
Click to expand...
Click to collapse
Just as a clarification:
You have 4.4.2, rooted with that method, and it didn't trip the Knox counter?
As far as I understand it, there is currently no way to root a 4.4.2 Note 3 which doesn't trip Knox. There is some trickery where you can attain root on 4.4.2 without tripping Knox using Mobile Odin Pro, but that process requires that you to start on 4.3.
tygerchylde said:
Just as a clarification:
You have 4.4.2, rooted with that method, and it didn't trip the Knox counter?
Click to expand...
Click to collapse
Oh crap, I didn't know you have 4.4.2. Sorry, Kingo won't work with Kit Kat.
I have 4.3.
Once your are on 4.4.2, there is currently no way to root it without tripping the KNOX. There are several ways to root but all will trigger the KNOX flag.
FFTony said:
I built this tread just because I have answered this question about 4 times in the last two days. It is a work in progress but I hope to help others with their rooting questions. Hope this helps and if you have questions please ask it in my thread so I can make updates. Thanks.
http://forum.xda-developers.com/showthread.php?t=2704340
Click to expand...
Click to collapse
Thanks for your posting and info. Read it and you go into a lot of detail.
I guess I am too lazy to try to go through so many steps to root. I personally am looking for a program that will Root without all the additional things to download and install, etc. Until that program is identified, I will remain Stock and unRooted. Personally I am not worried about tripping Knox as I keep my phones for 1 year then pass them down to wife or kids when I upgrade.
---------- Post added at 07:33 PM ---------- Previous post was at 07:31 PM ----------
imaleecher said:
Once your are on 4.4.2, there is currently no way to root it without tripping the KNOX. There are several ways to root but all will trigger the KNOX flag.
Click to expand...
Click to collapse
I am not worried about tripping KNOX. Is there one program like Kingo Android Root that I used on my Note 2 to Root the Note 3? If so, please let us know what it is. Thanks!
Look up CF-Auto-Root. That is a more simplified way to root. My way is if you are also looking to add a custom recovery.
sm-n900t: Powered by X-Note V13
FFTony said:
Look up CF-Auto-Root. That is a more simplified way to root. My way is if you are also looking to add a custom recovery.
Click to expand...
Click to collapse
That procedure is not complex. Install TWRP and it installs SuperSU as a bonus. The deterrant for some people, I think, is the need to use Odin to install TWRP. Maybe they will get that problem with GooApp fixed and TWRP installation will get easier. But if Odin is the problem then CF-Auto-Root is the same.
Frank
FFTony said:
Look up CF-Auto-Root. That is a more simplified way to root. My way is if you are also looking to add a custom recovery.
sm-n900t: Powered by X-Note V13
Click to expand...
Click to collapse
Don't mean to be stupid, however, CF-Auto-Root has many different versions such as:
1. hite-hitexx-smn9005
2. t03g-to3gxx-9tn7100
3. mo-moxx-fti9300
all of which are ZIP files.
I have Model SM-n900T using Android 4.4.2 T-Mobile Stock.
Does it matter which one of the three above that I would use?
I ASS U ME that I would use 1 since it is 9005?
Thanks for all your help. Maybe I am beyond help. LOL
asctony said:
Don't mean to be stupid, however, CF-Auto-Root has many different versions such as:
1. hite-hitexx-smn9005
2. t03g-to3gxx-9tn7100
3. mo-moxx-fti9300
all of which are ZIP files.
I have Model SM-n900T using Android 4.4.2 T-Mobile Stock.
Does it matter which one of the three above that I would use?
I ASS U ME that I would use 1 since it is 9005?
Thanks for all your help. Maybe I am beyond help. LOL
Click to expand...
Click to collapse
1 is correct that is the model of your phone. *Actually SM-N9005 is the international model and sm-n900t is the tmobile variant but it should work*
If you just want root then CF auto root is good. If you are planning on adding a custom recovery or ROM I would recommend following the root options provided in the link a few comments above.
SM-N900T: Powered by X-Note V13/CivZ-SnapKat 2.1
FFTony said:
1 is correct that is the model of your phone. *Actually SM-N9005 is the international model and sm-n900t is the tmobile variant but it should work*
If you just want root then CF auto root is good. If you are planning on adding a custom recovery or ROM I would recommend following the root options provided in the link a few comments above.
SM-N900T: Powered by X-Note V13/CivZ-SnapKat 2.1
Click to expand...
Click to collapse
FFTony: Thank you very much for your suggestions. I have flashed roms on many of my previous phones and tried so many that it got to the point that I was flashing daily and returning back to stock. I do customize my Note 3 and have done so on many of my other phones. So, I think I will just root to uninstall bloatware. Some of the apks that I use are:
Android Assistant,
Calendar Status
Clean Master
Dolphin Browser Mini
EvernoteGo SMS Pro
HD Widgets
Kingsoft Office
MXPlayer
n7Player
Next Launcher
QuickPic
Swipe Home Button
Swipe Dialer Pro
Tunein Radio Pro
Various News Apks (News360 my favorite)
Titanium Backup Pro (when rooted and on my Note 2)
Just to name a few.
Tried many more but go back to these favorites.
So, Thank again!!!!
You are welcome. I was never into rooting until I purchased the note 3 and this is a phone that is a must to root if you want to take full advantage of all that it can do. I am also glad to give back to this community that helped me learn so much.
SM-N900T: Powered by X-Note V13/CivZ-SnapKat 2.1
FFTony said:
You are welcome. I was never into rooting until I purchased the note 3 and this is a phone that is a must to root if you want to take full advantage of all that it can do. I am also glad to give back to this community that helped me learn so much.
SM-N900T: Powered by X-Note V13/CivZ-SnapKat 2.1
Click to expand...
Click to collapse
Totally agree with your comments regarding this community. They have helped me over the years, too.
I Unzip CF-Auto-Root and now have the following files:
TMAX.dll
Zlib.dll
ODIN3-V3.07.Exe
Odin3.ini
CF-Auto-Root-hite-hitexx-smn9005.tar.md5
Where do I go from here? I assume that I would connect my Note3 via USB and execute ODIN3-V3.07.exe.
All these unzipped files are in one folder.
Thanks again!
asctony said:
Totally agree with your comments regarding this community. They have helped me over the years, too.
I Unzip CF-Auto-Root and now have the following files:
TMAX.dll
Zlib.dll
ODIN3-V3.07.Exe
Odin3.ini
CF-Auto-Root-hite-hitexx-smn9005.tar.md5
Where do I go from here? I assume that I would connect my Note3 via USB and execute ODIN3-V3.07.exe.
All these unzipped files are in one folder.
Thanks again!
Click to expand...
Click to collapse
Yes, open Odin place the .tar file in the PDA section. Make sure you do not check any boxes on the left. The only ones that should be checked is auto reboot and F. Reset Time. Then hit start.
This conversation is growing silly, I don't know to fault the carriers, manufactures, Google, or us the consumers. This is stupid. It's our device we shouldn't need to do all this to gain certain features. I wouldn't need root if you stop putting all this bull ish on my device, restricting r/w to external sd etc just pathetic. I'm not worried about tripping KNOX, I pushed her down on purpose !
Sent from my SM-N900T using Tapatalk
bipoler said:
This conversation is growing silly, I don't know to fault the carriers, manufactures, Google, or us the consumers. This is stupid. It's our device we shouldn't need to do all this to gain certain features. I wouldn't need root if you stop putting all this bull ish on my device, restricting r/w to external sd etc just pathetic. I'm not worried about tripping KNOX, I pushed her down on purpose !
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Agree! So, what is your suggestion?
I upgraded to 4.4.2 on my TMobile Galaxy S4. I did this Via KIES. Afterwards, I tried to root - and this is where things seemed to go wrong.
I used ODIN 3.185, and used T-Mobile_OUDHS-Recovery-jfltetmo and then installed ROOT_M919UVUAMDL.
Since then, I have the
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Message at boot, and the Samsung Galaxy S4 logo.
I tried to use Odin to put over the top CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar
I tried also to use the SD card to update again to what I think is the stock firmware from here: http://forum.xda-developers.com/showpost.php?p=50977575&postcount=49&nocache=1&z=9496224221703208
When doing an update, there were a couple of errors - but it went through. However, on reboot the same error.
Any help would be extremely appreciated.
My next try is to do the unroot steps from this post: http://forum.xda-developers.com/showthread.php?t=2335109
But hopefully someone can give some more advice before I wipe the whole thing.
Since it's a work in progress, I figure I will post as I go along.
I downloaded the 1.5gb TMB-M919UVUFNB4-20140314115123 file from the unroot link above. I then used Odin to install it... and was able to stop at step 9 - before doing the data wipe/factory restore. I can now get my phone to boot.
I am feeling so good - that I'll try to root again.
Rooted, and SuperSU instaled - all is well to this point...
Since I was fairly freaked out, hopefully this helps someone down the line (or me - since I'm fast to forget).
You tripped the Knox flag. That's all that happened. It won't affect your ability to use the phone. You didn't do anything wrong. it's normal when you root a Knox protected device.
I ran into the same issue as you on my TMobile Samsung Galaxy S4 and I wanted to say thanks for this post! It helped me get my phone restored back to the way it was and thankfully I didn't lose anything! Thanks so much!
Was wondering however.....how did you get it to root successfully after this?
I used this guide to try to root my phone
http://www.androidrootz.com/2013/05/how-root-cwm-recovery-on-galaxy-s4-gt.html
Did you use another set of steps?
Thanks in advance!
0verfiend said:
Since it's a work in progress, I figure I will post as I go along.
I downloaded the 1.5gb TMB-M919UVUFNB4-20140314115123 file from the unroot link above. I then used Odin to install it... and was able to stop at step 9 - before doing the data wipe/factory restore. I can now get my phone to boot.
I am feeling so good - that I'll try to root again.
Click to expand...
Click to collapse
anoshwadia said:
I ran into the same issue as you on my TMobile Samsung Galaxy S4 and I wanted to say thanks for this post! It helped me get my phone restored back to the way it was and thankfully I didn't lose anything! Thanks so much!
Was wondering however.....how did you get it to root successfully after this?
I used this guide to try to root my phone
http://www.androidrootz.com/2013/05/how-root-cwm-recovery-on-galaxy-s4-gt.html
Did you use another set of steps?
Thanks in advance!
Click to expand...
Click to collapse
That procedure is so old and outdated, you should really pay attention to what you read and the sites you visit.. Everything you need is here on XDA.. Use cf-auto root to root the phone, do whatever you want afterwards..
Sent from my SGH-M919 using Tapatalk
Appreciate the response. I should have mentioned that I did start off at XDA. I used this thread
http://forum.xda-developers.com/showthread.php?t=2335109
....and it led me to use that link in my previous post. I figured since it was under the forums for my device and had been stickied, it would work fine. I didn't see anyone else on that thread report the issue I ran into, possibly because it worked prior to an update I had from Tmobile.
I will try your suggestions with cf-auto root. Thanks again for the help!
serio22 said:
That procedure is so old and outdated, you should really pay attention to what you read and the sites you visit.. Everything you need is here on XDA.. Use cf-auto root to root the phone, do whatever you want afterwards..
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Skipjacks said:
You tripped the Knox flag. That's all that happened. It won't affect your ability to use the phone. You didn't do anything wrong. it's normal when you root a Knox protected device.
Click to expand...
Click to collapse
Hi, is there a way to get rid of it?
I'm rooted and have TWRP 2.8 no problems, also I'm on Insanity V11 ROM, but those lines are too ugly :crying::crying::crying:
Railius said:
Hi, is there a way to get rid of it?
I'm rooted and have TWRP 2.8 no problems, also I'm on Insanity V11 ROM, but those lines are too ugly :crying::crying::crying:
Click to expand...
Click to collapse
Flash unmodified stock kernel
I really new to android and switch from apple to android But I saw the risks of flashing to get root vs with apple Ive never seen a hard brick happened. I was wondering if I should wait till theres an app/application to root my samsung galaxy tab S 10.5 or flash a rooted rom to get root? I also heard that Android L is gonna be out soon so.. should i wait till Android L is out to root also? Im scared to flash because I dont want to turn my tab s a brick D: Like some how i seem to mess the easy stuff up.
Thanks!
p.s Im not sure if im posting this in the right place or... yeah. Pretty new to android.
DUHAsianSKILLZ said:
I really new to android and switch from apple to android But I saw the risks of flashing to get root vs with apple Ive never seen a hard brick happened. I was wondering if I should wait till theres an app/application to root my samsung galaxy tab S 10.5 or flash a rooted rom to get root? I also heard that Android L is gonna be out soon so.. should i wait till Android L is out to root also? Im scared to flash because I dont want to turn my tab s a brick D: Like some how i seem to mess the easy stuff up.
Thanks!
p.s Im not sure if im posting this in the right place or... yeah. Pretty new to android.
Click to expand...
Click to collapse
I would wait if you are new to the scene. It seems that depending on your current OS version, 4.3 (open) vs 4.4.x (locked), we have a looked bootloader. So flashing sth might leave you with a bootloader that denies loading the images because of failed hashes.
As to really bricking it, I don't think it is that easy as long as you know your way with software and IT. But DON'T flash sth or toggle some switch you don't know about. simple. I tried flashing TWRP to the recovery partition and rooting from there with SU as suggested in a thread here, BUT it wouldn't accept TWRP because of a lock...still tripped the KNOX though
JoeRifle said:
I would wait if you are new to the scene. It seems that depending on your current OS version, 4.3 (open) vs 4.4.x (locked), we have a looked bootloader. So flashing sth might leave you with a bootloader that denies loading the images because of failed hashes.
As to really bricking it, I don't think it is that easy as long as you know your way with software and IT. But DON'T flash sth or toggle some switch you don't know about. simple. I tried flashing TWRP to the recovery partition and rooting from there with SU as suggested in a thread here, BUT it wouldn't accept TWRP because of a lock...still tripped the KNOX though
Click to expand...
Click to collapse
Oh Didnt know all that stuff until now All this is very different from jailbreaking which I know alot of. Thanks for the help! I only plan on getting root and not any of the custom roms yet since im trying to not get knox tripped and the fact that i cant return my tab s for any reason because of walmarts 15-day return. I guess ill stay unrooted for now thanks again
It sucks that they try so hard to cage us in but just wait a bit, people will find out how to root even the new OS 4.4.x. Although I am not sure whether it will ever be possible to do it without KNOX tripping. Maybe you can somehow restore a tripped KNOX to 0 though...but that is over my head If you are @4.3 Android though, you might just try going ahead and flashing TWRP with Odin, and then install appropriate SuperUser .zip. Your call
JoeRifle said:
I would wait if you are new to the scene. It seems that depending on your current OS version, 4.3 (open) vs 4.4.x (locked), we have a looked bootloader. So flashing sth might leave you with a bootloader that denies loading the images because of failed hashes.
As to really bricking it, I don't think it is that easy as long as you know your way with software and IT. But DON'T flash sth or toggle some switch you don't know about. simple. I tried flashing TWRP to the recovery partition and rooting from there with SU as suggested in a thread here, BUT it wouldn't accept TWRP because of a lock...still tripped the KNOX though
Click to expand...
Click to collapse
Are you sure you know what you're talking about? All our Tablet S came with Android 4.4.2, and they are rooted just fine.
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
DUHAsianSKILLZ said:
Oh Didnt know all that stuff until now All this is very different from jailbreaking which I know alot of. Thanks for the help! I only plan on getting root and not any of the custom roms yet since im trying to not get knox tripped and the fact that i cant return my tab s for any reason because of walmarts 15-day return. I guess ill stay unrooted for now thanks again
Click to expand...
Click to collapse
You're being given wrong info. Rooting is easy, as is installing a custom recovery. But yes, if you don't wish to trip knox then there is currently no way to do so.
kenkiller said:
Are you sure you know what you're talking about? All our Tablet S came with Android 4.4.2, and they are rooted just fine.
Click to expand...
Click to collapse
Well, I thought I was sure, wouldn't have said it else. My Tab S did not come with 4.4.2, as it installed some OTA when first connected.
You're being given wrong info. Rooting is easy, as is installing a custom recovery. But yes, if you don't wish to trip knox then there is currently no way to do so.
Click to expand...
Click to collapse
Please share your info on how to root it or install custom recovery. If I was babbling away, being mostly PC/new tab user, please correct my mistakes. No harm intended.
EDIT: Thinking about it. Do you by chance mean flashing the CF Auto t800 image from the development thread? That is not a t805 image so it did not really appeal to me, and it said in the same thread that it is not needed...since you can odin TWRP...which did not work for me. Mean that?
JoeRifle said:
Well, I thought I was sure, wouldn't have said it else. My Tab S did not come with 4.4.2, as it installed some OTA when first connected.
Please share your info on how to root it or install custom recovery. If I was babbling away, being mostly PC/new tab user, please correct my mistakes. No harm intended.
EDIT: Thinking about it. Do you by chance mean flashing the CF Auto t800 image from the development thread? That is not a t805 image so it did not really appeal to me, and it said in the same thread that it is not needed...since you can odin TWRP...which did not work for me. Mean that?
Click to expand...
Click to collapse
Read through the thread again.....many reports from users who got T805 rooted using the T800 cf-auto files without any problems.
kenkiller said:
Read through the thread again.....many reports from users who got T805 rooted using the T800 cf-auto files without any problems.
Click to expand...
Click to collapse
you are right. I did not find the image "elegible" as it was not based of a t805, and I tried the "other", "slicker" method which did not work. The only reason I could see as to why it did no accept the flash, INet research confirmed suspicion too btw, was that 4.4.x has a hash check at boot up. This would make it extremely hard to root/install TWRP by flashing w/out overcoming this check first.
My comments were based on these assumptions. So sry for the confusion @DUHAsianSKILLZ
JoeRifle said:
you are right. I did not find the image "elegible" as it was not based of a t805, and I tried the "other", "slicker" method which did not work. The only reason I could see as to why it did no accept the flash, INet research confirmed suspicion too btw, was that 4.4.x has a hash check at boot up. This would make it extremely hard to root/install TWRP by flashing w/out overcoming this check first.
My comments were based on these assumptions. So sry for the confusion @DUHAsianSKILLZ
Click to expand...
Click to collapse
If 4.4.2 has this so called hash check at boot up, why would it not matter in using cf-root for T800 then using Flashify to install TWRP? Think about it.
@DUHAsianSKILLZ
flashing the CF Auto for the t800 from the dev thread did the trick for me too. Rooted and can't seem to find problems. Knox tripped oc. Check this thread for more info if you like http://forum.xda-developers.com/gal...cf-autoroot-t800-t2802916/page17#post54769521
@kenkiller
I don't know. It should detect changes to system partition...at least.
kenkiller said:
But yes, if you don't wish to trip knox then there is currently no way to do so.
Click to expand...
Click to collapse
Is any way to delete trip knox? How about warranty after tripping knox?
szfagir said:
Is any way to delete trip knox? How about warranty after tripping knox?
Click to expand...
Click to collapse
Worrying about warranty? Don't root.
---------- Post added at 02:55 PM ---------- Previous post was at 02:54 PM ----------
JoeRifle said:
@DUHAsianSKILLZ
flashing the CF Auto for the t800 from the dev thread did the trick for me too. Rooted and can't seem to find problems. Knox tripped oc. Check this thread for more info if you like http://forum.xda-developers.com/gal...cf-autoroot-t800-t2802916/page17#post54769521
@kenkiller
I don't know. It should detect changes to system partition...at least.
Click to expand...
Click to collapse
Don't assume next time.
kenkiller said:
Worrying about warranty? Don't root.
Click to expand...
Click to collapse
Now know that
kenkiller said:
Are you sure you know what you're talking about? All our Tablet S came with Android 4.4.2, and they are rooted just fine.
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
You're being given wrong info. Rooting is easy, as is installing a custom recovery. But yes, if you don't wish to trip knox then there is currently no way to do so.
Click to expand...
Click to collapse
Yeah I thought so to since I saw the thread about rooting the tab s. I'll guess I'll wait till there's a one click app to root like towel root since towel root isn't gonna be updated no more.
DUHAsianSKILLZ said:
Yeah I thought so to since I saw the thread about rooting the tab s. I'll guess I'll wait till there's a one click app to root like towel root since towel root isn't gonna be updated no more.
Click to expand...
Click to collapse
You're gonna be in for a long wait.
kenkiller said:
You're gonna be in for a long wait.
Click to expand...
Click to collapse
Wow this was long ago... I rooted a week later after this thread was made.. . I do not regret tripping Knox. Ive installed many many roms and built one myself. I learned a lot since I got my tab s. Just wanted to say thank you and everyone else for their help I've done so many things and know a whole lot about Android now Currently working on a theme now. I can't believe I was still subscribed to this thread
Hey, so I really want to root my A5 as I have a few issues with it unrooted (mostly with wakelocks) and just generally dislike using it unrooted but as far as I can see there's isn't an option yet.
I'm offering a $50 bounty in BTC to whoever creates the tools and a short guide to root it without tripping Knox.
I know it's not much but others might chip in as well.
There is already root available since yesterday.
Unfortunately only with cwm look at this link.
https://m.youtube.com/watch?v=YtvJU9aDnHM&feature=youtu.be
bassbounce said:
There is already root available since yesterday.
Unfortunately only with cwm look at this link.
https://m.youtube.com/watch?v=YtvJU9aDnHM&feature=youtu.be
Click to expand...
Click to collapse
I see, nice. And do we know who made it?
I'll wait for a few replies if it's really works without tripping Knox though.
I'm out of the loop why people hate CWM.
bathrobehero said:
I see, nice. And do we know who made it?
I'll wait for a few replies if it's really works without tripping Knox though.
I'm out of the loop why people hate CWM.
Click to expand...
Click to collapse
CWM will trip knox for sure. Only way without knox tripped would probably be to get a hold of engineer sboot/boot combination from samsung and be able to root it through ADB.
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
I used this method today ive also used in the past the twrp method prefer the cwm one though far less steps found though cwm has a lot more chance of bootlooping but far easier ... so to sum up cwm version easy 2 steps really but very finicky... twrp lot more stable but a little more complicated dmverity etc... will again comment in a couple of days let you know how cwm is going now i have stabilized it....
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622 is thread for twrp method