Develop Bugs

[Q] "Knox" firmware and the m919 version?

I have read (<here> and <here>)
about new firmware versions that will not allow resetting the counter (warranty flag) to initial conditions when restoring to stock after after unlocking or rooting.
If the phone developed a hardware problem, warranty repair could be denied.
The firmware version "MGG" and beyond are reported to have this problem.
Questions:
Does this also apply to the m919 T-Mobile version?
Has anybody seen it on an m919?
Is it going out with an OTA update?
Or is MGG specific to the i9505?
I am shopping for a GS4 m919, and I want confirm that it has the "pre-MGG" firmware version before purchase.
Questions:
Is the ID contained in the "Baseband" ID string in the phone information?
Are there different identifier strings used on the M919?

The T-Mobile S4 has not received the KNOX Bootloader, it will most likely come with the 4.3 update. If anyone is on stock, I would recommend you guys disable OTA updates as you may get automatically updated to 4.3 with the KNOX bootloader.

for once...im dreading an update from tmobile

If I've already rooted and installed a custom recovery (Clockwork Mod), and nothing else, does anyone know if the 4.3 update with KNOX will still be usuable? In other words, will the phone still get an automatic OTA update and will that update install correctly?
Sent from my SGH-M919 using XDA Premium 4 mobile app

DigitalHeretic said:
If I've already rooted and installed a custom recovery (Clockwork Mod), and nothing else, does anyone know if the 4.3 update with KNOX will still be usuable? In other words, will the phone still get an automatic OTA update and will that update install correctly?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It wont let you get the update it will pop a box up saying unable to uodate your device has been modified. . Try to check for an uodate youll see what im talking about... I went back to stock just to see if there was anything for updates which there wasnt andbwent to reroot and installed su abd it didn't flash correctly thru odin said to heck with it till the am checked for an update for giggles in the am and wouldn't even check
Sent from my SGH-M919 using Tapatalk

i'm glad I read this thread. i was going to wait until i tried the stock 4.3 update before deciding to root and install custom ROMs. With KNOX coming, I'm just going to root ASAP. I like PA on my Nexus4, so I'll probably go with that for my S4.

So you guys are saying the new update with "knox" won't allow you to reset the counter and only that or will it stop you from completely rooting and installing custom roms?
Sent from my SGH-M919 using Tapatalk

futty said:
So you guys are saying the new update with "knox" won't allow you to reset the counter and only that or will it stop you from completely rooting and installing custom roms?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Let me clarify some things. The KNOX processes and functions are already on the stock ROM, most devs remove them, though. So many of you with custom ROMs haven't seen anything related to KNOX.
What the new T-Mobile update (when it gets pushed out) is most likely to come with is a "KNOX Bootloader" which will introduce a thing called "KNOX Flag" which is similar to the old counter we're all used to. This is the counter that @Chainfire was successful in resetting with his app, Triangle Away.
Unfortunately, @Chainfire or anyone else for that matter, has not been able to reset the KNOX flag.
The KNOX flags is this:
0x0 = You have not tripped the KNOX flag.
0x1 = You have tripped the KNOX flag.
Again, once you trip that flag, rooting, flashing a custom recovery, etc.. there is NO way to reset it as of now. And any KNOX functionality on your phone will not work. But the worst part is Samsung will refuse warranty on your device if they see a 0x1 in your bootloader.
Another thing.. on the new bootloader, if you try to downgrade, even with an official Samsung firmware, it will fail and you will trip the KNOX flag.
So once you're on the new bootloader, there's no going back.
There's been speculation that there's an eFuse at play here.
Anyway, this is the reason why I am suggesting you all disable OTA updates and wait until a ROM is built without the new bootloader and all the functions (Wifi, MMS, etc.) are working.

