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.
Related
Hi, I'm on NB4 KitKat rooted with Knox 0x0, and I'd like to upgrade to N9005DXUENE3 while preserving root. Is the procedure identical to upgrading from 4.3 to 4.4.2? Use Mobile Odin Pro, load firmware, reboot into download mode, use Odin to flash an extracted bootloader file, then reboot?
fterh said:
Hi, I'm on NB4 KitKat rooted with Knox 0x0, and I'd like to upgrade to N9005DXUENE3 while preserving root. Is the procedure identical to upgrading from 4.3 to 4.4.2? Use Mobile Odin Pro, load firmware, reboot into download mode, use Odin to flash an extracted bootloader file, then reboot?
Click to expand...
Click to collapse
Since you already are on the 4.4 bootloader files I would say 99.99% that you don't even need the final steps with normal Odin + bootloader files.
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.
hi,
my dad got i9515 4.4.2 with root and 0x0 and i really don't know how to update to 5.0.1 so the knox won't be 0x1 because of present time root the phone has.
kies update will only update the files but what about that root that is already on it? will it notice it and make 0x1 without root on 5.0.1?
what do odin? does flashing with odin is like fresh system so i just flash and it's 0x0 without root?
So many questions.
I'm not positive, but I don't believe you can use Kies on a rooted S4. It will pick up on the firmware status of "Custom" and not allow the update. OTA might work, but it may also check the firmware status, see that it's set to "Custom", and fail. Thus you should use Odin to do the update. If you do it through Odin you will not trip the Knox flag. You will however lose root and will need to root the device after the upgrade. Look through the forums as I'm not 100% sure on this, but to the best of my knowledge, there is no way to root Android 5.0.1 without tripping the Knox flag. I believe this is because the methods used to root without tripping the Knox flag no longer function on Android 5.0.1.
Morning everyone,
I have searched and searched, is it possible to root these A3's as yet?
I bought this s a replacement for my son as he broke his s5 mini sitting on it lol.
Best wishes
If tripping KNOX is not a worry, you can flash TWRP, and flash the SuperSU package. (Optionally, you can flash back the stock recovery, and retain the root.)
There is no solution without tripping KNOX yet, CF-AutoRoot has not been updated for A300FU Marshmallow yet.
PlutoDelic said:
If tripping KNOX is not a worry, you can flash TWRP, and flash the SuperSU package. (Optionally, you can flash back the stock recovery, and retain the root.)
There is no solution without tripping KNOX yet, CF-AutoRoot has not been updated for A300FU Marshmallow yet.
Click to expand...
Click to collapse
Hi,
I tried downgrading to lollipop without success, as it would stay on samsung logo.
So i had to use smart switch to re-install marshmellow.
Tripping knox is no issue, Therefore as supersu not been updated it would leave me with only option to go back to lollipop?
If so, is there a tut i could follow as doing usal way with odin etc did simply not work.
The A3 is on 02 network
Best wishes
Go for the 4 file package then, it is the only thing that keeps saving peoples phones around here.
Use SamFirm for to download them (make sure you tick binary update)