Develop Bugs

[Q] "Knox" firmware and the m919 version?

I have read (<here> and <here>)
about new firmware versions that will not allow resetting the counter (warranty flag) to initial conditions when restoring to stock after after unlocking or rooting.
If the phone developed a hardware problem, warranty repair could be denied.
The firmware version "MGG" and beyond are reported to have this problem.
Questions:
Does this also apply to the m919 T-Mobile version?
Has anybody seen it on an m919?
Is it going out with an OTA update?
Or is MGG specific to the i9505?
I am shopping for a GS4 m919, and I want confirm that it has the "pre-MGG" firmware version before purchase.
Questions:
Is the ID contained in the "Baseband" ID string in the phone information?
Are there different identifier strings used on the M919?

The T-Mobile S4 has not received the KNOX Bootloader, it will most likely come with the 4.3 update. If anyone is on stock, I would recommend you guys disable OTA updates as you may get automatically updated to 4.3 with the KNOX bootloader.

for once...im dreading an update from tmobile

If I've already rooted and installed a custom recovery (Clockwork Mod), and nothing else, does anyone know if the 4.3 update with KNOX will still be usuable? In other words, will the phone still get an automatic OTA update and will that update install correctly?
Sent from my SGH-M919 using XDA Premium 4 mobile app

DigitalHeretic said:
If I've already rooted and installed a custom recovery (Clockwork Mod), and nothing else, does anyone know if the 4.3 update with KNOX will still be usuable? In other words, will the phone still get an automatic OTA update and will that update install correctly?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It wont let you get the update it will pop a box up saying unable to uodate your device has been modified. . Try to check for an uodate youll see what im talking about... I went back to stock just to see if there was anything for updates which there wasnt andbwent to reroot and installed su abd it didn't flash correctly thru odin said to heck with it till the am checked for an update for giggles in the am and wouldn't even check
Sent from my SGH-M919 using Tapatalk

i'm glad I read this thread. i was going to wait until i tried the stock 4.3 update before deciding to root and install custom ROMs. With KNOX coming, I'm just going to root ASAP. I like PA on my Nexus4, so I'll probably go with that for my S4.

So you guys are saying the new update with "knox" won't allow you to reset the counter and only that or will it stop you from completely rooting and installing custom roms?
Sent from my SGH-M919 using Tapatalk

futty said:
So you guys are saying the new update with "knox" won't allow you to reset the counter and only that or will it stop you from completely rooting and installing custom roms?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Let me clarify some things. The KNOX processes and functions are already on the stock ROM, most devs remove them, though. So many of you with custom ROMs haven't seen anything related to KNOX.
What the new T-Mobile update (when it gets pushed out) is most likely to come with is a "KNOX Bootloader" which will introduce a thing called "KNOX Flag" which is similar to the old counter we're all used to. This is the counter that @Chainfire was successful in resetting with his app, Triangle Away.
Unfortunately, @Chainfire or anyone else for that matter, has not been able to reset the KNOX flag.
The KNOX flags is this:
0x0 = You have not tripped the KNOX flag.
0x1 = You have tripped the KNOX flag.
Again, once you trip that flag, rooting, flashing a custom recovery, etc.. there is NO way to reset it as of now. And any KNOX functionality on your phone will not work. But the worst part is Samsung will refuse warranty on your device if they see a 0x1 in your bootloader.
Another thing.. on the new bootloader, if you try to downgrade, even with an official Samsung firmware, it will fail and you will trip the KNOX flag.
So once you're on the new bootloader, there's no going back.
There's been speculation that there's an eFuse at play here.
Anyway, this is the reason why I am suggesting you all disable OTA updates and wait until a ROM is built without the new bootloader and all the functions (Wifi, MMS, etc.) are working.