mgbotoe said:
for once...im dreading an update from tmobile
Click to expand...
Click to collapse
Hey, its sammy we have to blame for this one :/ Not T-Mobile lol.
PSSSST! Don't let them know you are dreading it, or they might put it off longer xD
As to the OP.
The KNOX Warranty counter is rumored to be what is called an eFUSE. If this is true, then resetting the KNOX warranty counter will be impossible without taking apart your phone and replacing that specific eFUSE.
However, there are rumors that some root methods DO NOT trip this new counter. Is that good? Yes, is that bad? Yes. For those users who like stock kernels and just wanna root, this is okay for them. But for 99.999999 percent of us who love to flash new kernels and get more from our devices, then it trips the counter.
I personally congratulate Samsung as well as hate them at the same time for this. I congratulate them because what seems to be happening a lot is users flash a million and 2 things to their device having not one single clue what they are doing, thus bricking their 500+ dollar smartphone then claiming it as a warranty claim and getting another one. I also feel they are trying to flex their ego muscles too -.-
I also believe that if you have insurance, this does not apply. It is only for warranty claims. Which like you stated OP, it only means Samsung can choose to deny to repair or replace it. I have read a lot of thread before where users tripped the older binary flash counter, and still were given a new device. I honestly don't know how this is going to play out for the lot of us. For me, my warranty is over in a few months anyhow so i don't really care. But its still kind of a dickish thing Samsung is doing.
I am also hoping that we can extract the contents of the new update and keep our older bootloaders and create a flashable zip with the new update stuff and have it still work. I know there were some issues with the international S4 4.3 update but im not sure if it was entirely caused by the bootloader.

Exel said:
Anyway, this is the reason why I am suggesting you all disable OTA updates and wait until a ROM is built without the new bootloader and all the functions (Wifi, MMS, etc.) are working.
Click to expand...
Click to collapse
Where do you disable OTA updates on a stock S4?
Hitting "Software Update" takes me to a Boolean"Update Now" popup with no other option than choosing Yes, No or Wifi. No option to defeat future updates is offered.
Going into developer mode doesn't seem to add any pertinent options either (correct me if I'm wrong).
Clearly, Samsung doesn't want us to be able to disable updates unless or until we root, which I'm doing this weekend on the basis of this thread.

Reignogleph MMXI said:
Where do you disable OTA updates on a stock S4?
Hitting "Software Update" takes me to a Boolean"Update Now" popup with no other option than choosing Yes, No or Wifi. No option to defeat future updates is offered.
Going into developer mode doesn't seem to add any pertinent options either (correct me if I'm wrong).
Clearly, Samsung doesn't want us to be able to disable updates unless or until we root, which I'm doing this weekend on the basis of this thread.
Click to expand...
Click to collapse
You indeed have to root to disable OTA updates.

Once the update hits im going to extract the system.img to get all the files.
Then explore where all of the Knox crap is and get rid of it.
I know I want be alone in doing this...all who develop for the S4 will be on top of it.
Someone will figure out a way to get around this Knox BS...
Sent from a Insane S4
SICK MADE DEVELOPMENT

alloycowboy said:
Once the update hits im going to extract the system.img to get all the files.
Then explore where all of the Knox crap is and get rid of it.
I know I want be alone in doing this...all who develop for the S4 will be on top of it.
Someone will figure out a way to get around this Knox BS...
Sent from a Insane S4
SICK MADE DEVELOPMENT
Click to expand...
Click to collapse
thats fine and dandy for us with existing phones.. I already removed all the knox crap from my phone, and will update but not kernel and do the same..
But what about all future phones.. If indeed the kernel is locked with knox and there is no way to remove it we are screwed for new phones coming out.

lgkahn said:
thats fine and dandy for us with existing phones.. I already removed all the know crap from my phone, and will update but not kernel and do the same..
But what about all future phones.. If indeed the kernel is locked with knox and there is no way to remove it we are screwed for new phones coming out.
Click to expand...
Click to collapse
I agree. If thats the case....then alot of people will ditch Samsung.
But I have a feeling we will figure out Knox. Its man made so it can be hacked. Who when and how is the question.
Sent from a Insane S4
SICK MADE DEVELOPMENT

that's also why I paid 400 bucks for a T-Mobile sgs 4 and I am using it on at&t... I refuse to pay or support a phone with a locked bootloader.. matter of principle...i would ditch att if T-Mobile had decent service in my area.
Sent from my SGH-M919 using Tapatalk 2

Clarifications about KNOX and the S3

