Develop Bugs

Triangle Away

Do you need to use triangle away when you first root your phone? Or can you just use it when you need to return the phone back to stock? I want to root and if I need to return my phone for warranty I want to be able to put the phone back to stock with 0 flash counter.

later not needed right away

hold on but.....
dpshptl said:
Do you need to use triangle away when you first root your phone? Or can you just use it when you need to return the phone back to stock? I want to root and if I need to return my phone for warranty I want to be able to put the phone back to stock with 0 flash counter.
Click to expand...
Click to collapse
U can just hold on on if u need to return it for service, u don't have to use it rite now since u most likely will be flashing roms and u will be triggering ur counter everytime u flash or root ur device.
ONE THING TO KNOW ABOUT TRIANGLE AWAY, IS THAT AS FAR AS I KNOW ( I DON'T KNOW ANYONE THAT HAS TRIANGLE AWAY WORKING AFTER THE 1ST JB UPDATE ) TRIANGLE AWAY WON'T WORK ON OUR DEVICES PAST JB, SO IF U NEED TO RESET YOU COUNTER U NEED TO ODIN BACK TO ICS STOCK ROOTED AND THEN USE TRIANGLE AWAY.
sorry about the caps, just tryin to make my point clear, if anyone has triangle away working on JB please feel free to post about it.:laugh:

Mr_Jay_jay said:
U can just hold on on if u need to return it for service, u don't have to use it rite now since u most likely will be flashing roms and u will be triggering ur counter everytime u flash or root ur device.
ONE THING TO KNOW ABOUT TRIANGLE AWAY, IS THAT AS FAR AS I KNOW ( I DON'T KNOW ANYONE THAT HAS TRIANGLE AWAY WORKING AFTER THE 1ST JB UPDATE ) TRIANGLE AWAY WON'T WORK ON OUR DEVICES PAST JB, SO IF U NEED TO RESET YOU COUNTER U NEED TO ODIN BACK TO ICS STOCK ROOTED AND THEN USE TRIANGLE AWAY.
sorry about the caps, just tryin to make my point clear, if anyone has triangle away working on JB please feel free to post about it.:laugh:
Click to expand...
Click to collapse
This is not even close to the truth.

Aerowinder said:
This is not even close to the truth.
Click to expand...
Click to collapse
and u say this because? I mean I'm just talking on my experience with triangle away and JB It didn't work, I would use it and it would reset but once I restarted the counter would go back to "1" and honestly I'm not the only one, so please if u know the rite answer please explain, just calling me a liar is not helping anyone at all.

Mr_Jay_jay said:
and u say this because? I mean I'm just talking on my experience with triangle away and JB It didn't work, I would use it and it would reset but once I restarted the counter would go back to "1" and honestly I'm not the only one, so please if u know the rite answer please explain, just calling me a liar is not helping anyone at all.
Click to expand...
Click to collapse
I'm not calling you a liar. I simply stated that your post was not factually accurate. TriangleAway does indeed work as intended on even the new MD5.
Using a custom recovery will cause your flash counter to trip on newer JB builds. This may be what you meant, but the issue is not related to TA. It's a bootloader "feature". You can witness this yourself by resetting the flash counter, then rebooting into download mode. Count will be 0.

Aerowinder said:
I'm not calling you a liar. I simply stated that your post was not factually accurate. TriangleAway does indeed work as intended on even the new MD5.
Using a custom recovery will cause your flash counter to trip on newer JB builds. This may be what you meant, but the issue is not related to TA. It's a bootloader "feature". You can witness this yourself by resetting the flash counter, then rebooting into download mode. Count will be 0.
Click to expand...
Click to collapse
So what u're saying is that my custom recovery is to blamed? I can say that statement is partially true. Wait.. u think I havent tried to reset my counter while on JB before?? I'm telling it didn't work why don't you go head and try to reset your counter and show that it did work.
check it out.
http://www.youtube.com/watch?v=LxpL46-Zd0A&feature=youtu.be

Mr_Jay_jay said:
So what u're saying is that my custom recovery is to blamed? I can say that statement is partially true. Wait.. u think I havent tried to reset my counter while on JB before?? I'm telling it didn't work why don't you go head and try to reset your counter and show that it did work.
check it out.
http://www.youtube.com/watch?v=LxpL46-Zd0A&feature=youtu.be
Click to expand...
Click to collapse
He's correct. Having a custom recovery will always trip the flash counter to 1 after every subsequent reboot. If you use Ta and reboot, you'll see 0. But the next time you reboot and don't use Ta you will see 1. It doesn't matter what ROM you run or how you've rooted in the end, the custom binary (TWRP / CWM) will Always trip the counter.
That being said if you don't want to continously trip the counter you're going to need to go back to stock recovery.
Sent from my SGH-T999 using Tapatalk 2

TheLastSidekick said:
He's correct. Having a custom recovery will always trip the flash counter to 1 after every subsequent reboot. If you use Ta and reboot, you'll see 0. But the next time you reboot and don't use Ta you will see 1. It doesn't matter what ROM you run or how you've rooted in the end, the custom binary (TWRP / CWM) will Always trip the counter.
That being said if you don't want to continously trip the counter you're going to need to go back to stock recovery.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I do Agree with his statment, however while I was on any ICS rom even with custom recovery, TA would work even after a reboot, so my counter would stay at "0" it wasnt after I upgraded to JB when the TA would reset after reboot. I will upload a video of doing TA on ICS and everything just to prove I'm not just arguing just because. but it will have to wait til l8er tonite.

Mr_Jay_jay said:
I do Agree with his statment, however while I was on any ICS rom even with custom recovery, TA would work even after a reboot, so my counter would stay at "0" it wasnt after I upgraded to JB when the TA would reset after reboot. I will upload a video of doing TA on ICS and everything just to prove I'm not just arguing just because. but it will have to wait til l8er tonite.
Click to expand...
Click to collapse
There is no need for a video. I understand what you are saying, and I'm telling you, it's because of the bootloader. Not TriangleAway.

I am on 4.1.1 and TA 2.90 works FINE, the Counter shows "0" after a bunch of reboots, and "Allow tracker to run" is checked...
The ONLY time the counter trips is when/if I boot into the recovery or downloader modes.
I guess some structure of the setup makes a difference. I am using Root66 SGHT999 Build JR003L.T999UVDLJA with a T999UVDMD5 Baseband

bobolinko said:
I am on 4.1.1 and TA 2.90 works FINE, the Counter shows "0" after a bunch of reboots, and "Allow tracker to run" is checked...
The ONLY time the counter trips is when/if I boot into the recovery or downloader modes.
I guess some structure of the setup makes a difference. I am using Root66 SGHT999 Build JR003L.T999UVDLJA with a T999UVDMD5 Baseband
Click to expand...
Click to collapse
kool. maybe that's a good workaround. thanks. but in my case still won't work.. but then again i'm 4.1.2. thanks!

Mr_Jay_jay said:
U can just hold on on if u need to return it for service, u don't have to use it rite now since u most likely will be flashing roms and u will be triggering ur counter everytime u flash or root ur device.
ONE THING TO KNOW ABOUT TRIANGLE AWAY, IS THAT AS FAR AS I KNOW ( I DON'T KNOW ANYONE THAT HAS TRIANGLE AWAY WORKING AFTER THE 1ST JB UPDATE ) TRIANGLE AWAY WON'T WORK ON OUR DEVICES PAST JB, SO IF U NEED TO RESET YOU COUNTER U NEED TO ODIN BACK TO ICS STOCK ROOTED AND THEN USE TRIANGLE AWAY.
sorry about the caps, just tryin to make my point clear, if anyone has triangle away working on JB please feel free to post about it.:laugh:
Click to expand...
Click to collapse
You can avoid using Odin and flash old firmware (excluding system / kernel) directly via heimdall or dd (which can be nicely bundled into an update.zip), avoiding the whole mess of needing Odin/Windows and having to backup+restore your system.
I think I'll make an update.zip just to flash the oldest firmware onto our phones -- I just made one that flashes the latest UVDMD5 firmware. The ROM shouldn't make a difference as far as trying to clear the flash counter really, it's the firmware that would be blocking that.
Also, flashing ROMs through CWM Recovery (and probably other custom ones) avoids tripping the flash counter. If you can root your ROM and dd the recovery directly to your eMMC, it avoids tripping the flash counter. Then you can use CWM Recovery to flash things without tripping the counter as well.
Remember, these are just computers with Linux + kernel modifications + custom Java VM running on them, essentially. It's good to become comfortable with UNIX commands like dd.

mnasledov said:
Also, flashing ROMs through CWM Recovery (and probably other custom ones) avoids tripping the flash counter. If you can root your ROM and dd the recovery directly to your eMMC, it avoids tripping the flash counter. Then you can use CWM Recovery to flash things without tripping the counter as well.
Remember, these are just computers with Linux + kernel modifications + custom Java VM running on them, essentially. It's good to become comfortable with UNIX commands like dd.
Click to expand...
Click to collapse
I think you might be a tad off on this ......
just booting into recovery when you use anything other than a stock recovery will trip the flash counter. the ONLY way that counter won't trip is when you use a stock recovery. At least that's been the case with all of the doings on my rooted gs3 and Note 10.1

bobolinko said:
I think you might be a tad off on this ......
just booting into recovery when you use anything other than a stock recovery will trip the flash counter. the ONLY way that counter won't trip is when you use a stock recovery. At least that's been the case with all of the doings on my rooted gs3 and Note 10.1
Click to expand...
Click to collapse
Really? I mean I'm no authority on this, so I could be wrong but I based this off my findings last night. I was in Download mode quite a few times and got to see my Flash Counter which was at 3. I've gone into recovery dozens if not hundreds of times by now on this device as well as flashed dozens and dozens of things ...
Even if it was just an 8-bit counter that overflowed, I'd need to have flashed over 256 things which I don't think I've reached yet and it would be totally silly if Samsung made the counter so easy to defeat that an 8-bit numeric overflow would bring it back to 0.
Can anyone else chime/weigh in? I'm curious now. I heard that using dd is supposed to avoid the flash counter. As a software engineer, I'd think there has to be some hook to trip that counter and that hook would belong to whatever firmware is on the phone for flashing (i.e. the stock recovery) and that if any other software gains control of the phone, all bets are off.

bobolinko said:
I think you might be a tad off on this ......
just booting into recovery when you use anything other than a stock recovery will trip the flash counter. the ONLY way that counter won't trip is when you use a stock recovery. At least that's been the case with all of the doings on my rooted gs3 and Note 10.1
Click to expand...
Click to collapse
I don't know who told you all of that or where you read it but you are wrong.
The only things that trip the flash counter is when you flash a custom rom or a custom kernel.
Simply booting into stock or custom recovery will not trip the flash counter at all.
Think about it, that's why it's called a FLASH counter, it counts the number of rom and kernel flashes. LOL

Misterjunky said:
I don't know who told you all of that or where you read it but you are wrong.
The only things that trip the flash counter is when you flash a custom rom or a custom kernel.
Simply booting into stock or custom recovery will not trip the flash counter at all.
Think about it, that's why it's called a FLASH counter, it counts the number of rom and kernel flashes. LOL
Click to expand...
Click to collapse
It trips whenever I boot into TWRP though. Maybe some phones are different?
Sent from my SGH-T999 using Tapatalk 2

re: unlocked?
TheLastSidekick said:
It trips whenever I boot into TWRP though. Maybe some phones are different?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Perhaps since I have an unlocked phone it might make a difference?
I have a Galaxy S3 AT&T I747 Unlocked phone and am using it with Tmobile service.

That makes sense actually lol as it says I have an SGH-T999 and mine isn't unlocked. Probably the model of the phone acts slightly differently with Ta and recoveries.
Sent from my SGH-T999 using Tapatalk 2

In my case My counter won't move from "1" no matter what I do, Restart to download or Recovery ( TWRP), or flash a new rom which I do alot, only way it goes from 1 to "2" is when I do something to my phone and I need to odin back to stock and re root(which I did for research) ... it's then it gets trigger again.

[Q] How does Rooting affect Galaxy S3's Knox Counter?

I've read a little bit about Knox in the last few months, but wanted to make sure I've got everything right, especially since things have probably changed since the early days of Knox.
Here's my situation: I'm running a TMO Galaxy S3 w/ stock recovery. I was using mrRobinson's T999UVDMD5 and foolishly did the TMO update to T999UVUEMJC.
(I thought I'd be able to retain root, but ended up losing root, getting Knox, and a bootloader that won't let me roll back. )
Now my phone locks up during boot. If I'm lucky, it'll boot but locks up nearly immediately after boot.
And this is with stock everything. I've had the phone a year and a half, so it's out of warranty.
So what's Sammy's stance on their update breaking phones out of warranty?
Do they cover that? Can I get a TMO store to put DMD5 back on?
I'm thinking of using the root66 EMJC img. I'm pretty confident that it won't brick the phone, since it'll be the same bootloader I'm currently running.
And I'm not too worried if it trips the Flash Counter (flag, really) since I should be able to clear it.
But what about the Knox counter? Will that get tripped? mrRobinson's post leads me to think that it will.
Any other root options I should consider? (Above all else, I'd like to be able to restore back to stock if I need to.)
I kinda like the stock ROM (save for some bloatware) and TouchWiz doesn't bother me.

If it's out of warranty, it shouldn't matter if you trip the Knox counter, Should it? Some say as long as you don't install a custom recovery that if you do the root 66 method just for root that Knox doesn't trip. But I can never get anyone to confirm that.
Sent from my SGH-T999L using xda app-developers app

masondoctorjt said:
If it's out of warranty, it shouldn't matter if you trip the Knox counter, Should it? Some say as long as you don't install a custom recovery that if you do the root 66 method just for root that Knox doesn't trip. But I can never get anyone to confirm that.
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
Thanks masondoctorjt! That's one of my questions. (albeit, a lesser one)
If TMO/Sammy's update f'd up my phone will they cover it if it's out of warranty? especially when it was fine before?
(It's also a work phone, so I'd like to be able to return it like I got it, if need be.)
It's that confirmation I'm looking for here.
This Knox thread seems to state that as long as a Knox-enabled bootloader is used, the counter won't trip. But it also says flashing Knox-enabled fw via Odin trips the Knox counter too. (which I don't fully believe) Hence my confusion. A lot of contradictory info.
Add to that the loose usage of 'flash counter' to refer to both the triangle/flash counter/flag and the Knox counter/flag and you can see why my head is spinning!
It was tricky for me to see the Knox Counter info for my phone. Recovery and Bootloader mode didn't pop up the screen.
But when I used adb to enter bootloader, I saw the counter info.

So did you root it, and if so, did the trip the knox counter?
Sent from my GT-N8013 using xda app-developers app

No, not yet. I was hoping to hear back from someone who's tried this.
I didn't want to be the first guinea pig.
I'll probably take my phone down to the T-Mobile store this weekend and give them an earful to see if they can roll me back w/o tripping Knox flag and report back.

PhilipJFry said:
No, not yet. I was hoping to hear back from someone who's tried this.
I didn't want to be the first guinea pig.
I'll probably take my phone down to the T-Mobile store this weekend and give them an earful to see if they can roll me back w/o tripping Knox flag and report back.
Click to expand...
Click to collapse
I would be like to hear how you did after going to T-mobile. Thanks.

patcal said:
I would be like to hear how you did after going to T-mobile. Thanks.
Click to expand...
Click to collapse
I honestly don't expect a whole lot from them really. But it's an avenue I have to try.
I'm ultimately going to root this anyway. If TMO can successfully roll me back to T999UVDMD5 completely, I'll just root that and stick till the dust has settled somewhat on Knox.

For Rooting after getting that 4.3 update, the process is pretty simple really. Since you have 4.3, you flash Root66 Via Odin. Or you could flash a custom Recovery via Odin and then flash SuperSU zip via Recovery.
It is my understanding that either one will not trip the Knox Counter. If you wish you can follow this guide.
NOTE - Do not Try to flash Older Root66 versions. You can only flash UVUEMJC version. If you flash any other version even accidentally then you will get expensive paperweight.

patcal said:
I would be like to hear how you did after going to T-mobile. Thanks.
Click to expand...
Click to collapse
It was ultimately unproductive.
I went in and explained the situation (w/ less detail) and asked them to roll me back to UVDMD5.
They said Samsung doesn't let them roll back, so he then proceeded to recover my phone.
He booted into recovery and wiped cache. When that proved unsuccessful, he wiped data. (nothing I couldn't have done)
Wiping data ultimately made the phone usable again. He then proceeded to enter some short codes to bind me to the network quicker.
(all he mentioned was #NUM#)
So I'm back to stock (more or less ). Not sure when I'll root now.
Perseus71 said:
For Rooting after getting that 4.3 update, the process is pretty simple really. Since you have 4.3, you flash Root66 Via Odin. Or you could flash a custom Recovery via Odin and then flash SuperSU zip via Recovery.
It is my understanding that either one will not trip the Knox Counter. If you wish you can follow this guide.
NOTE - Do not Try to flash Older Root66 versions. You can only flash UVUEMJC version. If you flash any other version even accidentally then you will get expensive paperweight.
Click to expand...
Click to collapse
From what I've read, the custom recovery should trip Knox. Have you tried this yourself?
I'm fairly confident if I merely flash root66 that it won't trip Knox. But I'd like better than a 51% confidence interval, that's all.
(Again, it's a work phone and I'd like to return it as I got it.)

It will trip that previous counter bit. Don't think it will trip the Knox counter.
No I do not have the Knox Counter.

PhilipJFry said:
It was ultimately unproductive.
I went in and explained the situation (w/ less detail) and asked them to roll me back to UVDMD5.
They said Samsung doesn't let them roll back, so he then proceeded to recover my phone.
He booted into recovery and wiped cache. When that proved unsuccessful, he wiped data. (nothing I couldn't have done)
Wiping data ultimately made the phone usable again. He then proceeded to enter some short codes to bind me to the network quicker.
(all he mentioned was #NUM#)
So I'm back to stock (more or less ). Not sure when I'll root now.
From what I've read, the custom recovery should trip Knox. Have you tried this yourself?
I'm fairly confident if I merely flash root66 that it won't trip Knox. But I'd like better than a 51% confidence interval, that's all.
(Again, it's a work phone and I'd like to return it as I got it.)
Click to expand...
Click to collapse
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.
Pat

patcal said:
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.
Pat
Click to expand...
Click to collapse
Was that the Flash Counter or Knox Counter?

Perseus71 said:
Was that the Flash Counter or Knox Counter?
Click to expand...
Click to collapse
Well I reset the flash counter with Triangle away. The Knox counter was not tripped until I flashed the recovery.
Pat

patcal said:
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.
Pat
Click to expand...
Click to collapse
Pat,
So just to get this straight, you flashed the stock TMO update, so you were not rooted?
Or did you do a root-injected variant of the stock?
Either way, I'm surprised you tripped the (triangle) flash counter.
But I'm more worried about the Knox counter; not worried about the other since there is Triangle Away.

patcal said:
Well I reset the flash counter with Triangle away. The Knox counter was not tripped until I flashed the recovery.
Pat
Click to expand...
Click to collapse
Thanks for letting me know.

PhilipJFry said:
Pat,
So just to get this straight, you flashed the stock TMO update, so you were not rooted?
Or did you do a root-injected variant of the stock?
Either way, I'm surprised you tripped the (triangle) flash counter.
But I'm more worried about the Knox counter; not worried about the other since there is Triangle Away.
Click to expand...
Click to collapse
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.
Edit: Don't remember how I got root. Sorry.
Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.

patcal said:
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.
Edit: Don't remember how I got root. Sorry.
Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.
Click to expand...
Click to collapse
The Flash Counter (Triangle away kind) will trip due to the running tracer (read Sysscope) in that Rom. I'd not worry about it as Triangle away will take care of it. Yes it trips due to custom Recovery and Root.

Perseus71 said:
The Flash Counter (Triangle away kind) will trip due to the running tracer (read Sysscope) in that Rom. I'd not worry about it as Triangle away will take care of it. Yes it trips due to custom Recovery and Root.
Click to expand...
Click to collapse
Thanks for that Perseus71. Didn't know about Sysscope before, but sounds interesting. I figured root66 removed it, since mrRobinson claims that it doesn't trip the normal flash counter. And this matches my experience w/ his previous root66.
patcal said:
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.
Edit: Don't remember how I got root. Sorry.
Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.
Click to expand...
Click to collapse
So it sounds like you were able to flash a rooted ROM and not affect Knox, as long as you leave the stock recovery.
That was my plan anyway. I'll probably look into this later this week.

PhilipJFry said:
Thanks for that Perseus71. Didn't know about Sysscope before, but sounds interesting. I figured root66 removed it, since mrRobinson claims that it doesn't trip the normal flash counter. And this matches my experience w/ his previous root66.
So it sounds like you were able to flash a rooted ROM and not affect Knox, as long as you leave the stock recovery.
That was my plan anyway. I'll probably look into this later this week.
Click to expand...
Click to collapse
Yep. Let us know how it goes.

FYI, the Knox counter gets tripped.
I flashed the root66 T999UVUEMJC via Odin. That's it.
Oh, and the flash counter does not get set.

[Q] Successfully Rooted with Towelroot on Note 3(SM-N900T), have some questions...

Successfully rooted without tripping Knox with Towelroot. NE6 firmware. I have T-Mobile Jump and would like to Jump to the Note 4 when it comes out. If I install TWRP and make a backup of stock, will I trip knox and void my JUMP eligibility? Wanted to install via Flashify and install Xposed framework at some point down the line.
Thanks!

Steameffekt said:
Successfully rooted without tripping Knox with Towelroot. NE6 firmware. I have T-Mobile Jump and would like to Jump to the Note 4 when it comes out. If I install TWRP and make a backup of stock, will I trip knox and void my JUMP eligibility? Wanted to install via Flashify and install Xposed framework at some point down the line.
Thanks!
Click to expand...
Click to collapse
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk

effortless said:
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
If I flashed back to stock, did a factory reset, would it still say custom?

Steameffekt said:
If I flashed back to stock, did a factory reset, would it still say custom?
Click to expand...
Click to collapse
As long as you didn't flash a custom kernel or recovery, it should be OK once you flash stock.
Even if you trip Knox, flash back to stock and jump when the time comes. They generally don't care about that as long as your phone is not damaged.
Knox warranty void is not the phone warranty. It's telling you Knox can't secure your phone anymore. Its (Knox's) warranty is void. People all over the Internet don't even know what Knox is and they spread misinformation.
Look up what Knox really is. It is an app that runs on your phone and creates a secure Android environment within itself. It's like another phone with its own launcher and app store that is secure. It's meant for employees to use their personal phone for work purposes as well.
When you trip the Knox warranty, Knox triggers an efuse that will prevent the secure container from being able to be created... Meaning Knox will never work again on your phone. It's a security measure so that companies will take the Samsung phones seriously in the work space. In reality it has worked for them as the department of defense recently approved a few Samsung models with Knox.
If you don't plan on using Knox for anything, then trip Knox and enjoy custom kernels/recoveries etc. If you do plan on using it, it's not a good idea to even root your phone as the whole purpose of Knox is to be secure and rooting will make Knox vulnerable.. You might even get fired if your IT department finds out.
Sent from my SM-N900T using Tapatalk

effortless said:
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
effortless said:
As long as you didn't flash a custom kernel or recovery, it should be OK once you flash stock.
Even if you trip Knox, flash back to stock and jump when the time comes. They generally don't care about that as long as your phone is not damaged.
Knox warranty void is not the phone warranty. It's telling you Knox can't secure your phone anymore. Its (Knox's) warranty is void. People all over the Internet don't even know what Knox is and they spread misinformation.
Look up what Knox really is. It is an app that runs on your phone and creates a secure Android environment within itself. It's like another phone with its own launcher and app store that is secure. It's meant for employees to use their personal phone for work purposes as well.
When you trip the Knox warranty, Knox triggers an efuse that will prevent the secure container from being able to be created... Meaning Knox will never work again on your phone. It's a security measure so that companies will take the Samsung phones seriously in the work space. In reality it has worked for them as the department of defense recently approved a few Samsung models with Knox.
If you don't plan on using Knox for anything, then trip Knox and enjoy custom kernels/recoveries etc. If you do plan on using it, it's not a good idea to even root your phone as the whole purpose of Knox is to be secure and rooting will make Knox vulnerable.. You might even get fired if your IT department finds out.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Makes sense and I probably will flash a custom recovery. I just don't understand the fuss with people wanting not to trip knox if they're not even gonna use it.

I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible".
Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?

un-answered question............
I don't know why I have not asked this before, but here it goes..........
First, I just want to say that I could care less about Knox...
(my phone already has the knox pox)
But for future reference if I had a brand new Note 3 with official stock NB4 baseband
and I rooted it successfully using Towelroot (or root de la vaga) would it be possible
to simply rename a custom rom like Hyperdrive to "update.zip" and copy it to the
internal sdcard then boot into the stock NB4 recovery and flash/install "update.zip"?
If the only problem with this method would be the fact that a different kernel would
also flashed along with the rom it would be an easy fix by just removing the kernel
from the custom rom file before flashing the update.zip?
I know that more likely than not this method would not work.
But if it did work it should not trip the knox right?

Eudeferrer said:
I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible".
Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?
Click to expand...
Click to collapse
Sent from my SM-N900T using xda premium

re: modile odin - knox
Eudeferrer said:
I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible". Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?
Click to expand...
Click to collapse
I just checked and it's OK to "install" Mobile Odin on your phone and it
it will NOT trip the KNOX counter by simply installing it as long as you:
1: Don't flash any custom recoveries like twrp/cwm.
2: Don't flash any stock or custom kernels.
3: Don't flash any modems/baseband or bootloaders.
4: Don't flash any custom odin flashable firmwares.
In mobile odin there is no option to flash cwm/twrp
flashable zip files of any kind including custom roms.
Good luck!

Misterjunky said:
I just checked and it's OK to "install" Mobile Odin on your phone and it
it will NOT trip the KNOX counter by simply installing it as long as you:
1: Don't flash any custom recoveries like twrp/cwm.
2: Don't flash any stock or custom kernels.
3: Don't flash any modems/baseband or bootloaders.
4: Don't flash any custom odin flashable firmwares.
In mobile odin there is no option to flash cwm/twrp
flashable zip files of any kind including custom roms.
Good luck!
Click to expand...
Click to collapse
Why would flashing a stock kernel/baseband or firmware cause Knox to change to 0x1 when done through Mobile Odin? I thought this would happen only through custom based ones?

re: knox - mobile odin
Eudeferrer said:
Why would flashing a stock kernel/baseband or firmware cause Knox to change to 0x1 when done through Mobile Odin? I thought this would happen only through custom based ones?
Click to expand...
Click to collapse
First of all I never said not to odin flash stock official firmware in my post.
If you or anyone else knows for sure that the modem/baseband or kernel you are
wanting to flash are 100% official stock 4.4.2 Kitkat NB4/NE6/NF1 versions then
its just fine to flash those.
However since knox cannot be rolled back and to keep things on the SAFE side I
always suggest the very safest way to do these things which even a NOOB would
understand without getting into trouble with a lot of unexpected issues. :laugh:
Good luck!

Misterjunky said:
First of all I never said not to odin flash stock official firmware in my post.
If you or anyone else knows for sure that the modem/baseband or kernel you are
wanting to flash are 100% official stock 4.4.2 Kitkat NB4/NE6/NF1 versions then
its just fine to flash those.
However since knox cannot be rolled back and to keep things on the SAFE side I
always suggest the very safest way to do these things which even a NOOB would
understand without getting into trouble with a lot of unexpected issues. :laugh:
Good luck!
Click to expand...
Click to collapse
My bad. I guess I misunderstood you the first time. Thank you for your response.

[INFO][FAQ] All things KitKat - How to update, ROOT, return to stock, & more!

This thread contains information about the KitKat 4.4.2 update to the T999 variants of the Samsung Galaxy S3. Here you will be able to find information on updating, rooting, installing custom recoveries and roms, as well as how to return to stock should you feel the need to. If you feel you need additional help or would like further clarification on a subject just leave a reply in this thread and myself or someone familiar with the matter will do our best to answer and provide promptly help. This is a work in progress since KitKat is new to our devices. As we learn more, additional info and links will be posted. Huge thanks to DocHoliday77 for giving me ideas and helping me make things clearer!
Below I tried to put together a list of questions regarding KitKat in hopes to alleviate confusion and educate others.
F.A.Q.
[Q] Can I just flash the KitKat modem on my older firmware to see if my signal will improve?
WARNING! WARNING!
A) I feel like this is probably the most important thing to know about the KitKat update as of now. DO NOT I repeat DO NOT flash any 4.4.2 modems if you have not taken the official 4.4.2 update for your device via OTA or Odin. If you do, you will brick your device and you will not be able to unbrick it. The current debrick method does not work! Also please do not try to downgrade your bootloader, any such attempt can also brick your device.
YOU HAVE BEEN WARNED!!
Click to expand...
Click to collapse
[Q] My signal has been terrible with KitKat, how can I downgrade my modem to see if I will get a better signal?
A) You cannot use older modems with 4.4.2. You will have no service.
Click to expand...
Click to collapse
[Q] Will KitKat give me Knox?
A) Unsurprisingly, Knox is present in 4.4.2 as it was in 4.3. For more info on Knox, scroll down to the second post.
Click to expand...
Click to collapse
[Q] Is it possible to root my device without tripping the Knox/warranty bit counter, and how can I make sure it stays untripped?
A) Yes, it is possible to root and keep your counter untripped. Scroll down to "How to root" and you will find your answer. To keep the counter at 0, avoid flashing custom recoveries and kernels.
Click to expand...
Click to collapse
[Q] I have tripped my Knox/warranty bit counter, how can I reset it?
A) There is currently no way to reset this counter.
Click to expand...
Click to collapse
[Q] Can I still flash a custom recovery with KitKat firmware?
A) Yes. Please scroll to the end of this post for more info and recommendations.
Click to expand...
Click to collapse
[Q] I am in developer options and I cannot find the option to change my runtime to ART, how can I change it? I'm confused.
A) ART runtime cannot be chosen as default because the option is disabled by Samsung in all of their KitKat firmwares. The default will be Dalvik.
Click to expand...
Click to collapse
If your device has not yet received the KitKat update, please be patient and wait for your carrier to update. If you feel you cannot wait for an official update, there is the option to update unofficially by flashing a custom Rom, just remember that they will be taken from other device's firmware so it may not work the same with your device or it have missing features native to yours. For more information and what you need to update unofficially, check method 3 below on "How to update or return to stock."
General F.A.Q.s
[Q] What Rom's can I safely flash?
A) Any Rom and kernel in this section of the fourms should be okay. Roms labeled for d2lte will work for any d2 device, and T999 Roms will work on T999V & T999N for example.
BUT....some ROM's will not flash without a little intervention, so to speak. If you get a Status 7 error and the ROM will not flash, this is what you do:
Unzip the Rom.
In the Meta-Inf folder, delete the signatures (CERT.RSA, CERT.SF, MANIFEST.MF)
Browse to META-INF\com\google\android\ and open the updater-script in Notepad++
At the top of the script, there will be one or several lines beginning with "Assert". Delete these Lines. Save the updater-script.
Re-Zip the Rom and try again to flash.
Click to expand...
Click to collapse
[Q] Why is my WiFi and/or Bluetooth not working after flashing a T999 based Rom?
A) Most likely this is due to a kernel/module mismatch. Try flashing a custom kernel or a stock modified kernel to fix this.
Click to expand...
Click to collapse
[Q] Why does my phone say it is a T999 or other model?
Because you flashed a rom that was based on or intended for the original T999 model. This is perfectly normal.
If you really want to change it, go to /system/build.prop and edit all lines that say SGH-T999, to your model or whatever you like.
(WARNING!!!) If you change this to a different model than the T999 or T999L, some apps may think they are on that different model device. This can cause a brick if you try to flash firmware with Mobile Odin. Other apps may not function as intended. Use Caution!
Click to expand...
Click to collapse
How to update or return to stock:
Method 1:
The simplest method. If you are on official and unrooted stock firmware, you can simply check for update to your device by going into settings, more, about device, software update. This option is if you do not want root access or plan to root at another time.
Click to expand...
Click to collapse
Method 2:
You can use this method to update your device or return it to its factory state, should you need to. Simply download the stock firmware linked below and flash it with Odin. Just remember, you cannot downgrade your device once you have updated to 4.3 or higher firmware. You can, however, flash an equal or higher version. For example, you updated your device to 4.3 MJC firmware, you can only flash 4.3 MJC, 4.3 NC2, or 4.4.2. If on NC2 firmware you cannot downgrade to MJC even though it is 4.3 because it is a lower firmware. If you flashed 4.4.2, you can only flash 4.4.2. Follow the link below and scroll past the words "root66" where you will see "Official Firmware." Detailed instructions on how to use and flash firmware with Odin will also be found there. Thanks to my good friend @DocHoliday77 for the thread and mrRobinson for the firmwares!
Stock Firmware:
Download
Click to expand...
Click to collapse
Method 3:
You can flash a custom Rom with your custom recovery, but you will need at least a 4.3 bootloader and modem. Bootloader update is required otherwise your device will not boot, modem is needed for data. If you decide to go this route and are on 4.3 bootloader and modem do not upgrade them under any circumstance unless you want a brick and headaches! I will link stock Roms here overtime, meanwhile search for one you like in the development section Click to go to Development Section
Stock NB8 4.4.2 port from Sprint. Daily driver stable! Thanks Doc!
Download Sprint port here
Click to expand...
Click to collapse
How to root:
Method 1:
If you are looking to update your device and be rooted out of the box, check out the pre-rooted root66 firmware thread by @DocHoliday77. Just find the 4.4.2 firmware for your device, download it, and flash with Odin. Detailed instructions on how to use and flash with Odin can also be found in the link below. Make sure you click the box below the words "root66." Knox counter should remain untripped, but it is unconfirmed as of now. If you want to be safer about your counter staying untripped, continue to method 2.
Download root66
Click to expand...
Click to collapse
Method 2:
Use TowelRoot by the legendary geohot. This method is very simple and useful if you have already updated to 4.4.2 and want root access nice and easy. Confirmed to keep your Knox counter untripped!
Download TowelRoot
Click to expand...
Click to collapse
How to install a custom recovery:
Remember, any and ALL methods to flash custom recovery will trip Knox/warranty counter. After installing a custom recovery you will be able to flash custom ROMs, scripts, and mods!
Method 1:
Download your recovery tar file and flash it with Odin in download mode.
Instructions:
Flash File In ODIN
- Power down your device
- Simultaneously press and hold VOL DOWN + HOME BUTTON + POWER BUTTON
- At *Warning* screen, press VOL UP
- Connect your device to its USB cable and plug cable into PC
- Start ODIN on PC
- Verify that "Auto Reboot" and "F. Reset Time" are UNCHECKED
- Click PDA button ("AP" in newer versions)
- Browse PC and select your tar file
- WAIT for "START" button to be enabled (may take a minute)
- Click START button to begin recovery install
- Disconnect USB only when download is finished and you see the message "PASS!" in a green box.
- Remove battery and reboot straight to recovery, very important!
- Now you can either flash whatever you want, or reboot back into system.
Instructions were taking from a thread by az_biker and edited for our device
Click to expand...
Click to collapse
Method 2:
Use an app from the playstore to flash custom recovery like goomanager, ROM Manager, or my favorite, flashify! These method is useful if you have root access on your device, would prefer avoid using Odin, or do not have access to a computer to use Odin.
Click to expand...
Click to collapse

