I restored my knox warranty!!!!!!!!!!

[96DANGER96]

So, I was on CarbonKitkat rom by @F4k and I wanted to return on original samsung firmware.
I flashed that with odin:

I9195XXUAMF6_I9195VFGAMF2_I9195XXUAMF6_HOME.tar.md5

but won't boot, so I reflashed it and got an error:

image size too large!! W:1000, H:1920
display image fail
SECURE FAIL: KERNEL

So, now in download mode I saw that Knox Warranty Void flag was 0xfffffffc (or similar, i have not counted how many 'f' were there)

I searched on google and founded that i get that error on boot because I did a downgrade, so I can get all functional by flashing a newer firmware, so I flashed:

I9195XXUBNA2_I9195VFGBNA4_I9195XXUBNA2_HOME.tar.md5

And I got:

Phone boot.
Working wifi.
Knox warranty void 0x1 on Download Mode, but not yellow string on boot, What does mean?!

 

[Levent2101]

0x1 means you triggered knox.
0x0 means you didnt trigged knox
0xFFFFFFF probably means possible downgraded device/ not acceptable value.
so in the end nothing is changed.

 

[rrgrrg]

So, I was on CarbonKitkat rom by @F4k and I wanted to return on original samsung firmware.
I flashed that with odin:
I9195XXUAMF6_I9195VFGAMF2_I9195XXUAMF6_HOME.tar.md5
but won't boot, so I reflashed it and got an error:
image size too large!! W:1000, H:1920
display image fail
SECURE FAIL: KERNEL
So, now in download mode I saw that Knox Warranty Void flag was 0xfffffffc (or similar, i have not counted how many 'f' were there)
I searched on google and founded that i get that error on boot because I did a downgrade, so I can get all functional by flashing a newer firmware, so I flashed:
I9195XXUBNA2_I9195VFGBNA4_I9195XXUBNA2_HOME.tar.md5
And I got:
Phone boot.
Working wifi.
Knox warranty void 0x1 on Download Mode, but not yellow string on boot, What does mean?!

come on !!!! knox will never be back to 0x0 when its triggered ..i have tripped it I DONT CARE !!!

 

[96DANGER96]

0x1 means you triggered knox.
0x0 means you didnt trigged knox
0xFFFFFFF probably means possible downgraded device/ not acceptable value.
so in the end nothing is changed.

Thanks man.

But why the yellow string on boot doesn't appear now?

 

[rrgrrg]

Thanks man.

But why the yellow string on boot doesn't appear now?

The yellow string appears on 2 situations
-booting with custom kernel
-booting with custom recovery
-downgraded and failed

Sent from my GT-I9192 using XDA Premium 4 mobile app

 

[Razvan]

The yellow string appears on 2 situations
-booting with custom kernel
-booting with custom recovery
-downgraded and failed

How can i remove that yellow string to not apear on boot?
My configuration is:

AP: BNB3
CSC:BNA2
RF: 2014.04.14
HW: MP0.800

I'm rooted and custom kernel from @arco68 thread: http://forum.xda-developers.com/showthread.php?t=2364980

 

[Scorpiopt]

come on !!!! knox will never be back to 0x0 when its triggered ..i have tripped it I DONT CARE !!!

sorry if it seems a dumb question but why everyone thinks that knox will never be reversible

 

[Razvan]

sorry if it seems a dumb question but why everyone thinks that knox will never be reversible

Do you have some info's and you want to share? Do it!

 

[Scorpiopt]

Do you have some info's and you want to share? Do it!

I don't i am just asking , because everyone one talks about knox has impossible to reverse

 

[Marshian]

I don't i am just asking , because everyone one talks about knox has impossible to reverse

There's a difference between practical and theoretical impossibilities. Theoretically speaking, you're right. There might be a way to restore KNOX, but we just haven't figured it out yet.
Practically speaking, there's no way to do it yet and it doesn't seem likely there'll be a way to do it any time soon (*). Therefore, it's practically impossible.

(*) It's unlikely there'll be a way to do it for two reasons: it's difficult and there's barely anything to gain from it.

 

[fburgos]

I don't i am just asking , because everyone one talks about knox has impossible to reverse

It's supposed to be a physical efuse in the chip once tripped can't be fixed

 

[rrgrrg]

It's supposed to be a physical efuse in the chip once tripped can't be fixed

No .... u r deadly wrong ..some guyd in the s4/s3 got their hands on a knox-resetting bootloader from samsung ...leaked ....and when u flash it it restores the knox state or remove it altogether i dont remeber

Sent from my GT-I9192 using XDA Premium 4 mobile app

 

[fburgos]

No .... u r deadly wrong ..some guyd in the s4/s3 got their hands on a knox-resetting bootloader from samsung ...leaked ....and when u flash it it restores the knox state or remove it altogether i dont remeber

Sent from my GT-I9192 using XDA Premium 4 mobile app

do you have the link, i think someone in the s4 said that he's knox was restored at service center but he didn't have any proof.

Until a tool its releases for public for me it's still a phisical efuse that can't be fixed

Enviado desde mi GT-I9192 mediante Tapatalk

 

[rrgrrg]

do you have the link, i think someone in the s4 said that he's knox was restored at service center but he didn't have any proof.

Until a tool its releases for public for me it's still a phisical efuse that can't be fixed

Enviado desde mi GT-I9192 mediante Tapatalk

its not a physical efuse man ... im sure 100% ,... they have a sort of leaked bootloader and when u flash it it resets/removes the counter
...search it i dont remember what was the sammy phone ...also our s4 mini came with 4.1.2 before knox was released so if even this is an efuse we dont have the hardware thingie right !! :cyclops:

 

[fburgos]

its not a physical efuse man ... im sure 100% ,... they have a sort of leaked bootloader and when u flash it it resets/removes the counter
...search it i dont remember what was the sammy phone ...also our s4 mini came with 4.1.2 before knox was released so if even this is an efuse we dont have the hardware thingie right !! :cyclops:

Afaik the efuse, qfuse is present on all snapdragon devices and every manufacturer is free to use them in any way, Samsung decided to use in the knox security, motorola use them to lock the bootloader

The exynos devices could be reseted with a bootloader i think they don't have efuses

A modified bootloader might "mask" the knox void flag but that would break the booting and from this point i need to read and update my knowledge on the topic that is really "old" let's say from January

To be clear snapdragon 400 has efuses qualcomm put those in the chip Samsung is using them with knox and for bootloader increments that's why we can't go back to an old bootloader

Enviado desde mi GT-I9192 mediante Tapatalk