AFAIK nobody has asked anything about KNOX on the T999, so I have a few things I want to know before updating my phone to 4.3.
I bought my phone off-contract at full price and its flash counter has already been incremented many times from rooting, so I obviously don't care about setting the "KNOX warranty void" flag either, nor the enterprise-grade security features KNOX provides.
However, there is a rumor that once the KNOX warranty void flag is set to 0x1 you can't upgrade the ROM anymore, not even via Odin. Is this actually true? I know you can't OTA unless you're stock, but I don't care about OTA since I'd just upgrade via Odin anyways. But the fact you can't even upgrade via Odin seems a bit far-fetched.
Another variant of this rumor that seems more believable is that updating to a KNOX-enabled ROM also updates the bootloader to a KNOX-enabled variant, and that you can't upgrade to new KNOX-enabled ROMs if you decide to downgrade to a non-KNOX ROM after the bootloader has been updated. But if I never downgrade, can I continue to install updates, assuming Samsung releases ROMs for the S3 after 4.3?
Can anyone shed some light on this?

I somehow can't trust the first one. However the second one sounds more plausible. Anyway doc Holliday has removed KNOX from the most recent leaked Stock Rom. So this question becomes moot really.

Perseus71 said:
I somehow can't trust the first one.
Click to expand...
Click to collapse
Which is exactly why I asked this. I just wanted some more opinion.
Perseus71 said:
Anyway doc Holliday has removed KNOX from the most recent leaked Stock Rom.
Click to expand...
Click to collapse
And does this also mean that the bootloader isn't KNOX-enabled?

jim45 said:
Which is exactly why I asked this. I just wanted some more opinion.
And does this also mean that the bootloader isn't KNOX-enabled?
Click to expand...
Click to collapse
I don't think so. I flashed that Leak to test out the features. Afterwards flashed back my regular AOSP Rom.
NOTE - With the Leak, some reported that the Bootloader didn't get updated. I explicitly asked as well. If you are concerned with Knox'd Bootloader, you can Flash back UVDMD5 Bootloader too!

Here's what I know so far.
First, we do not have to worry about the Knox counter. One of my sources sent me a pic of their download mode and it was not there.
Second, I have reliable doubts that our official release will NOT include Knox. It's only included now for ease of using the same builds across multiple devices during internal testing.
Third, the bootloader is not included in any of the leaks. I do have a copy of it and have been considering releasing a recovery flashable firmware update, but haven't decided yet if I want to do this.
One of my sources ran into a problem at one point and soft bricked. Samsung simply connected remotely and flashed the firmware via Odin.
As for not being able to downgrade or flash certain things, I do not think this is the case at all. If you do something Knox doesn't like, it will lock down the secure containers it uses and you will not be able to regain access. I do not belie e it will restrict you from flashing something else, old or new, firmware or Rom, etc.
There is still a lot I do not know about it, but the information is out there. I stopped putting time into it when I found we probably won't need to worry about it anyway.
A quick Google search will net you more info, but if you really want an education on it I'd suggest visiting the S4 and Note3 forums. S4 users have been dealing with Knox longer than anyone, and the Note3 is the first device to ship with it fully implemented.
Sent from my SGH-T999 using Tapatalk

[FAQ] KNOX and you