Information about Knox
Knox allows people to use their device on a secure business (work) network. It allows the data which belongs to the business to be encrypted per DoD standards. Once the Knox/warranty bit is tripped, you can no longer use this service because it proves the device has been tampered with. You can imagine how much simpler it would be to manipulate this service without the restrictions Samsung had to enforce in order to protect sensitive data. This is the main reason I believe the Knox bootloader was added and why root access, once gained, is still limited in some cases. There is also claims that a tripped warranty bit means your warranty will be void, but I have not seen any cases where people have been denied warranty. However it is better to play it safe than sorry if you really do care about warranty.
Wikipedia sums it up pretty nicely.
Read more about Samsung Knox on Wikipedia
How to remove Knox
If you do not use or plan to use Knox, the limitations imposed by Samsung can affect your overall experience with root access, or make the service become bloatware. For this reason you may want to remove it. Follow the link below to make your device Knox free. Flash in custom recovery and do not forget to nandroid before you flash! Thanks to bilgerryan over in the Sprint forums!
Get Knox removal zip here

Ill take one!
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
And another!
---------- Post added at 02:08 AM ---------- Previous post was at 02:08 AM ----------
Good write up btw! Thanks!

Just a heads up for T999 users who are going to flash root66 in Odin: flashing root66 in Odin DID trip the warranty bit for my device. I was running NC2 on my T999 (T-Mobile), flashed root66 NC2 and the bit was tripped. If you're worried about maintaining warranty eligibility you should take note.

