yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] omniwolf:
yep agreed. As long as you can prove the phone has an issue with stock firmware, then KNOX shouldn't come into play with warranty returns.

wow, i think you're going a bit overboard here. My intention was never to offend anyone, I was just trying to explain the reasoning. If you never use your phone in a corporate environment, then why do you even care? the fact that your download screen talks about KNOX doesn't affect how you use the rest of your phone. You just can't use KNOX things, and THIS is fair IMO. Now, if they start refusing warranty returns that have nothing to do with KNOX, that's where they have gone too far.
[Galaxy S 4 General] EmDzei:
I'm new in this thread. On post #105 user sorg write about: "What i'm worrying is that KNOX can affect some other apps. For example, we all know that you cannot use wireless display feature if your phone has "custom" status"." And what I am telling you, I am very interesting to use this wireless display thing, or wish. And maybe this jumps to my eyes with HDMI cables too.

My early phone was Galaxy S (GT-I9000) where all this Samsung rise begin. I have flashed stock ROMs to my SGS with ODIN by Windows easily. But when KNOX efuse is burned/ flag rised, I cannot use Odin anymore? How I take backups or flash unbroken system? I guess KIES doesn't help me either. I need to flash custom recovery, but not with ODIN anymore. How? If I flash custom clockworkmod (CWM) I rise the KNOX flag. Rat race..

Btw. Whos is behind the ODIN app? SamMobile or Samsung itself? Do we need custom/ hacked/ new "ODIN" to flash?
[Galaxy S 4 General] Daagen:
You can flash newer firmwares via Odin but you can't downgrade or reset the knox-counter.

Custom recovery will raise the knox-flag.
[Galaxy S 4 General] wPatriot:
Spinky, your device has the flag, what ROM are you running? And if it's not stock, were you able to flash a different kernel as well? I know Knox basically locks your bootloader into place, but what happens to other, normally flashable, parts of the system?
[Galaxy S 4 General] arovik:
Also reflashing original rom sets the flag :( It does for me...
[Galaxy S 4 General] spinky360:
OK... So to understand: I have 2 units. One is MH8 and one is MF8. MH8 is 0x1. You can flash what ever you want that is not touching the file aboot.mbn. if you try to flash a stock ROM ( exe: MGA ) you can flash it but you have to remove from it about.mbn. on MH8 I'm running Slim Bean. You can install even kernel. I was running Blue Kernel from Faux123 but wasn't starting all the time. I was forced to go in recovery and to clear cache after reboot.
[Galaxy S 4 General] DjeMBeY:
Wow! :D Where did you get this idea from?? :p You can do with Odin whatever you want, root, flash Custom Recovery/Kernel etc even if your flag is 0x1.. Nothing to worry about, you can't go backwards or sideways anymore - can't go from XXUD... to ZHUD... nor ...MH8 down to ...MEA :(

KNOX WARRANTY VOID 0x1 is worrying only if it affects Warranty Rights in anyway but it's still unknown..

Hmm... it shouldn't but it's a good example that it can't affect Warranty Rights... IMHO ;)

I've flashed same STOCK FW many times and all the time was 0x0, it changed to 0x1 after I flashed XXUDMGG repacked with older Stock kernel.. (unofficial FW in some way...)
[Galaxy S 4 General] slig:
Going backward or sideways is completely impossible with Odin on this bootloader or it just rises KNOX flag?
[Galaxy S 4 General] DjeMBeY:
Impossible, Odin will fail on aboot.mbn (bootloader) and even if you repack whole FW without aboot, your phone will become useless , no WiFi, no sound, and it's a big chance that your flag will be risen as well.. :( bollocks... :p
[Galaxy S 4 General] malamen123:
When i can see if havê th e flag?

Enviado do meu GT-I9505 utilizando Tapatalk 4
[Galaxy S 4 General] Swanseatom:
I just got my phone returned from warranty claim. Sent in a dead s4 could only boot to download mode and was knox 0x1. They replaced the device no questions asked. Repair was arranged direct through Samsung in the UK.
[Galaxy S 4 General] malybru:
Hi,

What was your knox counter upon return...0x0 or 0x1 ?

:)
[Galaxy S 4 General] Joomlad:
I am currently using the UK 4.3 firmware as it is not yet available for Australian carriers. My question is if I root and use a custom ROM am I able to then flash the stock Australian 4.3 firmware when it is released?
[Galaxy S 4 General] Bordo_Bereli51:
Yes you can flash any 4.3 firmware with the new bootloader, but you can't downgrade to 4.2.2
[Galaxy S 4 General] samt3:
I haven't got the update yet (and don't want it) it says i have the latest even though i don't. But i cracked my screen yesterday and got a new one on the way. I'm positive its going to have the MJA update. I got my warranty back on this one by Mobile Odin and went back to MDL and reset the flash count and let it OTA to MF5. Like I said I don't have the update yet but I'm sure my S4 That's on the way will have it. Could I not just Mobile Odin (or nandroid) back to MDL then let the OTA update install the MF5 OTA with the MF5 bootloader and over write the MJA bootloader. Or is there more security that blocks you from being able to do that?

