yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 General] Sudo77:
Whoa, ok.

-> What I gather is you flashed official firmware, and that was successful.

-> You went to CM11 which caused your trigger to trip.

-> You just modified, libgnustl_shared.so to fix screen rotation (which is the proper file to use for this fix), Unexpectedly all went back to official including Knox flag.

Well, if it works for you once, it should work again. Like you say, you need to back trace, this time with certain conditions: (WARNING only test this at your own will, I don't want you to permanently trip Knox)

- You are NOT allowed to use/install safestrap of any kind. (Activities must happen on main system).

- You can use safe-root

- You can flash any ROM or use any file to aid in your process

- If Knox did truly un-trip, the next time you install FULL official ROM with Knox app components, you must be-able to create a Knox container without getting "Your device is not authorized to use Knox" error.

I see potential in this, but these conditions should be met. Best of luck on your next endeavours.
[Galaxy Note 3 General] Lt1streconbn:
Totally agree :)

You're correct. This does prove that with a lot of modification and time and patience (at this point) the prop can be reset, even though I'm still comparing files to see what I inadvertently done. Knox is a Samsung app though in reality... it is not at all unrealistic that it has some sort of relationship with one or more other Samsung application to create an interdependent application 'network' but I really can't see any point to that honestly... but apparently there are at least some relationships between these applications and those relationships might be the answer to this problem. I don't currently own another S4 but I do have an Note 3 I can try this with. The conditions should be very similar on that device. It's new and I've not even done setup on it at this time. It will take me several days to run thru repeat this, but this time I'll be certain to focus on this and nail down what happened hopefully. Thanks :) I'll post results when I succeed

I never flashed CM to my 337... I was referring why I flashed back to stock on the 337 from past experience with an sgh-i747 S3... no custom ROM ever flashed to the device or second OS using Safe Strap...
[Galaxy Note 3 General] Sudo77:
Yup. A reminder. The whole point of resetting Knox, is trying to get the device to go back to factory settings and operation as if nothing happened to it. (Everything must work if you return to stock) This will help the device to be re-sold, or repaired without warranty issues (as well a re-using Knox in a secure corporate environment). It is challenging, I know, but you must prove yourself that you can, trip, un-trip, and return successfully. I just am concerned that the flag does have a strong relationship with the Knox applications and how they operate. (Validation purposes).

First there was the flash counter. Triangle away solved that issue. Now there is Knox. A greater harassment.
[Galaxy Note 3 General] eRPeeX:
Would your untripping knox work also for the S5 Knox? Or is the knox implementation on S5 from another kind?
[Galaxy Note 3 General] Lt1streconbn:
I have no idea what-so-ever

Before a few a few days ago, I'd say Knox 3.0 would be basically the same from device to device, but finding other Samsung apps tied into to basic functions of the device makes me nervous, and hesitant to make that assumption. There's zero reason for one of the aforementioned apps to tie into screen rotation and un-installation of applications (aside from cloud backup functions). So... I really can't say.
[Galaxy Note 3 General] :
Knox sucks

I hate knox it will be on my Samsung Mega if I update to 4.4 so I haven't updated hoping a custom firmware comes without it but I don't know if that would stop it from tripping Knox I'm hopping it does tho.
[Galaxy Note 3 General] nitrous²:
Has anyone already tried [MENTION=5538533]Lt1streconbn[/MENTION] 's method? If not, I'll try it on my hltexx (n9005) and report if anyone's interested. I know, different device, CPU bla bla. I'm just gonna give it a try unless somone already tried it with no result.

-Update:

Nope. Still 0x1 :D

Regarding step 3. As we know, a prompt will appear, asking whether you want to continue to download mode or restart. Did you mean we should just stay at that prompt screen or hit volume + to actually enter download mode?

Regarding step 4. No matter how you press the power button while in download mode (or on dowload mode's prompt screen), the phone doesn't go into charging mode. It'll just boot to OS.
[Galaxy Note 3 General] Lt1streconbn:
Hit volume plus and enter download mode.... Then hold powder button down to shut off.
[Galaxy Note 3 General] mattish.91:
I pledge $50 would be great if that knox triger could be reset incase i need to sell the device later to get a new one :)
[Galaxy Note 3 General] nitrous²:
Been trying for some time now but no, I just can't reproduce the exact conditions.