[SIZE=+1]There seems to be a lot of confusion and misunderstanding circling the forums with regards to Knox and the 4.3 OTA.
This is an attempt to clear things up[/SIZE]
UPDATE: It seems that people can find this thread, but are unable to actually READ the information presented. The most important note here is that if you are on 4.3 firmware, you can flash ANY rom you like. No, you are not tied down or locked into stock only or 4.3 roms only. AOSP roms will work fine as well. Now scroll down and READ EVERYTHING IN THIS FIRST POST.
What is Knox? Knox is both a firmware and a software component. The OS has Knox apps, and the MK3 bootloader has a Knox component too. Having Knox apps does not necessarily mean you have the Knox bootloader, or vice-versa.
How does Knox work? Because Knox is both in the OS (apps) and in the firmware (bootloader) it works in two ways. The OS components prevent attempts to obtain root access and make rooting with these Knox apps a pain in the butt. Fortunately they can be removed. In the firmware component (bootloader), Knox works to prevent the flashing of custom kernels and recoveries. If you flash a custom rom or custom recovery WHILE on the Knox bootloader, your Knox flag will be tripped and your Warranty Bit will go from 0x0 to 0x1. The Knox bootloader cannot be downgraded to, say, the MD4 bootloader because of special protections built into it. If you attempt to downgrade it, your phone will instantly brick.
Can I get root on the Knox-enabled update? Yes. For those of us who DID NOT take the official OTA and DO NOT have the Knox bootloader, we can get root on 4.3 by injecting it and removing the Knox apps. For those WITH the Knox bootloader, you will need to wait until a full stock MK3 tar is available, which we can then use to make an Odin-flashable MK3 stock rom with root injected using the de-la-vega root method.
Can I downgrade while on 4.3? You can flash roms no matter what Android version they are. That is perfectly fine. But you cannot downgrade the bootloader if you have the Knox bootloader, or else it will cause your bootloader to become corrupted and give you a fancy paperweight. Again, for those who DO NOT have the Knox bootloader, you needn't worry about this/downgrading firmware since the Knox bootloader is what prevents you from doing this. Downgrading your bootloader includes: attempting to flash full stock tar of software versions < MK3, etc.
How can I tell if I've got the Knox bootloader?
Boot into download mode (through custom reboot menu, or by powering off then holding Power+Home+VolumeDown and then VolUp when prompted). If you see a line that starts with the following, then you've got the Knox bootloader. I will insert a picture showing how it actually looks soon
Warranty Bit:
Click to expand...
Click to collapse
[SIZE=+1]READ THIS TOO: http://forum.xda-developers.com/showthread.php?t=1788313
It's for the Verizon S3, but it applies to all the carrier 4.3 updates[/SIZE]
I will add to this as more questions come up
I hope the above helps to clear up some confusion. Ask questions if you are still concerned and I will do my best to answer them.

is there any way to make this a sticky @kennyglass123

This is great information man!
http://i.imgur.com/qrByUGN.jpg

[Q] For now, once you have Knox you'll always have knox? What's the possibility of removing Knox?

elephant007 said:
[Q] For now, once you have Knox you'll always have knox? What's the possibility of removing Knox?
Click to expand...
Click to collapse
as of right now none.

elephant007 said:
[Q] For now, once you have Knox you'll always have knox? What's the possibility of removing Knox?
Click to expand...
Click to collapse
No way to remove bootloader Knox ATM.

I've seen several posts mention "tripping KNOX" or "voiding KNOX." What does that mean, exactly, regarding rooting a phone? Does it just mean it voids the warranty if you need to get support from Samsung/Sprint? Or are there other adverse effects?

Mostly just a visible warranty void.

Samsung bought crapple disease. So sad, but its my excuse to buy a nexus.
Sent from my SPH-L710 using xda app-developers app

As said above, a voided Knox is mostly just a highly visible warranty void. Your local Sprint store may or may not care, or the specific Samsung rep that you deal with may not care, but it's easier just to not have to deal with it to begin with.

Does this mean there is already a touchwiz 4.3 ROM we can flash or do we still have to wait?
Sent from my SPH-L710 using Tapatalk

The biggest thing here is the fact that there is no full tar file to restore. So even if you do not care about knox or warranty. If something goes wrong with a flash or anything else you can't use an older tar file let's say MD4 or LJ7 or anything because you will end up with a brick. There is nothing to use to ODIN restore your device. Once you go 4.3 with Knox you have to stay 4.3 and even if you wanted to stay 4.3 and wanted to restore that there is no tar file at this time.
Have a great day!

I have a question I think we talked a bit about the problems the knox bootloader brings into the system. My question is the opposite what does it fix / change?
Im thinking along the lines of somebody modding the update so an old bootloader would be with the new rom would that be an issue? I think i remember hearing something about wifi being the problem but any clarification would be nice.

docnas said:
I have a question I think we talked a bit about the problems the knox bootloader brings into the system. My question is the opposite what does it fix / change?
Im thinking along the lines of somebody modding the update so an old bootloader would be with the new rom would that be an issue? I think i remember hearing something about wifi being the problem but any clarification would be nice.
Click to expand...
Click to collapse
Late to the party. CNexus already has a update cooking.
Sent from my SPH-L710 using Tapatalk