mgbotoe said:
for once...im dreading an update from tmobile
Click to expand...
Click to collapse
Hey, its sammy we have to blame for this one :/ Not T-Mobile lol.
PSSSST! Don't let them know you are dreading it, or they might put it off longer xD
As to the OP.
The KNOX Warranty counter is rumored to be what is called an eFUSE. If this is true, then resetting the KNOX warranty counter will be impossible without taking apart your phone and replacing that specific eFUSE.
However, there are rumors that some root methods DO NOT trip this new counter. Is that good? Yes, is that bad? Yes. For those users who like stock kernels and just wanna root, this is okay for them. But for 99.999999 percent of us who love to flash new kernels and get more from our devices, then it trips the counter.
I personally congratulate Samsung as well as hate them at the same time for this. I congratulate them because what seems to be happening a lot is users flash a million and 2 things to their device having not one single clue what they are doing, thus bricking their 500+ dollar smartphone then claiming it as a warranty claim and getting another one. I also feel they are trying to flex their ego muscles too -.-
I also believe that if you have insurance, this does not apply. It is only for warranty claims. Which like you stated OP, it only means Samsung can choose to deny to repair or replace it. I have read a lot of thread before where users tripped the older binary flash counter, and still were given a new device. I honestly don't know how this is going to play out for the lot of us. For me, my warranty is over in a few months anyhow so i don't really care. But its still kind of a dickish thing Samsung is doing.
I am also hoping that we can extract the contents of the new update and keep our older bootloaders and create a flashable zip with the new update stuff and have it still work. I know there were some issues with the international S4 4.3 update but im not sure if it was entirely caused by the bootloader.

Exel said:
Anyway, this is the reason why I am suggesting you all disable OTA updates and wait until a ROM is built without the new bootloader and all the functions (Wifi, MMS, etc.) are working.
Click to expand...
Click to collapse
Where do you disable OTA updates on a stock S4?
Hitting "Software Update" takes me to a Boolean"Update Now" popup with no other option than choosing Yes, No or Wifi. No option to defeat future updates is offered.
Going into developer mode doesn't seem to add any pertinent options either (correct me if I'm wrong).
Clearly, Samsung doesn't want us to be able to disable updates unless or until we root, which I'm doing this weekend on the basis of this thread.

Reignogleph MMXI said:
Where do you disable OTA updates on a stock S4?
Hitting "Software Update" takes me to a Boolean"Update Now" popup with no other option than choosing Yes, No or Wifi. No option to defeat future updates is offered.
Going into developer mode doesn't seem to add any pertinent options either (correct me if I'm wrong).
Clearly, Samsung doesn't want us to be able to disable updates unless or until we root, which I'm doing this weekend on the basis of this thread.
Click to expand...
Click to collapse
You indeed have to root to disable OTA updates.

Once the update hits im going to extract the system.img to get all the files.
Then explore where all of the Knox crap is and get rid of it.
I know I want be alone in doing this...all who develop for the S4 will be on top of it.
Someone will figure out a way to get around this Knox BS...
Sent from a Insane S4
SICK MADE DEVELOPMENT

alloycowboy said:
Once the update hits im going to extract the system.img to get all the files.
Then explore where all of the Knox crap is and get rid of it.
I know I want be alone in doing this...all who develop for the S4 will be on top of it.
Someone will figure out a way to get around this Knox BS...
Sent from a Insane S4
SICK MADE DEVELOPMENT
Click to expand...
Click to collapse
thats fine and dandy for us with existing phones.. I already removed all the knox crap from my phone, and will update but not kernel and do the same..
But what about all future phones.. If indeed the kernel is locked with knox and there is no way to remove it we are screwed for new phones coming out.

lgkahn said:
thats fine and dandy for us with existing phones.. I already removed all the know crap from my phone, and will update but not kernel and do the same..
But what about all future phones.. If indeed the kernel is locked with knox and there is no way to remove it we are screwed for new phones coming out.
Click to expand...
Click to collapse
I agree. If thats the case....then alot of people will ditch Samsung.
But I have a feeling we will figure out Knox. Its man made so it can be hacked. Who when and how is the question.
Sent from a Insane S4
SICK MADE DEVELOPMENT

that's also why I paid 400 bucks for a T-Mobile sgs 4 and I am using it on at&t... I refuse to pay or support a phone with a locked bootloader.. matter of principle...i would ditch att if T-Mobile had decent service in my area.
Sent from my SGH-M919 using Tapatalk 2

Clarifications about KNOX and the S3