friedchocolatesoda said:
Just a heads up for T999 users who are going to flash root66 in Odin: flashing root66 in Odin DID trip the warranty bit for my device. I was running NC2 on my T999 (T-Mobile), flashed root66 NC2 and the bit was tripped. If you're worried about maintaining warranty eligibility you should take note.
Click to expand...
Click to collapse
Thanks, but this thread is for touchwiz kitkat. Its not intended for 4.3 or any other build unless specifically related.
But still, im not sure why it tripped the bit on yours. It did just fine on mine and others...

I know this is a kitkat thread but it also tripped the warranty bit on my t999l
Sent from my SGH-T999 using XDA Premium 4 mobile app

friedchocolatesoda said:
Just a heads up for T999 users who are going to flash root66 in Odin: flashing root66 in Odin DID trip the warranty bit for my device. I was running NC2 on my T999 (T-Mobile), flashed root66 NC2 and the bit was tripped. If you're worried about maintaining warranty eligibility you should take note.
Click to expand...
Click to collapse
chalky7880 said:
I know this is a kitkat thread but it also tripped the warranty bit on my t999l
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this is odd as it should not trip the counter even though it was in jellybean.. to my knowledge the counter is tripped when you flash a custom recovery, but I will edit the OP until further confirmation.. thanks for the heads up guys
Edit: flashing kernel will also trip counter
Sent from my SGH-M919 using Tapatalk