the question im trying to ask is what do we lose if we use the old bootloader? any functionality? (besides the knox security bull$hit)

docnas said:
the question im trying to ask is what do we lose if we use the old bootloader? any functionality? (besides the knox security bull$hit)
Click to expand...
Click to collapse
Right now, wifi is broken with the old bootloader and 4.3 rom...happened on the other devices too (tmo s3 and sprint s4)
But there is a fix: flash at&t kernel. But it messes up screen rotation. So i'm trying to come up with another fix that will let wifi turn on properly and let screen rotation work properly too

You = rock. Or some other awesome thing.
Sent from my SPH-L710 using xda app-developers app

CNexus said:
Right now, wifi is broken with the old bootloader and 4.3 rom...happened on the other devices too (tmo s3 and sprint s4)
But there is a fix: flash at&t kernel. But it messes up screen rotation. So i'm trying to come up with another fix that will let wifi turn on properly and let screen rotation work properly too
Click to expand...
Click to collapse
So is this Knox a Sprint thing, or a Samsung thing?
I can understand the reasoning for Knox(money) but, dang, I guess it's a dog eat dog world out there.
This doesn't affect CyanogenMod does it? I'm scared...
edit... I remember reading about a brick api or command, I never executed it, sounds nasty, is this what they use to brick peoples phones if they try to "hack" it?

Edge-Case said:
So is this Knox a Sprint thing, or a Samsung thing?
I can understand the reasoning for Knox(money) but, dang, I guess it's a dog eat dog world out there.
This doesn't affect CyanogenMod does it? I'm scared...
edit... I remember reading about a brick api or command, I never executed it, sounds nasty, is this what they use to brick peoples phones if they try to "hack" it?
Click to expand...
Click to collapse
This would be a we-can't-update-the-bootloader thing lol. And we can't do that because it has Knox, which is Samsung's doing
This shouldn't affect any AOSP roms because it uses a different kernel and builds its own WiFi libs

docnas said:
the question im trying to ask is what do we lose if we use the old bootloader? any functionality? (besides the knox security bull$hit)
Click to expand...
Click to collapse
From what I've read Knox is Samsung's attempt to provide strong security to their phones for the enterprise customers. As you can imagine, allowing system level access to files can be used to get around a lot of security measures that IT people would like to enforce in their client's devices. It makes sense at the enterprise level, but it's a pain for anyone who want's to mod their phone.
So I think the answer to your question is, unless you are using your phone in a locked down corporate environment then there really is no advantage to Knox. Too bad it can't be turned off, at least not officially.

[Q] just received replacement S4.. questions regarding knox

Phone was lost, just got replacement this morning.
My last S4 had been rooted running custom firmware for months w/o issue.
Read through a bunch of threads, ranging from the opinion that the bootloader change + knox wont be a big issue to the sky is falling.
Is it recommended to root my phone at this time, I do have JUMP and would be replacing it once something better comes out? The phone is running 4.2.2, caught it trying to update to already.
Thanks.. I know this may seem redundant but haven't been active on these boards since I got my CFW going. Not seeking help in flashing or anything.. just advice

skrewler said:
Phone was lost, just got replacement this morning.
My last S4 had been rooted running custom firmware for months w/o issue.
Read through a bunch of threads, ranging from the opinion that the bootloader change + knox wont be a big issue to the sky is falling.
Is it recommended to root my phone at this time, I do have JUMP and would be replacing it once something better comes out? The phone is running 4.2.2, caught it trying to update to already.
Thanks.. I know this may seem redundant but haven't been active on these boards since I got my CFW going. Not seeking help in flashing or anything.. just advice
Click to expand...
Click to collapse
Up to you. If the stock rom is bearable and you wanna run the 4.3 stock rom then by all means, go for it.

