Related
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
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
Hey everybody,
I have a rooted N7100 on stock 4.3. I used triangle away and the normal counters are back to factory default. However the knox warranty void flag has been triggered.
Three questions:
- I'd like to receive OTA updates. But it looks like the knox flag is getting checked since I get "Your software has been mofified.." while checking for updates. Is there any way at all to remove the knox flag on a rooted note 2 with stock 4.3?
- If the question to above is a no, would flashing stock rom/bootloader all the way again patch the knox flag?
- If I'd like to flash my phone with the latest stock rom, I'm assuming the device gets wiped? Is there anything that'd let me backup my settings/files/apps/texts and have it restored once I flash the new rom? (I'm not sure if Titanium is the right software for this).
PS: My wararntly is long gone, but I'd like to have OTAs without having the phone wiped (like how I used to) OR manually flash the new stock ROMs without losing data. Any ideas?
Please help me out.
Thanks!
I have an issue with a modified status with a stock ROM, my device keep to say modified without root, I find out that the status revert back to normal without the SD Card.
It is to annoying to triangle away, disable root, remove sd card and update with ota. Now I download the update on Sammobile and I update with Mobile Odin.
Ba7oU said:
I have an issue with a modified status with a stock ROM, my device keep to say modified without root, I find out that the status revert back to normal without the SD Card.
It is to annoying to triangle away, disable root, remove sd card and update with ota. Now I download the update on Sammobile and I update with Mobile Odin.
Click to expand...
Click to collapse
Why bother at all, when your phone is no more warranty, 0 or 1 does not make a difference when u send in for repair, Samsung will still charge you for the service repair job.
Haha you're right, today I have a dual boot with 2 custom ROM. **** da police.
But I gave one OTA solution for the OP.
Hi guys,
I am new to the xda forums and I have been researching about rooting my note 10.1 2014 p600 (WIFI). I have three questions about rooting my device.
1. How would I update my tab with root? I heard you can't get OTA updates.
2. What is the best and safest way to root?
3. How do I get TWRP and is it good?
I haven't installed knox on it yet and I am a beginner to linux and have done research so I know what root is.
dudeian said:
Hi guys,
I am new to the xda forums and I have been researching about rooting my note 10.1 2014 p600 (WIFI). I have three questions about rooting my device.
1. How would I update my tab with root? I heard you can't get OTA updates.
2. What is the best and safest way to root?
3. How do I get TWRP and is it good?
I haven't installed knox on it yet and I am a beginner to linux and have done research so I know what root is.
Click to expand...
Click to collapse
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
1) Download this file https://dl.dropboxusercontent.com/u/11938873/CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here https://goo.im/devs/OpenRecovery/lt03wifiue/
That's all!
buhohitr said:
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
1) Download this file then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here
That's all!
Click to expand...
Click to collapse
Thanks! This is great help.
buhohitr said:
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
Click to expand...
Click to collapse
Knox is just a shortcut to the install link, Does this mean it's not installed or is the shortcut just extras (I don't know how to post screenshots).
dudeian said:
Knox is just a shortcut to the install link, Does this mean it's not installed or is the shortcut just extras (I don't know how to post screenshots).
Click to expand...
Click to collapse
I don't understand what you are saying???
When I said tripped Knox void warranty is that your device detected that you installed unauthorized software which tripped the knox counter. You can see this by boot into download mode (Odin mode) and you should see a line like this:
Warranty bit: 1 (factory is 0x0)
I hope that what you're asking!
buhohitr said:
I don't understand what you are saying???
When I said tripped Knox void warranty is that your device detected that you installed unauthorized software which tripped the knox counter. You can see this by boot into download mode (Odin mode) and you should see a line like this:
Warranty bit: 1 (factory is 0x0)
I hope that what you're asking!
Click to expand...
Click to collapse
Yup.
ok, now i'm getting confused.
my p600 is still on 4.3 jellybean. but from what i read, as long as did not update to kitkat firmware, i can still unroot and reverse the warranty bit bcoz they don't have knox yet. but it'll be too late if i updated to kikat right? btw, i used cf-auto-root.
just weeks ago i rooted my p600 and flashed stock recovery, so now my p600 thinks its stock official firmware, even say so in about device.
i haven't tried unrooting it yet to confirm that i can get warrenty back by flashing back whole stock firmware bcoz i don't want to redo all settings again. but thats the impression i'm geting.
anyhow if i can't really reverse that warranty thing i don't really care anyways. i warranty my stuff better than they do it, and since i think i can still get updates, it bothers me even less if its unreversible. but in the case if i'm right, and i can reverse that warranty bit. maybe one day i'd like to update to kitkat. then what? i'll have to have knox in my system and i can't reverse warranty counter anymore?
is there a way i can update to a custom kikat firmware (one day) and not have knox so i'll still be able to get warranty back?
i kind of realized the dilemma i have here since if i own the device for more than a yr, my warranty wouldn't matter anymore. am i just thinking too much and worrying myself?
kazukiflame said:
ok, now i'm getting confused.
my p600 is still on 4.3 jellybean. but from what i read, as long as did not update to kitkat firmware, i can still unroot and reverse the warranty bit bcoz they don't have knox yet. but it'll be too late if i updated to kikat right? btw, i used cf-auto-root.
just weeks ago i rooted my p600 and flashed stock recovery, so now my p600 thinks its stock official firmware, even say so in about device.
i haven't tried unrooting it yet to confirm that i can get warrenty back by flashing back whole stock firmware bcoz i don't want to redo all settings again. but thats the impression i'm geting.
anyhow if i can't really reverse that warranty thing i don't really care anyways. i warranty my stuff better than they do it, and since i think i can still get updates, it bothers me even less if its unreversible. but in the case if i'm right, and i can reverse that warranty bit. maybe one day i'd like to update to kitkat. then what? i'll have to have knox in my system and i can't reverse warranty counter anymore?
is there a way i can update to a custom kikat firmware (one day) and not have knox so i'll still be able to get warranty back?
i kind of realized the dilemma i have here since if i own the device for more than a yr, my warranty wouldn't matter anymore. am i just thinking too much and worrying myself?
Click to expand...
Click to collapse
Yes you're confused!!. Knox has nothing to do with warranty bit, once this tripped, you can't undo doesn't matter you on 4.3 or 4.4.
I'm a little confused on a few other issues. I have read over 40 pages on another thread here about rooting etc and I couldn't find the answer to a few questions. I've just successfully rooted using the most recent instructions (P600 - CF Auto root) but in earlier instructions (about a year ago) you had to also install the stock recovery file using Odin. Is that a necessary step? Is it needed for OTA updates? Since I've read that OTA updates will unroot and possibly prevent you from rooting at all, is it best to just forget about OTAs and flash up to date files from this site? Is it also prudent to turn off auto updating in the settings.
If I'm not installing custom roms and backed up using Titanium Pro do I really need to install TWRP? Any other benefits other than nandroid? Thanks
jbarr3 said:
I'm a little confused on a few other issues. I have read over 40 pages on another thread here about rooting etc and I couldn't find the answer to a few questions. I've just successfully rooted using the most recent instructions (P600 - CF Auto root) but in earlier instructions (about a year ago) you had to also install the stock recovery file using Odin. Is that a necessary step? Is it needed for OTA updates? Since I've read that OTA updates will unroot and possibly prevent you from rooting at all, is it best to just forget about OTAs and flash up to date files from this site? Is it also prudent to turn off auto updating in the settings.
If I'm not installing custom roms and backed up using Titanium Pro do I really need to install TWRP? Any other benefits other than nandroid? Thanks
Click to expand...
Click to collapse
Once you rooted you can't use OTA update any more. So the easiest going forward is to flash TWRP and use it to flash pre-rooted rom from this site.
Thanks buhohitr
I guess I'm installing TWRP tonight. There are many versions up to 2.8 I think. Which one do you recommend for P600? I've tried searching for "installing TWRP" but there were no obvious hits like there were for rooting. Which is the key thread?
To my first question, I'm assuming that the later root methods automatically installs or leaves the stock recovery as earlier methods needed to load it. Am I right?
jbarr3 said:
I've tried searching for "installing TWRP" but there were no obvious hits like there were for rooting.
Click to expand...
Click to collapse
OK found the thread and I just read the last 55 pages (that took a while) and boy is it scary. So many problems. Touch not accurate, inverted screens, certain versions failing eg 2.7, can't access external SD card, continual looping, booting into the old recovery , OTG cables not working, time zones can't be set properly, some say turn off autoboot in odin and some say don't change default settings etc etc. the list goes on and on. I likened it to a bushfire or tornado. Some houses still stand and some don't and you want to know the silly thing here, I am an experienced computer teacher with a degree in computer science and I've upgraded firmware on over a hundred devices over the years and yet all this rooting and recovery stuff is another world. The rooting process, admittedly, was a piece of cake and the instructions for flashing TWRP seems easy too but after that there seems to be so many problems. So hit and miss.
All i want to do is load TWRP on a P600. I will only load custom ROMs when a new firmware version comes out. Can someone alleviate my fears who has successfully loaded TWRP recently on a P600 using ODIN without massive tweaking to get it going. What version TWRP did you use and did you turn off autoboot or not?
PS Have I posted this in the correct section?
Took the plunge and loaded the latest TWRP 2.8.1 and it worked perfectly except I could only back to the main SD storage and not my extSD. I ended up, as a work around, moving the backup files to the extSD drive and PC.
I think I was worried unnecessarily.
Hi,
I rooted a new A3 (2017) sm-a320fl device for a friend using CF-Auto-Root from firmware.mobi.
However, it turns out that after tripping KNOX and blowing the eFuse automatic OTA updates are now broken.
Is there any way to return to OTA updates?
My friend would prefer to not have root and return to a newly flashed stock ROM rather than not receive automatic system updates. However, I'm not sure if this will be possible at all, now that KNOX is already tripped and eFuse blown?
And if there is no way to return to OTA updates, then what is the easiest way to install updates from now on?
I missed the whole KNOX/eFuse development and went ahead too quickly and thoughtlessly without thorough research and now I'm dreading that there may be no way back to a newbie-friendly device for my friend...
Hope some of you can help us out.
Greetings,
shevtak
Flash the latest firmware available for your country on Odin and your friend will gets updates again without root
Thanks for the quick response - I will try that.
But I'm still curious in case I run into this myself one day: Can you also tell me if there is a known place to get the update files from and install these manually on the CF-auto-root'ed system (i.e. using FlashFire)? So far, I was only able to find complete stock firmware images, but not update files...
shevtak said:
Thanks for the quick response - I will try that.
But I'm still curious in case I run into this myself one day: Can you also tell me if there is a known place to get the update files from and install these manually on the CF-auto-root'ed system (i.e. using FlashFire)? So far, I was only able to find complete stock firmware images, but not update files...
Click to expand...
Click to collapse
I don't recommend using FlashFire for flashing updates or so. With an locked bootloader it's highly to hard brick your phone ?. And yeah the only way to get the OTA's back is to flash the official firmware via Odin. A good rooting method is Magisk, you should try it out!