Related
Hello guys, I've read about knox and now I get how it works and all, warranty isn't an issue for me (long story) so now I have the new bootloader flagged 0x1, now my question is whenever I boot into recovery or into OS I'm greeted with "set warranty bit : recovery/kernel" and "recover/kernel is not seandroid enforcing", I also kind of understand that this is related to knox bootloader but is it something I should worry about? Will flashing different roms/kernels now that I'm on the new bootloader mess up anything other than the already flagged 0x1? Thanks.
reckoner_85 said:
Hello guys, I've read about knox and now I get how it works and all, warranty isn't an issue for me (long story) so now I have the new bootloader flagged 0x1, now my question is whenever I boot into recovery or into OS I'm greeted with "set warranty bit : recovery/kernel" and "recover/kernel is not seandroid enforcing", I also kind of understand that this is related to knox bootloader but is it something I should worry about? Will flashing different roms/kernels now that I'm on the new bootloader mess up anything other than the already flagged 0x1? Thanks.
Click to expand...
Click to collapse
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
haha I will definitely try that.
reckoner_85 said:
haha I will definitely try that.
Click to expand...
Click to collapse
how do u bypass the error? I want to use 4.4
Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
i kinda have the same issue, only i dont have video/audio, and wifi....and ideas?
Help
Hy i have big problem
I try to root Galaxy s4 and all is fine but when i turn on phone he say
"kernel is not seandroid enforcing"
and this is all
Please help me how to fix this
Thanks
martin93612 said:
Hy i have big problem
I try to root Galaxy s4 and all is fine but when i turn on phone he say
"kernel is not seandroid enforcing"
and this is all
Please help me how to fix this
Thanks
Click to expand...
Click to collapse
This appears coz u changed the STOCK kernel. The unique way to solve this is installing STOCK ROM again :good:
Can you send me where i can fnde to dowload stock ROM and i can't enter in CWM to instal can this instal from ODIN?
Thank you
martin93612 said:
Can you send me where i can fnde to dowload stock ROM and i can't enter in CWM to instal can this instal from ODIN?
Thank you
Click to expand...
Click to collapse
Check the Back to Stock link in my signature! Any queries direct to that thread:good:
Thanks finaly my phone working
Thank you :victory:
Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
Laughed loud. Just wanted to let you know.
Please Help! Ive been searching all day yesterday to fix my phone
So i wanted to be updated so i downloaded mf9 and mja and all the kernels or whatever and installed them and was on stock non rooted rom for a while, yesterday i wanted to install sacs custom rom so i downloaded the newest one and flashed via twrp, but now all that happens is i get a message saying "Kernel is not seandroid enforcing" in red "Set warrenty Bit: Kernel" in yellow, I cannot flash anything via odin except philz recovery so i have that on there but i tried to install the stock firmware through odin and everything fails. I even changed usb cords, took out the .md5 extension, plugged the usb cord directly to the motherboard instead of using the front usb which that allowed me to flash philz recovery but i just want a working phone, no rom is working and I cant install any roms please help i need my phone back! Thanks, Chris
Same here :/
chriscolby7 said:
So i wanted to be updated so i downloaded mf9 and mja and all the kernels or whatever and installed them and was on stock non rooted rom for a while, yesterday i wanted to install sacs custom rom so i downloaded the newest one and flashed via twrp, but now all that happens is i get a message saying "Kernel is not seandroid enforcing" in red "Set warrenty Bit: Kernel" in yellow, I cannot flash anything via odin except philz recovery so i have that on there but i tried to install the stock firmware through odin and everything fails. I even changed usb cords, took out the .md5 extension, plugged the usb cord directly to the motherboard instead of using the front usb which that allowed me to flash philz recovery but i just want a working phone, no rom is working and I cant install any roms please help i need my phone back! Thanks, Chris
Click to expand...
Click to collapse
I am having the same issue as you Chris, I'm on the sprint galaxy s4 and i get those same errors and get stuck on a black screen with the blue led illuminated on the top, I can access recovery and download mode. I hope we get some help soon
Stock
Joku1981 said:
This appears coz u changed the STOCK kernel. The unique way to solve this is installing STOCK ROM again :good:
Click to expand...
Click to collapse
But I can't go to recovery/download mode. How can I installing STOCK ROM?
Is there a way to bypass the error?
same problem here. gets stuck at the samsung galaxy s4 spash screen
Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
but gamekiller not working fine..
Here is the Solution
reckoner_85 said:
Hello guys, I've read about knox and now I get how it works and all, warranty isn't an issue for me (long story) so now I have the new bootloader flagged 0x1, now my question is whenever I boot into recovery or into OS I'm greeted with "set warranty bit : recovery/kernel" and "recover/kernel is not seandroid enforcing", I also kind of understand that this is related to knox bootloader but is it something I should worry about? Will flashing different roms/kernels now that I'm on the new bootloader mess up anything other than the already flagged 0x1? Thanks.
Click to expand...
Click to collapse
All Right I have the solution for you! I was lucky enough to find someone that knew how to fix this (Damageless) so here is what you need to do.
-Take out the battery and disconnect from computer
-Put battery back in and hold down Vol(down) and home key, then hold power button until it vibrates. Release only the power button after it vibrates.
-You should now be in the download mode, click Vol(up) to continue.
-Download Odin here: odindownload .com
-Download stock ROM here: (dont open click save) sammobile .com and (yes you have to create an account I'm sorry) search for your model number, ex. SM-N900t for tmobile note 3
-install Odin
-check the PDA box not phone and click PDA
-find the stock ROM in your downloads and select that one.
-hit Start and you should be back to normal
It will erase everything you had on your phone which sucks I know but at least your phone works! Good luck! Hope this helps!
Wroclaw7
i have same problem them flash carbon rom and works...
martin93612 said:
Can you send me where i can fnde to dowload stock ROM and i can't enter in CWM to instal can this instal from ODIN?
Thank you
Click to expand...
Click to collapse
You can get all stock firmwares from SamMobile : http://www.sammobile.com/firmwares/
Let me know if you need help with the flashing process.
THANK YOU
THANK YOU THANK YOU I found this post and it restored my phone back to stock!!!!
the only thing I can add to this is use the original cable that came with the phone I was using an aftermarket one and was getting error after error .
Hi guys,
So I have to send my phone away for a repair under warranty with the provider (O2) tomorrow, however, when I unrooted and re-flashed the stock ROM, I forgot to use TriangleAway to reset or even check my hidden flash counter.
My phone had updated to 4.3 before I realised, and now I am stuck between a rock and a hard place. I can flash the Root file onto my phone using Odin to allow me to use TriangleAway, but by doing so I am risking voiding my KNOX Warranty. As we know this is irreversible, but then leaving my flash counter at something other than 0, I'm risking my warranty being made void anyway.
I mean, my counter could be 0 anyway, but I doubt it with the several ROMs I flashed to it, including three CyanogenMod ROMs and a GPE ROM.
What do I do? And more importantly, how do I do it to avoid voiding my KNOX Warranty status?
Thanks guys!
Go to DOWNLOAD MODE and make us a screenshot or write here what appears there pls
Joku1981 said:
Go to DOWNLOAD MODE and make us a screenshot or write here what appears there pls
Click to expand...
Click to collapse
Sorry if I wasn't clear, my current status is "KNOX Warranty Void: 0x0". I want to root my phone to run triangle away to reset the flash counter, and then unroot it, all without changing this to 0x1.
Any ideas?
radiocaf said:
Sorry if I wasn't clear, my current status is "KNOX Warranty Void: 0x0". I want to root my phone to run triangle away to reset the flash counter, and then unroot it, all without changing this to 0x1.
Any ideas?
Click to expand...
Click to collapse
Yes.
- U can root it by this way: HERE. This method no void ur warranty.
- About triangle away u can ask Chainfire directly HERE
Joku1981 said:
Yes.
- U can root it by this way: HERE. This method no void ur warranty.
- About triangle away u can ask Chainfire directly HERE
Click to expand...
Click to collapse
Thank you, I will try that. Do you know if my device status will change to custom by rooting and will TriangleAway change it back to Official?
I did everything you said and it worked perfectly. My phone had a counter of 0 so it was all in vain, but at least I know now. I got my system status back to Official, counter is 0, KNOX is untouched. I just can't update OTA, but that's no problem as long as it looks unmodified ready for it to be sent off for repair under warranty tomorrow. Thanks man!
use xposerd framework and wanam framework to change status to oficjall. this method work and you can check ota updates
Hello,
there is any way for saferoot leaked i9505 4.4?
I tryed saferoot and vroot without luck
Disclaimer: I'm not liable to any demage to your device, including Knox. The information here is as good as I know, there is no guarantee.
(If you like to provide extra information or have a correction, I'll add it to the OP)
Read this first:
http://forum.xda-developers.com/showthread.php?t=2447832
Additional information:
- How to view if I've Knox enabled or not? Enter download-mode (Power the device off and then press volume down + home + power, then press volume up if the triangle screen appears) If it says Knox 0x1 instead of 0x0, you tripped knox
- You'll get Knox 0x1 (warranty void) when you flash: custom kernel (which is included in many roms) or custom recovery (Update: @gladson1976 claimed a custom recovery didn't trip Knox at him. But at me it did)
- The device will be functional as before, nothing changes, all apps work etc. (Just at booting recovery or system it says "Set warranty bit, custom recovery" and "Set warranty bit, custom kernel" (depending on if you use a custom kernel or recovery)) info provided by @rpgdev (It's been said though, that Knox related app's will stop working.) (Upate: @fburgos claims that tripping knox caused him signal issues)
Another thing is, that if you've Knox apps still installed, they'll give you a message when giving root rights to apps "there is something wrong with the app", as reported by @Flatric
If you get warnings about applications doing not permitted actions, delete the following files from system/app, or let SuperSU fix it for you.
KNOXAgent.apk
KNOXStore.apk
ContainerAgent.apk
(Use a root browser app for deleting the files)
(information provided by @arco68 throught @R_a_z_v_a_n , thanks.
- Can I reverse Knox? So far it's impossible, but maybe one day there is a workaround (Update: workaround for Exynos CPU available, but not s4 mini yet. (see at buttom))
- Will there ever be a workaround? Knox uses and eFuse chip according to @rogier666 so there will be probably no workaround.
- I heard that in Europe your warranty will not be void, even if it's Knox 0x1 (no guarantee) check this thread for germany: http://forum.xda-developers.com/gal...arranty-knox-warranty-void-behaviour-t2919994
- It's been reported that even flashing a newer stock firmware with Odin could cause Knox active @tinko975 (I assume this happens because of Odin update of the recovery and kernel (Use in phone Samsung updater to stay safe)
- Reflashing the firmware doesn't cause KNOX 0x1 as reported by @Gloris, confirmed by @Bullet92
- Many rooting method will enable KNOX too, thanks to @afme89 for the info.
Extra:
- People claimed that if you flash a certain rom and remove the custom kernel from it and flash it with odin then it doesn't get Knox (because no custom kernel, no custom recovery.)
Knox workaround news:
@masinj claimed claimed to has found a workaround for Exynos CPU (Not S4 mini) Further info about this:
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. Info provided by @R_a_z_v_a_n , thanks.
Credits:
XDA developers
Me
@tinko975
@Gloris
@Bullet92
@afme89
@rpgdev
@Flatric
@R_a_z_v_a_n
@arco68
@masinj
@gladson1976
@fburgos
@rogier666
Reserved
my device turns knox to 0x1 in the beginning when i flash newer stock firmware with odin..
in Croatia (Europe) Warranty is void if your knox is 0x1.
tinko975 said:
my device turns knox to 0x1 in the beginning when i flash newer stock firmware with odin..
in Croatia (Europe) Warranty is void if your knox is 0x1.
Click to expand...
Click to collapse
Good to know, I'll add this to the OP :good: Thank you for contributing
Information updated, thanks to @Gloris
Aronuser said:
Information updated, thanks to @Gloris
Click to expand...
Click to collapse
Can confirm that. Reflashed it via Odin yesterday and KNOX is still 0x0.
Many rooting methods will set the Knox flag 0x1 too.
Bullet92 said:
Can confirm that. Reflashed it via Odin yesterday and KNOX is still 0x0.
Click to expand...
Click to collapse
afme89 said:
Many rooting methods will set the Knox flag 0x1 too.
Click to expand...
Click to collapse
Thank you both, I added the infos and credits to you.
I think there could also be a list of firmwares which have knox.
Example mine doesn't have one, l9195XXUAMF5.
Edit: Added link to this to few of my threads, also linked this to my signature, thanks!
leripe said:
I think there could also be a list of firmwares which have knox.
Example mine doesn't have one, l9195XXUAMF5.
Edit: Added link to this to few of my threads, also linked this to my signature, thanks!
Click to expand...
Click to collapse
First off, thank you for adding the link to your signature, i really appreciate it.
About the firmware list, well the idea is good but I don't have time for doing that. If you like to provide it I'd add it to the thread if you like (second post).
You can add that your phone will be functionally the same, I bought a 9195 (after owning the 9190) that had knox and went ahead and flashed something else (knowing that it could trip it, guarantee doesn't cover me anyways) and while it is tripped I can still flash anything, use all of my apps, etc. I had an s3 before and knox was tripped and I still could do everything I used to do.
The only really annoying thing about tripping knox is that on the first boot screen it will always show this little message announcing the "set warranty bit" which can be 'kernel' (if you're just normally booting the phone) or 'recovery' if you're booting into recovery. It shows up everytime you turn on your phone. It looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rpgdev said:
You can add that your phone will be functionally the same, I bought a 9195 (after owning the 9190) that had knox and went ahead and flashed something else (knowing that it could trip it, guarantee doesn't cover me anyways) and while it is tripped I can still flash anything, use all of my apps, etc. I had an s3 before and knox was tripped and I still could do everything I used to do.
The only really annoying thing about tripping knox is that on the first boot screen it will always show this little message announcing the "set warranty bit" which can be 'kernel' (if you're just normally booting the phone) or 'recovery' if you're booting into recovery. It shows up everytime you turn on your phone. It looks like this:
Click to expand...
Click to collapse
Thank you I'll add the info to the OP and give you credits :good:
rpgdev said:
You can add that your phone will be functionally the same, I bought a 9195 (after owning the 9190) that had knox and went ahead and flashed something else (knowing that it could trip it, guarantee doesn't cover me anyways) and while it is tripped I can still flash anything, use all of my apps, etc. I had an s3 before and knox was tripped and I still could do everything I used to do.
The only really annoying thing about tripping knox is that on the first boot screen it will always show this little message announcing the "set warranty bit" which can be 'kernel' (if you're just normally booting the phone) or 'recovery' if you're booting into recovery. It shows up everytime you turn on your phone. It looks like this:
Click to expand...
Click to collapse
I've a question about that, I heard the knox app's will stop working. is this true or false?
Aronuser said:
I've a question about that, I heard the knox app's will stop working. is this true or false?
Click to expand...
Click to collapse
I know that sometimes on stock some persistent warning messages show up on the notification bar and to get rid of them you have to freeze some 'knox apps' or remove them from the system apps. I have yet to meet a useful 'knox app' but if there is let me know and next time I'm on stock I could try it out and report back.
Aronuser said:
I've a question about that, I heard the knox app's will stop working. is this true or false?
Click to expand...
Click to collapse
On my phone Knox was tripped after rooting my phone and everytime I wanted to give an application root rights knox said there's something wrong and I should uninstall the app and reboot my phone.
If you get warnings about applications doing not permitted actions, delete the following files from system/app, or let SuperSU fix it for you.
KNOXAgent.apk
KNOXStore.apk
ContainerAgent.apk
Click to expand...
Click to collapse
From arco's root thread.
Powered by CM11 - M6 snapshot
Flatric said:
On my phone Knox was tripped after rooting my phone and everytime I wanted to give an application root rights knox said there's something wrong and I should uninstall the app and reboot my phone.
Click to expand...
Click to collapse
Thanks for providing the info, I'll add it to the OP and give you credits :good:
R_a_z_v_a_n said:
From arco's root thread.
Powered by CM11 - M6 snapshot
Click to expand...
Click to collapse
Thank you, I'll add the info to the OP and give you credits. :good:
------------
To all further informations which can be added I'll add them too and give credits, but skip writing it down here
KNOX tripped
Hi, I like that there is someone taking care for this device.
I have a GT-I9192 (A Duos version of S4 Mini) and rooted it so the KNOX is 0x1
Also a friend of mine has one too, and I updated his phone to the latest stock rom (not rooted or anything other, just update) with Odin, and his warranty bit shows 0x1
but a couple of days ago, his phone had a hardware damage (I think so) there is a problem with the screen so the phone shuts down after 3 or 4 minutes, and then doesn't restart. Went to Samsung Costumer Care and they say that the phone has been rooted, so it's out of the warranty.
also about the knox and eFuse thing, as I could understand in some other topics ( like this one: http://forum.xda-developers.com/showthread.php?t=2486346 ) the eFuse thing comes in use in Snapdragon N9000 and above chips, and this device has a Snapdragon 400
however, it would be very good if we could make a Knox reset...
urtin said:
however, it would be very good if we could make a Knox reset...
Click to expand...
Click to collapse
A knox reset isn't possible right now and probably won't be in a while (or ever). Tripping knox voids your warranty, in many people's cases (like mine) this isn't a problem because they aren't covered by it but if you are then you should probably think it twice before messing with something that could trip knox. There's no way around it sadly. I hope your friend can at least repair the device with a third party.
Hi.
Yesterday I root my device with CF-Auto Root and flash a new recovery, Philz Touch. Now everytime I turn on my device, on the boot screen appears two lines, one red and other yellow, they say " Kernel is not seandroid enforcing " and " set warranty bit: kernel ".
Can someone help me how to remove this two lines every time I turn on or restart my device??? Really I don't like....
My phone is Galaxy S4 GT-i9505 LTE.
Thanks in advance.
Someone.... please...
It's normal. If you don't like it you need to unroot.
ferrarinews said:
Hi.
Yesterday I root my device with CF-Auto Root and flash a new recovery, Philz Touch. Now everytime I turn on my device, on the boot screen appears two lines, one red and other yellow, they say " Kernel is not seandroid enforcing " and " set warranty bit: kernel ".
Can someone help me how to remove this two lines every time I turn on or restart my device??? Really I don't like....
My phone is Galaxy S4 GT-i9505 LTE.
Thanks in advance.
Click to expand...
Click to collapse
That's what always appears when using a custom ROM. Also, check wether your Know hasn't been tripped.
emperorHadrian said:
That's what always appears when using a custom ROM. Also, check wether your Know hasn't been tripped.
Click to expand...
Click to collapse
I have a I9505G LTE with Cyanogenmod installed/rooted. I don't get those lines on reboot.
dratsablive said:
I have a I9505G LTE with Cyanogenmod installed/rooted. I don't get those lines on reboot.
Click to expand...
Click to collapse
Is your Knox tripped or not? It may have something to do with it...
emperorHadrian said:
Is your Knox tripped or not? It may have something to do with it...
Click to expand...
Click to collapse
Its a Knox thing. Not a root thing.
That would explain it. My phone was from Google Play and doesn't have Knox.
Hi All,I tried to root my J5 with CFautoroot it showed passed ,screenshot is attached (http://prnt.sc/dbj19y) but what phone does is show two lines after turning on
Recovery is not Seandroid Enforcing(in red)
(and)
set warranty bit : recovery
any help would be much appreciated
aliashraf4141 said:
Hi All,I tried to root my J5 with CFautoroot it showed passed ,screenshot is attached (http://prnt.sc/dbj19y) but what phone does is show two lines after turning on
Recovery is not Seandroid Enforcing(in red)
(and)
set warranty bit : recovery
any help would be much appreciated
Click to expand...
Click to collapse
@aliashraf4141
Because u r using custom recovery
aliashraf4141 said:
Hi All,I tried to root my J5 with CFautoroot it showed passed ,screenshot is attached (http://prnt.sc/dbj19y) but what phone does is show two lines after turning on
Recovery is not Seandroid Enforcing(in red)
(and)
set warranty bit : recovery
any help would be much appreciated
Click to expand...
Click to collapse
Thats very normal. Custom recoveries will provoke such notifications. If u flash stock firmware or stock recovery that message will disappear
Can you please guide me through steps please
aarushmukesh said:
@aliashraf4141
Because u r using custom recovery
Click to expand...
Click to collapse
How to solve this,any steps,your help would be much appreciated
aliashraf4141 said:
How to solve this,any steps,your help would be much appreciated
Click to expand...
Click to collapse
May i know why u want to solve that? If u dont want a custom Rom then flash official firmware and then root with Kingroot:good: . Lol i dont think those 2 lines should bother u
KingRaheel said:
May i know why u want to solve that? If u dont want a custom Rom then flash official firmware and then root with Kingroot:good: . Lol i dont think those 2 lines should bother u
Click to expand...
Click to collapse
They have no need to bother you, they only show up for 2 seconds whilst booting.
As kingRaheel has said that's what you get with these custom ROMs
John