Database Users

GT-N8013 and German 4.1.1 update

Hello all,
I have the GT-N8013 (US Version), and decided I wanted to get Jelly Bean on it, since Samsung hasn't really said anything about an update for the USA.
I just flashed the German 4.1.1 ODIN last night as per this thread. I was under the impression this would not affect the binary counter or the firmware status. However, my binary count is now 2 (I've never flashed anything else), and the firmware status is Custom, rather than Samsung Official/Normal.
As such, I can no longer receive OTA updates for this device. I wanted to keep myself in a position where I could still get OTA updates one way or another.
I've seen things about changing the CSC, but I'm not sure I want to wipe the device, especially if I wouldn't be guaranteed to get OTA updates afterwards. (Or would it be guaranteed that OTAs would work if I changed the CSC to DBT...?)
What is the best course of action to get back to Samsung Official/Normal status (USA or German), or can it even be done?
(If I can't get back to Samsung Official, is there somewhere to download GT-N8010 German update.zip files, rather than the 1GB ODIN files?)
Thanks in advance for any help!

You'll need to root and then use TriangleAway to reset your counter. Then you can unroot and reflash official 4.1.1 from sammobile.com or just keep your root. Either way, you have to root to reset your counter. I recommend ExynosAbuse. As for OTA updates, you'll have to unroot and flash back to stock for that. To accomplish this, I recommend bypassing ODIN and using MobileODIN to flash, just in case the 8010 firmware is what tripped your counter to begin with... you know, cause you put it on an 8013.
Sent from my GT-N7100 using XDA Premium HD app

kornfan71 said:
Hello all,
I just flashed the German 4.1.1 ODIN last night. I was under the impression this would not affect the binary counter or the firmware status. However, my binary count is now 2
Click to expand...
Click to collapse
Strange - Mine didn't do that for 4.11 or 4.1.2. It only changed when I rooted it. How are you checking that the Binary count is 2?
kornfan71 said:
The firmware status is Custom, rather than Samsung Official/Normal.
As such, I can no longer receive OTA updates for this device. I wanted to keep myself in a position where I could still get OTA updates one way or another.
Click to expand...
Click to collapse
This will be because there is a mismatch between the devices CSC and the Firmware that is installed. You WILL lose all data if you wipe the device (Yes I've done it - No ROMS for UAE either)
kornfan71 said:
What is the best course of action to get back to Samsung Official/Normal status (USA or German), or can it even be done?
Thanks in advance for any help!
Click to expand...
Click to collapse
Personally I'd wait a few days. JB is rolling out now, and I don't really believe that the US (8013) version will be that long behind the others. So if you can wait, then just download the 8013 JB ROM when it arrives, flash it with Odin and you will be back to official. I would tend to ignore the Binary count for now (see question above) and then fix it when you get the 8013 JB and your ready to go "Official"

Thanks for the replies!
Bulbous said:
How are you checking that the Binary count is 2?
Click to expand...
Click to collapse
I'm just looking at the information at the top left of the screen when the device is in download mode.
Thanks for pointing me to ExynosAbuse. That will definitely make life easier when I go to reset the binary counter!
I'll probably just wait to flash an 8013 JB ROM once one is available. The 8010 firmware doesn't have 5GHz WiFi support, which I use frequently.
Thanks for the advice!

kornfan71 said:
Thanks for the replies!
I'm just looking at the information at the top left of the screen when the device is in download mode.
Thanks for pointing me to ExynosAbuse. That will definitely make life easier when I go to reset the binary counter!
I'll probably just wait to flash an 8013 JB ROM once one is available. The 8010 firmware doesn't have 5GHz WiFi support, which I use frequently.
Thanks for the advice!
Click to expand...
Click to collapse
That's funny. My 8013 on 8010 firmware works perfectly on 5 GHz wireless n.
Sent from my GT-N7100 using XDA Premium HD app

Same thing happened to me. My counter is up to 2 now, one for the German ICS and one for the German JB.
My hypothesis is that you can swap ROMS within the same model - so any 8010 ROM works fine on any 8010 without upping the count, but that going between models (8010 -> 8013) trips the counter.
However, as far as I can tell, everything works fine except the ability to update OTA and it might even be better since you're getting the version that's not been modified for the US market to get past the legal issues with Apple.
The only iffy part is that you're going to be stuck relying on XDA for updates.. but to be honest, the gang here has been pretty reliable in that area for years.

kornfan71 said:
Thanks for the replies!
I'm just looking at the information at the top left of the screen when the device is in download mode.
Thanks for pointing me to ExynosAbuse. That will definitely make life easier when I go to reset the binary counter!
I'll probably just wait to flash an 8013 JB ROM once one is available. The 8010 firmware doesn't have 5GHz WiFi support, which I use frequently.
Thanks for the advice!
Click to expand...
Click to collapse
I also installed the 8010 JB and now wi-fi direct between my GS3 and the Note doesn't work anymore.

I'm not rooted, will having the flash counter at 2, if I have an official rom flashed (and it says official in download mode), prevent me from getting an OTA?

tisoyboy2 said:
I also installed the 8010 JB and now wi-fi direct between my GS3 and the Note doesn't work anymore.
Click to expand...
Click to collapse
WiFi issue are VERY common when flashing roms from different regions. Every country has different frequencies & bands that can be used publicly & in the UK & Germany, they differ from here in the US. If you change your CSC files in system to identify as an en_US device, or more precisely, change the line in the wifi config file from ccode=gb to ccode=ALL , you will then get 5Ghz. I have no issues with AllShare or WiFi direct, but I changed the wifi config files & edited the csc files to show XAR region with all wifi channels open (ccode=ALL).
BTW, there was an 4.1.1 region XAR leak recently, a few days ago I think. I am also pretty sure someone, maybe Darkman, released a deodexed version of it. There are also dumps of it in the Dev section of the Note 10.1 forums.

[Q] Any downside to rooting other than warranty/knox?

I am considering rooting my Canadian (Rogers) Note 3 (SM-N900W8) in order to defeat the ludicrous SD-Card crippling brought by the latest Kitkat 4.4.2 software update. I'm aware that by doing so the Knox 0x1 counter will void the warranty. What I'd like to know is whether there are any additional negative results besides this well-known one.
For example I've seen inconsistent reports of the Screen Mirroring function being disabled as soon as the device is rooted. Some claim it is more related to the presence of a custom kernel, recovery or ROM, while others insist that merely rooting with everything stock was enough to disable screen mirroring.
If I do nothing more than use CF-Autoroot as described here:
http://forum.xda-developers.com/showthread.php?t=2466423
...no custom recovery, kernel or ROM, do I risk any undesirable repercussions other than the warranty and Knox issue? Will screen mirroring or any other functions work worse than they did before?
Thanks for any help...

Rooting won't break any functionality of the phone except the security it was meant for i.e the secure container ( and of course, depending on who you ask, warranty ). Problems you mentioned are probably related to custom roms themselves.
Sent from my SM-N900W8 using xda app-developers app

hey_joe said:
Rooting won't break any functionality of the phone except the security it was meant for i.e the secure container ( and of course, depending on who you ask, warranty ). Problems you mentioned are probably related to custom roms themselves.
Click to expand...
Click to collapse
Thanks for your reply... and will it also not interfere with any potential future over-the-air updates that might come along, be it a 4.4.3 update or a more trivial software patch to fix an issue that gets released? I realize that a major enough OTA update might un-root the phone which is fine.. I just wouldn't want to brick or lose access to updates because of root. Would they continue to be accessible, or would I likely have to first un-root manually to enable them?
Thanks again...

Yes you can not OTA update on the rooted phone.
You can unroot and apply the OTA update.
Or use the fake system status option in the Wanam.

vndnguyen said:
Yes you can not OTA update on the rooted phone.
You can unroot and apply the OTA update.
Or use the fake system status option in the Wanam.
Click to expand...
Click to collapse
Thanks... if memory serves (been a while for me since last rooted device) all that is necessary to unroot is to run the administrative option from within the Superuser app itself, to remove the SU binary completely.. correct? And then to re-root just repeat the previous CF-Autoroot steps and regain SU?

paleozord said:
Thanks for your reply... and will it also not interfere with any potential future over-the-air updates that might come along, be it a 4.4.3 update or a more trivial software patch to fix an issue that gets released? I realize that a major enough OTA update might un-root the phone which is fine.. I just wouldn't want to brick or lose access to updates because of root. Would they continue to be accessible, or would I likely have to first un-root manually to enable them?
Thanks again...
Click to expand...
Click to collapse
You don`t need OTA`s mate, just download the new updated rom from Sammobile and flash it with Mobile Odin Pro and you`ll even keep root

gee2012 said:
You don`t need OTA`s mate, just download the new updated rom from Sammobile and flash it with Mobile Odin Pro and you`ll even keep root
Click to expand...
Click to collapse
So all ROM and software updates are always made available directly from Samsung as flashable downloads, on the same day they're released to devices over-the-air? As a general rule?

paleozord said:
So all ROM and software updates are always made available directly from Samsung as flashable downloads, on the same day they're released to devices over-the-air? As a general rule?
Click to expand...
Click to collapse
Within a day usualy you can download the full rom from here www.sammobile.com/firmwares/2/ and flash it with Odin or better yet Mobile Odin.

paleozord said:
So all ROM and software updates are always made available directly from Samsung as flashable downloads, on the same day they're released to devices over-the-air? As a general rule?
Click to expand...
Click to collapse
Or you can open the app Phone INFO ★Samsung★, select menu 'Firmware Browser...' to see a list of available stock firmwares for your phone.
Tap to view firmware's details, there is also a download link. You can download it and then flash by Kies or Odin.
(screenshots are attached)

Nk4 update

Update coming thru..
G900PVPU1ANK4
OTA file size: 366.65MB
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-g900p
http://support.sprint.com/support/a...ndUpdateTheSoftwareVersionOnYourSamsungGalaxy

Finally about time!
Sent from my SM-G900P using XDA Free mobile app

The update has been released downloading now

I'm downloading right now too
Sent from my SM-G900P using XDA Free mobile app

Insert obvious follow-up question about towel root
Sent from my SM-G900P using Tapatalk

There is already an RDF discussion thread here with announcements and links.
Please refer to this thread to prevent multiple cross posting.
RDF Discussion Thread for Sprint Galaxy S5 (SM-G900P)

This is about the update itself and specific discussions about the update. This is not about the RDF itself.
Why would you want to fill that thread with stuff not immediately about the RDF discussion?
tdunham said:
There is already an RDF discussion thread here with announcements and links.
Please refer to this thread to prevent multiple cross posting.
RDF Discussion Thread for Sprint Galaxy S5 (SM-G900P)
Click to expand...
Click to collapse

tdunham said:
There is already an RDF discussion thread here with announcements and links.
Please refer to this thread to prevent multiple cross posting.
RDF Discussion Thread for Sprint Galaxy S5 (SM-G900P)
Click to expand...
Click to collapse
Nope
Sent from my SM-G900P using XDA Free mobile app

Can anyone confirm whether or not NK4 can be rooted freely at the moment? And if so, your method of choice? I've been hearing rumors about root-killing updates(especially in regards to Lollipop) and am hesitant to do any updating. I don't want to lose superuser access just so I can get an HD Voice icon.

Jay5583 said:
Update coming thru..
G900PVPU1ANK4
OTA file size: 366.65MB
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-g900p
http://support.sprint.com/support/a...ndUpdateTheSoftwareVersionOnYourSamsungGalaxy
Click to expand...
Click to collapse
Can someone grab and post the ota from your cache/fota folder.

Yes new update can be rooted

The official 4.4.4 and unofficial 5.0 can both be rooted with CF auto root
Sent from my SM-G900P using Tapatalk

banccalif said:
The official 4.4.4 and unofficial 5.0 can both be rooted with CF auto root
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I wouldn't use that unless you care to trip KNOX and give up warranty. If all you want is root to remove bloat and tweak you can without tripping.
I can say I am now on the official 4.4.4 update, rooted without knox flagged (IE still full warranty).
Runs great.
The only change I don't like is before I had WiFi calling always set to on and it would be on when I turned my WiFi on and not when Wifi was off.
Now if I have it on and my WiFi off, it turns my Wifi on randomly or on reboots, even if it was prior off.
Oh well.
Anyway. For those that want to root and keep Knox 0x0 (not tripped) it's simple.
I used Kies to update to the latest release (OTA kept giving an error that many others on sprint forum are getting).
After this I installed towelroot (don't run yet). Next I used Odin to flash the NE5 stock kernel. Ran towelroot, ran Odin to flash NK4 kernel back, after installed SU and now all is well. Full root, good performance and not knox tripped. One thing to note is that while on the NE5 kernel you will get tons of errors, just ignore them, the original kernel will fix when all done.
I don't care for custom recovery and the stock kernel honestly runs great and I can manually do any tweaks I want but have the piece of mind of not having tripped knox.
Just wanted to share though that this work around works on sprint. I know other forums mention how to do on other providers etc.
**update**
I posed the files I used in another thread (as seems we have duplicate topics). So if anyone needs the kernels I got em already converted to tar and ready to go.
http://forum.xda-developers.com/showpost.php?p=57139088&postcount=76

Nice work. I'm sure some would find this helpful! I tripped knox within the fist 20mins of owning my device ?

banccalif said:
Nice work. I'm sure some would find this helpful! I tripped knox within the fist 20mins of owning my device ?
Click to expand...
Click to collapse
Yea, I've been fighting hard to avoid tripping it for the moment. I mean I guess when all said and done I don't care TOO much, but for now if I can root without tripping I will do it. (resale value also higher if not tripped so might get new phone in March).
I imagine this work-around won't work when 5.0 comes out as the kernel is changing too much so unless someone finds a new exploit to root without knox trip I will probably end up tripping it upon official 5.0 lol but until that time I have some piece of mind if anything stops working.
I'm actually fine with stock I just hate all the damn bloat they put on it so have to root to ditch it all. I don't know why they don't just make it so we can uninstall whatever we want...

Is there any reason to update to this? I might just skip and wait for Lollipop.

slickdealers said:
Is there any reason to update to this? I might just skip and wait for Lollipop.
Click to expand...
Click to collapse
Performance, bug fixes etc. etc.
Remember this is already a skipped update. Sprint skipped 4.4.3.
It also includes new modem firmware among other things.
The wait game could be a bit. I don't expect Sprint to get 5.0 until around the time the S6 is releasing. Samsung is almost done with it but it takes months before Sprint will pump it out. Do you think they would have bothered with 4.4.4 if this was going to be out in a month?
I see no reason why one would wait? Nothing is lost, root is still possible. It may also be a prep for 5.0. Maybe they are using it as a firmware stepping stone. Who knows. I wouldn't bother waiting.

bryanu said:
Performance, bug fixes etc. etc.
Remember this is already a skipped update. Sprint skipped 4.4.3.
It also includes new modem firmware among other things.
The wait game could be a bit. I don't expect Sprint to get 5.0 until around the time the S6 is releasing. Samsung is almost done with it but it takes months before Sprint will pump it out. Do you think they would have bothered with 4.4.4 if this was going to be out in a month?
I see no reason why one would wait? Nothing is lost, root is still possible. It may also be a prep for 5.0. Maybe they are using it as a firmware stepping stone. Who knows. I wouldn't bother waiting.
Click to expand...
Click to collapse
So you think we won't get Lollipop until April when we already have a leaked (pretty damn stable) build?? I'm sorry but that is straight up idiotic. We will have Lollipop by the end of Dec-Jan.

As of now there is no towelroot for 5.0 so you might have to. Xposed also doesn't work and might be a while before its able to run on the new platform.
I'm running the 5.0 leak now, we will definitely have Lollipop by Jan at the latest, I think more like late Dec
Sent from my SM-G900P using Tapatalk

JoeFCaputo113 said:
So you think we won't get Lollipop until April when we already have a leaked (pretty damn stable) build?? I'm sorry but that is straight up idiotic. We will have Lollipop by the end of Dec-Jan.
Click to expand...
Click to collapse
Might not be April but it won't be by February or probably March even.
The key word you said is "Leaked"...
Sprint had 4.4.4 builds in testing for months also, they just don't always leak out.
Just because you have a non-production version doesn't make it magically release sooner.
If you look around you will notice Sprint is generally a tad slower on some releases at times. This is because they like to wait and see what other providers do and also avoid having to do more releases.
Take Verizon S5 for example. It got 4.4.4 a lot sooner vs. we did, but the downfall was it had issues and security holes that they had to go back and patch again with more OTA's.
Sprint waited longer, didn't have to turn around and do all of this.
Waiting longer can often mean a more stable product as it allows other things to mature.
Sprint also generally doesn't like to update an phone right away if a newer model is about to come out with the new stuff also as it could cut into sales.
S5 will get 5.0 but based on how Sprint operates and historical events I don't see them doing it before a new flagship model comes out in which some people may feel they can now hold off longer. The leak FWIW is kind of like a marketing toy. It shows that they are committed to upgrading the OS so people don't do the whole "I'll never use sprint/samsung on sprint again cause they stopped updates". They are doing the updates, just doing it slower.
At the end of the day we are all speculating. You don't know for 100% just as I don't. I'm just saying (in my head at least) my thought makes more "sense".
FWIW I hope I am wrong because like you I own this phone too and want to have the new fancy stuff

SM-T320 March 2015 Firmware Upgrade

I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.

horseycraze said:
I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.
Click to expand...
Click to collapse
IPTV or torrent tv, normally plays through mx player ?. Was a bug, half of the screen black
http://forum.xda-developers.com/app...f-screen-black-watching-t3017829#post58842303

That firmware is just for the UK, which I believe went to NI1 last fall about a month before the U.S. went to NK1.
I don't know that I'd read a lot into it. If anything, they could be getting UK firmware better aligned with other locations for a smoother universal upgrade to 5.
Edit: Okay, looks like it's indeed out now for the U.S., too. Still hoping it's progress towards a Lollipop upgrade.

So does anyone actually know what changes this update brought? I was having some issues with my tab pro 8.4 missing touches, i 1st noticed it during gaming but was able to replicate it with display tester multitouch test.
It seems to be fine now, i thought for sure it was a hardware defect but now I'm not so sure. Anyone else in a similar position as me?

Hey there
I m downloading it, but not sure i will apply it .. does it makes root going byebye ? Wanna stay with my device rooted !
thanks

I just downloaded and installed in California. Still 4.4.2 no issues so far.
Sent from my SM-T320

+1. Got excited over nothing.
johna2u said:
I just downloaded and installed in California. Still 4.4.2 no issues so far.
Sent from my SM-T320
Click to expand...
Click to collapse

Rooted device? Able to root after update?
Thx

Just finished updating and was very disappointed that it's still 4.4.2, I didnt check this forum beforehand so was hoping for a nice surprise.
I hope we see official 5.0 for our devices...

Still. Nothing here! Will we ever get lollipop?

biroot said:
Rooted device? Able to root after update?
Thx
Click to expand...
Click to collapse
Without thinking I took the update and lost root. So, I'm searching to see if root is available for the update.

Rooted T320UEU1AOC1
66gt350 said:
Without thinking I took the update and lost root. So, I'm searching to see if root is available for the update.
Click to expand...
Click to collapse
I rooted with Chainfire"s CF-Auto-Root for Odin. download.chainfire.eu/383/CF-Root/CF-Auto-Root/CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.zip (For T320). Main web page here autoroot.chainfire.eu/. As you know To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding! So don't forget http//:

Rooted i747 said:
I rooted with Chainfire"s CF-Auto-Root for Odin. download.chainfire.eu/383/CF-Root/CF-Auto-Root/CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.zip (For T320). Main web page here autoroot.chainfire.eu/. As you know To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding! So don't forget http//:
Click to expand...
Click to collapse
Thanks for the quick reply. Reading on the main page, did using the Chainfire's CF-Auto-Root trip the Knox Counter and the custom firmware counter?
thanks

A little bit less lag going from TW to Magazine tiles. Tried removing them with no luck. Hopefully this update sets us up for lollipop.
Sent from my HTC One mini using XDA Free mobile app

66gt350 said:
Thanks for the quick reply. Reading on the main page, did using the Chainfire's CF-Auto-Root trip the Knox Counter and the custom firmware counter?
thanks
Click to expand...
Click to collapse
It trips knoxs
Ported Note 4 on 3

Anyone try use towelroot method to root T320 without trip knox?
>flashing old kernel
>run towelroot
>flash new kernel again

M4r10 22 said:
Anyone try use towelroot method to root T320 without trip knox?
>flashing old kernel
>run towelroot
>flash new kernel again
Click to expand...
Click to collapse
I'm in the process of trying to line up everything to do this. My update that pushed through took me to T320UEU1AOC1. I haven't located the extracted US kernel file for that and unfortunately don't know how to pull it from my current build. Sammobile has an AOC1 file noted as Cellular South and the build time is same date as mine but different timestamp. Anyone know if that would work to get me back to my current build and keep my US region?

horseycraze said:
I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.
Click to expand...
Click to collapse
How did you do this? I have mine rooted and have TWRP but can't figure out how to get that stupid Touchwiz back. Any help would be great
---------- Post added at 02:25 AM ---------- Previous post was at 01:27 AM ----------
horseycraze said:
I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.
Click to expand...
Click to collapse
Could you put the steps I need in order to what you did here?

I have the Romanian version of the updated ROM on a T325.
The biggest issue I have noticed is with the light sensor, with the previous ROM the auto setting worked smoothly, now with the new ROM the screen doesn't fade continuously. Whenever I turn on the screen the brightness just switches from a higher to a lower setting or inversely (without smooth fading and with lag), also the screen flickers horribly when it detects a change so I can't use the auto anymore.
The second issue is with the Samsung keyboard with learning disabled, in a Facebook floating chat window I tried to respond to someone and the keyboard would auto complete with empty words and after every word I had to delete the word before to be able to write the next word. I had to re-enable the learning to get rid of this very annoying problem.
I will try to downgrade to the previous ROM and root it with towelroot and say goodbye to any future official Samsung updates. Samsung has the ****tiest update developers, actually I had the same problem with the auto light setting (but not so serious) with the ROM which was before the good one.
By the way, if Lollipop comes DON'T UPGRADE. Lollipop on S5 sucks bigtime, the phone has major issues, android eats more battery than the screen.
Stick with the previous ROM, for me it was the most flawless one. I might try a cache wipe on the current ROM but I doubt it has anything to do with the screen flickering.

M4r10 22 said:
Anyone try use towelroot method to root T320 without trip knox?
>flashing old kernel
>run towelroot
>flash new kernel again
Click to expand...
Click to collapse
stormygal said:
I'm in the process of trying to line up everything to do this. My update that pushed through took me to T320UEU1AOC1. I haven't located the extracted US kernel file for that and unfortunately don't know how to pull it from my current build. Sammobile has an AOC1 file noted as Cellular South and the build time is same date as mine but different timestamp. Anyone know if that would work to get me back to my current build and keep my US region?
Click to expand...
Click to collapse
After losing root when I took the T320UEU1AOC1 update, I was able to flash the T320 kernel in this thread then use Towelroot again. I did have to reboot, even though it told me I wouldn't need to. I uninstalled and reinstalled SuperSU (hit cancel when I got the SuperSU notice about Knox) and verified root with Root Checker Basic. Then installed the AOC1 kernel. I still have root and Knox is not tripped. (KNOX KERNEL LOCK: 0x0; KNOX WARRANTY VOID: 0x0)

S health knox warning on Nougat final. Not rooted

I'm not rooted but I can't launch s health on the final version of Nougat that my phone updated to today. (Xxu1dplt)
It says about a Knox warning and device compromised?
It's running stock though! Anyone else with the same issue?

Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app

Once knox is tripped, game over even if you unroot.

jadaress1 said:
Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.

Try uninstall and re-install again s-health

Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?

CuBz90 said:
Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?
Click to expand...
Click to collapse
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.

f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
Ye if Knox has tripped, Samsung will have nothing to do with it, even if it's their fault, they just don't want to hear about it.

f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.

f1ux said:
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.
Click to expand...
Click to collapse
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.

joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
people lie. the dindu nuffins

joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
yes, i've been flashing my phone for around 10times with official binaries and never tripped knox. I flashed BTU(from INS) and updated to N, s health working fine here

Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.

1stlynx said:
Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.
Click to expand...
Click to collapse
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.

Punisher159 said:
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.
Click to expand...
Click to collapse
Hi,
i used this guide :
https://www.sammobile.com/forum/showthread.php?t=30800
dont know if i am allowed to post the link.
i did step 3.

Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit

kartonick said:
Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit
Click to expand...
Click to collapse
i have tried that but i wont count steps. so its of no use. when updated it... stopped working completely

poncespr said:
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.
Click to expand...
Click to collapse
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance

does samsung pay works with u? i bought a second hand uk handset without having any knowledge of knox which was tripped. though i got it to work following a post here, samsung pay doesnot work evenon stock firmware.

elkhalifi said:
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance
Click to expand...
Click to collapse
Thank you poncespr, your solution woked for me.
I am able to launch SHealth again