installed and was working prperly, didnot use for some time
changed firmware via odin stock roms to install lang
knox warranty 0x0 valid
software is official
tried to use knox was locked and reset lock from myknox.com
tried but failed until enrolled it from myknox.com
tried to reinstall again and said custom binary installed or previously installed, factory reset but noway, tried to contact support but didn't answer.
any advice ??????
Related
Hello. Today, i rooted my S4(i9505) and i instaled a wrong font package and my phone entered in bootloop mode. How can i get out of it without voiding my warranty and knox counter still remain at 0x0? Can i flash a stock rom by odin? Please help me with this problem. thanks in advance!
Hello folks,
today I flashed official Lollipop 5.0.1 via ODIN on my N910-F and accidently tripped my KNOX Counter. So be careful if you do not want to void your warranty.
My phone is carrier branded DTM (T-Mobile) and had latest OTA firmware 4.4.4 *ANK4 on it. Back when i did buy my device I decided to debrand my phone as soon as Lollipop comes out.
So I did and flashed in one step from KitKat (T-Mobile) to Lollipop (Open). From what I read a assumed it would be no problem because it's a newer build but in some way it tripped my Knox Counter to 0x1 (3).
I did use Odin 3.09 as suggested by sammobile but ended up with an error (Fail) at the end of the flashing procedure. I downloaded Odin 3.10 and reflashed without any problems. This might be also considered as a reason for tripping the counter (as it says 3). I checked my counter after 2 factory resets afterwards.
Now I'm actually good to root I guess. Be careful.
EDIT: When I'm performing a factory reset from within the ROM it fails with "dm-verity verification failed..." message and takes me to the Android system recovery. From there I can do the factory reset. I think there is something gone wrong. Ideas on that message?
raupe1337 said:
Hello folks,
today I flashed official Lollipop 5.0.1 via ODIN in my N910-F and accidently tripped my KNOX Counter. So be careful if you do not want to void your warranty.
My phone is carrier branded DTM (T-Mobile) and had latest OTA firmware 4.4.4 *ANK4 on it. Back when i did buy my device I decided to debrand my phone as soon as Lollipop comes out.
So I did and flashed in one step from KitKat (T-Mobile) to Lollipop (Open). From what I read a assumed it would be no problem because it's a newer build but in some way it tripped my Knox Counter to 0x1 (3).
I did use Odin 3.09 as suggested by sammobile but ended up with an error (Fail) at the end of the flashing procedure. I downloaded Odin 3.10 and reflashed without any problems. This might be also considered as a reason for tripping the counter (as it says 3). I checked my counter after 2 factory resets afterwards.
Now I'm actually good to root I guess. Be careful.
Click to expand...
Click to collapse
I never heard of this? You tripped Knox with the official firmware? Did you maybe have the wrong options selected in Odin, as you would be the first who is able to trip Knox with official firmware???
I don't know why it tripped it. I haven't tripped it even after using Z3X box.
Everytime I use a firmware from sammobile it never tripped any counter of my phones.
marleyb said:
Did you maybe have the wrong options selected in Odin, as you would be the first who is able to trip Knox with official firmware???
Click to expand...
Click to collapse
Had standard options selected which are "Auto Reboot" and "F. Reset Time".
I might think the trip is not caused by flashing but performing a factory reset afterwards which results in "dm-verity verification failed..." message in the recovery menu. From what I know this error is caused by root which I didn't.
Update: Device is now working as supposed. After two failed attempts to flash the firmware via Kies new it worked on a third time. No error on factory reset.
My assumption is that there went something horribly wrong on first time flashing the firmware via ODIN, which preventet the factory reset from performing as usual. Knox detected that inexplicable status and graded it as modified which tripped the Knox counter then. I have no other explanation for this, maybe the 0.01% got real in my case.
So I sold my buddy the note 3. It was rooted so I flashed a 4.42 stock firmware back on, knox is already tripped. Apparently there's an update for the device and the msg when he tries to update is software has been modified. I download root checker and it is indeed no rooted. Any ideas?
Because knox has been tripped to 0x1, that phone can never updated via ota or the samsung app. You must now download a updated stock rom, or some other fancy rom. Untill someone can fix knox back to 0x0... This is the only way to upgrade.
Experienced this running stock rom and all (recovery, boot etc). But knox is already 0x1. When i was running XTC (Philippine stock kk rom) i get the message about modified software when checking with ota. But when I use XSG(is the csc correct for Singapore?) And try to do an ota it downloaded the update without a problem.
Heres what you can do use triangle away to reset thr binary recovery to official then flash stock rom and see if you can do an ota without any problems.
after modding i returned to stock to back warranty. i flashed stock firmare with odin.. now the status is official also for binary counter. but the samsung apps doesnt works!!! how can i do?
No processing performed is the error
Hello everyone
Sorry for my bad English but i really need help
Recently i bought g950f but it was have sim locked and twrp on it i decided to flash phone with latest firmware to remove twrp i download the firmware and flash it but after flash stuck on encryption failed message and ask me to reset the Device i factory reset and flash again and even wipe internal storage in twrp then flash but no thing happened and the message still showing please i need help to back my phone to life ..thank alot
I have a feeling because Knox counter is tripped, it is failing to encrypt, Use Odin and flash device back to factory condition. I have a feeling the Knox being tripped is your issue here.
sofir786 said:
I have a feeling because Knox counter is tripped, it is failing to encrypt, Use Odin and flash device back to factory condition. I have a feeling the Knox being tripped is your issue here.
Click to expand...
Click to collapse
i tried more than stock with no luck but i found a solution finally i flashed no-verity-opt-encrypt-5.1.zip by twrp and my proplem solved thank you any way and i hope i was helpful:fingers-crossed: