yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] donalgodon:
I thought might be helpful to clarify and state explicitly which firmware actually introduced the KNOX mess, because the other thread does not do so. What is the timeline/progression surrounding this? I don't know where MH8 falls in relation to MGA, for example.

Is it certain that MH8 is the beginning of KNOX?

I also said that I flashed:

I9505XXUBMGA_I9505OXXBMH1_I9505XXUBMGA_HOME.tar (Is this ROM known as MH1 or MGA?? :confused:) via Odin before knowing anything about this situation, so it seems I got lucky.

Is the release progression: MGA No-KNOX, ==> MH1 No-KNOX, ==> MH8 KNOX? :confused:
[Galaxy S 4 Q&A, Help & Troubleshooting] malybru:
Hi,

I am not 100% sure of all of this either.

I think MH5, MH8 and MGG are the same FW,different regions.

But they were all in the mix when the Knox fiasco kicked off.

So,I cannot give a definitive answer.

:)
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Its a shame Samsung aren't a little more open/transparent with their change lists:(:rolleyes:
[Galaxy S 4 Q&A, Help & Troubleshooting] SV3NNER:
So i updated my phone to I9505XXUDMHB and didn't hear about Knox yet. Rooted my phone and installed cwm, now my counter says 0x1 and root is not working good. If i flash a custom rom do i have full root acces?
[Galaxy S 4 Q&A, Help & Troubleshooting] scandiun:
MIUI should be working perfectly, since has everything of its own:

MIUI ROM 3.9.27
[Galaxy S 4 Q&A, Help & Troubleshooting] DjeMBeY:
XXUDMGG was the first one....

The letters changed from XXUB... to XXUD...

XXUB... - BOOTLOADER KNOX FREE

XXUD... - NEW KNOX BOOTLOADER with 0x0 / 0x1

Simple as that ;)

BTW, great idea. Big thanks for this thread! I'll keep an eye on it ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] unstandardized:
4. with the new knox bootloader you cannot install a custom kernel, insecure kernel, use custom recovery or root the device.

Ive seen some people able to root but it seems to be hit and miss

if I move to an AOSP/AOKP/GE Roms, would custom kernel/recovery and root work?
[Galaxy S 4 Q&A, Help & Troubleshooting] Bilokf:
Kernel/Fw Question

Hi guys,

My new S4 I9505 Lte have this ANDROID 4,2,2 kernel 3,4,0-1029328 Baseband I9505DVUBMG1 Build JDQ39.I9505XXUBMG4

I didn´t find a right match on the FW´s list .... can someone help me please?

Thank you
[Galaxy S 4 Q&A, Help & Troubleshooting] donalgodon:
Help you with what, exactly? What are you looking for?
[Galaxy S 4 Q&A, Help & Troubleshooting] samkuek:
There are a few XXUBMG4 firmware correspond to your phone at samsung update website for download, just choose your country, refer to attached picture
[Galaxy S 4 Q&A, Help & Troubleshooting] chickentuna:
I've read somewhere that you can install a 4.3 GE custom kernel on the leaked 4.3. If so, can anyone confirm that wifi and sound is working using the old non-knox bootloader?
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
There isn't a flashable version yet of the 4.3 leak without the new bootloader. It is being worked on

Follow here http://xdaforums.com/showthread.php?p=46191314

At the moment there isn't a way to get it into the phone successfully without the new bootloader
[Galaxy S 4 Q&A, Help & Troubleshooting] chickentuna:
There is one actually from that same thread. It's the repacked pre-rooted version which is bootloader free. I've also flashed the 4.3 leak excluding the new bootloader but sound and wifi was broken.