Edit: Sorry lack of sleep. Just hit me even if you Mobile Odin back your not going to be able to get a OTA because your still going to have the MJA bootloader which cant be reset. Ignore this question.
[Galaxy S 4 General] Joomlad:
ok. i had just read somewhere that once u get the knox flag it breaks ODIN also. so how would i then go about flashing stock firmware? does Mobile ODIN work with 4.3 yet?
[Galaxy S 4 General] samt3:
Don't know about a flag breaking Odin. But mobile Odin works

Mobile Odin

"v3.85:

- Fixed SGS4 I9505 on Android 4.3 issues

- Fixed CSC issue with >2gb firmwares"
[Galaxy S 4 General] Joomlad:
ok so if i was to put the stock australia firmware on my sd card (when they release it) i should be able to flash it from Mobile Odin without problems?
[Galaxy S 4 General] samt3:
Yes that should defiantly work.
[Galaxy S 4 General] szczeslaw:
From your signature i can see you're from Poland.

Try searching for act called "Ustawa o szczególnych warunkach sprzedaży konsumenckiej". It's basically a law that is made according to UE directive.

It says, that you can basically choose i you want to use manufacturers warranty, or go we your claim directly to the seller. The seller is obliged to fix your phone, give you new one or give you refund.
[Galaxy S 4 General] Joomlad:
Can anyone else confirm this? Need to be sure before I go rooting and losing my Knox warranty :P
[Galaxy S 4 General] samt3:
I didnt say anything about having the warranty I just said it would work. Warranty depends of if you have the 4.3 bootloader or not. If you dont have the 4.3 bootloader yet Mobile Odin back 2 updates reset the flash count and everything. Then OTA to the next update then just double check that everything says official if not factory reset and it will. Then OTA to 4.3. If you already have the 4.3 boatloader your out of luck atleast for now anyway.
[Galaxy S 4 General] Joomlad:
OK so since I am using stock UK 4.3 with bootloader I can't root and then flash stock later? So my best bet is staying unrooted until Australian firmware is released?
[Galaxy S 4 General] samt3:
How did you put the UK 4.3 on your phone? If you used Mobile Odin or cwm/twrp your fine you still have the old bootloader.
[Galaxy S 4 General] Joomlad:
I use pc Odin. I know that I have the new bootloader. I was hoping I could use a custom room for a bit while I wait for the Australian firmware but if I can't flash it after rooting then there's no point
[Galaxy S 4 General] samt3:
Yea theres nothing you can do if you have the new bootloader. Im surprised you have got a flag just for using Odin to install it. I read a few people installed stock firmware but Odin triggered a flash count.
[Galaxy S 4 General] Joomlad:
I used pc Odin. And I know.that I have the new bootloader. So maybe i should just hold off rooting my phone until my countries firmware is released and not root. Hopefully someone can figure out how to make it so we can reinstall stock firmwares after tripping the Knox flag. If it was to use Mobile Odin or some other means
[Galaxy S 4 General] Mittaa:
Can you confirm that I can flash stock Samsung firmware 4.3 with Odin Mobile,

keep old bootloader

,

keep root

(EverRoot) and

keep custom recovery

... and NOT trigger KNOX 0x1 :confused:
[Galaxy S 4 General] Joomlad:
I don't know. I have flashed it twice without a problem so not sure. Maybe it will flag me after I flash the Aussie firmware when Sammy release it lol
[Galaxy S 4 General] samt3:
It will be fine. There wasnt a knox flag on the old bootloader.
[Galaxy S 4 General] nikos k:
knox ....

knox ....

Dear Mr. . N. .......

Thank you for contacting the Samsung Electronics Hellas, relative to your request, we would like to inform you that under normal circumstances , any modification of the machine constitutes breach of warranty , as Samsung does not guarantee proper operation of a modified product. The KNOCH stops working permanently with the root or attempt any action to change the software. The KNOX WARRANTY VOID 0x1, which changes from 0x0 constitutes proof of use of the device under conditions deductible warranty . The operating KNOX reset now only by changing the central board . If you wish , you can cite your device in one of our authorized repair centers to make changes mainboard fee
[Galaxy S 4 General] Mistertac:
I'm on 4.3(Verizon S4)and retained root through that update my Knox is still 0x0. The same goes for my girls Sprint S4 I've checked . Now wouldnt that in theory constitute a '' change in software '' ? I've read some people's Knox have been tripped that way.
[Galaxy S 4 General] Mittaa:
Happy to hear, but to be honest i'm a bit confused!

