Database Develop

No knox status in ODIN mode? Need to warranty rooted i537

So I bought this i537 used a while back, the previous owned never registered it with samsung but I did when I bought it so I do have a warranty on it. I know it was previously rooted then unrooted before I bought it but I don't know if it ever had a custom rom on it. I rooted the phone with activeroot (still on 4.2.2 stock rom) and have since unrooted it with superSU.
I am having problems with the touchscreen and samsung has confirmed warranty coverage and gave me a shipping label but I want to be totally sure it a-ok before I send it in.
When I boot into odin mode there is no KNOX status, is that normal for this device? Did 4.2.2 not come with knox on this device?
Also the status says custom? When the phone WAS rooted it said official ??? seems bass ackwards.
Also, I would like to reload stock 4.2.2 via ODIN just to make sure everything is kosher before sending it it, would this void my warranty?
My phone is also sim unlocked, i imagine this is okay as far as warranty goes? Would reflashing with ODIN break my sim unlock?
Thanks so much!

CaseyR22 said:
So I bought this i537 used a while back, the previous owned never registered it with samsung but I did when I bought it so I do have a warranty on it. I know it was previously rooted then unrooted before I bought it but I don't know if it ever had a custom rom on it. I have rooted the phone with activeroot (still on 4.2.2 stock rom).
When I boot into odin mode there is no KNOX status, is that normal for this device? Did 4.2.2 not come with knox on this device?
Also, I would like to reload stock 4.2.2 via ODIN just to make sure everything is kosher before sending it it, would this void my warranty?
My phone is also sim unlocked, i imagine this is okay as far as warranty goes? Would reflashing with ODIN break my sim unlock?
Thanks so much!
Click to expand...
Click to collapse
Let's start from the top:
This phone came with MF2 (4.2.2), which was then immediately updated to MF3 (4.2.2). Both of these versions came with Knox enabled. If he just rooted then he probably didn't trip the Knox flag, but there could have been other things he did or tried to do that did trip the flag.
If it is indeed the i537, I can guarantee he did not flash a custom ROM. The i537 has a locked bootloader which means no custom recovery and no custom ROMs. However there is the ability to use TouchWiz-based ROMs, if you want to learn more about this and how it works read about SafeStrap.
We do not have official 4.2.2 stock firmware available to flash. We have a pre-release of 4.2.2, a pre-release of 4.3, official 4.3, and an OTA to go from 4.3 to 4.4.2. You can read more about the different firmwares in the i537 Firmware Thread.
Flashing firmware with Odin will erase your SIM unlock, but you can either enter the unlock code again or there are other methods that can be used. I'm not familiar with SIM unlocking so you'll have to do a little searching.
You never mentioned what you're sending the phone in for. I would try flashing the MF1 firmware first to see if it's a software issue. If it's a hardware issue then unfortunately you'll have to send it in.

Devo7v said:
Let's start from the top:
This phone came with MF2 (4.2.2), which was then immediately updated to MF3 (4.2.2). Both of these versions came with Knox enabled. If he just rooted then he probably didn't trip the Knox flag, but there could have been other things he did or tried to do that did trip the flag.
If it is indeed the i537, I can guarantee he did not flash a custom ROM. The i537 has a locked bootloader which means no custom recovery and no custom ROMs. However there is the ability to use TouchWiz-based ROMs, if you want to learn more about this and how it works read about SafeStrap.
We do not have official 4.2.2 stock firmware available to flash. We have a pre-release of 4.2.2, a pre-release of 4.3, official 4.3, and an OTA to go from 4.3 to 4.4.2. You can read more about the different firmwares in the i537 Firmware Thread.
Flashing firmware with Odin will erase your SIM unlock, but you can either enter the unlock code again or there are other methods that can be used. I'm not familiar with SIM unlocking so you'll have to do a little searching.
You never mentioned what you're sending the phone in for. I would try flashing the MF1 firmware first to see if it's a software issue. If it's a hardware issue then unfortunately you'll have to send it in.
Click to expand...
Click to collapse
Thank you for the quick response. I edited the first post to add more details but you must've already quoted me before I hit send.
Basically the problem is the screen will randomly detect 1, 3 or 5 nonexistent touches across the center of the screen (confirmed by enabling "show touches" in the developer options). While this is happening the touchscreen becomes unusable, rebooting several times will eventually fix it but the problem comes back randomly, sometime within a couple minutes and sometimes after several hours.
I did confirm my device is running MF3 and it is absolutely a i537. I'm using the phone on straight talk not ATT so I have not received any OTA updates beyond this point.
So,anyhow I understand I can fix the device status:custom with triangleaway but I don't understand why there is no KNOX counter in ODIN mode and how this may effect my warranty.
Also, if I did ODIN to 4.3 or 4.4 would this trip the knox counter? (Assuming it isnt tripped already).
Thanks for your input, truly appreciated!

