hi to all so i have been searching about knox tripping i have found something system property ro.boot.warranty_bit which is what the knox status samsung apk looks at when checking to see if knox has been tripped i was woundering if someone could help me of pulling this file from there samsung s8 or anything on firmware 7.0
im still new to this developmentt of android devices
modz2014 said:
hi to all so i have been searching about knox tripping i have found something system property ro.boot.warranty_bit which is what the knox status samsung apk looks at when checking to see if knox has been tripped i was woundering if someone could help me of pulling this file from there samsung s8 or anything on firmware 7.0
im still new to this developmentt of android devices
Click to expand...
Click to collapse
The new Knox implementation is different from previous iterations, when Knox is tripped, it permanently triggers an e-fuse, there is no way to revert that, Knox can only be faked to show intact Knox with a custom kernel.
i see but then you cant reset the counter tho and flash back stock to see if knox been triped tho
modz2014 said:
i see but then you cant reset the counter tho and flash back stock to see if knox been triped tho
Click to expand...
Click to collapse
You don't need to flash anything to check if Knox is tripped. Just go into download mode and it will tell you if warranty is void 0x1 = tripped 0x0= Not tripped.
You'll never be able to fix the e-fuse as it's in the exynos socket chip so it's litteraly impossible now.
it could be done something through the bootloader and kernel i just need them dumped files and ill look into it
In computing, eFuse is a technology invented by IBM which allows for the dynamic real-time reprogramming of computer chips.
By utilizing a set of eFuses, a chip manufacturer can allow for the circuits on a chip to change while it is in operation
The Nintendo Switch and Xbox 360's bootloaders for instance will check the amount of burned fuses before attempting to install new firmware
modz2014 said:
hi to all so i have been searching about knox tripping i have found something system property ro.boot.warranty_bit which is what the knox status samsung apk looks at when checking to see if knox has been tripped i was woundering if someone could help me of pulling this file from there samsung s8 or anything on firmware 7.0
im still new to this developmentt of android devices
Click to expand...
Click to collapse
You can reset knox by changing the motherboard.
andrei1412 said:
You can reset knox by changing the motherboard.
Click to expand...
Click to collapse
that's not resetting knox that's changing motherboard lol
modz2014 said:
that's not resetting knox that's changing motherboard lol
Click to expand...
Click to collapse
Hahaha, right! I was in need of a laugh today, im glad i visited XDA lol..
modz2014 said:
that's not resetting knox that's changing motherboard lol
Click to expand...
Click to collapse
This answer you'll get from Samsung service
You can reset knox by go back in time with a DeLorean DMC-12
ok its not a joke now its being serious about development anyway im sure there is something that can bee done with bootloader and kernel
Is there actually any proof that it's an e-fuse? I have seen a lot of conjecture, but no real evidence. It could just be a section of memory that is normally read-only.
Either way, we currently have no way to reset it.
BLuFeNiX said:
Is there actually any proof that it's an e-fuse? I have seen a lot of conjecture, but no real evidence. It could just be a section of memory that is normally read-only.
Either way, we currently have no way to reset it.
Click to expand...
Click to collapse
Hi
BLuFeNiX said:
Is there actually any proof that it's an e-fuse? I have seen a lot of conjecture, but no real evidence. It could just be a section of memory that is normally read-only.
Either way, we currently have no way to reset it.
Click to expand...
Click to collapse
It's not anything physical as far as I can tell, it there's plenty of xda articles, but there is definitely what's called an e-fuse involved with tripping knox
sofir786 said:
It's not anything physical as far as I can tell, it there's plenty of xda articles, but there is definitely what's called an e-fuse involved with tripping knox
Click to expand...
Click to collapse
Ok, can you provide a link to something that actually proves that it's an efuse? I have never seen any actual evidence. People merely calling it an efuse is not evidence.
BLuFeNiX said:
Ok, can you provide a link to something that actually proves that it's an efuse? I have never seen any actual evidence. People merely calling it an efuse is not evidence.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s7/help/how-knox-warranty-void-efuse-burning-t3407518
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
BLuFeNiX said:
Ok, can you provide a link to something that actually proves that it's an efuse? I have never seen any actual evidence. People merely calling it an efuse is not evidence.
Click to expand...
Click to collapse
Older phones which had Knox did not have e-fuse which is why in phones like the galaxy s3 you could revert Knox to 0x0, from the s5 or s6 they implemented Knox with e-fuse hence why there's been no way to revert it since then, only way was too fake Knox 0x0 through custom kernel
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
sofir786 said:
https://forum.xda-developers.com/galaxy-s7/help/how-knox-warranty-void-efuse-burning-t3407518
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
Older phones which had Knox did not have e-fuse which is why in phones like the galaxy s3 you could revert Knox to 0x0, from the s5 or s6 they implemented Knox with e-fuse hence why there's been no way to revert it since then, only way was too fake Knox 0x0 through custom kernel
Click to expand...
Click to collapse
https://en.m.wikipedia.org/wiki/Samsung_Knox
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
sofir786 said:
https://forum.xda-developers.com/galaxy-s7/help/how-knox-warranty-void-efuse-burning-t3407518
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
Older phones which had Knox did not have e-fuse which is why in phones like the galaxy s3 you could revert Knox to 0x0, from the s5 or s6 they implemented Knox with e-fuse hence why there's been no way to revert it since then, only way was too fake Knox 0x0 through custom kernel
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
https://en.m.wikipedia.org/wiki/Samsung_Knox
Click to expand...
Click to collapse
Just to add, chainfire confirmed a long while back thay e-fuse was involved
---------- Post added at 05:40 PM ---------- Previous post was at 05:40 PM ----------
sofir786 said:
https://forum.xda-developers.com/galaxy-s7/help/how-knox-warranty-void-efuse-burning-t3407518
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
Older phones which had Knox did not have e-fuse which is why in phones like the galaxy s3 you could revert Knox to 0x0, from the s5 or s6 they implemented Knox with e-fuse hence why there's been no way to revert it since then, only way was too fake Knox 0x0 through custom kernel
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
https://en.m.wikipedia.org/wiki/Samsung_Knox
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
Just to add, chainfire confirmed a long while back thay e-fuse was involved
Click to expand...
Click to collapse
Just a few more bit and bobs here too
http://omegadroid.co/wanted-knox-void-warranty-0x1/
sofir786 said:
It's not anything physical as far as I can tell, it there's plenty of xda articles, but there is definitely what's called an e-fuse involved with tripping knox
Click to expand...
Click to collapse
sofir786 said:
https://forum.xda-developers.com/galaxy-s7/help/how-knox-warranty-void-efuse-burning-t3407518
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
Older phones which had Knox did not have e-fuse which is why in phones like the galaxy s3 you could revert Knox to 0x0, from the s5 or s6 they implemented Knox with e-fuse hence why there's been no way to revert it since then, only way was too fake Knox 0x0 through custom kernel
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
https://en.m.wikipedia.org/wiki/Samsung_Knox
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
Just to add, chainfire confirmed a long while back thay e-fuse was involved
---------- Post added at 05:40 PM ---------- Previous post was at 05:40 PM ----------
Just a few more bit and bobs here too
http://omegadroid.co/wanted-knox-void-warranty-0x1/
Click to expand...
Click to collapse
None of this is proof. Most of what you posted just explains what an efuse is. Where is the actual evidence? Chainfire said he does not know whether it is an efuse or not, and if you read the top post at this link, would suggest that it is not an efuse...
https://plus.google.com/+Chainfire/posts/LCfF5A9fsTG
BLuFeNiX said:
None of this is proof. Most of what you posted just explains what an efuse is. Where is the actual evidence? Chainfire said he does not know whether it is an efuse or not, and if you read the top post at this link, would suggest that it is not an efuse...
https://plus.google.com/+Chainfire/posts/LCfF5A9fsTG
Click to expand...
Click to collapse
They've used the word fused here, now I know this doesn't prove anything but it more than likely is pointing to it considering the language used, having actual proof would mean a Samsung dev releasing closed sourced info.
sofir786 said:
They've used the word fused here, now I know this doesn't prove anything but it more than likely is pointing to it considering the language used, having actual proof would mean a Samsung dev releasing closed sourced info.
Click to expand...
Click to collapse
Or perhaps a savvy engineer with a microscope could show us real evidence of an efuse.
That is not what "fused" means in that context. Listen, I'm not saying that it definitely isn't an efuse, but to assume that it is without proof is a bit foolish. If it is an efuse, then can you explain how the Exynos processor-equipped variants HAVE been resettable from 0x1 back to 0x0?
BLuFeNiX said:
Or perhaps a savvy engineer with a microscope could show us real evidence of an efuse.
That is not what "fused" means in that context. Listen, I'm not saying that it definitely isn't an efuse, but to assume that it is without proof is a bit foolish. If it is an efuse, then can you explain how the Exynos processor-equipped variants HAVE been resettable from 0x1 back to 0x0?
Click to expand...
Click to collapse
Old Samsung phones have been able to reset Knox, as far as I can tell from s6 which i owned, once Knox was tripped that was it, the only way to have 0x0 is though faking it through at a kernel level, that's why 100% of custom kernels available for the exynos variation have fake 0x0 flag. If you've seen otherwise please show me that, as far as I know no one with 0x1 Knox flag on exynos has done that, i have the exynos variant btw.
Related
Hi,
I tried to delete Knox from my Note 3 via Root Explorer. But now I just wanted to see if I could reinstall Knox by reinstalling the stock rom firmware for my device but it is not showing up though I think Knox is still on my phone but hidden. Does anyone have a foolproof method of getting Knox back to its original state?
On another issue, I've backed up my (rooted) Note 3 rom via CWM recovery, but when I try to restore it my Note 3 goes into a perpetual loop. Any solutions?
okizen said:
Hi,
I tried to delete Knox from my Note 3 via Root Explorer. But now I just wanted to see if I could reinstall Knox by reinstalling the stock rom firmware for my device but it is not showing up though I think Knox is still on my phone but hidden. Does anyone have a foolproof method of getting Knox back to its original state?
Click to expand...
Click to collapse
your the 1st person ive heard wants knox back lol
---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------
okizen said:
Hi,
I tried to delete Knox from my Note 3 via Root Explorer. But now I just wanted to see if I could reinstall Knox by reinstalling the stock rom firmware for my device but it is not showing up though I think Knox is still on my phone but hidden. Does anyone have a foolproof method of getting Knox back to its original state?
On another issue, I've backed up my (rooted) Note 3 rom via CWM recovery, but when I try to restore it my Note 3 goes into a perpetual loop. Any solutions?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=46296537&postcount=138 found this
jaythenut said:
your the 1st person ive heard wants knox back lol
---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------
http://forum.xda-developers.com/showpost.php?p=46296537&postcount=138 found this
Click to expand...
Click to collapse
Thanx for the link. I just wanted to see if it could be done. Lol
jaythenut said:
your the 1st person ive heard wants knox back lol
Click to expand...
Click to collapse
:laugh: :good:
I found a guide on androidxda(.)com (can't link directly to it since I'm a new poster) and I'm wondering if that will work or if you can point me in the right direction?
Reddit said you'll should know.
Thanks!
SoundGoddess said:
I found a guide on androidxda(.)com (can't link directly to it since I'm a new poster) and I'm wondering if that will work or if you can point me in the right direction?
Reddit said you'll should know.
Thanks!
Click to expand...
Click to collapse
Hello fellow redditor. I assume you're referring to this method. It will work, however it will also void your warranty (if you have one, of course). You should not lose any data however.
SoundGoddess said:
I found a guide on androidxda(.)com (can't link directly to it since I'm a new poster) and I'm wondering if that will work or if you can point me in the right direction?
Reddit said you'll should know.
Thanks!
Click to expand...
Click to collapse
If you want to lost warranty use androidxda method . If you want to save warranty use this method http://forum.xda-developers.com/showpost.php?p=58418821&postcount=227 . Only use the your kernels . I can to help you with kernels .
repey6 said:
If you want to lost warranty use androidxda method . If you want to save warranty use this method http://forum.xda-developers.com/showpost.php?p=58418821&postcount=227 . Only use the your kernels . I can to help you with kernels .
Click to expand...
Click to collapse
Thanks, I downloaded your files, can you tell me the steps how to root my tablet without voiding warranty? I don't worry much about losing warranty since I probably wouldn't need to make a warranty claim, but I would rather keep the warranty if that is an option:
SoundGoddess said:
Thanks, I downloaded your files, can you tell me the steps how to root my tablet without voiding warranty? I don't worry much about losing warranty since I probably wouldn't need to make a warranty claim, but I would rather keep the warranty if that is an option:
Click to expand...
Click to collapse
Only use the your kernels . I can to help you with kernels
---------- Post added at 07:17 PM ---------- Previous post was at 07:14 PM ----------
Wait your kernel
repey6 said:
Only use the your kernels . I can to help you with kernels
---------- Post added at 07:17 PM ---------- Previous post was at 07:14 PM ----------
Wait your kernel
Click to expand...
Click to collapse
Ok thank you I just installed towelroot and now it says that I'm rooted in root checker. Is that all there is to it then? How do I know if my warranty is intact? Thank you for saving me so much hassle
Deleted
SoundGoddess said:
Ok thank you I just installed towelroot and now it says that I'm rooted in root checker. Is that all there is to it then? How do I know if my warranty is intact? Thank you for saving me so much hassle
Click to expand...
Click to collapse
If you used towelroot your warranty is fine but if you want to check you can use the Phone info app in the playstore. It should say your knox warranty void is 0x0.
Hi,
I am little confused about this. Is there a working root available for this Snapdragon model ? If yes, can I use secure folder while using a rooted ROM ?
Please suggest .Thanks in advance .
Trijunction said:
Hi,
I am little confused about this. Is there a working root available for this Snapdragon model ? If yes, can I use secure folder while using a rooted ROM ?
Please suggest .Thanks in advance .
Click to expand...
Click to collapse
There is no Root available on Canadian or American variant.
Please use "Google Search" for details.
Hi, Can anyone verify if these roots work?
https://www.skyneel.com/root-samsung-galaxy-s8-sm-g950w
---------- Post added at 03:42 PM ---------- Previous post was at 03:42 PM ----------
Hi, Can anyone verify if these roots work?
https://www.skyneel.com/root-samsung-galaxy-s8-sm-g950w
tarunscool said:
Hi, Can anyone verify if these roots work?
https://www.skyneel.com/root-samsung-galaxy-s8-sm-g950w
---------- Post added at 03:42 PM ---------- Previous post was at 03:42 PM ----------
Hi, Can anyone verify if these roots work?
https://www.skyneel.com/root-samsung-galaxy-s8-sm-g950w
Click to expand...
Click to collapse
Give it a try and let us know, good luck
chainfire auto root method doesn't work at all either. Bummer
---------- Post added at 12:51 AM ---------- Previous post was at 12:49 AM ----------
tarunscool said:
Hi, Can anyone verify if these roots work?
https://www.skyneel.com/root-samsung-galaxy-s8-sm-g950w
---------- Post added at 03:42 PM ---------- Previous post was at 03:42 PM ----------
Hi, Can anyone verify if these roots work?
https://www.skyneel.com/root-samsung-galaxy-s8-sm-g950w
Click to expand...
Click to collapse
That's just the chainfire auto root method which doesn't work. Just fails
How come the snapdragon variant can't be rooted?? I remember a time ago when they were the first and easiest to root now its impossible?? What the hell happened?? Too many idiots screwed their devices and took them back for warranty or what??
root is now out. look for sampwnd.
Has anyone done it ?
thatsupnow said:
How come the snapdragon variant can't be rooted?? I remember a time ago when they were the first and easiest to root now its impossible?? What the hell happened?? Too many idiots screwed their devices and took them back for warranty or what??
Click to expand...
Click to collapse
It's down to having a locked boot loader
mweinbach said:
root is now out. look for sampwnd.
Click to expand...
Click to collapse
Have you tried it ? Mine is on android 9 pie
Hi everyone,
quick question - bought myself the galaxy s8 (G950F) and as a new member to the Samsung community, can you tell me how does this whole Knox works?
Once I root the phone, and than install a custom ROM, there is any way to change/reset the Knox level?
Are the warranty is completely gone while I do that?
If it is, that also apply for physical fault (like burned pixel etc)?
And in general, is it worth it? Is there much benefits for the custom roms or is the stock version is just fine
Thanks in advance!
Not sure about warranty but cannot restore Knox once rooted
Why were you planning to root?
Sent from my SM-G955U using Tapatalk
---------- Post added at 10:17 PM ---------- Previous post was at 10:17 PM ----------
IMHO stock is fine and stable and secure
Sent from my SM-G955U using Tapatalk
---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------
Not to mention device value falls by rooting
Sent from my SM-G955U using Tapatalk
iii2 said:
And in general, is it worth it? Is there much benefits for the custom roms or is the stock version is just fine
Click to expand...
Click to collapse
I don't believe so, the only roms available are still based on samsungs touchwiz, if aosp would be available then i would root the phone. Don't root it unless you actually have a need to do it. You can block ads without root with adhell from the playstore.
I'm currently on firmware version T380DXU3BSD1 and I'm trying to remove the FRP lock on my device. I've looked online but I haven't been able to find a combination file for my bootloader version (only found U1 and U2). Does anyone know if the file exists/is available for download somewhere, or another way to remove the FRP lock?
Thanks
t-what said:
I'm currently on firmware version T380DXU3BSD1 and I'm trying to remove the FRP lock on my device. I've looked online but I haven't been able to find a combination file for my bootloader version (only found U1 and U2). Does anyone know if the file exists/is available for download somewhere, or another way to remove the FRP lock?
Thanks
Click to expand...
Click to collapse
Any luck?
gadeyka said:
Any luck?
Click to expand...
Click to collapse
Unfortunately not, I’ve had to give up on the device. The only thing I found were obvious scam websites that I doubt actually had the file.
https://androidfilehost.com/?fid=6006931924117922314
Good Luck!
---------- Post added at 10:04 PM ---------- Previous post was at 10:04 PM ----------
https://androidfilehost.com/?fid=6006931924117922314
Good Luck!
---------- Post added at 10:09 PM ---------- Previous post was at 10:04 PM ----------
bullracing said:
https://androidfilehost.com/?fid=6006931924117922314
Good Luck!
Im not the owner of that file, I just sharing the Link
Click to expand...
Click to collapse