If I'm in Odin mode, there is no way to power off the device. The only thing I'm left with is the option to reboot, so no way to enter charging mode. Dang it =(

I'll wait others to report.

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 General] panosfast:
I was trying it 5 times and 1 time I succeeded to go to charging mode but nothing happen still 0×1
[Galaxy Note 3 General] Ethan Mckane:
What about the G800H?

I use the single-sim variation with a qualcomm sticker on the top, i haven't got the time to check the specs, but then, does it at least have exynos?

Sorry for that question, but i'm new to this, still, i hope there are ways to reset it back to 0X0 there (i'm waiting for overclocking kernels and custom roms for my s5 mini), just like everyone else (Tough, i haven't wrecked this phone after rooting it thankfully :p , even so, i rarely end up breaking the entire phone), hope that there are also options for other phones.
[Galaxy Note 3 General] Lt1streconbn:
It's probably a difference in our models. I'm running thru every tiny step with a note 3 ATM, because I wasn't intending to do this actually. It was very much accidental... I have no real idea if one or more of the things I done before this happened lent to this or not. At the time they were dead ends in my goals, but I always keep track of things in case of something like this. I ordered a new S4 to test with also, since I really don't want to flash this one back to stock as it is the phone I use for my own use, and I finally have it where I really like using it finally more or less. It'll take me time to go thru everything properly, but that's what I'm doing now :)
[Galaxy Note 3 General] nitrous²:
It's a good idea to keep track of things like this. That's what I'm going to do from now on. If I find the time, I'll do a deep research on this topic. Maybe I'll find useful information. I also have some friends over at some service points and official repair shops which I could ask. If not, I'll ask one of my professors :D I can't and so I do not promise anything. Last time I did something like this, I wanted to find information on achieving S-OFF on the HTC One X. I ended up finding the solution but only by signing a NDA and paying nearly a thousand euros for hardware which didn't helped at all :(

Anyway. Here goes nothing!
[Galaxy Note 3 General] shayind4:
Same experience here. No way to power off device. Seems this method has not worked for anyone else. A reset method will surely come up.
[Galaxy Note 3 General] BROKEN1981:
Lol only thing that did was stop S-health from counting my steps
[Galaxy Note 3 General] Sudo77:
Wait... Are you trying to get root access/set SE Linux to permissive to edit scripts like build.prop to modify the ID of the Knox flag? It dawned on me that, following issues discussed earlier, you do understand that the Knox flag is much deeper than on an OS/Kernel level right? For example, if you were able to modify those scripts to get the value back to 0, the evidence will still remain in the emmc and my guess is that the bootloader is responsible for fetching those values. So, if you re-stock (re-install) your system the flag will still remain 1, or even revert to it, and I don't see much reason to modify individual scripts on the OS. Pardon my skepticism.

This is why I want to stress devs to take a look at the BL first. The evidence must be removed from those areas. But Samsung is smart. Since both, the areas of the emmc and the bootloader locked, it is a real challenge to even be modifying those areas in the first place. Thought this is worth consideration, as I have repeatedly been doing.
[Galaxy Note 3 General] BROKEN1981:
So if chain fire is not going to help, should this be considered a dead issue?
[Galaxy Note 3 General] Sudo77:
I wouldn't go as far as calling it a "dead issue" but its pretty close. Also, its not that Chainfire doesn't want to help any longer, I'm sure he would gladly. It's just commonly accepted that the solution to this issue is

not feasible

due to security constraints. If you haven't already, go read his post here: http://xdaforums.com/showthread.php?p=52293397#post52293397 and post #1568 on the same page. I feel both theories hold true to the current situation. It's not saying I am with them, I did my research separately. But my sources did point to the same conclusion.

I can repost my findings but I have done so far too many times already. If you'd like to understand more I suggest you take your time to go through this thread. To end on a brighter note, I did come across a user who did replace their emmc on an Exynos variant, and stated that their Knox bit did "reset" to 0. This is great proof that the warranty bit indeed is within internal memory. This solution is inefficient, costly and difficult but it should work.

It's similar like you loosing your main password (key) during log-on. You have two options, hack the OS for the key/keyring (nobody does this, its difficult time consuming as hell) or you can just re-install the system. Of course the private data will be safe (and gone) once reformatted. Like Knox, if you want to remove evidence of tampering, you need to replace old hardware with new untampered. It's cool to imagine how Knox implementation does this so flawlessly. Preserve data integrity. Oh, forgive me, now I'm ranting. :D
[Galaxy Note 3 General] msasm09:
I think you might end with charging after go to download mode press volume up leave it for couples minutes and hold power button for enough time only when you plug usb cable not charger any one please report back
[Galaxy Note 3 General] drew071:
I just tested the odin made power off.

Hold power and vol down.

Theb press vol up to continue.

Then hold power till screen in black and the phone doesnt reboot it goes to charging mode ie power off charging.

Worked first time here.

Drew
[Galaxy Note 3 General] nitrous²:
[MENTION=2786013]drew071[/MENTION]

Yeah, that's exactly what I've tried about twenty times
[Galaxy Note 3 General] shayind4:
Do we leave out the HOME button?
[Galaxy Note 3 General] drew071:
Seems odd it worked first time here.

Could it be bootloader issue?

Drew
[Galaxy Note 3 General] BROKEN1981:
I really doubt its as simple as replacing that one file. Samsung would not be that stupid. Not with knox. All the methods if root is because Samsung allows it. If you tripped knox they want to keep it like that.

Whats odd on my end, is i tripped knox. Yet was able to use the container. I no longer can. Not sure what happened. And no, not talking about private mode. Is it possible for gliches to happen? My phone does love to random reboot ALOT. Happens with texting on Google+ with response to people posting on YouTube videos.

Either way, i should never have been able to get the container to work at all.

Ive asked this question before, figure this thread ill get a response.

Just also want to say it's not the knox launcher from Samsung Apps.
[Galaxy Note 3 General] intel.imran:
knox counter reset

is this work for Note 3 N9005.???
[Galaxy Note 3 General] ryanbg:
Knox is only going to 0x0 temporarily, because the method you guys are trying temporarily corrupts the memory where the flag is stored.
[Galaxy Note 3 General] brandonsisco:
I know of a solution to reset knox, how to show proof to the community and collect the bounty? :D
[Galaxy Note 3 General] JonSCSL:
Keep in mind this thread is for the Note 3 Snapdragon variant. Not the international Exynos variant.
[Galaxy Note 3 General] Sudo77:
So, we have another user who claims to have "found" a solution. At this point, all solutions proposed previously failed or doesn't meet the solution criteria. I'm also getting so skeptical is not even funny. But hey, if truly think you've got it post it right here, but not only post it, PROVE IT. :mad: If we, as a community, see that it works, you can notify the original poster and arrange a bounty claim. NO PROOF == NO $$$. LOL

Oh, actually it doesn't really matter now if it's Snapdragon or Exynos, Note 3 or any other device (Yes, I understand the thread rules). Let's just see a solution that actually WORKS. We can use the findings to check for other models, it may even be universal.
[Galaxy Note 3 General] beausmith94:
From Root to Rom to Brick to Knox fix? Maybe

Hello,

Total newbie here, but I figured I would share my experience.

I had a T-mobile Galaxy Note 3 a while back and I recently just returned because the charging port was damaged. Anyway, when I first got the thing I rooted it with the chainfire method (I got it in january of 2013), and then installed a few ROM's before I was happy.

One day I got bored of the old ROM and tried to do some fancy stuff and change to a different one, but it wouldn't mount and yadayadayda. Impatience led to a mistake and boombingbang I have a bricked Note 3. (May-ish)

There was no literature on how to fix a bricked phone (it would turn on, but not boot, and recovery wouldn't flash). So what do I do?

I used the Samsung KIes emergency firmware recovery tool! It's kind of a pain, but essentially it has you report a few numbers under the battery (so write these down before you attempt a recovery), and then it recovers the device.

The cool thing was, it replaced my bootloader, my recovery, and everything feasibly possible, with the original firmware.

The Knox counter was reset!

How do I know?

When I returned the device, the T-mobile tech gave it the cursory check and also informed me that any software changes would be noted (lol) and checked when they sent the device in. I was hardly worried because I had already checked the device for any signs of my previous tinkering.

A week later, after receiving my new phone and confirming that they had received and checked my old one, I didn't have to pay for anything.

IT HAD NO KNOX COUNTER DESPITE BEING PREVIOUSLY modified with ROM's, recovery, and root.

I wish I had screenshots, because it was a damn miracle, but it makes me wonder if my success was because the phone was "soft bricked" rather than hard bricked, or if that mattered at all.

Let me know if this worked for anyone else, and good luck!
[Galaxy Note 3 General] headhood:
Me 820$
[Galaxy Note 3 General] Sudo77:
Hello beausmith94, welcome to XDA. I just want to ask for some clarification on your event because your post threw me off a bit. You said that you received your Note 3 on January 2013?? If I remember correctly, the Note 3's opening was on September of that same year, so how is it possible to receive a phone 8 months before release date let alone on a T-mobile carrier? Perhaps you are talking about a different phone? That or you must be a time traveler. :D

Anyhow, Knox was introduced with Note 3 along with Android 4.3, so it is not possible for your phone NOT to have a Knox counter (dev phones aside). But let's say you didn't have a Knox counter, your download mode screen would look similar to THIS. At this point, it doesn't really matter how many times you flash or root your phone. Only the flash counter will increment (Notice the 63 counts...Damn).

As you were fixing a soft-brick with Kies OTA (which was the correct procedure to take), it indeed did replace and upgrade your official bootloader amongst many other things and locked it. Hence an extra line (or two) was added to download mode seen HERE. Now the Knox counter is added, it will initially start at (not reset to) 0. Perhaps you thought this constitutes as a reset, but really doesn't. A miracle would be Knox counter 0 to 1 and back to 0. But I have never seen this happen... (Keyword here)

PROPERLY

that is. Then you took your phone to the shop. It this similar to what happened? I just thought to explain this because I see many people get confused about this matter.

I believe that the concept of Knox was created by some brilliant people, and it will not falter easily as most people think.
[Galaxy Note 3 General] beausmith94:
Definitely meant January 2014, sorry about that!

If memory serves the Knox was fully reset, but it could have been 0x0. I tried a number of boot loop flash fixes prior to the firmware recovery as well.

My primary point is that I was able to return my phone for a trade in with no questions asked, after the recovery, and for most people this is enough. All I want to be able to do is return my phone under warranty or upgrade, and this method worked:)
[Galaxy Note 3 General] dodgebizkit:
Sounds legit, I hope it is :)
[Galaxy Note 3 General] SXXMEN:
hey guys,

anyone in this thread know how to revert knox 0x1 to 0x0

or how to get knox working in 0x1 i did root by Odin3-v3.07 then after that my note 3 from 0x0 to 0x1 and knox not working anymore so

any body know how to fix

plz help me thank you
[Galaxy Note 3 General] ryanrazer:
Have you tried his method? :)