From all the threads talking about old and new bootloader, I understood that newer firmwares with new bootloader, won't work with old bootloader.

So if one just avoid using Odin PC everything is OK ... then why all this fuss about KNOX 0x1?

As far as I recall Chainfire have warned about flashing 4.3 because of the new bootloader!

PLS read this ... link

So I need a bit more confirmation before I take the jump towards ANY Samsung 4.3 firmwares with new bootloader!
[Galaxy S 4 General] roomoonek1991:
knox comes with 4.3 upgrade which turn it on and add a knox flag. If we will made a patched bootloader from original one, and remove the lines from code which turning on knox flag, and flash it via odin, that can disable knox feature from our devices. Is that possible? I'm newbie but maybe that can work.

Sorry for bad english.
[Galaxy S 4 General] ryan2202:
I just got pwnd by this crap. My volume key is screwed up and I was going to put the phone back to stock to take it to Sprint. Wiped, installed stock image, and ran updates. Didnt realize the 4.3 update added the bootloader changes. I decided NOT to take the phone back in for service until later. Went through the motions to restore my ROM and couldnt get into recovery. NOT. HAPPY.

---------- Post added at 04:06 PM ---------- Previous post was at 03:27 PM ----------

So...no idea how this happened. But I just got into CWM recovery after I couldnt before. I didnt do anything different than I was doing early other than rebooted again. I even got that message that "recovery is not seandroid enforcing" and next thing you know CWM came up instead of the stock android bot recovery. CWM Restore is running now, we'll see if it boots.

---------- Post added at 04:24 PM ---------- Previous post was at 04:06 PM ----------

OK, restore worked. I am now back on PAC All In One 4.2.2. And Im am able to reboot back into CWM recovery. I still get the message "recovery is not seandroid enforcing" on the Galaxy S4 splash screen, but CWM comes up not the stock recovery. Not sure if its useful or not but heres a summary of what took place: Basically went from 4.2.2, to stock 4.2 and upgraded to 4.3, lost recovery, and somehow got back into CWM 6.0.4.4 while still on 4.3, and restored back to 4.2.2 and can still access CWM 6.0.4.4.

- broke my volume button, so was going to take phone back to Sprint to inspect and/or replace.

- wiped, and flashed stock image.

- accidentally updated 4.3 OTA (wasnt paying attention and thought it was the MF9 update).

- decided not to take my phone back today, so tried to restore back to PAC Man 4.2.2.

- couldnt get into recovery, was getting the "recovery is not seandroid enforcing" message on splash screen.

- found this thread, and felt doomed.

- rooted the stock image, installed ROM Manager, flashed 6.0.4.4, still couldnt get into custom recovery.

- tried all kinds of stuff through ODIN. Flashing various recoveries appeared to complete, but still couldnt get into custom recovery. Couldnt flash stock image through ODIN.

- gave up. Made a mess of the stock image, so I was going to reboot, wipe and start from scratch with 4.3.

- when I rebooted, expecting stock recovery, CWM came up.

- wiped, restored my 4.2.2 PAC ROM successfully.

- still get the "recovery is not seandroid enforcing" error message on the Galaxy S4 splash screen, even when not trying to go into recovery.

- rebooted again, can still get into CWM 6.0.4.4 even though the error comes up.

- Download mode screen still shows Knox Warranty Void: 0x1, with Current Binary and System Status: Custom

- GS4 splash screen shows: "KERNEL is not seandroid enforcing" and "Set Warranty Bit: kernel." When I couldnt get into custom recovery, both of those showed "recovery" instead of "kernel." I am on the stock kernel that came with the phone on 4.2
[Galaxy S 4 General] Joomlad:
wow from what i've been reading it sounds like once on 4.3 the only place to go if u want to root is custom roms, and to use stock firmwares better to stay unrooted. crazy samsung, just crazy. knox :confused:

---------- Post added at 09:08 AM ---------- Previous post was at 09:01 AM ----------

what does everyone else think? that's just what i gather but i could be wrong. so what's your opinions? rooted and go custom or stay 100% stock?

---------- Post added at 09:13 AM ---------- Previous post was at 09:08 AM ----------