skrewler said:
Phone was lost, just got replacement this morning.
My last S4 had been rooted running custom firmware for months w/o issue.
Read through a bunch of threads, ranging from the opinion that the bootloader change + knox wont be a big issue to the sky is falling.
Is it recommended to root my phone at this time, I do have JUMP and would be replacing it once something better comes out? The phone is running 4.2.2, caught it trying to update to already.
Thanks.. I know this may seem redundant but haven't been active on these boards since I got my CFW going. Not seeking help in flashing or anything.. just advice
Click to expand...
Click to collapse
Being that your'e using the T-Mobile M919, the whole KNOX bootloader situation doesn't pertain to you as long as you're sure you're on 4.2.2. Root it, flash it, theme it with Hello Kitty... whatever, it doesn't matter; you can still revert back to stock and reset any tripped counters. 4.3 is when the problems begin and the KNOX counter is implemented and can't be reset.

lordcheeto03 said:
Being that your'e using the T-Mobile M919, the whole KNOX bootloader situation doesn't pertain to you as long as you're sure you're on 4.2.2. Root it, flash it, theme it with Hello Kitty... whatever, it doesn't matter; you can still revert back to stock and reset any tripped counters. 4.3 is when the problems begin and the KNOX counter is implemented and can't be reset.
Click to expand...
Click to collapse
I second this.
SO LONG AS YOU ARE ON 4.2.2
- You can root flash do whatever, theme with hello kitty or barbie xD like lordcheeto said or keep it stock
- Install recovery and flash away.
- Will always be able to revert back to 100 percent stock
TAKE 4.3 UPDATE
- I think you are still able to root it without tripping knox counter. Can't remember the last status of that was. But as long as you root it without a custom recovery, i think you are ok. From what i can remember, the bootloader checks the recovery status and trips the knox counter based off the recovery that is on the device. If its different then stock, it trips. But double check with Google about this first.
- If you trip knox counter, you will NEVER (as of now and possibly forever) get it back to zero.

Rooting with safe root won't trip knox and also disables it. But recoveries, kernels, roms, etc will trip the flag
Sent from my SGH-M919 using Tapatalk

Root it with chain fire and never look back.
You're on 4.22, so you're golden. Just flash a rooted stock ROM that's on 4.3 and you'll avoid Knox.
I'm running 4.4.2 and never seen this Knox stuff.
Sent from my SGH-M919 using XDA Premium 4 mobile app

elesbb said:
- I think you are still able to root it without tripping knox counter. Can't remember the last status of that was. But as long as you root it without a custom recovery, i think you are ok.
Click to expand...
Click to collapse
ShinySide said:
Rooting with safe root won't trip knox and also disables it. But recoveries, kernels, roms, etc will trip the flag
Click to expand...
Click to collapse
Correct. I've rooted my my second GS4G on 4.3 MK2 and it did not trip the KNOX counter. If you're still on 4.2.2 MDL, then there is no need to update your bootloader. Simply flash ROMs through recovery and flash the 4.3 modem. You will have the goodness of 4.3 on KNOX-less 4.2.2 bootloader. :highfive:

Samsung Note 2 LTE (N7105) Stuck at Samsung logo after 4.3 to 4.1.1 downgrade

Hi guys,
I'm new to this forum and I am a beginner so I must apologise in advance for my ignorance.
I was looking to downgrade my Note 2 from 4.3 to 4.1.1 to unlock it, and I found this http://forum.xda-developers.com/showthread.php?t=2612485
I followed the instructions properly. I rooted my 4.3 with CF auto root, and then I tried to flash the 4.1.1 firmware onto my phone.
Now it is stuck at the boot screen, and I'm so shocked because I did everything correctly.
I can still get to "ODIN Mode" by holding volume down, home and power, and it says:
Current Binary: Custom
System Status: Custom
Knox warranty void: 1
What have I done wrong?
Thank you.

nigzy said:
Hi guys,
I'm new to this forum and I am a beginner so I must apologise in advance for my ignorance.
I was looking to downgrade my Note 2 from 4.3 to 4.1.1 to unlock it, and I found this http://forum.xda-developers.com/showthread.php?t=2612485
I followed the instructions properly. I rooted my 4.3 with CF auto root, and then I tried to flash the 4.1.1 firmware onto my phone.
Now it is stuck at the boot screen, and I'm so shocked because I did everything correctly.
I can still get to "ODIN Mode" by holding volume down, home and power, and it says:
Current Binary: Custom
System Status: Custom
Knox warranty void: 1
What have I done wrong?
Thank you.
Click to expand...
Click to collapse
On the first post that you've followed says that "It may or may not work for you" so you only have 50% chance. AFAIK 4.3 firmware has Knox already. Did you flash the 4.1.1 successfully? If yes, maybe Knox is restricting it from booting. If not successfull, maybe the files of your device have been messed up. So you have to flash again your previous rom using Odin. Why don't you try it. Since you already tripped your Knox to 1. Meaning you've already voided your warranty.