I just need to confirm that a 4.3 custom tw kernel fixes sound and wifi on an old bootloader, else I'll try it myself and report back
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
Good question. I've not seen anyone try and report yet but because the Knox stuff is bootloader level I'm guessing it's still likely to trip the flag u just won't have the root problems tw ROMs have been having....
[Galaxy S 4 Q&A, Help & Troubleshooting] bombaybadboy:
Haven't tried going back yet I like 4.3 but yes we are infected to with the knox pox :)
[Galaxy S 4 Q&A, Help & Troubleshooting] yvliew:
so that's means once I updated to firmware with knox bootloader there is no turning back. I can't flash customs rom that's without knox and google play edition roms. is that right? So the answer is not YES for all..... If i'm into flashing customs roms and google play edition I should stay away from KNOX right?
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Hi there,

Once you have updated to the new KNOX enabled bootloader and you want to carry on using KNOX features/container etc then DO NOT ROOT OR INSTALL A CUSTOM RECOVERY......You will void the KNOX warranty and render your device insecure (as samsung like to put it)and unable to use KNOX features.......However, if this does not worry you and you wish to use custom ROMS then you can by installing custom recovery and flash away.

OR Do NOT upgrade and carry on:cyclops:
[Galaxy S 4 Q&A, Help & Troubleshooting] yvliew:
I still don't understand. I mean someone said that if I updated to the latest bootloader, there is no way to downgrade to old bootloader that does not have knox. Hence I won't be able to flash google play edition rom which does not have knox bootloader. Flashing a rom that does not support knox bootloader will result a non bootable device.
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Yes...Upgrading will mean you cannot go back to the pre-knox bootloader....Dev's are finding ways around these thing's in order for users to use their roms WITHOUT updating the bootloader. Omega [MENTION=2576548]::indie::[/MENTION] will be releasing 4.3 TW without the need to upgrade your bootloader. There are users still on MGA (old bootloader) firmware using 4.3 This will only result in KNOX features not being included in the ROMS....I am sure there are other ROMs and dev's doing the same thing.

I am not sure what you real concern is if you do not upgrade....I do not know much about the GE rom so cannot comment.
[Galaxy S 4 Q&A, Help & Troubleshooting] jas-singh:
Please help.

Last night after upgrading my S4 i9500 to Stock 4.3 Indian version through Kies, I rooted my S4 with Cf-root without knowing what Knox is. Now after spending hours reading comments in Xda forums, I'm now realizing that it was a terrible mistake. Now my question is fairly simple here, what now I can do to make sure I get future updates through OTA since now my device status is showing custom, should I flash official Indian 4.3 version again in Odin to get my device status to official? I know I cant reset my warranty bit to zero....:(...any help would be highly appreciable...
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Yes....Flashing back official stock ROM should restore your OTA........:good:
[Galaxy S 4 Q&A, Help & Troubleshooting] jas-singh:
Thanks, Carl.
[Galaxy S 4 Q&A, Help & Troubleshooting] ongbac:
I think you're wrong mister. I flashed and got still 0x0 knox..
[Galaxy S 4 Q&A, Help & Troubleshooting] :
What did you flash?
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Hi....I hope I have understood you! If you go ahead with the OTA update that includes new knox bootloader and then ROOT OR install custom recovery you WILL trip your KNOX counter and VOID it 0x1.
[Galaxy S 4 Q&A, Help & Troubleshooting] Wuby986:
right but if i i'm not wrong there are 3 kind of bootloader.. make shure you have the older...

---------- Post added at 01:29 AM ---------- Previous post was at 01:22 AM ----------

i've understood it in the other way!!!
[Galaxy S 4 Q&A, Help & Troubleshooting] Vexxx:
I think the same. I made ota update to MH8 ( had new bootloader). After that flashed with odin 4.3 leak. And after that with odin official 4.3. Knox is still 0x0.
[Galaxy S 4 Q&A, Help & Troubleshooting] LoveMyNewTelephone:
He is not wrong, except for one thing. Even Root de-la-Vega will trip your Knox flag with the new bootloader from the official 4.3 ROM.

