So I have a problem guys, I'm going to tell you all the long story, I just recently bought a S4 from Telcel in México, LTE edition, the model is SGH-I337M, and came with build I337MUMUAMG1, 4.2.2.
I was anxious to tinker with it, so first thing I did as soon as I came home was rooting it with CF-Auto-Root, everything until that point was smooth sailing, but I couldn't make the I337M version of Philz Touch Recovery to flash via Odin, so I flashed the GT-i9505 version and IT WORKED, it booted to recovery normally, rebooted to system, etc. So I thought "oh boy, I'm ready to go". But before that, I read that for data & Wi-Fi to work properly in 4.3 Custom Roms I had to flash the 4.3 modem.bin file via Odin, so I did that. No OTA, no 4.3 Stock Rom, only the modem-bin file. The modem version never changed in the "About Device" tab to "I337MVLUEMK6" like it was supposed to do, it stayed as "I337MUMAMB2" but I also read that was normal so I didn't think about it much.
After that I went into recovery with my ready-to-flash files in my SD, wipe my system/data/cache/etc without making a Backup because that's how retarded I am and try to flash my ROM only to get it aborted every time due to "assert failed: getprop("ro.product.device") == "jfltecan" ||" issues, so I assumed it had to do with me using the GT-i9505 version of Philz Touch with a I337M Canadian Custom ROM. I shat bricks for a while because I had wiped my system and I had no backup, so I just turned my phone off, downloaded the "I337MUMUAMG1" Telcel Stock Rom, turned on my phone in Download Mode and flashed it via Odin while I prayed.
It worked, it booted, everything was alright with the world again (but not so much on my pants where tons of bricks were shat), I had voided my warranty but whatever, I was gonna Root and Triangle Away that thing to make my phone fully stock again, so I get ready to do exactly that, get my phone into Download Mode, and Root it with CF-Auto-Root, again, it worked, it booted, and had the SuperSU icon, smooth sailing again, OR SO I THOUGHT.
I open SuperSU to update dem binaries and a pop-up emerges saying that Samsung Knox had been detected and if I want to attempt to disable it. Oh boy, I was not ready for this, I hadn't recovered from the last shatbricking session, and now my pants were a national disaster area. Anyway, I also read that using Triangle Away with a Knox enabled phone was a highway to a very expensive paperweight, so thankfully I was smart enough to don't try it.
As I kept shatting bricks I decide to reflash the Stock "I337MUMUAMG1" Telcel Rom via Odin to keep my phone as safe and near stock as possible, everything worked, and now I'm running the "I337MUMUAMG1" build, with no root, stock, with yellow triangle and apparently, Knox. :crying:
I got curious about it, so I went into Download Mode to search for the Knox Warranty Void Flag... But I didn't got it, neither the Warranty Bit. On Download Mode I get only the Usual:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
USB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
And I don't have any Knox apps on my drawer, but they appear on the "Application Manager -> All" menu, so I'm confused as hell, and since I can't check my Bootloader version I can't know if I have Knox on my bootloader or only on my Rom. And I'm way to scared to try anything, and also scared about OTAs and updates since I don't know the state of my phone. Any help on this?
tl;dr: Got brand new SGH-I337M with I337MUMUAMG1 as Stock. Rooted, Flashed Philz Touch for GT-i9505, Flashed 4.3 modem.bin only, Tried to flash Custom Rom, messed up, Flashed Stock I337MUMUAMG1 again, Rooted, got Knox popup upon opening SuperSU for the first time, shat bricks, Flashed Stock I337MUMUAMG1 again to be as stock as posible. If I boot into download mode I don't get Knox Warranty Void Flag in the Download Mode, don't have Knox apps on my App Drawer but I see them on the Application Manager -> All. Too scared to try anything until I know if I have Knox enabled on my Bootloader or only Knox Apps on my Rom.
Any help with this will be greatly appreciated, many thanks in advance, and thanks for reading.
EDIT: FORGOT ABOUT SOMETHING. After Flashing Stock I337MUMUAMG1 For the second time after getting the Knox warning popup on SuperSU, I got an OTA, couldn't cancel it but I don't know if it changed anything, since my build number was it was I337MUMUAMG1 still, it was a 250mb file.
sounds like you have knox yes. As to why it doesnt show in download mode, I can only speculate that when you flashed back to 4.2.2 the recovery was replaced with a pre-knox variant. If you're seeing knox in app manager>all as you mentioned, then you have knox yep. I have the same, just a shortcut, then knox crap in app manager> all.
Interestingly, I came from gummy 1.1, with root and CWM recovery. However since i was rooted, i couldnt obtain the 4.3 update OTA. So, I downloaded the 4.3 stock, flashed with odin (auto-reboot/f reset selected) and my knox shows 0x0. Granted I don't have root, but my main reason for this was battery life, which sucked balls on 4.2.2 rogers variant. 4.3 rogers variant is MUCH improved. I'm actually getting better life out of the stock fw, then i was with gummy 1.1. I hear all these horror stories, but I have yet to have a single app crash on 4.3 stock (i do miss xposed tho)
I haven't' re-flashed and tripped KNOX because it isn't just some security crap samsung threw on to stop custom recoveries/kernel's etc. It's actually Samsungs corporate solution for BYOD policies. The whole reason it blows the fuse, isnt just to stop warranties either, it's to communicate with exchange/corporate policies and let exchange/network know that your device is secure and following corporate policies. We all know android and linux are one in the same, adding this now gives samsung the ability to sell a managment suite (like BES in blackberry world) that uses knox for remote wipes/locks/factory reset/anti-theft. granted these exist already, but in a basic state. Look for these to be expanded on shortly.
If you blow your efuse, and use active sync , your going to be up **** creek shortly. I'm going to wait until this is defeated. Yes Knox is a hardware based efuse (the flag), but make no mistake, it is software solution and thus can be exploited. Patience is key here, imho. Just wait until the knox based sys admin tool is released for admins. anyone with a tripped flag is going to have a problem (if in business world). Sorry if I ran on a bit there, but yes, it sure seems you have knox and you should treat the device as though you do.
oh and the new SSO functionality is provided by knox, so if you can't use it, no single sign on for you i'm afraid.
http://www.samsung.com/global/business/mobile/solution/security/samsung-knox
Certain KNOX elements are present in 4.2.2 builds, however, the entire KNOX implementation (Kernel and KNOX suite) are only on 4.3 builds. More than likely, the version of SuperSU you are using detected that those certain KNOX apks (from 4.2.2) are on your phone and reported the "Samsung KNOX has been detected..." message.
scott14719 said:
Certain KNOX elements are present in 4.2.2 builds, however, the entire KNOX implementation (Kernel and KNOX suite) are only on 4.3 builds. More than likely, the version of SuperSU you are using detected that those certain KNOX apks (from 4.2.2) are on your phone and reported the "Samsung KNOX has been detected..." message.
Click to expand...
Click to collapse
So that means there is no Knox in my boot loader so I can reset my triangle counter to be as stock as possible to keep my warranty?
Aelyus said:
So that means there is no Knox in my boot loader so I can reset my triangle counter to be as stock as possible to keep my warranty?
Click to expand...
Click to collapse
I have no idea about resetting the triangle counter. I've never needed to do it, so I can't help you there.
Guys, I have a question related to this.
I have I9195L (Latin version of S4 mini) and I have read about knox software which may cause issues to rom flashers like me (I used to have S Advance and tried many roms until it died)
When I enter into flash mode, I noticed that there was no knox flag at all (like the ones I saw on some other users shots), so my question is, do
Do I have that knox crap or not?
I do realized that I have some knox software installed, like knox store (I didnt touched anything of this just in case).
Can I safely try other ROMs, including Cyanogen mod?
I have rooted using the safe method posted somewhere around here in the forums.
BTW: I have stock rom... for the moment...
Please let me know.
Thank you in advance.
Aelyus said:
So that means there is no Knox in my boot loader so I can reset my triangle counter to be as stock as possible to keep my warranty?
Click to expand...
Click to collapse
Yes. However, the best way to keep knox untripped to return for warranty is to simply flash the stock fw via odin. Poof, root gone, and check the f reset flag to reset the flash counter safely. You also have same scenario I did. I was running gummy 1.1 (back in nov) when 4.3 ota was released, so I flashed 4.3 via odin and knox is still 0x0. Kingo will root 4.3 and keep knox at 0x0, it did for my i377m and a coworkers as well. You can use wanam to fake official and keep ota updates for the upcoming kitkat update. Just be prepared to flash it via odin, as nobody really knows how supersu in survival mode will react to the 4.4.2 update ota. Only stipulation is you CANNOT run a custom recovery without tripping knox, or a custom rom. So I simply use xposed + wanam and customize the TW firmware that way. I have root, I have my warranty, and I can rip out any bloat I care to. HTH.
Guys, cyanogen does trip Knox and Odin does not trip Knox?
Enviado desde mi GT-I9195L mediante Tapatalk
cenovita said:
Guys, cyanogen does trip Knox and Odin does not trip Knox?
Enviado desde mi GT-I9195L mediante Tapatalk
Click to expand...
Click to collapse
Cyanogen trips knox yes. Odin will not, provided you arent attempting to downgrade to say, 4.2.2 from 4.3. Once on a knox "infected" bootloader, cant downgrade without knox tripping.
Sent from my SGH-I337M
azuziel said:
Cyanogen trips knox yes. Odin will not, provided you arent attempting to downgrade to say, 4.2.2 from 4.3. Once on a knox "infected" bootloader, cant downgrade without knox tripping.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Thank you very much for your response.
Final question, if I don't have Knox in my loader (I don't see the flag in Odin mode) I can install cyanogen and go back to stock (4.2.2) if I want to and the guaranty should be fine, right?
Enviado desde mi GT-I9195L mediante Tapatalk
cenovita said:
Thank you very much for your response.
Final question, if I don't have Knox in my loader (I don't see the flag in Odin mode) I can install cyanogen and go back to stock (4.2.2) if I want to and the guaranty should be fine, right?
Enviado desde mi GT-I9195L mediante Tapatalk
Click to expand...
Click to collapse
Provided you dont see any knox lines while in download mode, or odin mode, yes.
Sent from my SGH-I337M
azuziel said:
Provided you dont see any knox lines while in download mode, or odin mode, yes.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Nope, no lines related to Knox in download mode.
Thank you!
Enviado desde mi GT-I9195L mediante Tapatalk
Related
Hey folks,
One of the forum moderators pointed me at this thread ( http://forum.xda-developers.com/showthread.php?t=2586586 ) as a suggestion to getting a ROM for my S4 that would alleviate the com.android.phone process crashes I had with other ROMS.
After flashing jfltespr_mk2_deodexed from micro-sd card through the Team Win recovery, my phone is now stuck at the Samsung Galaxy S4 logo screen with (Set Warranty Bit: Kernel) in the upper left.
Having looked through numerous threads on this issue, it seems there's a number of different remedies, from reflashing to simply powercycling.
There wasn't anything that was of much use in http://forum.xda-developers.com/showthread.php?t=2527706 either.
I have odin, and can boot into Team Win Recovery, or download mode. Suggestions/tips/ideas would be appreciated. Thanks.
Seems like you already have Knox tripped. And those warnings are because Knox detected modified files on your phone at boot up. I would suggest to odinto stock MK2
Sent from my SPH-L720 using Tapatalk
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
cruise350 said:
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
dearastronomer said:
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
Click to expand...
Click to collapse
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
From the advice in this thread I was able to get back to stock ROM w/ root (CF-Auto-Root). Thanks for the tips, and for being patient.
I'm going to do some reading on Knox, because I'm getting conflicting reports on the ability to remove it.
leaderbuilder said:
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
Click to expand...
Click to collapse
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
cruise350 said:
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
Click to expand...
Click to collapse
True but it lock the bootloader from what I’m hearing
Hence stopping the installation of custom roms
Dear XDA,
I come from the HTC One forum and I've sold since I've had camera issues numberous of times.
I decided to switch to an SGS 4, currently on 4.4.2. I have the i9505xxufnb9 variant.
I have a question regarding root.
1. I do not have knox installed yet, should I install it or leave it as it be when using CF-auto root? I'm currently on 4.4.2.
2. Is CF auto root compatible with my variant?
3. What version of Odin should I be running? I guess this is the most important. I don't want a sketchy Odin.exe that comes pre-set up. It might have some setting on that erases something that is crucial for my device.
4. Is there some sort of bootloader unlock I need to do first? My device is unbranded GT9505 version with the above written variant.
5. How likely am I to brick my device? I mean I come from the HTC one forum which was fairly easy. Setup fastboot and unlocking the bootloader did the job.
6. I came to understand it WILL trigger knox, does it mean voided warranty here in the Netherlands?
7. I understand that SuperSU has an option to unroot at any given time. When I want to return to stock for say warranty purposes, Can I download triangleaway, run it, and then unroot using SU app?
Thank you so much for your time!!
No one?
Cf autoroot comes with correct odin, if you do not have Knox don't install it, (you automatically get it if you took an ota). And no bootloader unlock is needed almost all Samsung devices come with an unlocked bootloader, and the only way you'll brick your device is if you flash something not meant for your phone or if you have knox and try downgrading your firmware...
And if you do have knox, rooting will permanently flag your device as modified with no way of going back. If you don't have knox you can use triangle away to reset the flash counter.
Sent from my GT-I9505 using Tapatalk
aryehzev said:
Cf autoroot comes with correct odin, if you do not have Knox don't install it, (you automatically get it if you took an ota). And no bootloader unlock is needed almost all Samsung devices come with an unlocked bootloader, and the only way you'll brick your device is if you flash something not meant for your phone or if you have knox and try downgrading your firmware...
And if you do have knox, rooting will permanently flag your device as modified with no way of going back. If you don't have knox you can use triangle away to reset the flash counter.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I'll make sure to give you your thanks tomorrow . I also got alot of help from the ask everything thread, thank you!
**UPDATE**
So I un-rooted with SuperSU and Knox is still 0x0. How can I just re-flash my phone back to factory (where/what file do I download) with what software? I can't recall if I deleted any stock apps. I just want it 100% back to factory out-of-the-box.
Thanks in advance!
*old info for reference*
Hi there,
I'm sure I've missed it but I just want to be 100% sure so I apologize if this has (probably) been asked 100 times.
I rooted my Galaxy Note 3 Verizon with Towelroot as soon as it was released. It worked great and knox is still 0x0. I need to do a warranty replacement on my device due to a faulty charging port and need to remove my root access.
Info:
Model: SM-N900V
Hardware Version: N900V.07
Android Version 4.4.2
Knox status: 0x0
No ROMs have been added. Just added root access to stop some apps from running.
What is the proper way to remove root access without tripping Knox?
Probably better safe to just do a full on reset. I found a guide but I'm prevented from posting links... But it involves running Odin and reflashing the default firmware. would this be the correct way to reset/unroot and not trip Knox?
I would like to unroot and just do a full 100% reset as if it was just being pulled out of the box without of course tripping knox. In searching, someone said to just use Samsung Kies software: "under the firmware upgrade menu. It will fully wipe the phone and return it to stock." Is this a correct method?
Thanks!
-edit-
Also just found this on kingoapp:
"How does this KNOX Counter work?
Under what circumstances will KNOX Counter be flagged or tripped?
The KNOX Counter WILL NOT be flagged or tripped when using Samsung Kies or Odin to flash a stock ROM."
Seems like I'm answering my own question. So is Samsung Kies the best route? Does the above statement apply even if you're already rooted?
In superuser setting, there is a menu 'full unroot', use that.
fadhil3536 said:
In superuser setting, there is a menu 'full unroot', use that.
Click to expand...
Click to collapse
Hi, thanks for the reply. I never could get superuser setup and working, main reason for root was to freeze/remove some stock apps. I would like to unroot and just do a full 100% reset as if it was just being pulled out of the box without of course tripping knox. In searching, someone said to just use Samsung Kies software: "under the firmware upgrade menu. It will fully wipe the phone and return it to stock." Is this a correct method?
Thanks!
-edit-
Also just found this on kingoapp:
"How does this KNOX Counter work?
Under what circumstances will KNOX Counter be flagged or tripped?
The KNOX Counter WILL NOT be flagged or tripped when using Samsung Kies or Odin to flash a stock ROM."
Seems like I'm answering my own question. So is Samsung Kies the best route? Does the above statement apply even if you're already rooted?
fadhil3536 said:
In superuser setting, there is a menu 'full unroot', use that.
Click to expand...
Click to collapse
So I un-rooted with SuperSU and Knox is still 0x0. How can I just re-flash my phone back to factory (where/what file do I download) with what software? I can't recall if I deleted any stock apps. I just want it 100% back to factory out-of-the-box.
Thanks in advance! +1 for Thanked as well!
sharpshot152 said:
So I un-rooted with SuperSU and Knox is still 0x0. How can I just re-flash my phone back to factory (where/what file do I download) with what software? I can't recall if I deleted any stock apps. I just want it 100% back to factory out-of-the-box.
Thanks in advance! +1 for Thanked as well!
Click to expand...
Click to collapse
Knox will not trip as long you doesn't flash custom recovery or kernel or custom Rom.
Warning:
Factory reset using stock recovery will wipe your internal storage.
Backup all your file in Internal storage first.
Software needed to flash stock rom,
I use Odin V3.09
Firmware = download at sammobile website.
Apparently this does not prevent OTA's. Like most, I didn't like Magazine UX or Knox so I flashed. Tripped the Knox Warranty Void =1. So I went to Sammobile and downloaded the July 2014 release and flashed it. Lo and behold, when I hit software updates it started downloading. Will let you know of my progress.
pworcester said:
Apparently this does not prevent OTA's. Like most, I didn't like Magazine UX or Knox so I flashed. Tripped the Knox Warranty Void =1. So I went to Sammobile and downloaded the July 2014 release and flashed it. Lo and behold, when I hit software updates it started downloading. Will let you know of my progress.
Click to expand...
Click to collapse
OK. It took me from ANF4 to ANI1!
pworcester said:
OK. It took me from ANF$ to ANI1!
Click to expand...
Click to collapse
and from ANI1 to ANK1! Sweet!!
KNOX is mainly meant to ensure an untampered device for corporate security purposes; not to prevent OTAs.
yes it just causes to end your guarantee in case you take it to samsung service
benveq said:
yes it just causes to end your guarantee in case you take it to samsung service
Click to expand...
Click to collapse
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
redpoint73 said:
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
Click to expand...
Click to collapse
I came from a tab2 10.1 that I could reset completely. Wasn't sure if knox would keep me from getting updates.
pworcester said:
I came from a tab2 10.1 that I could reset completely. Wasn't sure if knox would keep me from getting updates.
Click to expand...
Click to collapse
Its good to get more confirmation, in any case. There seems to be a good amount of mixed info about KNOX. So thanks for posting it.
redpoint73 said:
KNOX is mainly meant to ensure an untampered device for corporate security purposes; not to prevent OTAs.
Click to expand...
Click to collapse
Regardless of what it's meant for, if you trip Knox and then try to do an OTA you will get a message telling you you can't do that. Now, apparently manually flashing something removes that restriction, which is great, but the fact remains.
redpoint73 said:
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
Click to expand...
Click to collapse
I used Odin to flash the July 2014 relase. Prior to that I had the current relase falshed through Odin When I would check for updates it would tell me my device was modified. Going back to July and letting it OTA to current, now when I check for updates it says the latest software is installed.
thebobmannh said:
Regardless of what it's meant for, if you trip Knox and then try to do an OTA you will get a message telling you you can't do that. Now, apparently manually flashing something removes that restriction, which is great, but the fact remains.
Click to expand...
Click to collapse
You're right, I wasn't completely clear on the details of the situation (once modded, I don't believe in OTAs) so thanks for clarifying.
---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------
pworcester said:
I used Odin to flash the July 2014 relase. Prior to that I had the current relase falshed through Odin When I would check for updates it would tell me my device was modified. Going back to July and letting it OTA to current, now when I check for updates it says the latest software is installed.
Click to expand...
Click to collapse
Again, thanks for the clarification.
It's not the Knox status that matters for OTAs. It is the flag that identifies your setup as Custom that prevents OTAs. That is a result of having a custom recovery. For example, if I root my device, tripping Knox, and later decide to Odin back to stock without custom recovery, I can (and have) receive OTAs because my status is returned to Official. I can then re-root, flash custom recovery (thus resetting status to Custom), and no longer receive OTAs.
Sent telepathically
RiverCity.45 said:
It's not the Knox status that matters for OTAs. It is the flag that identifies your setup as Custom that prevents OTAs. That is a result of having a custom recovery. For example, if I root my device, tripping Knox, and later decide to Odin back to stock without custom recovery, I can (and have) receive OTAs because my status is returned to Official. I can then re-root, flash custom recovery (thus resetting status to Custom), and no longer receive OTAs.
Click to expand...
Click to collapse
Weird, all I did was root my T900 (via Odin), without installing a custom recovery, and was subsequently unable to take an OTA. I didn't really mess with it after that -- I switched to CM shortly after -- but that was my very limited experience. Could have been a fluke.
If you used CF Auto Root, part of the automated process mucks with recovery to achieve root (thereby rendering your status as Custom). One can Odin flash back to complete stock (which unroots and resets recovery to Official), but Knox remains tripped.
RiverCity.45 said:
If you used CF Auto Root, part of the automated process mucks with recovery to achieve root (thereby rendering your status as Custom). One can Odin flash back to complete stock (which unroots and resets recovery to Official), but Knox remains tripped.
Click to expand...
Click to collapse
Great info, thanks! THis is my first Samsung / Knox device so still learning the basics.
Would it be safe to dirty flash (flash without wiping /data, only /cache and dalvik) latest stock ROM over older stock ROMs (modified with custom recovery)?
Sorry to necro-ish-post. Just got one of these on sale and I'm getting used to the "Samsung Way" after a Nexus tablet.
Suppose I've rooted my ROM without tripping Knox. I'd imagine if another OTA comes along it might fail due to modifications to the ROM. Can I use Odin to reflash the system part of the ROM back to stock without tripping Knox, so that the OTA will subsequently work?
cmstlist said:
Sorry to necro-ish-post. Just got one of these on sale and I'm getting used to the "Samsung Way" after a Nexus tablet.
Suppose I've rooted my ROM without tripping Knox. I'd imagine if another OTA comes along it might fail due to modifications to the ROM. Can I use Odin to reflash the system part of the ROM back to stock without tripping Knox, so that the OTA will subsequently work?
Click to expand...
Click to collapse
Yep. You can get a stock ROM and flash it with ODIN. Knox won't be tripped and you will loose root. Other thing you can do is stay rooted, and flash with ODIN the new ROMs as soon as they are available. Instead of re-flashing the same ROM you are on right now, so you can get an OTA, why not wait until a new ROM is released and flash that new ROM then? You can reroot then, if you want (towelroot). Of course you have to keep an eye on the forum so you know when a new ROM is available. Or check samfirmware from time to time :good:
Good to know. I don't know if Lollipop is ever on the agenda for Tab Pro, but if so I'd imagine there won't be a way to get it Towelrooted.
HELP!!! U.S. version of sm-T520
I have the Sm-T520nzwaxar. I needed to flash a firmware to revert it to stock. I was aware of the region based firmwares, but I still flashed one. The process failed near the end. Odin said "Failed" and my tablet remained in download mode, didn't boot. Now, I have a tablet that is pretty damn bricked. It will only go to a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" and Download Mode.
I have determined that there is no such firmware for T520nzwaxar, despite being the U.S. model. The only thing I can hope for now is that such a file does exist or another firmware from another country would work.
PLEASE any help that can be given to a frimware that would work with this would be HUGELY appreciated.
OK, so I'm new to this ROM-flashing stuff, and would like to install TWRP on my S4. The problem is, Samsung runs these trade-up programs every so often, so I do eventually plan on restoring the S4 to its original recovery. I was able to find an article from 2013 about the S4's stock recovery, and it also provided a download link to the recovery, but my question is, since that was released was 4.3 JB was the newest version, will that be an issue if the device is running 5.0 Lollipop instead? Basically my question is: did the Lollipop/KitKat update come with a new version of the recovery mode that is required to run these versions? Or is the recovery never updated throughout a device's lifetime?
You should consider this first:
Flashing a custom recovery will trip Knox.
The question now is: Will Samsung accept the phone if Knox is 0x1?
As you may or may not know, Knox status 0x1 is permanent. So even if you return to a stock recovery, Knox will still be 0x1.
GDReaper said:
You should consider this first:
Flashing a custom recovery will trip Knox.
The question now is: Will Samsung accept the phone if Knox is 0x1?
As you may or may not know, Knox status 0x1 is permanent. So even if you return to a stock recovery, Knox will still be 0x1.
Click to expand...
Click to collapse
They're unlikely to check that part. They look at the device, call the secret code to test the mic, camera, display etc, and it's marked good to go. Heck, I highly doubt they'll even notice if I was running TWRP, but just to play it safe.