You are joking right? People are busting their asses on how to reset knox for almost 2 years now and now you come and ask if someone knows how to do it, like you asked if someone has a bubble gum...

No, it was not figured out yet (at least verified method).
[Galaxy Note 3 General] radzio27:
Hi.

I am not sure, if you know that, or is it important, but few day ago I received my Note 3 from service center. They change mainboard, but the knox 0x1 still persist, and the other phone statistics are same (blouetooth, charger counter). I dont know, maybe they have done some kind of backup of old mainboard, or these things are written somewhere else.
[Galaxy Note 3 General] Ricky Divjakovski:
surely the flag is not stored within /system.
[Galaxy Note 3 General] BROKEN1981:
Lol!!!! Best post ever!!!!!
[Galaxy Note 3 General] Sn0w0nS:
Lol :p
[Galaxy Note 3 General] Sudo77:
No, it isn't. I was just asking about his methods at the time. Perhaps it is within one of the dev/block/mmcblk0 partitions, but you don't have access to it (the size of it is very small, about 512kB). The point I'm trying to make is, the flag isn't bound to the OS, if you delete everything on the phone even Android itself the flag will still be there. Makes editing scripts and config files pretty useless don't you agree? Which leads me to ask the following user...

Hi. :) Yes your story is very important to me. Why did you say Knox still persists even when they replaced your motherboard? Is your mac address still the same? Are you sure they didn't just replace PARTS of your motherboard? And lastly, what Note 3 are you using N900 or N9005. Explain, as best as you can. Thank you kindly.
[Galaxy Note 3 General] Ricky Divjakovski:
ofcoarse it would be.