asin_punk said:
On the first post that you've followed says that "It may or may not work for you" so you only have 50% chance. AFAIK 4.3 firmware has Knox already. Did you flash the 4.1.1 successfully? If yes, maybe Knox is restricting it from booting. If not successfull, maybe the files of your device have been messed up. So you have to flash again your previous rom using Odin. Why don't you try it. Since you already tripped your Knox to 1. Meaning you've already voided your warranty.
Click to expand...
Click to collapse
Thank you for your reply I flashed the 4.1.1 successfully, but it just wouldn't boot. 4.3 does have Knox but I disabled it when I rooted it.
I flashed 4.3 again, and to my surprise it worked, I'm really grateful mate thanks a lot
What does it mean for me now that I've voided my warranty? I can't update it anymore with Kies?

nigzy said:
Thank you for your reply I flashed the 4.1.1 successfully, but it just wouldn't boot. 4.3 does have Knox but I disabled it when I rooted it.
I flashed 4.3 again, and to my surprise it worked, I'm really grateful mate thanks a lot
What does it mean for me now that I've voided my warranty? I can't update it anymore with Kies?
Click to expand...
Click to collapse
Great! AFAIK you can still update with kies. But you have to unroot your device first using supersu. There are a lot of rumors around there. Some said yes and some says no. Haven't tried it myself before actually. I always use odin. Since you got back to 4.3, what's your next plan? Hehehe.

asin_punk said:
Great! AFAIK you can still update with kies. But you have to unroot your device first using supersu. There are a lot of rumors around there. Some said yes and some says no. Haven't tried it myself before actually. I always use odin. Since you got back to 4.3, what's your next plan? Hehehe.
Click to expand...
Click to collapse
Ok got it, thanks man. I'll probably use Odin from now on too.
Is there currently no way to restore the Knox count? The phone doesn't have warranty anyway but if I can't use Knox enabled software in the future I guess it will be difficult
Since I'm back on 4.3 I'm looking to see if I can unlock my phone somehow, I'm looking to study abroad soon and I need it done, and I can't do it through the official carrier so I'm a bit desperate. What do you reckon I should do?
In the tutorial that I mentioned in my first post, he didn't say that I should factory reset the phone. Shall I try downgrading again and then do the factory reset? Will it help at all? Like it says here: http://www.droidviews.com/how-to-downgrade-firmware-on-samsung-galaxy-devices/2/
Cheers

nigzy said:
Ok got it, thanks man. I'll probably use Odin from now on too.
Is there currently no way to restore the Knox count? The phone doesn't have warranty anyway but if I can't use Knox enabled software in the future I guess it will be difficult
Since I'm back on 4.3 I'm looking to see if I can unlock my phone somehow, I'm looking to study abroad soon and I need it done, and I can't do it through the official carrier so I'm a bit desperate. What do you reckon I should do?
In the tutorial that I mentioned in my first post, he didn't say that I should factory reset the phone. Shall I try downgrading again and then do the factory reset? Will it help at all? Like it says here: http://www.droidviews.com/how-to-downgrade-firmware-on-samsung-galaxy-devices/2/
Cheers
Click to expand...
Click to collapse
Downgrading from Knox-enabled-bootloader to Non-Knoxed-Bootloader may brick your device. Your lucky that it didn't happen on your first try. From what carrier are you locked on? Since your on 4.3 Knox bootloader, maybe you can try other custom rom that depends on your current bootloader. Or try to upgrade to Official 4.4.2 from sammobile then install PhilzTouchRecovery 6.26.6 then root it, then find a custom rom that fits your device and can also unlock your device. Maybe you can ask Dr. Ketan if he has a rom like in this thread http://forum.xda-developers.com/showthread.php?t=2472270 for your device. And I think he can help you with all of your concerns. Cheers!