AFAIK nobody has asked anything about KNOX on the T999, so I have a few things I want to know before updating my phone to 4.3.
I bought my phone off-contract at full price and its flash counter has already been incremented many times from rooting, so I obviously don't care about setting the "KNOX warranty void" flag either, nor the enterprise-grade security features KNOX provides.
However, there is a rumor that once the KNOX warranty void flag is set to 0x1 you can't upgrade the ROM anymore, not even via Odin. Is this actually true? I know you can't OTA unless you're stock, but I don't care about OTA since I'd just upgrade via Odin anyways. But the fact you can't even upgrade via Odin seems a bit far-fetched.
Another variant of this rumor that seems more believable is that updating to a KNOX-enabled ROM also updates the bootloader to a KNOX-enabled variant, and that you can't upgrade to new KNOX-enabled ROMs if you decide to downgrade to a non-KNOX ROM after the bootloader has been updated. But if I never downgrade, can I continue to install updates, assuming Samsung releases ROMs for the S3 after 4.3?
Can anyone shed some light on this?

I somehow can't trust the first one. However the second one sounds more plausible. Anyway doc Holliday has removed KNOX from the most recent leaked Stock Rom. So this question becomes moot really.

Perseus71 said:
I somehow can't trust the first one.
Click to expand...
Click to collapse
Which is exactly why I asked this. I just wanted some more opinion.
Perseus71 said:
Anyway doc Holliday has removed KNOX from the most recent leaked Stock Rom.
Click to expand...
Click to collapse
And does this also mean that the bootloader isn't KNOX-enabled?

jim45 said:
Which is exactly why I asked this. I just wanted some more opinion.
And does this also mean that the bootloader isn't KNOX-enabled?
Click to expand...
Click to collapse
I don't think so. I flashed that Leak to test out the features. Afterwards flashed back my regular AOSP Rom.
NOTE - With the Leak, some reported that the Bootloader didn't get updated. I explicitly asked as well. If you are concerned with Knox'd Bootloader, you can Flash back UVDMD5 Bootloader too!

Here's what I know so far.
First, we do not have to worry about the Knox counter. One of my sources sent me a pic of their download mode and it was not there.
Second, I have reliable doubts that our official release will NOT include Knox. It's only included now for ease of using the same builds across multiple devices during internal testing.
Third, the bootloader is not included in any of the leaks. I do have a copy of it and have been considering releasing a recovery flashable firmware update, but haven't decided yet if I want to do this.
One of my sources ran into a problem at one point and soft bricked. Samsung simply connected remotely and flashed the firmware via Odin.
As for not being able to downgrade or flash certain things, I do not think this is the case at all. If you do something Knox doesn't like, it will lock down the secure containers it uses and you will not be able to regain access. I do not belie e it will restrict you from flashing something else, old or new, firmware or Rom, etc.
There is still a lot I do not know about it, but the information is out there. I stopped putting time into it when I found we probably won't need to worry about it anyway.
A quick Google search will net you more info, but if you really want an education on it I'd suggest visiting the S4 and Note3 forums. S4 users have been dealing with Knox longer than anyone, and the Note3 is the first device to ship with it fully implemented.
Sent from my SGH-T999 using Tapatalk

[Q] chainfire root

Just got two T-Mobile Note 3's and want to root them as I did our Verizon Note 2's.
Was watching the XDA video on using the chainfire method (which I used to root my Note
tablet) and it looks like the way to go.
That video came out in Oct of 2013. The little owners manual thingie that came
with the phones states that any "If unauthorized firmware is placed on the device it will not
work."
Question: Does anyone know if Samsung has buggered up the phone since October
so that the root no longer works, or am I still good to go?
Thanks!

dal71 said:
Just got two T-Mobile Note 3's and want to root them as I did our Verizon Note 2's.
Was watching the XDA video on using the chainfire method (which I used to root my Note
tablet) and it looks like the way to go.
That video came out in Oct of 2013. The little owners manual thingie that came
with the phones states that any "If unauthorized firmware is placed on the device it will not
work."
Question: Does anyone know if Samsung has buggered up the phone since October
so that the root no longer works, or am I still good to go?
Thanks!
Click to expand...
Click to collapse
You can root a couple different ways. It depends on if you want to trip Knox or not.

I literally just used chainfires auto-root via Odin and it worked fine
Sent from my SM-N900T using XDA Premium 4 mobile app

Beefvvl said:
You can root a couple different ways. It depends on if you want to trip Knox or not.
Click to expand...
Click to collapse
Thanks for the response, but I'll admit to being enough of a newbie not to know what you mean by trip Knox?