im not sure if its the bootloader, its possible but the flag could reside in a seperate partition
[Galaxy Note 3 General] Sudo77:
Right. The way I see it, the bootloader doesn't contain the flag. It's job is to fetch the flag value at boot time from wherever it resides in memory. That is why if you can modify the bootloader code, you can change it's operation drastically. But it locked, so the end. LOL

Normally the partition can be found at /dev/block/mmcblk0rpmb, but when I was going through all the listed partitions it wasn't there. :( So, there can be two possibilities, either it is merged with existing partitions, or Samsung hides it so that is not readable by the OS (to protect it's chances from getting hacked).
[Galaxy Note 3 General] Ricky Divjakovski:
Exactly, but with that being said disassembling of the boot loader could possibly lead to finding where the flag is fetched from.
[Galaxy Note 3 General] Sudo77:
Right, I thought like that a few month ago. Say you do find the location of the partition of where the flag is. Then what? The RPMB is likely to be securely encrypted with a key that is tedious to break. Also, say if you knew the key; how are you going pass it to the RPMB for access, and rewrite the value of the flag to 0? (via JTAG?) As I mentioned above, that is the bootloader's job. But again, that's locked and can't really be modified or flashed on locked devices (without Samsung resigning the code with a certificate so that it can replace the locked one). Oh... brick wall. Do you follow?