Your probably right. I did flash a custom recovery so I bet that's what tripped it
Sent from my SGH-T999 using XDA Premium 4 mobile app

chalky7880 said:
Your probably right. I did flash a custom recovery so I bet that's what tripped it
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's all good, all feedback is appreciated. Believe it or not, it actually gave me the idea to mention in the OP how to keep the warranty bit from being tripped for those who want to avoid tripping it. Thank you!
Sent from my SGH-M919 using Tapatalk

Just fyi for everyone, there have been claims for both in the root66 thread. Some say it tripped the bit, while for others like myself it did not. No idea why, but I do not believe it has anything to do with the root66 firmware. There have been people who tripped the warranty bit just by taking the ota!

DocHoliday77 said:
Just fyi for everyone, there have been claims for both in the root66 thread. Some say it tripped the bit, while for others like myself it did not. No idea why, but I do not believe it has anything to do with the root66 firmware. There have been people who tripped the warranty bit just by taking the ota!
Click to expand...
Click to collapse
That would be a big screw up for Samsung. Really hope this is not the case
Sent from my SGH-M919 using Tapatalk

Its not a common occurrence, but it has happened.

Knox on hold?

I just got the note. Love the hardware but the software is pissing me off. I was waiting to root until I get the lollipop but I can't handle the lack of control and all the advertisements. I gave my S4 to my son and it is still running better than this new machine that should be a Monster.
So... Can I root without a custom recovery? If so what can I do about the knox before it unroots. If it's disabled or gone will I still get my 5.0?
More preferably can I get the stock recovery so I can get a copy of the 4.4.4 before it upgrades?