Knox is new Samsung secure environment, if you start flashing ROMS etc it will trip Knox flag which no one knows how to reset, if it ever can be reset. Samsung can and did refuse any warranty repairs if the Knox flag is tripped. As far as rooting goes if your firmware is below MJ7 I think, you won't trip the flag, if it's MJ7 and above the flag will be tripped I think. For example I have MI7 (last 3 digits of FW build) so I can root, without setting flag. Anyhow, I would suggest you read and learn as much as you can here, before you do something you can't undo.

I really wanted to wait until the 4.4.2 Kitkat update before I root.... but I can't wait.
I think I will cave in and get root this weekend!

If I decide to root my A5 2017 should I do it before I update it to the latest OS?

Hi, I wanted to know if I decide to root my A5 2017 should I do it before I update it to the latest OS? Also I'm not sure if rooting it would close me off from getting the update or connecting to the store, or if updating it after rooting it would undo the root.
Lastly, I understand that rooting the phone will void the warranty but I bought this phone off of someone I know who had it for 1 year so I don't know if I would be covered under a warranty or not.
Thanks.

Rooting usually locks you off from the updates, so you should definitely update first

Thanks, I did the main update but it now wants to install a 20MB security update. I wasn't sure if I should allow this or not since often these "updates" just block ways of rooting.
Also, does anyone know if I would even have a warranty? I bought the A5 2017 from someone else who had it for about 1 year.
Thanks

accessing google play store has never been an issue for me after rooting with latest updates , some advanced security features might get disabled but overall no big deal
i would take root anyday
i think rooting would render the warranty void by tripping the knox counter , setting "knox warranty void 0x1" , this cannot be reset , if your phone has not already been rooted at some stage before your ownership (knox 0x0) . so the question is has the warrany already been void by any previous rooting? if so .. no reason to not root a second time since warrany void cannot be undone if a new major firmware update comes out in the future for your phone or you just wish to go back to standard unrooted operation you can always re-flash manually (not OTA) with odin.
wipe data required , full clean flash with ODIN (in turn unrooting , but still knox remaining tripped 0x1 , but now with OTA re-enabled) and go back to OTA updates.
just make sure you follow the latest rooting guides after installing the latest security updates so you don't get temporarily locked out.
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
root and enjoy the benefits

Thanks. The previous owner had it for about 1 year and never rooted it so nox shouldn't be tripped as far as I know. Is there a way to check?
The phone is unlocked but in the developer settings "OEM Unlock" is set to disabled. Should I enable it? Will that trip nox?
I don't know if the bootloader is unlocked, if it even can be unlocked, or if that will trip nox.
Lastly, and I know this is sort of 'better late then never' but is there a site that would give me some sort of idea of what I could do with root that I can't do currently? I know I can remove bloatware but the A5 2017 seems to handle the installed software pretty well. For me it would be more about what it would open up for me for options. Running emulators for old games maybe? I dunno...
Thanks

Darkmatterx76 said:
Thanks. The previous owner had it for about 1 year and never rooted it so nox shouldn't be tripped as far as I know. Is there a way to check?
The phone is unlocked but in the developer settings "OEM Unlock" is set to disabled. Should I enable it? Will that trip nox?
I don't know if the bootloader is unlocked, if it even can be unlocked, or if that will trip nox.
Lastly, and I know this is sort of 'better late then never' but is there a site that would give me some sort of idea of what I could do with root that I can't do currently? I know I can remove bloatware but the A5 2017 seems to handle the installed software pretty well. For me it would be more about what it would open up for me for options. Running emulators for old games maybe? I dunno...
Thanks
Click to expand...
Click to collapse
If Samsung pay and s health work then knox isn't tripped. Doing the "OEM unlock" won't trip knox, but if you flash something nonstock, then it will. Once you do the "OEM unlock" switch bootloader is unlocked. And with root, there are a million ways to benefit from it. Just do a google search of things you can do with root and you will see a few things that are cool.(at least in my opinion) Good luck!
Sent from my SM-A520W using XDA Labs

help/info about samsung rooting

hello everyone,
I have and use android phones last 10+ years, always rooted. But I never had samsung phone.
Now I hear only half informations from my buddy, that its dangeous to root samsung because of knox (i dunno what knox even is).
So, now I'm thinking to buy S20 and want to root it, and my question is..:
If I root it, is anything ''broken'' on the phone ? Can phone still recieve official Samsung OTA updates?
What are minuses? what to look for? What about this "knox"?
Please need informaions

