I've had a terribly laggy experience on my SM-P605 ever since turning it on for the first time. The original firmware was Vodafone infested so I spent the first week trying to find bloat free versions before trying custom editions (xKat).
Long story short my Knox is triggered but I am no closer to fixing any of the really annoying issues:
- WiFi constantly reconnects (35 other devices are fine)
- Google Chrome top bar 'jiggels' (distracting)
- Mobile data and WiFi stop working after 2+ days and only work again after rebooting
- Video playback in embedded web pages stutters
I'm fed up and would like to finally have a properly working device, my 3 year old S3 (i9300) running CyanogenMod exhibits none these issues...
My question: Is there a way I can reset Knox, apply a stock firmware and get Samsung to credit the unit?
Nope, once tripped it cannot be reset (un-tripped)
Sent from my SM-P600 using Tapatalk
As to the Knox warranty bit, it probably CAN be un-tripped, however, no-one knows how to do it (yet...?) ...
As you may know, a working, Knox-resetting Odin package for one of Note 3 variants leaked some time ago (heh don't get too enthusiastic, it does work only on the specific variant of Note 3 with specific bootloader version...). This seems not to be very helpful, however, it confirms that resetting Knox IS possible (at least on Exynos based devices). It also confirm that Samsung did not tell us all the truth, stating that the Knox is absolutely unrecoverable, because it is based on e-fuse (so it gets physically blown when Knox is triggered) - it seems that either e-fuse is a myth or there are some "substitution" e-fuses included in the hardware.
But as for now, it is true that you unfortunately cannot do anything with the triggered Knox (BUT there is a chance that Samsung service centre won't notice that... there were also ideas such as putting the device into microwave oven for 2-3 secs so the device will be damaged in a way making it impossible for samsung to check the knox status, but they shall be considered as illegal...)
And as to your issues with the device - have you tried adding:
ro.securestorage.support=false
to your build.prop (or changing the value from "true" to "false" if the property "ro.securestorage.support" is present there...).
Related
I have a Note II (N7100) from Germany (DBT), carrier-free, and was on the Samsung stock Jelly Bean LL7 (DBT) ROM. I only CF-Auto-Root'ed (and Triangle Away'ed) this ROM but that's enough to get a "Modified" system status and thus not being able to get system software update notifications (for example, manually triggering the check for new firmwares only gets you to the "wait, checking for new firmwares" window, which keeps checking forever until you cancel it).
...Or so I thought.
Yesterday I received the notification that the new MC3 firmware was available even though if I manually check for updates it never finishes the check and, above all, even though I DISABLED the automatic check for new updates since the system doesn't seem to be able to find new updates with a modified status!
Trying to accept the update only brought me to the same "wait, checking for new firmwares" window which still hung forever so I tried to connect to Kies (latest version, of course) and it too told me that the new MC3 firmware was available so I tried to update it through Kies and... it worked!
Previously I had temporarily checked "keep root" in SuperSU Pro and I had disabled USB Debug (which I need especially for GMD Gesture Control, which I also temporarily disabled).
The update was completely successful (if a bit long) and everything works perfectly fine.
Does somebody have an explanation for why I received the notification even though manual checks don't work and (especially) I even had the automatic checks disabled (thinking it doesn't work)?
At first I even thought it was a fake notification from some malware (although I have only a couple of games, which are the usual source of malware -which I have never got before BTW-, installed)! LOL
I had same problem until i updated with kies. yesterday my phone was so hot i almost got burned from touching it and almost discarged, even thougt i was in charger, i think i was because it was constant searching for update. my guess is the servers was overloaded so my phone could not get the update or samsung pulled the update before my phone could download it. my phone is Dansih version.
Question is: did it kept your phone rooted? ( after you updated through Kies )
Answer is No root after update.
Sendt fra min GT-N7105 med Tapatalk2
jca1981 said:
I had same problem until i updated with kies. yesterday my phone was so hot i almost got burned from touching it and almost discarged, even thougt i was in charger, i think i was because it was constant searching for update. my guess is the servers was overloaded so my phone could not get the update or samsung pulled the update before my phone could download it. my phone is Dansih version.
Click to expand...
Click to collapse
That should not be possible and sounds to me like you have a serious fault there, and quite likely a fire hazard.
jca1981 said:
I had same problem until i updated with kies. yesterday my phone was so hot i almost got burned from touching it and almost discarged, even thougt i was in charger, i think i was because it was constant searching for update. my guess is the servers was overloaded so my phone could not get the update or samsung pulled the update before my phone could download it. my phone is Dansih version.
Click to expand...
Click to collapse
Actually I didn't mean it as a "problem" at all :laugh:
The overheating problem doesn't sound like something "normal" anyway, try doing something CPU-intensive like a benchmark or a heavy game for say 15 minutes and check the temperatures against another Note II doing similar tasks if you can, getting "almost burned" is NOT normal, you might have an HW fault (assuming of course you haven't OC'ed your phone).
Stressing CPUs/GPUs gets the phone *warm*, even "very warm" (they all are subjective definitions after all), but never "almost burning" hot!
carlitos66 said:
Question is: did it kept your phone rooted? ( after you updated through Kies )
Click to expand...
Click to collapse
I have SuperSU Pro and I checked Survival Mode but the SuperSU app wasn't there after the update.
TBH maybe simply reinstalling it from the market might have been all that was necessary but I simply re-rooted via PC Odin because I don't care about the warranty since my personal data on my devices are worth much more than the devices themselves to me (i.e. sending my devices for repair with my data on them is unthinkable to me and if they are broken in some way but can boot and can let me securely erase everything first then I can always "unroot" and "triangle away" later).
I got impatient last night and finally bit the bullet and rooted. Froze a bunch of apps (including Knox ofcourse) and made some changes with MultiWindow and Wanam Xposed. I tried playing one of the movies I bought wiht the $50 Samsung cred and it says: "This item expired. Connect to PC and download license."
Anyone else see this and know how to fix?
Thanks!
alias747 said:
I got impatient last night and finally bit the bullet and rooted. Froze a bunch of apps (including Knox ofcourse) and made some changes with MultiWindow and Wanam Xposed. I tried playing one of the movies I bought wiht the $50 Samsung cred and it says: "This item expired. Connect to PC and download license."
Anyone else see this and know how to fix?
Thanks!
Click to expand...
Click to collapse
If you're device status show "custom" you probably won't be able to use Samsung's DRM protected apps. It breaks AllShare Cast also.
BarryH_GEG said:
If you're device status show "custom" you probably won't be able to use Samsung's DRM protected apps. It breaks AllShare Cast also.
Click to expand...
Click to collapse
Well I did have a "Custom" status, but I used Wanam to trick the system to saying "Official" again. When it said custom, checking for updates would fail. Now that it is tricked it says that the tablet is up to date. So I think that if Hub used that as a gauge it would work. I am worried that it is going deeper than that and checking the Warranty Bit in the bootloader. OR it could be checking to see if another program is available (like Knox) but since I froze it, it's failing.
Thoughts?
alias747 said:
Well I did have a "Custom" status, but I used Wanam to trick the system to saying "Official" again. When it said custom, checking for updates would fail. Now that it is tricked it says that the tablet is up to date. So I think that if Hub used that as a gauge it would work. I am worried that it is going deeper than that and checking the Warranty Bit in the bootloader. OR it could be checking to see if another program is available (like Knox) but since I froze it, it's failing.
Thoughts?
Click to expand...
Click to collapse
I connect to secure networks and have stayed away from rooting my N3 and N10.1-14 because with KNOX I can't take a chance that some flag somewhere in the s/w would be tripped preventing me from connecting and potentially having to replace my device. KNOX hasn't been around for that long and there are tons of threads across multiple forums swearing that "XYZ" method is KNOX safe. Pre-N3/N10.1-14 I'd root my device, clean it up, and then un-root it while still keeping "official" status. Now, who knows?
Hi,
Have just bought a T-Mobile Note 3 on prepaid and plan to use it to access my company emails (we've just made the switch from Blackberry's to something called mymobile, we bring our own phone and SIM, company gives access to Exchange), the restriction is, the device can't be rooted or modified in any way. I know that, even an unrooted Note 3, flashed to stock gets caught out - the set-up stops with a message saying The Device is Compromised - the dreaded KNOX counter is almost definitely what the secure email access (MobileIron is the name, not sure if its a mainstream app for purely a corporate tool) app looks up.
The question is, is it possible to flash the T-mbile note 3 with a standard international ROM - I don't really have any use for WI-FI calling and stuff and could do without the T_Mobile bloatware.
Regards.
Rizwan
Forgive me if this has already been answered somewhere, but as I've been away from Samsung devices since the SGS3 I'm not familiar with Knox at all and coudn't find any information about it. I know it's an e-fuse and when you trip it, you just won't get it back to untripped status. My question is, what features exactly are affected by this status? Fingerprint sensor/private mode? The ability to run enterprise-protected apps? Some other minor issue? Or is there no consequence at all, just the status change?
Steve_max said:
Forgive me if this has already been answered somewhere, but as I've been away from Samsung devices since the SGS3 I'm not familiar with Knox at all and coudn't find any information about it. I know it's an e-fuse and when you trip it, you just won't get it back to untripped status. My question is, what features exactly are affected by this status? Fingerprint sensor/private mode? The ability to run enterprise-protected apps? Some other minor issue? Or is there no consequence at all, just the status change?
Click to expand...
Click to collapse
Warranty status. Private mode is only affected by root which can be fixed. In certain countries, even if you trip Knox, you still have warranty no matter what (due to laws and such). Most likely, if it's an software issue and you tripped Knox, you aren't covered. But if it's and hardware issue out of the box, then you are covered. Some of claimed getting warranty either way.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Warranty status. Private mode is only affected by root which can be fixed. In certain countries, even if you trip Knox, you still have warranty no matter what (due to laws and such). Most likely, if it's an software issue and you tripped Knox, you aren't covered. But if it's and hardware issue out of the box, then you are covered. Some of claimed getting warranty either way.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Thanks. Is that all? Warranty and a fixable glitch on Private mode? Even "useless" stuff will just keep working? I'll be able to use secure, enterprise-installed stuff that go through Samsung? Pay Pal integration keeps working fine?
Steve_max said:
Thanks. Is that all? Warranty and a fixable glitch on Private mode? Even "useless" stuff will just keep working? I'll be able to use secure, enterprise-installed stuff that go through Samsung? Pay Pal integration keeps working fine?
Click to expand...
Click to collapse
As for banking apps and all that,I do not know Hopefully someone else can tell you. I don't use any of those things.
Sent from my SM-T800 using Tapatalk
Knox is for keeping and encrypted and secured environment for several apps to work more secure. The idea is that you will have a secured container for you apps (like contacts, bank apps, etc) for use at work, that's it you can have a said application with work confidential data and at the same application have personal data no confidential. So far I did see any big corporation using it, but I'm pretty sure they will start to use it. Unfortunately when you break knox you loose the ability to create that secured container or environment for ever. The idea behind it is that is impossible to break that container even through flashing over something to recreate the phone or tablet clean knox environment.
My references: I use to work with security... don't ask where...
It's a very useful thing if you are into it, but 99% of users, even some like me, don't needed. I have both my phone and tablet encrypted (well everything at my home is encrypted), but no because I'm paranoid about our government knowing my little secrets, they have the means to know it anyway, but because identity thief and such... As for the government, I don't care, they always have a backdoor to access everything. The only way to control the government is through electing honest politicians (don't laugh, there are some of them), so they control the abuse of those tools.
Hello everyone.
I'm totally new here. This is my first post on XDA.
Recently I bought a 2nd hand phone, Samsung Note 10 Plus with a very good condition. Everything seems to me perfect when I purchased it. All features are working great.
Recently I tried to add an educational google account that was provided from one of educational institution.
When I tried to add this account on this particular phone, it's showing an error that -
"Can't create work profile!!
The security policy prevents the creation of a work profile because a custom OS has been installed on this device."
(I'm posting the screenshot also)
I don't know why it's showing this error message, because I'm not using any custom OS, according to my knowledge. I got official OTA update after purchasing it.
So as far as I know, it's running on stock OS.
The model number of my Note 10 Plus is "SCV45". It's a Japanese variant named "au".
What is reason of this error behind it? I didn't install any custom OS nor root my phone. I don't know the previous history as it's a 2nd hand phone. What should I do now to fix this issue. Please help me as I'm new to this thread.
Settings>About Phone>Status>Phone Status
Phone status should be "Official" otherwise it's been rooted and the Knox efuse tripped.
Can you set up/use Secure Folder?
Thanks for your earliest reply.
Here, phone status is showing "Official".
But after using some days, I get t know about "Knox Security" & I found heart breaking fact that my phone's "Knox Security" is void & I have to live with it as there is no workaround for that issue. (Found on XDA)
But the fact is, currently I didn't found any root access & from the about section, it's showing Official OS.
Then why it's giving error msg that I am using custom OS?
I got to know from xda that if knox security is tripped then I can't use some of Samsung app like Samsung Pass, Secure Folder, Samsung Heath....
But why I can't use a work profile when I am running on stock OS & which is not ever rooted (according to my knowledge).
So what I can do now to fix this issue?
Please help.
So much for that efuse trip method indicator... there are other ways to tell. Lol, always thought that one worked. You're questions have me curious as well.
My guess it was Knox efuse, but as for work profile not sure if it was or is tied together with Knox.
I avoid the Knox features as they're rules are convoluted... and I have no need for them.
You might want to reflash the firmware to be on the safe side. There are many here that can give you a better appraisal about this than me though.
I run stock N10+'s.
Lastly you could consider returning the device if it has been rooted in the past and the seller didn't state so.
blackhawk said:
So much for that efuse trip method indicator... there are other ways to tell. Lol, always thought that one worked. You're questions have me curious as well.
My guess it was Knox efuse, but as for work profile not sure if it was or is tied together with Knox.
I avoid the Knox features as they're rules are convoluted... and I have no need for them.
You might want to reflash the firmware to be on the safe side. There are many here that can give you a better appraisal about this than me though.
I run stock N10+'s.
Lastly you could consider returning the device if it has been rooted in the past and the seller didn't state so.
Click to expand...
Click to collapse
I didn't think so it is tied with knox security. Because I have used that work profile on another mobile other than a Samsung phone. So there is no link up between my work profile and the knox security.
Now I want to reflash the stock firmware by Odin3. But the problem I faced is, when I visited SamMobile for downloading the exact firmware, I didn't see any model number with "SCV45".
All the model numbers are like - SM-N975F, SM-N975U, SM-N975U1, SM-N975N... & so on.
So, should I flash any of them? I can't choose the proper version.
My mobile is snapdragon variant.
If I flash any of the version, what will happen?? I need to know about that.
And lastly, about returning the device.
I have purchased it as 2nd hand, and the first unit that I got, has the hardware problem. So I already returned that one. So they already gave me a replacement.
So I know, there must be some issues & I have to accept that as I am getting at very cheap price. But the last one I received, is totally in fresh condition. Even the screen paper that comes with intact phone, is still there. I have checked all the the hardware and sensors. All are working perfectly. And battery backup is also good. I am getting almost 7.5hr SOT. I have checked the battery cycle. Battery discharge cycle count is 164 (I don't know whether it is modified or not). I checked the other phones that have battery discharge cycle count is almost 500 to 700.
That's why I pick this last one. All seems perfect. Only have the issues with knox security, but I get to know about that later. And knox security is also not important for me. But at least I need to use my work profile.
That is the Japanese variant.
If you're stateside a Samsung Experience center at a Best Buy can run advanced diagnostics on it and reflash it if needed.
I would stay on Android 10. Either 9 or 10 run well. 11 not so much so and 12 is a mess, both have fully active cpu cycle sucking scoped storage.
blackhawk said:
That is the Japanese variant.
If you're stateside a Samsung Experience center at a Best Buy can run advanced diagnostics on it and reflash it if needed.
I would stay on Android 10. Either 9 or 10 run well. 11 not so much so and 12 is a mess, both have fully active cpu cycle sucking scoped storage.
Click to expand...
Click to collapse
When I purchased the Mobile, It has Android 10. I've upgarde to andoird 11 just. Everything is working fine except that issue.
Can I flash SM-N975U or SM-N975U1 firmware? there will be any problem??