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.
Related
Hi, i have note 3 sm n9005 or something and rooted my phone for some stupid reason, its still on stock the only thing that i think happened was i have supersu, i paniced and factory reset, now supersu has a error thing with something to do with binary settings or something. All i want to do it fully reset my phone, if its any help im british with EE... does flashing supersu trip knox counter? Am i actually rooted for if i were to flash stock? Will that trip it? Iv knly had phone few months and im scared... if i flash stock can i then update legally coz i cant update because the device is modified? I used odin... can someone help please, i know nothing and yes, i should look into what im doing more before hand. Can you explain everything and what to do please? Every little thing, please and without tripping knox and as if it was out the box new. Please
Firstly, flashing SuperSU trips KNOX. In the first place, to install SuperSU you need a custom recovery which would ALSO trip KNOX. Flashing back to stock unroots your phone too.
If you are convinced that you have not tripped KNOX, just re flash your phone back to stock with ODIN.
This_Guyse said:
Firstly, flashing SuperSU trips KNOX. In the first place, to install SuperSU you need a custom recovery which would ALSO trip KNOX. Flashing back to stock unroots your phone too.
If you are convinced that you have not tripped KNOX, just re flash your phone back to stock with ODIN.
Click to expand...
Click to collapse
I dont have a clue what i first did but what i did magically apeared with supersu. Can i flash stock which will get rid of supersu and can i reset my knox counter? And am i actually rooted seen as i factory reset?
MarkDyer1 said:
I dont have a clue what i first did but what i did magically apeared with supersu. Can i flash stock which will get rid of supersu and can i reset my knox counter? And am i actually rooted seen as i factory reset?
Click to expand...
Click to collapse
Flashing stock will get rid of SuperSU and root but you cannot reset KNOX. It is permanently 0x1 and will always be.
This_Guyse said:
Flashing stock will get rid of SuperSU and root but you cannot reset KNOX. It is permanently 0x1 and will always be.
Click to expand...
Click to collapse
What about the fact i factory reset? Is it still rooted to flash stock? And doesnt it have to be a unrooted stocked rather than flashing rooted stock? And where do i got stock and do i need to unzip files and stuff?
MarkDyer1 said:
Hi, i have note 3 sm n9005 or something and rooted my phone for some stupid reason, its still on stock the only thing that i think happened was i have supersu, i paniced and factory reset, now supersu has a error thing with something to do with binary settings or something. All i want to do it fully reset my phone, if its any help im british with EE... does flashing supersu trip knox counter? Am i actually rooted for if i were to flash stock? Will that trip it? Iv knly had phone few months and im scared... if i flash stock can i then update legally coz i cant update because the device is modified? I used odin... can someone help please, i know nothing and yes, i should look into what im doing more before hand. Can you explain everything and what to do please? Every little thing, please and without tripping knox and as if it was out the box new. Please
Click to expand...
Click to collapse
Reboot in download mode I. E. Volume down+home+power, check the knox counter if it's 0x1 then it has already been tripped and you have been set free ?? and if it's 0x0 you are still locked in a cage.
Report back with what you see.
saadramiz said:
Reboot in download mode I. E. Volume down+home+power, check the knox counter if it's 0x1 then it has already been tripped and you have been set free ?? and if it's 0x0 you are still locked in a cage.
Report back with what you see.
Click to expand...
Click to collapse
I know i have done something coz when i want to update it says this device has been modified. But i havent flashed any roms so surely knox should be 0x0 and flashing stock keeps it 0x0 doesnt it?
MarkDyer1 said:
I know i have done something coz when i want to update it says this device has been modified. But i havent flashed any roms so surely knox should be 0x0 and flashing stock keeps it 0x0 doesnt it?
Click to expand...
Click to collapse
Yes, if your Knox is still 0x0, flashing stock keeps it 0x0.
Use Phone INFO ★Samsung★ app to check for the Knox Warranty Void status (in the GENERAL INFO section).
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.
So, a long time ago I towelrooted my gs5 on 4.4.2 and just left it like that (no custom rom , kernel, or bootloader). I recently upgraded to an N6 and would like to sell the old phone now. I'm trying to return to stock, but my craptop died and I'm not able to Odin a stock .tar file. I've already used 'full unroot' in SU, but I'm still showing 'Custom' status. I can't OTA and I can't find a stock rom to flash from the factory recovery, so are there any other options I'm missing?
Thanks in advance!
Just factory reset it from stock recovery
*Detection* said:
Just factory reset it from stock recovery
Click to expand...
Click to collapse
Thanks for the reply. I actually tried factory resetting through the settings menu and the stock recovery. Both leave me with a 'custom' status and unable to OTA.
I'd suggest using ODIN to flash a stock ROM from sammobile dot com, but with it being Verizon, it's likely got a locked bootloader, and I'm not sure if you can flash anything with ODIN when the bootloader is locked, worth a try though, it'll just fail with an AUTH! if it doesn't work
Instructions are under the download on their site
if u rooted and trip your knox into 0*1 your are nvr getting OTA updates for my knowledge
vinura kithmal said:
if u rooted and trip your knox into 0*1 your are nvr getting OTA updates for my knowledge
Click to expand...
Click to collapse
Wrong, I tripped KNOX ages ago and can still receive OTA updates fine if I'm on 100% stock
*Detection* said:
Wrong, I tripped KNOX ages ago and can still receive OTA updates fine if I'm on 100% stock
Click to expand...
Click to collapse
i did not get any
thts why
sorry
Hi
I have a new Samsung S4 (i9505) (yep - new with waranty, apparently). The phone came with Lollipop but I downgraded to Kitkat (4.4.2) to root without tripping Knox.
I have successfully rooted (after several soft bricks) and my Knox counter remains at 0x0 - but I cannot boot to recovery (the phone says "recovery booting..." in blue small text at the top but then goes to a normal boot with boot loop). I can boot in to the normal mode, and can boot to safe mode, and can boot to download mode - but not to recovery. And cannot factory reset the phone (from settings - the procedure just leaves the phone as it is). I have tried (successfully) to flash the Lollipop bootloader, and have tried (unsuccessfully) to flash the image file extracted from the stock lollipop ROM (extracted recovery.img, used 7zip to create a tar file, and tried flashing as AP with Odin 3.09 but it fails to write the file)... I also tried the OTA update back to Lollipop (using the settings, update option on the phone) but that too failed.
The phone seems to work but I just cannot get in to recovery mode (and cannot factory reset the phone). I am using the original usb cable and a usb port directly connected to the mother board (and have successfully flashed other components). Any suggestions as to how to re-enable or restore the recovery (without tripping Knox warranty counter)?
Many thanks for any help
Flash the whole firmware with Odin.
Custom recovery is a no-go as it will trip Knox.
GDReaper said:
Flash the whole firmware with Odin.
Custom recovery is a no-go as it will trip Knox.
Click to expand...
Click to collapse
Thanks for that.
I was leaving a complete reflash to Lollipop (with Odin) as a last resort - as this would cause me to lose root. However, yesterday I chose the backup function on FlashFire to backup (to the external SD card) the phone with Kitkat and root and... following the backup, all apps (system and user) fail on boot so I have no option but to reflash anyway (worked without issue). Not sure what happened with FireFlash - all I did was to select backup - but is must have affected the phone in some way... I guess it is incompatible with the S4 or Kitkat (or both).
I am still confused: what will have prevented the phone from booting to recovery with the Kitkat image (and prevented me from reflashing the stock Lollipop recovery via Odin)? And what is the issue with FireFlash (I can not understand why taking a backup should cause a problem when rebooting the phone).
I will start again trying to gain root without tripping Knox (downgrading to Kitkat, using TR to root, then, hopefully, upgrading via Mobile Odin with everroot)...
Thanks again for your help.
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
GDReaper said:
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
Click to expand...
Click to collapse
Thanks again for your response. When I tried removing Knox with the Knox removal script in Mobile Odin having downgraded my device to Kitkat, I got a soft brick which did take a while to fix (but did get fixed eventually). I had thought of perhaps trying to upgrade from rooted Kitkat to Lollipop using FireFlash but was a bit disconcerted at the way it crashed my device when I only tried backing up the phone (and not flashing anything at all) using it.
Do you know whether the issue I had with FireFlash is indicative of FireFlash being incompatible with my device or is the symptom I had just something that may randomly occur (ie is there any point trying to use FireFlash upgrade from rooted but not Knoz tripped 4.4.2 to rooted and not Knox tripped 5.01)?
Many thanks for all your help and best wishes, Boris.
bprtzel said:
Thanks again for your response. When I tried removing Knox with the Knox removal script in Mobile Odin having downgraded my device to Kitkat, I got a soft brick which did take a while to fix (but did get fixed eventually). I had thought of perhaps trying to upgrade from rooted Kitkat to Lollipop using FireFlash but was a bit disconcerted at the way it crashed my device when I only tried backing up the phone (and not flashing anything at all) using it.
Do you know whether the issue I had with FireFlash is indicative of FireFlash being incompatible with my device or is the symptom I had just something that may randomly occur (ie is there any point trying to use FireFlash upgrade from rooted but not Knoz tripped 4.4.2 to rooted and not Knox tripped 5.01)?
Many thanks for all your help and best wishes, Boris.
Click to expand...
Click to collapse
Sorry - FlashFire not FireFlash!
Mobile Odin and bricked phone?
GDReaper said:
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
Click to expand...
Click to collapse
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
bprtzel said:
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
Click to expand...
Click to collapse
I tried to update my modem and bootloader with it. I also was on a custom ROM.
bprtzel said:
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
Click to expand...
Click to collapse
Just to say I finally got my phone to Lollipop (5.01) rooted with Knox guarantee void remaining at 0x0.
I downgraded (again) to 4.4.2 with Odin, installed the GF1 kernel, used towel root (my wifi was still working though it would not remember the wifi passwords), the used FireFlash to upgrade back to stock 5.01 plus SU beta.zip as OTA/ZIP. All worked great - except I now cannot get the wifi to switch on. Used Odin to load the Lollipop BL and also Lollipop kernel, and did a factory reset for good measure too but still no wifi... (can't switch the switch to on). Guess I will try the GSM modem to just to see if that helps (unless anyone has other suggestions)...
Sorry if this is a noob question but I've been away for a while...
I flashed TWRP and rooted my S7 Edge, I also disabled encryption in the process and, of course, tripped the knox counter.
If I download the latest stock fw for my country from sammobile and flash it through ODIN I know it will not reset the counter but will it re-enable encryption of my device?
uishido said:
Sorry if this is a noob question but I've been away for a while...
I flashed TWRP and rooted my S7 Edge, I also disabled encryption in the process and, of course, tripped the knox counter.
If I download the latest stock fw for my country from sammobile and flash it through ODIN I know it will not reset the counter but will it re-enable encryption of my device?
Click to expand...
Click to collapse
Yes. Device will be wiped and encrypted again. Just make sure you use CSC and not HOME_CSC. HOME_CSC doesn't wipe the device, which is what you need to become encrypted.
uishido said:
Sorry if this is a noob question but I've been away for a while...
I flashed TWRP and rooted my S7 Edge, I also disabled encryption in the process and, of course, tripped the knox counter.
If I download the latest stock fw for my country from sammobile and flash it through ODIN I know it will not reset the counter but will it re-enable encryption of my device?
Click to expand...
Click to collapse
yes