Well, I've owned a couple of Samsung devices over the years and I guess I can speak a bit from experience. Here's what you should know:
1.- U.S. phones have their bootloaders locked, so avoid buying a U.S. variant if you want to root it (some people want them for their Snapdragon chips)
2.- Knox is an e-fuse in the phone motherboard. Once you trip it by flashing custom software (root it), then that fuse will be tripped forever. You cannot get your Knox your status back to official unless you change the motherboard. Even flashing stock firmware will never get you this back to official.
3.- A lot of Samsung's security apps check for this fuse and will refuse to work if they detect that you've tripped it. Samsung Pay, Pass, Secure Folder are just some examples of features that will stop working when they detect a tripped Knox fuse. Some of these have bypass with root, but some don't.
4.- You will not get OTA updates with an unlocked bootloader, let alone root. It IS possible to get them back but only after flashing stock firmware and blocking the bootloader. These don't seem to check for Knox.

Understood, Thank You alot for informations and help!

ShaDisNX255 said:
Well, I've owned a couple of Samsung devices over the years and I guess I can speak a bit from experience. Here's what you should know:
1.- U.S. phones have their bootloaders locked, so avoid buying a U.S. variant if you want to root it (some people want them for their Snapdragon chips)
2.- Knox is an e-fuse in the phone motherboard. Once you trip it by flashing custom software (root it), then that fuse will be tripped forever. You cannot get your Knox your status back to official unless you change the motherboard. Even flashing stock firmware will never get you this back to official.
3.- A lot of Samsung's security apps check for this fuse and will refuse to work if they detect that you've tripped it. Samsung Pay, Pass, Secure Folder are just some examples of features that will stop working when they detect a tripped Knox fuse. Some of these have bypass with root, but some don't.
4.- You will not get OTA updates with an unlocked bootloader, let alone root. It IS possible to get them back but only after flashing stock firmware and blocking the bootloader. These don't seem to check for Knox.
Click to expand...
Click to collapse
Hiiii. I currently have a Samsung S20 and I have rooted it before. Once you root it Knox security will be tripped and you will not be able to get it back. This means you will lose access to apps like Samsung Pay, Samsung Pass and Samsung Health. You will not receive OTA updates if you're rooted, but if you flash stock firmware again and lock the bootloader you can start receiving updates again. I currently have a custom ROM installed and I have my ROM rooted. To me, it's been a great experience overall. I didn't really use the Knox features, so I didn't care much about losing it. I have loved rooting my S20 and using a custom ROM !!

victoriam8a said:
Hiiii. I currently have a Samsung S20 and I have rooted it before. Once you root it Knox security will be tripped and you will not be able to get it back. This means you will lose access to apps like Samsung Pay, Samsung Pass and Samsung Health. You will not receive OTA updates if you're rooted, but if you flash stock firmware again and lock the bootloader you can start receiving updates again. I currently have a custom ROM installed and I have my ROM rooted. To me, it's been a great experience overall. I didn't really use the Knox features, so I didn't care much about losing it. I have loved rooting my S20 and using a custom ROM !!
Click to expand...
Click to collapse
Actually you can use Samsung Health, just currently no version above 6.19 (2 versions behind current) until we find a way to patch it...i use it daily with my Watch 4 on Rooted S20+ 5G....

73sydney said:
Actually you can use Samsung Health, just currently no version above 6.19 (2 versions behind current) until we find a way to patch it...i use it daily with my Watch 4 on Rooted S20+ 5G....
Click to expand...
Click to collapse
Ohh okay !!! Thank you for letting us know !! I don't use Samsung Health so I had not tested it myself, but I had heard that Samsung Health doesn't work with root. Thanks for telling us it works fine !!

so, when rooted there are no OTAs.. thats a nono for me heh.. but question, if no OTAs come from mobile itself, is it possible to get uprades through PC then.. (Kies) maybe ?

maxis123 said:
so, when rooted there are no OTAs.. thats a nono for me heh.. but question, if no OTAs come from mobile itself, is it possible to get uprades through PC then.. (Kies) maybe ?
Click to expand...
Click to collapse
Yeah you can flash updates with something like Odin (never used Kies myself, I don't know if it still works)

maxis123 said:
so, when rooted there are no OTAs.. thats a nono for me heh.. but question, if no OTAs come from mobile itself, is it possible to get uprades through PC then.. (Kies) maybe ?
Click to expand...
Click to collapse
ODIN
Flash HOME CSC if you want to keep your data