i did read on the Mobile Odin thread that it is now working for 4.3 (04.11.2013 - v3.85

- Fixed SGS4 I9505 on Android 4.3 issues (new flashkernel!)

- Fixed CSC issue with >2gb firmwares)

so what would happen if i rooted my 4.3 and then had a custom rom and tried then to flash stock from mobile odin?
[Galaxy S 4 General] samt3:
You would be stock again just no warranty. Once you have the 4.3 bootloader you have it for good and once you have a flag on it the flag isn't going anywhere.
[Galaxy S 4 General] Roberto797:
Caught out

Got caught by this last night.

Updated to 4.3 and rooted a week ago, my troubles started when I used Odin to flash CWM recovery, it came up with the seandroid and knox warranty warning and I lost my root. Took about two hours to get it back. Teamwin recovery and SU worked.

Still Samsung have kindly voided the warranty on a three month old phone, I have run custom software on every phone I've had for the past four years without incident and this is the first time I've seen a company take such a strong stance against it.

I will keep my eye on this fourum till the end of the month for a solution but I have allready resolved to buy an LG phone next payday and never go back to Samsung again, I'm sure many technical users will feel the same way.
[Galaxy S 4 General] chubby65:
Well mate if you are going for LG you're gonna need to google LG gate because that's going to be similar to knox :(
[Galaxy S 4 General] Joomlad:
I just thought I read somewhere that rooting and tripping the flag breaks Odin and it will no longer flash firmwares. So from what I gather mobile Odin is the only option for flashing firmware?
[Galaxy S 4 General] lamplighter13:
So can I assume since my Knox is at 0/1 that is why I can not install a custom recovery ? I am currently using Echoe custom Rom so does this essentially mean that I am stuck on Echoe custom ROM for the life of the device ?

Thanks to anyone for clearing this up !

LL13-
[Galaxy S 4 General] Bessagabriel:
don't think the 0x1 flag will break odin.

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 General] lamplighter13:
I don't know but since I am 0x1 Odin is not working for me, for anything.

LL13-
[Galaxy S 4 General] bungadudu:
I flashed new modem and philz without problem...
[Galaxy S 4 General] lamplighter13:
And are you 0x1 ? If you did flash philz then that is good news because maybe it's just me. I been trying to flash philz recovery and am getting "Odin has stopped responding" and tried another .tar file for custom clockwork mod recovery and it always goes back to stock recovery, no matter what.

Will have to try in the morning, beddie bye time.

Cheers, LL13-
[Galaxy S 4 General] Joomlad:
So i am really now wanting some people to verify that if i root and trigger the knox flag, can i then flash an official rom at a later date using pc odin or mobile odin? has anyone tried/done it?
[Galaxy S 4 General] mlavende:
I triggered knox whilst on 4.2.2 and was able to flash the latest official EEVM MJ8 4.3 rom using odin.

Went back to my 4.2.2. backup after a while though since the battery was a bit pants. Since discovered that I have a swollen battery which I've now exchanged so it might be worth trying 4.3 again. Mind you there are lots of issues so I might just wait for 4.4.

Thanks

-Mat
[Galaxy S 4 General] samt3:
They will fix 4.3 at some point way before 4.4 comes out. You got a long while before you see 4.4 on touchwiz.
[Galaxy S 4 General] LEENO:
Hello, i have new bootloader and 0x1 flag, i want to install knox but it say "device not authorized",

i have no chance to use it?
[Galaxy S 4 General] samt3:
No. Once you have a flag knox no longer works.
[Galaxy S 4 General] irfan0303:
KNOX is a software treigger and can be reset.

Story of someone:

Hi all,

First of all pardon me for my poor English.

Today I went to Samsung service center to fix my note 3 SM-N9005 after I missed up with it.. no efs folder, no IMEI, bootloader flashed to MJ3 and the Konx was 0x1 actually warranty void..

The technician guy checked the Konx and told me the warranty is void but don't worry I will fix it for free.

The surprised thing is that they have fixed my mobile within 10 minutes.

After fixing it.. I checked the the Konx is back to 0x0 so they reset it !.

The bootloader back to MJ1 so they downgraded the bootloader !!.

IMEI and serial no. never changed !!.

And no hardware change at all.. so now, its very clear the Konx trigger is a software trigger and can be reset again with some how.
[Galaxy S 4 General] Kwbmm:
If it's true that is a good news..

Inviato dal mio Samsung Galaxy S IV
[Galaxy S 4 General] Tanis64:
Exactly same text was posted a couple of weeks before (end of October), so this seems to me faked, cause it's never confirmed seriously. :confused:

Send from the outback with my GT-I9505
[Galaxy S 4 General] bungadudu:
He said "story of someone"

And by now we gathered enough reports to conclude that Sammy can reset knox.