( it happend to me sadly :( )

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

Yes, you're comming from the leak.. Try flashing the official again now, and you will have Knox 0x1.
[Galaxy S 4 Q&A, Help & Troubleshooting] :
Don't make him loose his precious warranty. I'm annoyed that mine came back with new bootloader from use service center. But don't let him try to see if he will still have 0x0
[Galaxy S 4 Q&A, Help & Troubleshooting] LoveMyNewTelephone:
You're not understanding my message correctly. It is meant hypothetical. Of course he shouldn't try it. I know it WILL trip his Knox flag.
[Galaxy S 4 Q&A, Help & Troubleshooting] :
Then my apologies for misunderstanding your comment :)
[Galaxy S 4 Q&A, Help & Troubleshooting] mega00:
Sorry for reposting this, but I really want someone to discuss with...

I am one of the unlucky ones who upgraded to knox before knowing this...

But I do not concern about warranty, just one thing makes me annoying, did anyone also found that when booting with a custom kernel, there's a message on the first screen saying set warranty bit, and sometimes the device got stuck there. I have to long press the power button to restart the booting process. Sometimes the device restarts by itself due to unstable system, and I find the device stuck in boot screen for hours if I don't check it, making me unreachable by mobile.

Did anyone noticed this problem, and has a solution?
[Galaxy S 4 Q&A, Help & Troubleshooting] malybru:
Hi,

Correct me if I am wrong.

You have original bootloader (no knox)

You want to flash one of the new custom 4.3 ROMS where the dev has removed the knox bootloader.

Will you have the knox pox after that? (I doubt it)

You will have to ask in the thread.

Maybe you could let us know...

:)
[Galaxy S 4 Q&A, Help & Troubleshooting] Th3DON:
I have few questions.

At what condition, the new firmwares will write the KNOX values ? 0x0(Secure) or 0x1 (Insecure)

Is it based on rooting status and kernel installed while installing the new samsung firmware?

If yes, then why can't we unroot and go back to official old firmware and then try to install new firmwares ?

Is it ? Then it won't affect my 19500 right, i have a plan to upgrade to 4.3. Is it cause any issues. ?

So my device is 19500 rooted, i don't know my kernel status (custom or official)

I will post a screenshot, can someone says whether it's official or not.

Thanks and regards

AJ

noob in here.
[Galaxy S 4 Q&A, Help & Troubleshooting] Vexxx:
So I have now 4.3 DBT. When 4.3 for my region comes out we will see what happens to knox flag as I am going to flash it with odin. :)

Or what if I flash 4.3 leak again and then 4.3 for my region. Would that leave knox 0x0?
[Galaxy S 4 Q&A, Help & Troubleshooting] DjeMBeY:
NO..... CWM ROM's contain only Kernel+System+CSC , no other components included.. You're safe ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] jonatutu:
Sorry to ask maybe this is not the correct thread too. When you said feel free to flash any custom rom when I have the old bootloader, but some custom rom has a specify base. So if the custom rom is base off a new bootloader that means I would have flash a knov enable rom?
[Galaxy S 4 Q&A, Help & Troubleshooting] LoveMyNewTelephone:
If you have the DBT version, and have kept it totally original. You will probably be safe.

But if you have rooted it, and especially if you've used Xposed, changes are that you will trip the Knox flag.

DjeMBeY advises to de-root your phone before doing anything else.

Flashing the leak, solves nothing. The new bootloader is already on your phone.
[Galaxy S 4 Q&A, Help & Troubleshooting] timberwolf60:
A post above you had the answer for you.

Send via i9505 using TapatalkPro,

ROM: I9505XXUEMJ3_Vega

CSC/Modem: OLBEMJ2(STH)/XXUEMJ3

Kernel/recovery: Stock