You can root stock without custom recovery but you'd need custom recovery for a nandroid backup or custom ROM or kernel.
Chain Fire auto root will disable Knox enough for root and Knox would not disable root. It's an Odin tar flash so no custom recovery required for root.
As far as upgrading, you'd have to fully un-root for OTA upgrade but there's always Kies or Odin for updates which would mean rooting again. As far as having a stock backup, the stock NK2 tar is available for download both in the Sprint Note 4 XDA forum and sammobile.com or even Kies. Voiding the warranty with Knox trip and risking root are the only true risks to consider. I'd suggest having the tools you need in a folder before you begin. CF auto root includes Odin; have a backup of NK2 stock tar and TWRP in case you need them. It wouldn't hurt to also have a custom ROM on hand to flash if you run into root issues.

samep said:
You can root stock without custom recovery but you'd need custom recovery for a nandroid backup or custom ROM or kernel.
Chain Fire auto root will disable Knox enough for root and Knox would not disable root. It's an Odin tar flash so no custom recovery required for root.
As far as upgrading, you'd have to fully un-root for OTA upgrade but there's always Kies or Odin for updates which would mean rooting again. As far as having a stock backup, the stock NK2 tar is available for download both in the Sprint Note 4 XDA forum and sammobile.com or even Kies. Voiding the warranty with Knox trip and risking root are the only true risks to consider. I'd suggest having the tools you need in a folder before you begin. CF auto root includes Odin; have a backup of NK2 stock tar and TWRP in case you need them. It wouldn't hurt to also have a custom ROM on hand to flash if you run into root issues.
Click to expand...
Click to collapse
Sprint's OTA is disabled with root or with out Knox. I rooted my daughter's S3 a week ago. Just used Odin to TWRP and flashed superuser. Chains asked if he could fight back and I said no. within 12 hrs Sprint sent an update and on reboot it was full un root. I was hoping if I was able to just put Superuser in that things would be manageable until I get 5.0.
If you have the stuff to unroot that would be awesome. It's impossible to say when I'll get the update. I can't get KIES to work on stock devices much less anything with root. Sprint doesn't use a serial number that samsung recognizes for a push. Does a Knox trip really void the Warranty if the phone is broken?