CaseyR22 said:
Thank you for the quick response. I edited the first post to add more details but you must've already quoted me before I hit send.
Basically the problem is the screen will randomly detect 1, 3 or 5 nonexistent touches across the center of the screen (confirmed by enabling "show touches" in the developer options). While this is happening the touchscreen becomes unusable, rebooting several times will eventually fix it but the problem comes back randomly, sometime within a couple minutes and sometimes after several hours.
I did confirm my device is running MF3 and it is absolutely a i537. I'm using the phone on straight talk not ATT so I have not received any OTA updates beyond this point.
So,anyhow I understand I can fix the device status:custom with triangleaway but I don't understand why there is no KNOX counter in ODIN mode and how this may effect my warranty.
Also, if I did ODIN to 4.3 or 4.4 would this trip the knox counter? (Assuming it isnt tripped already).
Thanks for your input, truly appreciated!
Click to expand...
Click to collapse
It sounds like it might be a software issue so it would be worth it to try to flash the official 4.3 firmware. Flashing official firmware shouldn't trip the Know flag, but I'm not really an expert on Knox. I have read that Knox being tripped doesn't affect warranty repairs.

Devo7v said:
It sounds like it might be a software issue so it would be worth it to try to flash the official 4.3 firmware. Flashing official firmware shouldn't trip the Know flag, but I'm not really an expert on Knox. I have read that Knox being tripped doesn't affect warranty repairs.
Click to expand...
Click to collapse
Thanks, I went ahead and flashed 4.3 via ODIN and the KNOX status is showing 0x0 so that is a good sign. Has only been about a half hour so I cant say whether or not the touchscreen issue is fixed yet but I will post back and update what happens after a day or so.
Another plus is the update finally got rid of that god awful default font on 4.2 (changing the system font wouldn't change the fontface for plain text in the browser).

Quick update in case anyone is having a similar problem with "phantom touches" in the future.
After flashing to 4.3 the touchscreen problems have continued so i do believe it is a hardware problem that will require disassembly to fix.
Also the phone keeps trying to download the OTA update to 4.4 but I've heard bad things about the update so far so I've left my wifi turned off.
Going to be stuck using a windows 8 phone for a week or while my phone is out for warranty repair.

There is an app in the play store called phone info. There it tells you your knox status without root or being in download mode.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app

One final update in case anybody runs into similar problems in the future. Samsung confirmed it was a hardware problem and fixed the phone 100% free of charge under warranty.
It appears they replaced everything which is pretty awesome because I now have a brand new digitizer and bezel without a single scratch or scuff on them. Also my usb port cover flap was feeling pretty worn/sloppy so now thats new and even the USB port itself looks brand new which tells me the motherboard was replaced. I can tell they peeled the old serial/IMEI sticker off the old phone and stuck it on this one.
Surprisingly they didn't update it to 4.4 while it was there which kind of sucks because I'm nervous about doing it myself after reading horror stories on the forums.
Anyway I'm very pleased with Samsung's support!

Downgrade from Lollipop to Kitkat without tripping knox SM-G900F

Hi all!!
After spending a huge amount of hours, searching the forum, I still have doubts...
Is it possible to downgrade from Lollipop, to kitkat, without tripping knox (warranty void) in the S5???
Some say, that flashing with Odin it's ok, others say that will go in a loopboot, others say that the bootloader is not compatible, and flashing a new rom will trip knox, others say that if the rom is official, will not trip knox...
What to believe??????
If there is a way to downgrade, safely and without tripping knox, please show me how, in a step-by-step process, I really appreciate it.
Here are the mobile phone data:
SM-G900F
Firmware: G900FXXU1BOD3
Thanks in advance!

Downgrade away, I have the G900F, and flashing KK over LP works fine and does not trip KNOX
You only trip KNOX by flashing custom stuff, stock ROMs are signed by Samsung so do not trip KNOX
The only issue I had was having to flash KK twice, first flash worked but wouldn't boot, flashed again, booted first time

*Detection* said:
Downgrade away, I have the G900F, and flashing KK over LP works fine and does not trip KNOX
You only trip KNOX by flashing custom stuff, stock ROMs are signed by Samsung so do not trip KNOX
The only issue I had was having to flash KK twice, first flash worked but wouldn't boot, flashed again, booted first time
Click to expand...
Click to collapse
Hi Detection!
Thank you for your enlightement, but tell me, you flashed your device using Odin, right?
Thanks!

Yep, ODIN 3.10.6

*Detection* said:
Yep, ODIN 3.10.6
Click to expand...
Click to collapse
Ok, will give it a go!
Thanks Detection!

And how did it go?? Did You safely downgraded to KK?? I was thinking about it, got my S5 with pre-installed Lollipop but without root I can't block adds and stuff - it's rather annoying.

cichy20a said:
And how did it go?? Did You safely downgraded to KK?? I was thinking about it, got my S5 with pre-installed Lollipop but without root I can't block adds and stuff - it's rather annoying.
Click to expand...
Click to collapse
You can root lollipop, but it'll trip KNOX
CF Auto Root

Yeah i know that CF-AutoRoot works on lolly but I'd rather keep my warranty void Guess no new method on gaining root w/o tripping knox was introduced to S5 design If i recall S6 is rootable now without knox messed up but no go for S5

I flashed my S5 a few months ago from 5.0 back to 4.4.2, and last week the same thing, but on my gf's Note3.
It's kind of easy and safe to do, if you do some research in advance:
- find exactly which ROM you need (the wrong one won't work and make ur phone temporarily unusable).
- download the official stock ROM
- KNOX won't trip if it's an official stock ROM.
- Boot the phone in recovery mode to wipe the cache partition and do a factory reset (after backing up the important data).
- Flash with Odin. There's many youtube tutorials on that one.
Enjoy.
If you didn't do a factory reset, wipe cache partitions etc you'll almost certainly get stuck in bootloop after flashing. In that boot up in recovery mode again, do those wipes and then restart.

*Detection* said:
Downgrade away, I have the G900F, and flashing KK over LP works fine and does not trip KNOX
You only trip KNOX by flashing custom stuff, stock ROMs are signed by Samsung so do not trip KNOX
The only issue I had was having to flash KK twice, first flash worked but wouldn't boot, flashed again, booted first time
Click to expand...
Click to collapse
gluecks said:
I flashed my S5 a few months ago from 5.0 back to 4.4.2, and last week the same thing, but on my gf's Note3.
It's kind of easy and safe to do, if you do some research in advance:
- find exactly which ROM you need (the wrong one won't work and make ur phone temporarily unusable).
- download the official stock ROM
- KNOX won't trip if it's an official stock ROM.
- Boot the phone in recovery mode to wipe the cache partition and do a factory reset (after backing up the important data).
- Flash with Odin. There's many youtube tutorials on that one.
Enjoy.
If you didn't do a factory reset, wipe cache partitions etc you'll almost certainly get stuck in bootloop after flashing. In that boot up in recovery mode again, do those wipes and then restart.
Click to expand...
Click to collapse
Hi all!
Tell me something, after flashing KK, software update is allways trying to update to LP... is there a way of avoiding this, without root access?
Thanks in advance!

you need to disable the FOTA processes, but I'm not sure you can do that without root

Ok guys so let me get this straight - I only need proper KK image, provided by Samsung (their signature and so on) with my CSC (in my case Polish XEO)? Then connect my phone with PC, start ODIN (any particular version?) and what to choose, what check and what not? Sorry for this only had HTC before (and Sony and LG but those are wifes phones) and flashing on it was a bliss, especially when You had S-OFF.

dicemaster said:
Hi all!
Tell me something, after flashing KK, software update is allways trying to update to LP... is there a way of avoiding this, without root access?
Thanks in advance!
Click to expand...
Click to collapse
Not stop, but you can delay it indefinitely by clearing the cache in recovery each time it has the update ready for you to install
Then boot back into droid, and hit the install button, which will fail because you just deleted the update in recovery
Rinse and repeat
You can root KK without tripping KNOX though, so no reason to not root it really

*Detection* said:
Not stop, but you can delay it indefinitely by clearing the cache in recovery each time it has the update ready for you to install
Then boot back into droid, and hit the install button, which will fail because you just deleted the update in recovery
Rinse and repeat
You can root KK without tripping KNOX though, so no reason to not root it really
Click to expand...
Click to collapse
Hi Detection!
I know we can root without tripping knox, but I am afraid of doing something wrong...
Can you tell me how to do it, in a safe way???
Thanks in advance!

dicemaster said:
Hi Detection!
I know we can root without tripping knox, but I am afraid of doing something wrong...
Can you tell me how to do it, in a safe way???
Thanks in advance!
Click to expand...
Click to collapse
Either make sure your KK ROM is a pre June 2014 build, if not, either flash with ODIN, or read up on how to downgrade only the Kernel to a pre June 2014 KK kernel, then use towelroot app to root it, and flash your original Kernel back
All the info you need is here on XDA, might take a bit of reading, but you should really learn as much as you can before blindly flashing things anyway

I read in another thread, someone said that if your S5 came with LP out of the box, you can't downgrade to even official samsung KK without tripping knox. I'm not sure how true is this or whether that person is just blowing smoke.

Planning to root my t815. How easy is it to go back to total stock? Will Sammy know?

Well actually it seems fairly straighfoward to go back to stock, if you have the appropriate stock image to flash with Odin. I'm just used to do the whole "unlock bootloader, flash recovery, flash autoroot/rom/whatever" process on other devices and it feels weird to just load up Odin and do everyhing. So that's an insecurity.
I'm more interested in knowing whether Samsung "knows" that you rooted/unlocked the device, for warranty reasons. If sometime I decide to go back to full stock and at some point I need to return/send the device for some service, I want to know if they can tell whether the device had been previously rooted. On my motorola xt1092 unlocking the bootloader requires some sort of code from Moto itself, so even if you go back totally stock you can't get rid of the "unlocked bootloader" msg, let alone that they have you already registered on their system as having non-valid warranty.

YES. Atm there is no root method that won't trip knox and if knox is 0x1 samsung will always know. Some providers don't care about that and will fix ur phone/tablet. Especially if it don't even boot or some mechanic problem, just flash stock firmware with odin. My personally was very insecure when flashed firmware 5.1.1 then kernel and then root with odin (always used TWRP on S4) but all worked ok, just read the guide, real all post and all will be ok. If u wan't then go go stock just flash the same stock firmware and you will have it stock with no root stock recovery but knox will be 0x1

mk89pwnz said:
YES. Atm there is no root method that won't trip knox and if knox is 0x1 samsung will always know. Some providers don't care about that and will fix ur phone/tablet. Especially if it don't even boot or some mechanic problem, just flash stock firmware with odin. My personally was very insecure when flashed firmware 5.1.1 then kernel and then root with odin (always used TWRP on S4) but all worked ok, just read the guide, real all post and all will be ok. If u wan't then go go stock just flash the same stock firmware and you will have it stock with no root stock recovery but knox will be 0x1
Click to expand...
Click to collapse
Thanks for the info! I found out there was a piece of software called "Triangle Away" which helped reset counter to 0x0 when going back to full stock, but i can't find out if it would work on the Tab S2... http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114

kokotron said:
Thanks for the info! I found out there was a piece of software called "Triangle Away" which helped reset counter to 0x0 when going back to full stock, but i can't find out if it would work on the Tab S2... http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Click to expand...
Click to collapse
It was flash counter not knox. Knox is literally impossible to reset. Triangle Away only works on older devices. List can be found here: http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114

mk89pwnz said:
YES. Atm there is no root method that won't trip knox and if knox is 0x1 samsung will always know. Some providers don't care about that and will fix ur phone/tablet. Especially if it don't even boot or some mechanic problem, just flash stock firmware with odin. My personally was very insecure when flashed firmware 5.1.1 then kernel and then root with odin (always used TWRP on S4) but all worked ok, just read the guide, real all post and all will be ok. If u wan't then go go stock just flash the same stock firmware and you will have it stock with no root stock recovery but knox will be 0x1
Click to expand...
Click to collapse
Just to reconfirm that, since I was also a little concerned about that (I have a T810 btw, not a T815): While the stock firmware on my device works 'well enough', there are certain things i'd rather it was able to do. Knox however has me holding off (at least until the warranty expires). Does the same apply to the T810? (There is no root method that won't trip knox.)

ATM no. The only way to root Tab s2 is to trip Knox. King root will root your device with no Knox tripping but it will last until you reboot

what is missed after Note5 unroot!

Hello,
I knew that if I root my Note5 (N920C) I will lose Knox and Samsung pay.
I've a question, If I revert to the original firmware shall I get back Samsung pay and knox?
generally, If I installed back the original firmware, is everything will back to normal or some issues would happen??
if there are issues after unrooting and installing the stock firmware, please list them all.
thank you for your support.

Samsung pay is gone. Knox will always be 0x1.you will have no deepsleep.

mdxii said:
Hello,
I knew that if I root my Note5 (N920C) I will lose Knox and Samsung pay.
I've a question, If I revert to the original firmware shall I get back Samsung pay and knox?
generally, If I installed back the original firmware, is everything will back to normal or some issues would happen??
if there are issues after unrooting and installing the stock firmware, please list them all.
thank you for your support.
Click to expand...
Click to collapse
Hi ,
in short , if you flash your latest official stock Rom
You obviously loose root .!
Secondly ,if Knox is tripped it stays like that ., permanently
It's what they called a "e fuse " that was tripped.
(Nothing you do ,can will fix knox ,Only Samsung can and the most probably won't )
Also if you unroot chances are that your phone won't "deep sleep" ?
Samsung Pay ,i don't know.
Good luck

Thank you guys. the stock firmware is pretty good already. there is no good reason for rooting

Nougat rooted ?? I think how to unroot n920c

Hello guys please help today I just followed one thread for enabling volte and in that they suggested me to install two and later some cris volte fix and before that one file I don't know what exactly it is and they told me to zip flaw by twrp so I did later I found my know is tripped and Samsung pay and stealth app is not working is my device rooted?? If it's I want to uproot help me guys this is really annoying ?

Help me to fix shealth app at least
Help me to fix shealth app and also any suggestions for Samsung pay also

dandamatrix said:
Hello guys please help today I just followed one thread for enabling volte and in that they suggested me to install two and later some cris volte fix and before that one file I don't know what exactly it is and they told me to zip flaw by twrp so I did later I found my know is tripped and Samsung pay and stealth app is not working is my device rooted?? If it's I want to uproot help me guys this is really annoying ?
Click to expand...
Click to collapse
1)By flashing Volte zip by recovery i.e.TWRP you have surely rooted your device and its obvious that you have tripped knox counter
2)You can unroot your device by flashing stock firmware using odin
3)But for your kind information you have tripped your knox counter once, you can't reset it to normal again by anything even after flashing stock firmware back
4)So samsung pay and s-health will not work on stock rooted devices(Remember i said stock rooted or unrooted firmware)
5)There are many custom nougat roms running S-Health effectively so if you want s-health working you can flash them but not Samsung Pay is still working on custom roms due to kernel limitations