If your bootloader WASN'T locked previously you could remove the contents of Knox from the firmware BEFORE initial flash. Done here (No Knox counter will be added):

http://www.youtube.com/watch?v=75DKAGNstbM

But that wouldn't help users who already have Knox in their system would it? :(
[Galaxy Note 3 General] sajjjjjjad:
can i reset my N9005 knox flag?!
[Galaxy Note 3 General] ownjoouk:
Oh my god. Have you actually bothered to read any of this thread.
[Galaxy Note 3 General] dodgebizkit:
Yes.

Insure your phone. Smash your phone. Claim a new phone on insurance. 0x0 :)

-------------------------->SIG<------------------------

Even my house phone's better than your iPhone.
[Galaxy Note 3 General] BROKEN1981:
That method is only good for peoole who never had knox to begin with. I saw the uploader state this in the comments
[Galaxy Note 3 General] Sudo77:
I know, gosh! :mad: The last sentence was rhetorical. The whole point of my last post was to prove to you that once Knox is in your system, it is very difficult to get out. Contrariwise, do you see how easy it is to prevent Knox on a Knox free system? People, for goodness sakes, try to get a deeper understanding of things and what going on before commenting. Anymore of "can anyone reset Knox on N900x" without even reading, I will urge mods to close this thread.

Pardon if I spoke sternly, but useless information leads to a useless thread. Think of the people who posts bounties which is was this thread was originally for.
[Galaxy Note 3 General] BROKEN1981:
Sorry i had no clue. At first i thought i could take knox out of my system till i read the comment from the uploader. So either way my comment was not all that bad. Anyone with the same thought as me will have a clear answer. =)

As far as resetting knox this is a dead issue im sure. I just follow to see how it plays out. You have the note 3, note 4, s4, s5. Soon the s6 in 8 months. (Nothing confirm, going by how devices get pushed)
[Galaxy Note 3 General] radzio27:
I sent my Note 3 N9005 (BTU) to service center, because it had a freeze and restart problem. I sent it with Knox 0x1. When I received it, in service documents was wrote, that they changed those parts:

gh82-07651a Mainboard [A/s ASSY-PBA MAIN (COMM);]

GH59-13654A Power key tape(?) (I am translating this from polish to english, so I am not sure for 100%) [Module-PWR key + Motor (SM-N900P);]

But It still had Knox 0x1. Imei is same, but I dont knwo if mac address is the same.

Counters of charger and headset are the same as in old one, but manufacturing date is not correct. It had ~10.2013 (not sure about month), and now it is 2014.11.19
[Galaxy Note 3 General] Kernel ranger:
I tend to think that the reboot signal is an interrupt initiating a checksum like process that compares stored values to values given by the custom recovery and when they don't tally it returns a unity that knox flags as a 1. So I think there might be more than one way to skin a cat. The other way is to crack the bootloader.
[Galaxy Note 3 General] acme1974:
https://futureservice.samsung.it/

---------- Post added at 11:55 PM ---------- Previous post was at 11:55 PM ----------

In italy 15 euro e reset Knox!