Root/Knox trip voids warranty as far as Samsung is concerned. Sprint and other extended warranties may not check but it's a warning that gets reiterated often for non liability reasons.
Odin the stock tar is only true un-root method that should work to restore OTA updates but also Odin the lollipop stock tar, when available, would be an option many rooted users would choose.

When I say root with stock ROM I don't mean install a ROM. I just want to have root control over apps. If I can just get super user unstalled things would be great. I"m lost where it comes to the knox though. and there seems to be a whole lot of it on this ROM. Can knox be disabled with out a trip. I know it can on the S4 and earlier. I just sent TWRp in with ODIN 3 or 4 times in a row then booted straight to recovery flashed superuser then as soon as it booted back in into Andoid I gave superuser permission to jump on knox.
I downloaded an app that says it can make ADB work with out root. But I can't get it to work on my pc

Knox trips now; no way known to undo that.
The stock kernel blocks ADB access. I haven't tried it but I thought I had read that ADB will work if phone is in recovery. Don't hold me to it.
Edit: reading your earlier post about Knox undoing root for OTA if flashing superuser and keeping Knox enabled, many rooted users found that they could un-root and download the NK2 update but it wouldn't flash due to "modified" system. I think Knox is evolving more complex in Note 4. Your method may be simpler but may not work as intended to OTA to lollipop. Odin is the method you'd have to be comfortable with before rooting.

