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.
Related
Hello Guys,
Let's start with the story :
Old Bootloader, Stock Kernel , PhilZ CMW and Rom XXUDMBA with Chainfire Root.
Then i've installed through CMW the Know Free XXMI1, with Adam Kernel and Modem XXMI1 and still CMW Philz.
Suddenly my phone started to get crazy. Not able to receive calls, pohone freeze , screen blinking etc... Tried with factory and wipe but stucked on S4 logo (not even the samsung one)
Installed, through Odin, the MH8 pre-rooted, Modem MH8, Stock Kernel.
Now i've the new Bootloader, Knox Status stil 0x0, New Modem and New Rom. Everything is working but i've a question.
If i would like to have back the Philz Custom Recovery, flashing with odin, the Knox status will reach 0x1 ?
And why now my device says that my status is modified. I have stock kernel, recovery, rom (just knox free).
and if i would like to update the Rom with a stock one, with knox and all the other s***t, do i need to go necessary through Odin ? because OTA are compromised.
Last question is : Is the wifi-fix mandatory ? i don't know how to know if my wifi has problem. So far seems to work perfectly.
riccardoroma said:
Hello Guys,
Let's start with the story :
Old Bootloader, Stock Kernel , PhilZ CMW and Rom XXUDMBA with Chainfire Root.
Then i've installed through CMW the Know Free XXMI1, with Adam Kernel and Modem XXMI1 and still CMW Philz.
Suddenly my phone started to get crazy. Not able to receive calls, pohone freeze , screen blinking etc... Tried with factory and wipe but stucked on S4 logo (not even the samsung one)
Installed, through Odin, the MH8 pre-rooted, Modem MH8, Stock Kernel.
Now i've the new Bootloader, Knox Status stil 0x0, New Modem and New Rom. Everything is working but i've a question.
If i would like to have back the Philz Custom Recovery, flashing with odin, the Knox status will reach 0x1 ?
And why now my device says that my status is modified. I have stock kernel, recovery, rom (just knox free).
and if i would like to update the Rom with a stock one, with knox and all the other s***t, do i need to go necessary through Odin ? because OTA are compromised.
Last question is : Is the wifi-fix mandatory ? i don't know how to know if my wifi has problem. So far seems to work perfectly.
Click to expand...
Click to collapse
Modified because its pre-rooted...
Flashing anything through ODIN will change the void warranty from 0x0 to 0x1 unless its a stock rom (from MH8 up otherwise you will soft brick)....
You might be able to get rid of the modified status if you flash a totally stock rom but who wants to do that?
So the next question is :
If i would like to flash a new pre-rooted or custom rom i'll void my knox anyway. Because now i have stock recovery and this mean that i can flash only through Kies to a stock Rom right ?
Flashing a custom recovery with Odin (Knox 0x1)
Flashing a stock pre-rooted rom with Odin (Knox 0x1)
Flashing a stock rom newer then mine with kies or Odin (Knox 0x0)
am i right ? so i'm stucked on this ROM in other words, unless i'll just don't care about Knox.
Hi, quick question. I read that with Note 3, because all the stock ROMs are knox-enabled, I can upgrade by flashing via Odin (even if I have Knox tripped).
So this:
If you try to downgrade to KNOX-disabled system(MGA for example) your device will be flaged as KNOX Void Warranty 0×1 and will get a special lock – you won’t be able to update to any KNOX-enabled firmware even by ODIN.
Click to expand...
Click to collapse
doesn't apply because there aren't knox-disabled firmwares.
What about if I downgrade using Odin? By flashing an older firmware? If I'm not on the newer bootloaders I can, right? But will Knox be tripped?
I also read that if you try to flash a non-Knox firmware onto a Knox phone you'll be bricked. I can't remember which thread/what circumstances, so hoping someone can shed some light on that.
Lastly, if I'm on unrooted stock firmware, can I use URDLV to "patch" the newest firmware, then flash it to get the rooted latest firmware WITHOUT the newer bootloader and WITHOUT tripping knox? So I can choose to downgrade should the new firmware has any problems.
Situation on trip the Knox or not: (No idea on downgrade as I never try, I think it won't under same bootloader version)
Flash any stock ROM including Kitkat officially or not with odin without rooting - won't trip knox.
Officially phone came with MJ1 or older - root with URDLV won't trip knox.
Officially phone came with MJ7 or later - root with any method will trip knox.
Officially phone came with MJ1 but later updates to MJ7 with OTA/KIES/PC Odin and later - root with any method will trip knox.
Officially at MJ1 and rooted and update to any firmware excluding KitKat ROM using Mobile Odin Pro only - root will remain and won't trip the knox.
Install any custom recovery and custom kernel will trip the knox.
Update KitKat via Mobile Odin Pro (MOP) without trip the Knox:
Your current bootloader is not newer than MJ1.
Load Official Poland ROM in MOP
Enable EverRoot, Choose option "Download mode" in after flashing. Start flashing.
After booted into Download Mode, connect your phone to your computer and run PC Odin 3.09.
Load this bootloader http://forum.xda-developers.com/showpost.php?p=49425513&postcount=352 in the BL section
Check Phone Bootloader Update and F.Reset.time, un-check Auto Reboot and Start Flashing.
When Odin says RESET!, switch off your phone and reboot normally.
Hello.
I rooted my S5 when I first got it simply to use the volume boost mod. A week ago I decided to unroot so I can OTA update, ready for when major updates to the firmware on the phone are released. Anyway. An updated firmware became available so I tried to OTA update (not really expecting it to work) and got the "Modified firmware such and such" error come up. Obviously, rooting the S5 is different from the S3 due to the addition of Knox to the latest firmware, so I've got a few questions to ask.
Is there any way at the moment to reset Knox?
Does Knox stop you from being able to get OTA updates, even if you use TriangleAway to reset the flash counter?
Also. I checked today in Kies and it let me update my firmware but I didn't proceed with it because I'm worried about it bricking my device. I actually unrooted using SuperSU and checked the status of root afterwards using a Root Checker, which said I'm not rooted. Is it safe then to use Kies to install updates to the firmware instead of using OTA updates or will that brick my device?
rsdntbplr said:
Hello.
I rooted my S5 when I first got it simply to use the volume boost mod. A week ago I decided to unroot so I can OTA update, ready for when major updates to the firmware on the phone are released. Anyway. An updated firmware became available so I tried to OTA update (not really expecting it to work) and got the "Modified firmware such and such" error come up. Obviously, rooting the S5 is different from the S3 due to the addition of Knox to the latest firmware, so I've got a few questions to ask.
Is there any way at the moment to reset Knox?
Does Knox stop you from being able to get OTA updates, even if you use TriangleAway to reset the flash counter?
Also. I checked today in Kies and it let me update my firmware but I didn't proceed with it because I'm worried about it bricking my device. I actually unrooted using SuperSU and checked the status of root afterwards using a Root Checker, which said I'm not rooted. Is it safe then to use Kies to install updates to the firmware instead of using OTA updates or will that brick my device?
Click to expand...
Click to collapse
- Triangle Away doesn`t work with the S5 and neither us it possible to reset the KNOX flag
- Unroot with the Towelroot or superSU app (wich ever you have installed)
- Flash a stock rom (firmware)
- Data factory reset in recovery after the flash
- Done and now you can update with Kies/OTA.
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.
After 2 years being on a MDM bootloader to avoid knox ,i decided to flash it, to make lolipop roms work correctly. After flashing it I booted back to download mode to flash recovery and there are no signs of a knox counter there. I even checked the system and knox was installed under apps. Running danvdh's 5.0.2 GPE rom now. any ideas what is up?
Ok, somehow, bootloader and baseband didnt stick, any idea why?