Hi all, sorry if my questions have been answered already, I have previously rooted my phone but am now running stock 4.1.
I'm a little concerned about KNOX, the phone is still rooted but after running triangle away status is normal, but SuperSU and CWM is still on the phone. I believe I can use Kies to update when 4.3 is out for my country, but do I need to fully unroot before upgrading? Or will the update as I believe remove root, hopefully without triggering KNOX? Thank you for any help
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!
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.
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
Hi I have a note 4 (marshmallow 6.0.1).
If I tripped knox by either rooting or flashing a custom rom, and then if I decided to revert back say i unrooted and re-flashed the stock rom.
Assuming everything is back normal except that
now you have "knox warrnety void 0*1"
Will I still be able to:
-Enable Knox active protection from Samsung's "smart manager" app.
-Use "Samsung my knox" app
-Use Samsung pay or android pay
-Do OTA updates
Or is having a "stock non-rooted rom" still not enough and you won't be able to do all of the above as long as you have already tripped knox?
(Also apparently you cannot enable it while "rooted" even if you have managed to root it without tripping Knox).
Thanks in advance :good:
I did root my phone 2h after buying it and making sure everything works all right. Never regretted it. This info just for start if you have any doubts.
If you trip Knox and install sock Rom you will have force-close notifications from Knox app (at least I had). Just run debloating script through recovery and you will be fine.
Not sure about Ota updates, I did Kies update (to 6.0.1) and it worked. Never used my phone with Samsung or Android pay, wait for somebody else to reply.
xaforib said:
I did root my phone 2h after buying it and making sure everything works all right. Never regretted it. This info just for start if you have any doubts.
If you trip Knox and install sock Rom you will have force-close notifications from Knox app (at least I had). Just run debloating script through recovery and you will be fine.
Not sure about Ota updates, I did Kies update (to 6.0.1) and it worked. Never used my phone with Samsung or Android pay, wait for somebody else to reply.
Click to expand...
Click to collapse
Alright thanks for your helpful reply, honestly I don't really care about knox app and Samsung pay if they are the only things affected