SuperSU Pro 1.65, 64GB FAT32 Card
[Galaxy S 4 Q&A, Help & Troubleshooting] Vexxx:
Very confusing. Why flashing DBT again would trip the flag, as bootloader would not change, but flashing some other region would not?
[Galaxy S 4 Q&A, Help & Troubleshooting] LoveMyNewTelephone:
It is very confusing for sure. As far as I know, nobody really understands what is going on yet. Check out the opening post of this thread: http://xdaforums.com/showthread.php?t=2250824
[Galaxy S 4 Q&A, Help & Troubleshooting] Vexxx:
Ok, thank you. Seems like OP of this thread is not updated with latest info. :)
[Galaxy S 4 Q&A, Help & Troubleshooting] LoveMyNewTelephone:
Yes you are right. Maybe Hawke84 can change the OP so that it states that there is no known way still, to root the GS4 without tripping the Knox flag, once it is on the new bootloader (custom ROM's etc. are also out of the question, of course).

For a while it looked like the MEGA rom of DjeMBeY would be the answer (with root de-la-Vega), but Samsung seems to have patched this vulnerability.
[Galaxy S 4 Q&A, Help & Troubleshooting] MistahBungle:
This is also something we may end up being faced with in future - any/every workaround that's developed, Samsung patches future firmwares to make these workarounds ineffective, an 'arms race' type scenario if you will.

Edit to add - Obviously they've done that sort of thing in the past with patching vulnerabilities used to root/etc (some stuff that worked under GB didn't work under ICS/JB & so on), but the Knox thing (& devising ways to get around it) takes it to another level with regard to the warranty issue/the locking down of the phone/etc.
[Galaxy S 4 Q&A, Help & Troubleshooting] atmozfreak:
this one says odin mode

current binary Custom

system status Custom

knox kernel lock 0x0

knox warranty void 0x1

csb- config -lsb 0x30

write protection enable

emc burst mode enable

I now have 0x0 or 0x1?

i have now Original Stock ROM XXUEMJ5 (new 4.3)+ [i9505][CWM Advanced Edition] PhilZ Touch+ no root

this one says odin mode

before I'm in recovery mode, comes first three lines of text on blue recovery is booting.

red can be difficult reading is very small recovery not seandroid enforcing and yellow set warranty bit recovery

I have previously also those mega preflashed not root but I had problems and that stock 4.3 but did not then simply insisted that stock Stock RECOVERY and there Factory Data Reset or wipe data done and then reboot and then worked all stock XXUEMJ5

my question is can I trouble now

Installing EchoeRom_v5 + via philz Touch (cmw) and then wanam xposed
[Galaxy S 4 Q&A, Help & Troubleshooting] leijonasisu:
Yes your KNOX Warranty stayed at 0x0 but your Custom Firmware changed to 0x1. Which is what I explained.

One of them still changes. No matter what you flash SOMETHING will change. The point of what people are trying to explain is that there is no way to ever go back to 0x0 for everything after you flash something.

---------- Post added at 03:27 PM ---------- Previous post was at 03:24 PM ----------

This thread's purpose is not to be a reference for every custom rom that will trip the flag, or that has the KNOX Bootloader or not. You are misunderstanding the point of this thread. It is not this threads duty or the OP's or anyone else's here to provide an updated of list of every single thing you can or can't do.

It should be common knowledge (by now) that flashing ANYTHING

after

XXUD

WILL TRIP A FLAG.​
[Galaxy S 4 Q&A, Help & Troubleshooting] LoveMyNewTelephone:
I think you are missing my point. My point is that there is no currently known way to keep Knox at 0x0 with the new bootloader, and root it or use custom roms. That has nothing to do with any specific rom. It couldn't hurt to put that in the opening thread.
[Galaxy S 4 Q&A, Help & Troubleshooting] leijonasisu:
I was under the impression that there never was any way to keep it at 0x0, and that after you had flashed to it. Flashing anything afterwards would always trip the flag (except Root-de-la-vega but that would still trip your Custom Firmware flag to 0x1). Unless you are talking about something that's only a few days old or whatever that has changed in top of what we've already known for ages.
[Galaxy S 4 Q&A, Help & Troubleshooting] LoveMyNewTelephone:
Q1: Your Knox flag has been set to 0x1.