DroidHackeR said:
1)By flashing Volte zip by recovery i.e.TWRP you have surely rooted your device and its obvious that you have tripped knox counter
2)You can unroot your device by flashing stock firmware using odin
3)But for your kind information you have tripped your knox counter once, you can't reset it to normal again by anything even after flashing stock firmware back
4)So samsung pay and s-health will not work on stock rooted devices(Remember i said stock rooted or unrooted firmware)
5)There are many custom nougat roms running S-Health effectively so if you want s-health working you can flash them but not Samsung Pay is still working on custom roms due to kernel limitations
Click to expand...
Click to collapse
but i use stock firmware for N7 and s health work fine on my rooted device n920c .. there is a fix for that ...
https://forum.xda-developers.com/no...ficially-started-rolling-note-t3574405/page12

firefox50 said:
but i use stock firmware for N7 and s health work fine on my rooted device n920c .. there is a fix for that ...
https://forum.xda-developers.com/no...ficially-started-rolling-note-t3574405/page12
Click to expand...
Click to collapse
I have stated in my previous post that s-health is working on rooted custom nougat roms and yes i have seen your reference post for working s-health for rooted stock nougat firmware..But what about samsung pay and secure folder? They will probably never work on stock rooted firmware untill custom kernel will come out am i right?

DroidHackeR said:
I have stated in my previous post that s-health is working on rooted custom nougat roms and yes i have seen your reference post for working s-health for rooted stock nougat firmware..But what about samsung pay and secure folder? They will probably never work on stock rooted firmware untill custom kernel will come out am i right?
Click to expand...
Click to collapse
sure you are right ... we all waiting .