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
Related
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)
Just hooked up my 8.4 with Kies 3 and got this:
-----update-----
reroot: OK
Make sure you don't disable KNOX (hit cancel when you're prompted)
Wi-Fi seems to be faster
Touch looks OK.
Great I have been waiting for the US version,
On your upgrade did root carry over from your previous install or did you re-root with TR or use the kernel swap method?
mingkee said:
Just hooked up my 8.4 with Kies 3 and got this:
-----update-----
reroot: OK
Make sure you don't disable KNOX (hit cancel when you're prompted)
Wi-Fi seems to be faster
Touch looks OK.
Click to expand...
Click to collapse
I also got the update on my tab pro 12.2 ota
otyg said:
Great I have been waiting for the US version,
On your upgrade did root carry over from your previous install or did you re-root with TR or use the kernel swap method?
Click to expand...
Click to collapse
I rerooted with CF.
What the changes for NK1? Is it still 4.4.2?
HKSpeed said:
What the changes for NK1? Is it still 4.4.2?
Click to expand...
Click to collapse
Yes, it's still 4.4.2.
It's a bit snappier and the Wi-Fi performance is better.
mingkee said:
Just hooked up my 8.4 with Kies 3 and got this:
-----update-----
reroot: OK
"
Wi-Fi seems to be faster
Touch looks OK.
Click to expand...
Click to collapse
Can you explain for a new user please.
Is this the recent update I hear people are getting yesterday and today?
:Make sure you don't disable KNOX (hit cancel when you're prompted)"
Is this something for those rooted or does it apply to stock application. Have no clue what KNOX or Kies 3 is
It is for those who are rooting. This is the notice from the SuperSu app which is used in the routing process
mingkee said:
I rerooted with CF.
Click to expand...
Click to collapse
doesn't CF trip knox, has anyone tried TR on this firmware yet?
otyg said:
doesn't CF trip knox, has anyone tried TR on this firmware yet?
Click to expand...
Click to collapse
It will trip KNOX, so you go other route if it's your concern.
GTT1 said:
Can you explain for a new user please.
Is this the recent update I hear people are getting yesterday and today?
:Make sure you don't disable KNOX (hit cancel when you're prompted)"
Is this something for those rooted or does it apply to stock application. Have no clue what KNOX or Kies 3 is
Click to expand...
Click to collapse
If you disable KNOX during root process, it will crash some services which causes system crash when waking up (see Q&A section).
TR won't work anymore but you can swap kernels with AN3 (or 1) root with TR then swap back to NK1 and not trip knox.
Anyways someone (on another thread) said the ANG1 firmware have + - adjustment for auto brightness however I'm not seeing that option in this firmware did they remove it in this revision (I never tested ANG1) so just wondering.
mingkee said:
If you disable KNOX during root process, it will crash some services which causes system crash when waking up (see Q&A section).
Click to expand...
Click to collapse
I did this, then froze all the knox stuff in titanium backup. Not a single crash or reboot with knox disabled.
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T
---------- Post added at 07:22 PM ---------- Previous post was at 06:47 PM ----------
Just added a thread with the this FW and it's parts in odin flash-able form.. Here: http://forum.xda-developers.com/gal...320xar1ank1-extracted-stock-firmware-t2954549
I just got the OTA and installed it, I wasn't rooted though so just your basic OTA install.
Too soon to notice any changes but wondering why it isnt 4.4.4? My wife has an S4 and it was just updated to 4.4.4 and I think the S4 is older than the tab pro.
mingkee said:
I rerooted with CF.
Click to expand...
Click to collapse
Can you please tell me how you were able to root with CF? I tried using the method from android central. Everything worked like the guide stated but the tablet still don't have root access.
The day that I installed the OTA my battery life was pretty bad, on a very basic level it drained a little more than twice as fast when using the table the same way in the past.
It could just be because the new software was flashed and it needs to settle a bit and maybe a reboot or two, well that is what I am hoping at least.
Raistlin1 said:
The day that I installed the OTA my battery life was pretty bad, on a very basic level it drained a little more than twice as fast when using the table the same way in the past.
It could just be because the new software was flashed and it needs to settle a bit and maybe a reboot or two, well that is what I am hoping at least.
Click to expand...
Click to collapse
I updated yesterday and it seems the battery consumption is the same. Maybe a reboot or one cicle charging will do it.
The only difference I noted is that it seems a little bit snapier, but again, it could be the placebo effect...
I noticed you said you went from NG1 to NK1 and that it was snappier
Did you try NI1? That was already snappier than NG1, so I wonder if there's any diff for those of us on NI1
locutusx said:
I noticed you said you went from NG1 to NK1 and that it was snappier
Did you try NI1? That was already snappier than NG1, so I wonder if there's any diff for those of us on NI1
Click to expand...
Click to collapse
I didn't try the NI1. I haven't rooted my tablet yet, a bit of lazyness and lack of time.. hahahahah
But it seems the difference between the NI1 and the NK1 is the CSC (UK vs USA). I don't think they differ much if differ at all. Maybe someone with more knowledge can tell better.
how can you root nk1?
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)
When I had my S3 and other Samsung devices, I could jump back and forth between updates.
Which was cool and all.
But when I flashed an S4 Mini, KNOX got tripped on it.
I flashed a NEWER firmware to it, and it was from sammobile.
Others also complained about having this issue.
But what about the Note 4?
I have a 910C, and I love the phone. On wifi, battery life is beastly.
But it seems Samsung did not patch the mobile data issue (like LG did), and if I get on mobile internet, my battery is ded.
So... would a downgrade trip KNOX?
h8Aramex said:
When I had my S3 and other Samsung devices, I could jump back and forth between updates.
Which was cool and all.
But when I flashed an S4 Mini, KNOX got tripped on it.
I flashed a NEWER firmware to it, and it was from sammobile.
Others also complained about having this issue.
But what about the Note 4?
I have a 910C, and I love the phone. On wifi, battery life is beastly.
But it seems Samsung did not patch the mobile data issue (like LG did), and if I get on mobile internet, my battery is ded.
So... would a downgrade trip KNOX?
Click to expand...
Click to collapse
KNOX shouldn't get tripped if you flash an official Samsung firmware.
Ashatar said:
KNOX shouldn't get tripped if you flash an official Samsung firmware.
Click to expand...
Click to collapse
That's what I thought too, but after that trip... well, I have my fears.
It is a company phone, which came with 2 years of warranty.
Well, I will cross my fingers and hope for the best.
There is no way I can use the phone like this abroad, on the road, on the field. (With such terrible battery on LP.)
h8Aramex said:
That's what I thought too, but after that trip... well, I have my fears.
It is a company phone, which came with 2 years of warranty.
Well, I will cross my fingers and hope for the best.
There is no way I can use the phone like this abroad, on the road, on the field. (With such terrible battery on LP.)
Click to expand...
Click to collapse
Good luck!
Ashatar said:
Good luck!
Click to expand...
Click to collapse
It works. You can downgrade, upgrade.
BUT, you cannot downgrade permanently.
Because the phone WILL check for updates (no matter what you try, or do) and WILL download the new firmware.
Is there a way to root without tripping KNOX? (the 4.4.4 firmware of course, so I can keep the update away.)
Okay I had an idea.
I will download the older version (one older than 4.4.4 latest), and then do this sim card / wifi trick.
It will notice the update and download it once Wifi is on, but should ignore L after the reboot.
What do you guys think?
(Shame it takes forever to download anything from sammobile.)
Okay, its' really weird.
The old version works. (latest 4.4.4 - 1 version)
You can install it, disable update checks, and you are good.
BUT! Once you update to the latest 4.4.4 from OTA - 4.4.4 will instantly download 5.0 after the boot.
Even if you disabled auto-update from way back.
It's basically in the system to force check an update as soon as there is ANY data connection,
and download it once there is a wifi connection available. (unless you untick wifi only.)
Once it downloads, there is no going back.
App Alet popup
---------------------------------------------------
"Your device has been compromised
Because of a new security policy
intruduced in version 5.0 knox is not
available on compromised devices."
---------------------------------------------------
I have same problem, cannot use my Gear S3 now, funny is that S health works at non Samsung rooted devices :/
Some say to uninstall s health and install a previous version.. to open it and set it up and then to update the app
Check your knox. Its probably 0x1.
Knox is tripped ofc after root, i tried to unistall app but i cannot get it unistall, tried app from play store and link2sd to unistall it but it still there so if i try to flash older version i get error saying that file is corrupted.
Flashing official ROM using Odin does not trigger Knox (at least it shouldn't). I have the same problem after flashing official 7.0 ROM and my Knox Counter is NOT triggered (it is 0x0000).
I cannot uninstall or downgrade S Health since it's a "default app".
Any workarounds?
Nalix said:
Flashing official ROM using Odin does not trigger Knox (at least it shouldn't). I have the same problem after flashing official 7.0 ROM and my Knox Counter is NOT triggered (it is 0x0000).
I cannot uninstall or downgrade S Health since it's a "default app".
Any workarounds?
Click to expand...
Click to collapse
If knox is triggered then:
- make a root
- remove S health with Titanium Backup
- install older version S health before version 5
- launch app, sync account and then update to new version of S health
Working, tested one hour ago, i had this problem after flashing and rooting 7.0 stock rom.
Mystero said:
If knox is triggered then:
- make a root
- remove S health with Titanium Backup
- install older version S health before version 5
- launch app, sync account and then update to new version of S health
Working, tested one hour ago, i had this problem after flashing and rooting 7.0 stock rom.
Click to expand...
Click to collapse
Thanks for the tip but I'm not ready to trigger Knox just yet Again - My knox is NOT triggered.
Mystero said:
If knox is triggered then:
- make a root
- remove S health with Titanium Backup
- install older version S health before version 5
- launch app, sync account and then update to new version of S health
Working, tested one hour ago, i had this problem after flashing and rooting 7.0 stock rom.
Click to expand...
Click to collapse
Hi
I've just come across this problem upgrading to Nougat today. I'd like to try your suggestion but how do I find an older version of S Health like you suggest?
TIA
Just found 4.8.1. I'll give it a go.
norm2002 said:
Hi
I've just come across this problem upgrading to Nougat today. I'd like to try your suggestion but how do I find an older version of S Health like you suggest?
TIA
Just found 4.8.1. I'll give it a go.
Click to expand...
Click to collapse
Same problem and my Knox is 0×0. Anyone found what is wrong yet?
norm2002 said:
Hi
I've just come across this problem upgrading to Nougat today. I'd like to try your suggestion but how do I find an older version of S Health like you suggest?
TIA
Just found 4.8.1. I'll give it a go.
Click to expand...
Click to collapse
I had to try three versions. Two kept saying they were corrupt when trying to install. I managed to install the third but, when I try to sync, I keep being told the server is temporarily offline. I suppose that may be true but I doubt it.
And now whenever I try to open the app, it freezes and the only way to open it is to clear the data in the app settings.
So I think it's back to Marshmallow for me for now. I need S Health for my Gear S3.
norm2002 said:
I had to try three versions. Two kept saying they were corrupt when trying to install. I managed to install the third but, when I try to sync, I keep being told the server is temporarily offline. I suppose that may be true but I doubt it.
And now whenever I try to open the app, it freezes and the only way to open it is to clear the data in the app settings.
So I think it's back to Marshmallow for me for now. I need S Health for my Gear S3.
Click to expand...
Click to collapse
I tried going back to Marshmallow but after I boot the Galaxy S7 it asks for a code. I have no idea what to do next because no code seems to work.
norm2002 said:
I had to try three versions. Two kept saying they were corrupt when trying to install. I managed to install the third but, when I try to sync, I keep being told the server is temporarily offline. I suppose that may be true but I doubt it.
And now whenever I try to open the app, it freezes and the only way to open it is to clear the data in the app settings.
So I think it's back to Marshmallow for me for now. I need S Health for my Gear S3.
Click to expand...
Click to collapse
Where did you find those versions?
Cya
alehawk said:
Where did you find those versions?
Cya
Click to expand...
Click to collapse
Here under Show more.
norm2002 said:
Here under Show more.
Click to expand...
Click to collapse
thank you very much!
This guide will work for everyone. Including those getting force closes and corrupt file messages.
CuBz90 said:
This guide will work for everyone. Including those getting force closes and corrupt file messages.
Click to expand...
Click to collapse
This is for those who have triggered Knox. Our's not triggered...
theoaman said:
This is for those who have triggered Knox. Our's not triggered...
Click to expand...
Click to collapse
Have you checked if it's tripped or are you just guessing? Are you on your phones official firmware or did you flash different firmware in Odin?
I think it's not compatible with N.
I flashed MM after trying RR, and then it worked just fine. Strange though, Samsung should be able to get their apps working.
Bjaped said:
I think it's not compatible with N.
I flashed MM after trying RR, and then it worked just fine. Strange though, Samsung should be able to get their apps working.
Click to expand...
Click to collapse
Can you explain what you mean? You had the same problem and now it is solved?