Q2: Custom roms work fine with the Knox flag set to 0x1.
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
Honestly not sure about i9500... I know the SOC has a totally different level of security. ..
[Galaxy S 4 Q&A, Help & Troubleshooting] atmozfreak:
Thx LoveMyNewTelephone

If I now in recovery mounts and storage

can I also format / system and what other still perform in that menu

I always do first Wipe Cache, Wipe Dalvik Cache, Wipe data / factory reset but what should I do anything for real videos, mp3, folders, etc to remove
[Galaxy S 4 Q&A, Help & Troubleshooting] LoveMyNewTelephone:
Those are really questions about the recovery, not about Knox. If you do a factory reset, all your personal data should be gone (except for all the data on the external SD card).
[Galaxy S 4 Q&A, Help & Troubleshooting] liviu993:
can i flash the new custom xxumj5 foxhound 3.0 via recovery and flash the new modem without getting the knox bootloader and flag ?
[Galaxy S 4 Q&A, Help & Troubleshooting] Doeyourthing:
Question about downgrade KNOX 0x1

I have a question. My Knox flag has been set to 0x1. And I did not use odin to install stock v4.3 XXUEMJ5 can i do a downgrade to v4.2.2?
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
Yes as long as the KNOX bootloader isn't included and ad long as u don't have KNOX already. If u do and u flash anything it will trip your flag. ..
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
Yes there is a version of 4.2.2 that had knox bootloader. Basically odin won't let u downgrade pre knox
[Galaxy S 4 Q&A, Help & Troubleshooting] jjnhl68:
Are you sure about this? I think you can't downgrade from new 4.3, becouse new bootloader is more secured than on for example MH8 4.2.2 with Knox.
[Galaxy S 4 Q&A, Help & Troubleshooting] hirodina:
That's not true, I flashed MEGA rom and I'm rooted with KNOX 0x0, secure boot status: Samsung and I even had binary status and the other thing official, untill I played with wanam a lot. Now I got "custom" but that's easily reversible by flashing stock rom.
[Galaxy S 4 Q&A, Help & Troubleshooting] Faith140291:
sorry guys, im in crisis. im on xxubmh1, how can i check if i have already flagged knox? (because i know that ubmh1 is the first with secured bootloader). thanks.
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Put your phone into download mode (power + volume down)......Compare yours with PIC in OP!

EDIT

XXUDMGG was the first one....

The letters changed from XXUB... to XXUD...

XXUB... - BOOTLOADER KNOX FREE

XXUD... - NEW KNOX BOOTLOADER with 0x0 / 0x1
[Galaxy S 4 Q&A, Help & Troubleshooting] Faith140291:
thanks for quick answer! i think its all ok, but i dont have the two lines of knox information, so i am safe? i have never flashed a firmware newer than mine.
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
If you have no mention of KNOX in download mode then YES you are OK...No KNOX bootloader......Lucky You! :)
[Galaxy S 4 Q&A, Help & Troubleshooting] Faith140291:
very very helpful! thanks man!!
[Galaxy S 4 Q&A, Help & Troubleshooting] vohom001:
this sucks. i rooted my s4 so i can get my hands on the 4.3 omega. but not realising that i have xxudmh8 firmware which is knox enabled.

i rooted my phone and then tried to install 4.3 and it didnt work so i played with the phone more and after 2 hours i read a post about knox and everything, so i went to check my status and its 0x1.

I dont care if Samsung steals the warranty away from me but all i want to do is flash omega 4.3 but i cant flash the modem. odin says its succesful but when i check it, there is nothing there..