samep said:
Root/Knox trip voids warranty as far as Samsung is concerned. Sprint and other extended warranties may not check but it's a warning that gets reiterated often for non liability reasons.
Odin the stock tar is only true un-root method that should work to restore OTA updates but also Odin the lollipop stock tar, when available, would be an option many rooted users would choose.
Click to expand...
Click to collapse
How do you get he tar for Odin? Your totally right. about Odin and the tar. I really don't have to wait to get the OTA when I can just find it myself.
How did you root, a recovery and Odin? I'm trying to get the ADB to work first. I guess ADB unlock OEM will wipe everything you have but opens the firmware also. I'm not going to try that way right now I just want to shoot superuser in that way.
Sorry didn't word that very well. How do you use Odin to root without installing a custom recovery?

http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
Find the 910P link and download it; open the archive and placed the contents into a folder placed and named something like Odin or Note 4 root.

There are many users around xda that have sent their phones to samsung for a warranty repair with Knox tripped and had no problem. If you really look around you'll see this Knox bit thing is really no big deal. Just don't truly brick your phone and you'll be fine

Voiding Samsung warranty isn't an issue for most people anyways. I don't warranty through Samsung. I purchased my phone from Sprint and Sprint handles the warranty.

samep said:
http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
Find the 910P link and download it; open the archive and placed the contents into a folder placed and named something like Odin or Note 4 root.
Click to expand...
Click to collapse
Thanks for the instructions here. It worked like a charm. I had no idea I could root with out a custom recover.

planb234 said:
Thanks for the instructions here. It worked like a charm. I had no idea I could root with out a custom recover.
Click to expand...
Click to collapse
You're welcome. If you want to backup stock recovery and use custom recovery and go back to stock recovery without flashing the the stock tar in Odin, try Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
You'd need custom recovery for backup nandroid or flashing custom ROMs, kernels, and mods (remember stock Rom is Odexed and some mods are intended for the ROM it was based on and may also be deodexed).
Flashify can also backup the stock kernel but I'd recommend the stock kernel flash because custom kernel will swap some modules that Flashify won't restore. You could skip the custom kernel unless you enjoy fiddling with custom apps and settings. The custom kernel will also have to be worked around for some video streaming and games. The stock kernel is quite capable and in my experience holds it own in benchmarks and battery savings.

