I just got my new S4 recently and I took the 4.4.4 update that was avaliable for it. I have been reading on here for hours about how if you root it/upload custom boot loader it'll trip knox.
Could someone answer me a few questions. I would really appreciate it!
Does knox matter if you don't have a warranty etc?
Is there a way to go ahead and root 4.4.4/NH7 without tripping knox or at all?
Also, is there custom boot loaders and all that for this update as well?
1) nope.. only if it still has Samsung warranty
2) not at the moment
3) no, they are not needed
Someone reset Knox on note 3 exynos.......
Related
I'm currently using stock MF6 firmware and there is no indication of the Knox warranty void flag in download mode. Does anyone know which firmware introduced this flag on the S4 mini or is it not implemented, yet? I'm asking because I want root access and need to know which prerooted firmwares I can choose from without this flag.
kodan2k said:
I'm currently using stock MF6 firmware and there is no indication of the Knox warranty void flag in download mode. Does anyone know which firmware introduced this flag on the S4 mini or is it not implemented, yet? I'm asking because I want root access and need to know which prerooted firmwares I can choose from without this flag.
Click to expand...
Click to collapse
As far as I can tell, there's no Knox flag known on any S4 mini firmware or variant. Definitely mine has no sign of it either. And from what I read, at least ith the S4 it was never transparent, only when the flag appared could you kill it, in older firmwares no matter what you did the flag was never set until you upgraded and there was something considered wrong then.
4.4 is supposed to bring Knox for the mini so it may bring the flag, which could be easier, harder or the same to avoid as the S4, only time will tell I guess. If it's similar, hopefully enough will have been learnt by the time S4 mini get 4.4 that we can easily get around it.
@Nil Einne
Thank you for your reply. Which firmware version are you using?
(I9195XXUA)MG3 (which is 4.2.2 / JDQ39). It's currently the latest for my CSC. I may root soon perhaps using a prerooted firmware (since mine is so old) but I'm waiting to see if anyone has tried it on a 16GB version. I didn't mention before but I guess it's clear now I have an I9195 but I haven't seen any mention of Knox flag seen for any variant of the S4 mini on current firmwares.
My s4 mini (I9195) came with firmware MF7 and was upgraded OTA to MG8.
After that I flashed with Odin to MH2 (Android 4.2.2).
Thereafter I flashed a custom rom (Slim with 4.3.1).
Where and how can I see whether my Knox warranty void might be 0x1 now.
And what if I flash back with Odin to firmware MF7?
Is that still possible without a later upgrade problem?
Curious about your info.
New Rom XXUBMJ7 whit KNOX bootloader (aboot.mbn) and aplications.
After flash this Rom we have on Download Mode:
KnoxKernelLock: 0x0
KnoxWarrantyVoid: 0x0
Like on Note 3 N9005, if we flash something, customer, root, KnoxWarrantyVoid: go to 0x1 and this is not reversible.
To Root
The Root-Kit-V1 install all superuser, SU and busybox but after reboot the SuperSU can't access to system, KNOX not permit.
To solve this we must flash after, on recovery the UPDATE-SuperSU-v1.65.zip from Chainfire. After we have root alright.
My case like on Note 3:
I not need the KNOX, the phone is only for me, then after root I delete all KNOX apk + odex from system/app.
Good luck
Is it possible to go back to old bootloader WITHOUT knox?
ladislav.heller said:
Is it possible to go back to old bootloader WITHOUT knox?
Click to expand...
Click to collapse
See response on Development Thread to this your question.
Always the KNOX:
You can read this post Always the KNOX.
Many info about KNOX.
Hi all
Quick inquiry and I didn't see an exact answer to a question that I have. So I have a note 3 rooted and knox flag currently set to 0x0. I was reading I think on here and some other fourms that knox has locked the bootloader. I want to flash a custom recovery and I know it will trip the knox flag. Is the bootloader locked already or am I able to load custom recovery without any issue?
Do you have the T-mobile version? If so, then no, the bootloader is NOT locked.
Flashing a custom recovery WILL trip the Knox flag though.
idtheftvictim said:
Do you have the T-mobile version? If so, then no, the bootloader is NOT locked.
Flashing a custom recovery WILL trip the Knox flag though.
Click to expand...
Click to collapse
Hi. I kind of in the same situation.
I am a Note 2 user since it came out and have tried many ROMs without problems. I recently upgraded to Note 3 and I haven't touched anything (rooting and flashing) because I remember reading before about some problems with Knox and eFuse or something. I got a T-Mobile note btw.
Do I have to treat Note 3 differently when rooting and flashing because of this knox, efuse issues?
I tried to look for a clearer answer but I'm still hesitant to proceed. Or is the process the same as rooting and flashing ROMs on Note 2?
Also, I have a Jump insurance with TMO, is this going to have some problem if later I have to claim replacements or upgrade? Thanks a lot. Really appreciate the help.
jinda628 said:
Hi. I kind of in the same situation.
I am a Note 2 user since it came out and have tried many ROMs without problems. I recently upgraded to Note 3 and I haven't touched anything (rooting and flashing) because I remember reading before about some problems with Knox and eFuse or something. I got a T-Mobile note btw.
Do I have to treat Note 3 differently when rooting and flashing because of this knox, efuse issues?
I tried to look for a clearer answer but I'm still hesitant to proceed. Or is the process the same as rooting and flashing ROMs on Note 2?
Also, I have a Jump insurance with TMO, is this going to have some problem if later I have to claim replacements or upgrade? Thanks a lot. Really appreciate the help.
Click to expand...
Click to collapse
Well, from where we are right now with the Knox counter, if you flash ANY ROM or Kernel, then the Knox will trip, and will void your warranty. You can root using Root de la vega, or Kingo root without tripping the Knox counter.
I am not sure from a T-Mobile standing if they will give you a hard time with warranty if the Knox is 0x1. I have tripped my Knox counter, and have Jump also, but I honestly don't care. I am sure that SOMEHOW in the future we will be able to reset the Knox counter....I hope anyways.
Did that answer your question?
idtheftvictim said:
Do you have the T-mobile version? If so, then no, the bootloader is NOT locked.
Flashing a custom recovery WILL trip the Knox flag though.
Click to expand...
Click to collapse
I have note 3 with tmobile. Thanks for the help
idtheftvictim said:
Did that answer your question?
Click to expand...
Click to collapse
Yes you did! Thanks a lot. Important thing is at least I can root. I think I'll be happy with the stock TW, I'll just install some launcher instead.
But I need root for TB and other stuff.
Thanks!
Phone was lost, just got replacement this morning.
My last S4 had been rooted running custom firmware for months w/o issue.
Read through a bunch of threads, ranging from the opinion that the bootloader change + knox wont be a big issue to the sky is falling.
Is it recommended to root my phone at this time, I do have JUMP and would be replacing it once something better comes out? The phone is running 4.2.2, caught it trying to update to already.
Thanks.. I know this may seem redundant but haven't been active on these boards since I got my CFW going. Not seeking help in flashing or anything.. just advice
skrewler said:
Phone was lost, just got replacement this morning.
My last S4 had been rooted running custom firmware for months w/o issue.
Read through a bunch of threads, ranging from the opinion that the bootloader change + knox wont be a big issue to the sky is falling.
Is it recommended to root my phone at this time, I do have JUMP and would be replacing it once something better comes out? The phone is running 4.2.2, caught it trying to update to already.
Thanks.. I know this may seem redundant but haven't been active on these boards since I got my CFW going. Not seeking help in flashing or anything.. just advice
Click to expand...
Click to collapse
Up to you. If the stock rom is bearable and you wanna run the 4.3 stock rom then by all means, go for it.
skrewler said:
Phone was lost, just got replacement this morning.
My last S4 had been rooted running custom firmware for months w/o issue.
Read through a bunch of threads, ranging from the opinion that the bootloader change + knox wont be a big issue to the sky is falling.
Is it recommended to root my phone at this time, I do have JUMP and would be replacing it once something better comes out? The phone is running 4.2.2, caught it trying to update to already.
Thanks.. I know this may seem redundant but haven't been active on these boards since I got my CFW going. Not seeking help in flashing or anything.. just advice
Click to expand...
Click to collapse
Being that your'e using the T-Mobile M919, the whole KNOX bootloader situation doesn't pertain to you as long as you're sure you're on 4.2.2. Root it, flash it, theme it with Hello Kitty... whatever, it doesn't matter; you can still revert back to stock and reset any tripped counters. 4.3 is when the problems begin and the KNOX counter is implemented and can't be reset.
lordcheeto03 said:
Being that your'e using the T-Mobile M919, the whole KNOX bootloader situation doesn't pertain to you as long as you're sure you're on 4.2.2. Root it, flash it, theme it with Hello Kitty... whatever, it doesn't matter; you can still revert back to stock and reset any tripped counters. 4.3 is when the problems begin and the KNOX counter is implemented and can't be reset.
Click to expand...
Click to collapse
I second this.
SO LONG AS YOU ARE ON 4.2.2
- You can root flash do whatever, theme with hello kitty or barbie xD like lordcheeto said or keep it stock
- Install recovery and flash away.
- Will always be able to revert back to 100 percent stock
TAKE 4.3 UPDATE
- I think you are still able to root it without tripping knox counter. Can't remember the last status of that was. But as long as you root it without a custom recovery, i think you are ok. From what i can remember, the bootloader checks the recovery status and trips the knox counter based off the recovery that is on the device. If its different then stock, it trips. But double check with Google about this first.
- If you trip knox counter, you will NEVER (as of now and possibly forever) get it back to zero.
Rooting with safe root won't trip knox and also disables it. But recoveries, kernels, roms, etc will trip the flag
Sent from my SGH-M919 using Tapatalk
Root it with chain fire and never look back.
You're on 4.22, so you're golden. Just flash a rooted stock ROM that's on 4.3 and you'll avoid Knox.
I'm running 4.4.2 and never seen this Knox stuff.
Sent from my SGH-M919 using XDA Premium 4 mobile app
elesbb said:
- I think you are still able to root it without tripping knox counter. Can't remember the last status of that was. But as long as you root it without a custom recovery, i think you are ok.
Click to expand...
Click to collapse
ShinySide said:
Rooting with safe root won't trip knox and also disables it. But recoveries, kernels, roms, etc will trip the flag
Click to expand...
Click to collapse
Correct. I've rooted my my second GS4G on 4.3 MK2 and it did not trip the KNOX counter. If you're still on 4.2.2 MDL, then there is no need to update your bootloader. Simply flash ROMs through recovery and flash the 4.3 modem. You will have the goodness of 4.3 on KNOX-less 4.2.2 bootloader. :highfive:
Hello,
Seeing how future updates to the Note 3 supposedly causes the knox warranty void flag to be tripped for rooting with RDLV... Is it a good idea to root our devices now while we can? As in, rooting before one of these updates will both keep root on the device and have knox warranty flag 0x0 after updating to kitkat?
Bumping! I suppose it would be easy for Samsung to release an update that triggers knox counter if root is detected... I've never rooted a device though. So my question is do phones keep root when you receive an android update?
If you are rooted, you normally don't want an update over the air. There so far have been no updates to the T-Mobile version of the note 3 though.
Well I was wondering about that as well. I keep reading that the Tmo Note 3's bootloader is unlocked. If it is truly unlocked would it not matter to take updates as we should be able to continue to root and put a custom recovery back on the phone? I mean i personally would wait to know if it is safe to take an OTA before actually taking it. I came from the VZW S4 which had that crazy locked down bootloader after the 1st OTA (I luckily never took an OTA and it's on the original FW). I mean I guess they can always lock down a bootloader on any OTA but why would they if it came already unlocked?
All the ota does is download via wifi or data for the update...that is the only difference... it doesn't do any extra checking or anything like that. The only thing that will happen is after the update has been downloaded it will flash your phone and then it will erase root because it will be flashing the phone back to a stock new firmware. You then would have to root your phone again.
Sent from my SM-N900T using XDA Premium 4 mobile app
re: rooting
Dreamgun said:
Bumping! I suppose it would be easy for Samsung to release an update that triggers knox counter if root is detected... I've never rooted a device though. So my question is do phones keep root when you receive an android update?
Click to expand...
Click to collapse
If you are rooted and you accept an OTA or KIES update or if you Odin flash official
stock firmwareyou will lose root but you can root the phone again if you want.
Fortunately all the cwm/twrp flashable custom roms found here in XDA
all come pre-rooted and if you flash one of those you will not lose root.
Either way you will trigger the KNOX if you flash kernels, custom roms or custom recoveries.
The only two things that KNOX does is it prevents you from downgrading to an older version
of the rom and or firmware as well as the possibility of voiding your warrany if you have one.
Good luck!
Hello everybody,
My current device is a Captivate, and I'm thinking about upgrading to an i747. After doing some research in the forums I found out about knox, but find it a little bit confusing, let's see..
1) Has there been any known cases of devices that were shipped with a knox bootloader?
2) In a i747, what does a knox bootloader look like in Download Mode (as opposite to a non-knox one, does it say knox warranty void or something else?)
3) This is where I'm most confused. If you've got a knox bootloader, then you can't downgrade it, and can't flash anything except for new official otas? would anything except the ota void it? can you flash CM11 for example? and if it's void, that means that it's a hard brick? or does it still work? Can you go foward if it's void (again, like cm11)?
4) Let's say the one I get comes with 4.0, I can root and move freely between CM and stock as long as I don't flash 4.3?
I also have the option to go for a S4 Mini, but given it has the same issue and similar hw.. love the S3 screen
Thanks in advance!
Samsung s3, s4, Note 3, etc. that shipped with 4.3 will include Knox.
If the device shipped with Knox, you will see something like warranty bit in the text at the top of the download screen.
If you have a knox bootloader, you cannot downgrade to an earlier bootloader but you can still install a custom recovery and custom ROMs which voids the warranty but does not brick the phone.You can flash any ROM you want with a 4.3 Knox bootloader as long as the ROM does not try to flash a new bootloader.
If you have a stock 4.3 phone and try to load anything that is not official Samsung software, it will trigger the knox counter (change from 0 to 1 or 0x0 to 0x1) and void your warranty. At the moment, there is no way to reset the knox counter to 0.
Yes, if you get a 4.04 phone, you can install a custom recovery, custom ROM, and move freely among custom ROMs if these ROMs are support but the installed bootloader.
I have done all of this with an i747m (Bell version of the s3).
That's crystal clear, I was confused and thought that if you had knox and flashed anything else over it it would brick... but I see now, just avoid bootloaders.
Thanks!