So does anyone know a way i can flash omega 4.3?
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Answered in Omega i9505 thread:good:
[Galaxy S 4 Q&A, Help & Troubleshooting] Enfield bullet:
is anyone found solution to rest knox??? or any other solution???
[Galaxy S 4 Q&A, Help & Troubleshooting] blion:
Am getting my s4 next week so wanted get this sorted before i play with it. Assuming my s4 does not come with 4.3 then i can avoid getting the knox bootloader by mever updating samsung firmware (eg through kies or ota)? Is this correct or are there other ways i can get the knox bootloader? Also i assume its safe to update to any custom 4.3 roms if the developer says knox has been removed? Does this also apply to aosp, aokp etc?? Thx!!
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Nope......and probably won,t be any time soon:(

---------- Post added at 12:52 PM ---------- Previous post was at 12:43 PM ----------

When it arrives check the firmware it has installed....some 4.2.2 firmware has KNOX boot loader. Be very careful if you wish to upgrade with custom roms as most will need a custom recovery installed....and.....if you have a KNOX boot loader......flashing a custom recovery will trip your KNOX void 0x1........It is currently a bl**dy nightmare and all too many dive in with flashing custom stuff BEFORE they realize what they have done. BE CAREFUL and research some more before hand.
[Galaxy S 4 Q&A, Help & Troubleshooting] volemangler:
I9505 camera and keyboard broken in XXUEMJ5

I have KNOX WARRANTY VOID 0x1 on my i9505, and after flashing the latest official XXUEMJ5 4.3 firmware ( upgrading from a pre-rooted 4.2.x) and using CF Auto Root, I find that the video recording and Samsung Keyboard don't work. Worse than that, I find that I can't reflash the same firmware file (or the previous one I'd used) in Odin as it fails each time. Nor can I install zips from recovery as they all now come back with signature errors.

I think I understand the Knox flagging system and its implications, but why I can't re-flash the firmware in Odin or install from SD card zip. Help please!!
[Galaxy S 4 Q&A, Help & Troubleshooting] philip2000:
Hi mate,

I'm on official 4.3 DBT with new bootloader and tripped knox flag. I don't gave a rat's *** about the warranty. All I want is to load a custom version of 4.2.2, but don't seem to be able to. Was/Is your situation the same as mine before you successfully got MEGA rom on there, or do you still have the old bootloader. I'm getting the impression that Knox is gatekeeper over every attempt to do something dodgy and steps in to stop these "attacks" of my attempts to root/load a customer rom, etc.

Please let me know.

Thanks

Philip
[Galaxy S 4 Q&A, Help & Troubleshooting] harlum69:
nice touch mate, seen so many questions about this.
[Galaxy S 4 Q&A, Help & Troubleshooting] hirodina:
It has been discovered that 4.3 will trip KNOX with MEGA rom... I'm on knox-enabled bootloader from 4.2.2 and I've rooted using MEGA rom. It worked like a charm, no problem with odin or with rooting. Just checked download mod and I still got knox 0x0, binary official and status: CUSTOM (which is reversible by flashing stock rom). I had problems with titanium backup. I restored everything with data and almost every app was force closing or "resetting" (every time I opened it, it gave me "welcome" screen etc. again). Lately it's been stated by developers of Titanium Backup that there is problem with knox enabled firmware (because of SELinux: Enforcing) and they are working on solution. I solved this by deleting apps and then batch restoring only apps without data. And then I had to set everything again in Foldermount etc... so yeah...few hours setting things up because of restoring without data. System was unstable and gave force closes etc. But I found out it was because of restored apps.. mostly google apps.. now everything works like a charm. Root apps work correctly and system is smooth. So for now I' m happy... I got what I wanted...root..and 0x0. Because of wanam exposed I don't even need custom rom, I enable everything trough modules of wanam. So basically I build custom rom from inside of stock (MEGA) rom. Bootloaders in 4.3 are again...safer from 4.2.2 so it's getting worse only :\ I'm thinking of buying Nexus 5 but 32gb is small for me, without microSD (and smaller usable display because of onscreen buttons). But Samsung really pisses me off ! And I can't buy Oppo in my country.
[Galaxy S 4 Q&A, Help & Troubleshooting] Scruffyblake:
This is Excellent news - I was going to see if anyone had tried this yet in Australia. :laugh::good:

Did you actually have a warranty repair request, or just pose the question to them?