planb234 said:
Voiding Samsung warranty isn't an issue for most people anyways. I don't warranty through Samsung. I purchased my phone from Sprint and Sprint handles the warranty.
Click to expand...
Click to collapse
You pay the extra $$ for sprints protection plan?

jhill110 said:
You pay the extra $$ for sprints protection plan?
Click to expand...
Click to collapse
Yes I pay 11 a month for insurance. Everything is covered for 6 months or something like that. The insurance is for breakage.
samep said:
You're welcome. If you want to backup stock recovery and use custom recovery and go back to stock recovery without flashing the the stock tar in Odin, try Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
You'd need custom recovery for backup nandroid or flashing custom ROMs, kernels, and mods (remember stock Rom is Odexed and some mods are intended for the ROM it was based on and may also be deodexed).
Flashify can also backup the stock kernel but I'd recommend the stock kernel flash because custom kernel will swap some modules that Flashify won't restore. You could skip the custom kernel unless you enjoy fiddling with custom apps and settings. The custom kernel will also have to be worked around for some video streaming and games. The stock kernel is quite capable and in my experience holds it own in benchmarks and battery savings.
Click to expand...
Click to collapse

I'm going to give this method a shot. I'm sick of waiting on v Sprint to delivery anything but hidden costs. I thought it would be cool to have the original lollipop delivered to my phone but honestly I wouldn't use it long anyways. There is bound room for outside influence in a 700 dollar device. I'm going with the deodexed 5.0 on xda. I'll let you know how the flashify toy recommended goes. Your your saying it can be used to back entire stock device without custom recovery so i can lock it down before i start sending repeated knox trjps to Samsung? In putting all good Samsung apps into backup and then locking Samsung from my device indefinite

planb234 said:
I'm going to give this method a shot. I'm sick of waiting on v Sprint to delivery anything but hidden costs. I thought it would be cool to have the original lollipop delivered to my phone but honestly I wouldn't use it long anyways. There is bound room for outside influence in a 700 dollar device. I'm going with the deodexed 5.0 on xda. I'll let you know how the flashify toy recommended goes. Your your saying it can be used to back entire stock device without custom recovery so i can lock it down before i start sending repeated knox trjps to Samsung? In putting all good Samsung apps into backup and then locking Samsung from my device indefinite
Click to expand...
Click to collapse
I believe I was saying you could backup stock recovery, Odin flash a custom recovery, perform a nandroid backup, flash a custom ROM.
Not sure who it was that asked but attempting to restore a nandroid and restore stock recovery in order to gain OTA update of lollipop may not be a sure thing. I'm not sure if it would work coming from CM12 because the partitions may be different; unsure myself. It's also no guarantee that the update feature wouldn't still flag the system as modified and refuse to install the update. Don't hold me to that; I'd recommend Odin stock tar to come back to KitKat but still unsure if OTA would be possible, if that is your goal. And most, if not all developers, recommend a full wipe/clean install before flashing custom ROMs and updates. Odin to stock tar is also a common suggested troubleshooting step as well. There is Kies and Odin for Samsung lollipop that would still give you the update for rooted devices.
I'd also recommend having CF Auto Root that includes Odin downloaded and standing by along with tar for TWRP, and NK2 stock tar. If things go wrong, you'll recover quicker with less stress. And wait until you have some to time to recover before attempting. Gotta be comfortable with Odin and have the Samsung PC drivers pre-installed and willing to risk the consequences. Others and myself can offer helpful advice, if needed.
The rooted warranty concerns have been explained away by a few. But if you feel more comfortable taking a phone in for repair with stock recovery and a restored stock nandroid go for it. You at least have to accept the notion that your custom ROM may be flashed over if taken in as well.
As far as skipping the CF auto root, I think you can if flashing a rooted ROM in custom recovery but I don't know for sure you can. I'm guessing you can because there's a flashable SuperSU that you can flash to root stock after Odin of custom recovery. A rooted ROM shouldn't be different.
Sorry if I've made assumptions. Just wanted to be clear and not misleading. Flashify can simplify things, especially stock recovery backup and restore. But don't use Flashify to backup and restore kernels unless you're also manually restoring the lib modules along with it; Flashify won't do that for you.

The flashify worked i doubt i will ever put my device back to stock. Waitng for the ota i noticed that Samsung was running updates to my device at least 10 times a day. Security updates meaning they are securing their own interests. yes it says warranty voided but I'm not sure what that means. Samsung won't sell me a phone they would rather let sprint sprint fiscally rape me in the deal. I've not seen on any Samsung site where i can purchase or warranty a device. there access is denied. The only company i allow is Google. True they market some of my information but the majority of their interest is bug reports which is used for improvement. Improvement warrants bandwith. I had the lollipop on my s4 months ago and Samsung is not even releasing it in the us. In short Samsung is left wanting in support. I rooted my device this morn and will install deodexed lollipop when i get off work. Your advice has been helpful and i lookforward to more on upgrading my kernel.

Here's my experience this past week. I flashed the stock tar and hit update now. I got the up to date message. Rooted, tried again... No dice system has been blah blah blah. I unrooted system update : system up to date. Rerooted flashed twrp of course no go. Unrooted flashed stock recovery and.... No go. Re-flashed stock rom... System up to date. Flashed twrp no go. Flashed stock recovery and still no go.
So, it seems once you flash custom recovery there's no going back without flashing the stock rom. Whew, that was a mouth full.
It's mho this Knox thing is blown way out of perportion. Hardware warranty repairs will be done even if Knox is tripped. Plenty of members have done so. If one were to brick their phone flashing that might be a different story.

I don't want the stock ROM anyways. Samsungs overkill with the Knox is equivalent to Microsoft Security update. Samsung makes some sweet hardware but fails the open source. Their trying to be Steve Jobs or Bill Gates. If wanted a to not upgrade I would stick with a Nexus. Google is the only company who agrees that your device is yours and you should always try and improve it. I was seriously getting angry being put last in the world for the newest software. Samsung saying they are updating my device which basically meant Knox was spying and correcting any changes I made. Bricking is most likely to occur if you upgrade with stock recovery.

I will say this for sprint warranty. They don't care. As long as they are able to slip in a several hidden costs with any change or purchase they are satisfied. Sprint repair are all 3rd party representatives. If you happen to find an actual sprint location you will be sent to a third party sprint store. The 3rd party will fix you up as of they don't they don't get paid.