We just don't know how..
[Galaxy S 4 General] kingofthe440:
Im not the most advanced in the area of rooting or KNOX, and would prefer to avoid this huge headache until a solution comes to light. Is there any way to avoid installing the OTA update from sprint? Right now i have a notification that I cant clear that informs me an update has been downloaded and is ready to be installed when I touch the notification. Can I turn this notification off and keep MF9 while we wait for a solution?
[Galaxy S 4 General] samt3:
Should just be able to freeze the OTA apk if your rooted. Im on a custom rom right not so I cant tell you the exact name of the apk. Then when you want the update defrost the apk. If your not rooted there is a chance you might be able to disable it under app manager.
[Galaxy S 4 General] matale0:
Why normal user need knox? Got flag. Its not working but can live with it. Well still waiti g for god news of reseting it...

Wysłane z mojego GT-I9505 przy użyciu Tapatalka
[Galaxy S 4 General] My1xT:
how about warranty?
[Galaxy S 4 General] samt3:
Warranty is gone with a knox flag.
[Galaxy S 4 General] My1xT:
I know that. the question was a response to
[Galaxy S 4 General] kingofthe440:
So i have not updated yet, been dodging the OTA update bring pushed, and while I was trying to freeze the OTA update I went into Titanium pro and was looking for the update app and noticed Knox was listed? I thought Knox wasnt supposed to be on the system untill this latest MJA update? Im still on MF9...
[Galaxy S 4 General] xiocer:
Samsung fix this!!!!!!

Hi there all of you guys!!!!

Well it has been a wile i did not post anything , but here is what happened to me yesterday.

I have an S4 i9505 Brand New from Samsung Store!!!!

I got home and started to use it everything perfect.

Well my nightmare is here....

i got a message that there is a new firmware etc

i did put accept started to do his thing and almost at the end crashed for no reason.

it did restart and i was back to 4.2.1 but!!!!!!!!!!! with knox!!!!!!!!!????????????

KNOX Warranty 0x1

I did not use anything , no odin just ther stock firmware OTA

Why do i get this???? And who is responsible for this??? i when to the store and they said warranty is void because the phone says voided????

thank you

With this F U SAMSUNG!!!!!!
[Galaxy S 4 General] :
Can you please go to the settings and "About Phone" and make a screenshot?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 General] Mittaa:
First: are you sure it was brand new? Somebody might have burned the fuse and then returned it to shop :eek:

Second: If you prior to update have installed custom recovery like CWM/TWRP or rooted, then the fuse will become 0x1 :(
[Galaxy S 4 General] cooza:
I read a while ago on SamMobile that KNOX was made to stop phones being sold outside their regions.So a phone in Europe cant be sent to another country to be used if its unlocked to escape carrier devices and keep sales in their respective areas.

So...heres my question...I go my S3 and Note2 when living in Spain and moved not long ago to the US.The S3 is vodafone Spain now unlocked rooted custum ROM to work here and Note2 is international model obviously rooted custom ROM but had Spanish firmware.I brought them both with me and now are on at&t.When you flash KNOX apparently it locks you phone in to its region and then cant be used outside of it so if I flash a ROM with KNOX will my phones get locked back into the European region and leave me phone-less.In theory it should...at least that is what I read anyway.
[Galaxy S 4 General] Kwbmm:
i suppose you don't have an European sim card to check..

Inviato dal mio Samsung Galaxy S IV
[Galaxy S 4 General] cooza:
Mate Im to scare to try HA HA!!!:silly:

Im just interested to see (and maybe worried for the future too) what would happen if I did flash a KNOX bootloader.I dont want the S3 (VF Spain) to lockup on me:crying:

Maybe a long shot and way off but interested anyway.Apparently once you use the phone the first time it stays in the memory so taking it out of the country doesnt help.I think Im fine since I didnt use the phone first with a KNOX bootloader.I think its locked to the region once you put in the sim and it registers to the KNOX security but since I,we have foreign firmware from flashing then where does it lock to...the carrier I guess.Although I also read that some KNOX European phones are made not to except US sims...:confused:
[Galaxy S 4 General] Kwbmm:
i don't think the phone will be locked if you try.. To me, the worst it can happen is tha you insert the sim card and the phone tells you it's not supported..

But, as always, I'm no tech guy here..

Inviato dal mio Samsung Galaxy S IV
[Galaxy S 4 General] jamcar:
What actually happens if you void the KNOX warranty? I know the bootloader shows 0x1 rather than 0x0, but does that actually do anything? Is it still possible to install a custom recovery/ROM/kernel? Does Samsung just not honor the warranty anymore?