So I'm locked out of my phone via Samsung Reactivation lock and someone said try to use Knox as a work around. I used an OTG to get into settings and installed Knox but when I tried to open it, it says "My Knox cannot be installed because a custom OS has previously been installed on this device" ... Granted I did try to root the phone originally but in the Download Mode it says Knox Warranty Void 0x0. So my knox should be fine right? please help. Thanks!
I am experiencing something similar on my S5 G900A. I have only installed official ROMs using ODIN, my knox is 0x0, have never attempted to root my phone. When trying to set up my corporate email using knox I cannot do it. Using the My Knox app gives me the exact same message you are getting.
have you been able to workaround this issue?
yesterday I rebooted my device and to my surprise, during the initial bootscreen, a padlock and the label "Custom" appeared. Funny thing is I have never flashed a custom ROM on my device or attempted to root. I rebooted again and the message did not show up anymore. I think it might have something to do with a flash counter, but I am not sure if it is possible to reset it. Again, my knox flag is 0x0, so I don't know what is going on. Any insight will be helpful.
I think I solved it. Download the sammobile app and check if your bootloader matches your ROM. If not, then Odin flash the correct files. In my case I had PA2 ROM with OI5 bootloader, but once I flashed PA2 BL, I am now able to use KNOX again.
Related
Rooted the phone, decided I didn't really care or need to have a phone rooted. Phone was fine. So I decided to grab the stock ATT firmware and reload it via Odin. All goes well until the very end when the phone tells me:
SECURE CHECK FAIL : system
Pretty sure this is related to the locked boot-loader. I cannot get into recovery mode, and I cannot boot into regular android, but I can get into download mode. It just fails after nearly completing everything using different Odin versions, and I've used two different firmware files. I was on 4.4.2 and had all of the latest ATT OTA updates.
Everything is still listed as official and KNOX is 0x0 and KNOX Warranty void is 0x0. I guess Kies emergency firmware recovery doesn't work with the Note 3.
What are these Odin files, and where did you obtain them? Add far as I know there is no Odin flashable file for 4.4
You're going to have to visit a Samsung kiosk at a Best Buy and see if they can fix it. If not, you're probably screwed, and will have to try for a replacement, or send to Samsung for service.
I tried unrooted with SuperSU and it still shows custom, KNOX still shows 0x0 the real issue is how to remove customer and get back to official without bricking.
raduque said:
You're going to have to visit a Samsung kiosk at a Best Buy and see if they can fix it. If not, you're probably screwed, and will have to try for a replacement, or send to Samsung for service.
Click to expand...
Click to collapse
This was the recommendation from my local att corporate store. It's also what worked. The Samsung consultant let me restore my phone with her computer. She didn't realize how to get it into download mode. Either way, the Samsung program flashed the phone. It was super easy to use. Certainly meant for an non tech person. Same instructions as doing an emergency firmware recovery within Kies.
I have an ATT Galaxy S5 that has to go back.
I was towel rooted until the last ATT update the NG3. No roms, just rooted. Never even got around to the bloatware removal.
Boot screen has the custom boot screen. Checked knox in phone info app and its showing 0x0.
Went into download mode and its showing 0x0 so knox is not tripped.
Will they give me [email protected] over that custom logo? Is there a way to reset that?
I didnt see this addressed anywhere in a search on xda or on the web anywhere
Thanks
I know, that rooting set the Knox to 0x1, but I wonder if putting one of stock ROMs to miniS5 do the same?
Greetings,
JA
With offical firmware Knox stays at 0.
cult007 said:
With offical firmware Knox stays at 0.
Click to expand...
Click to collapse
Hmm... I am not sure now, why they write on http://forum.xda-developers.com/showthread.php?t=2595889 that
"Even if you flash a KNOX-enabled firmware via odin (e.g. the latest fw) knox will be set to 0x1" ?
May I use a ROM from http://www.sammobile.com/ and Knox will be not set to 0x1 ?
Thanks in advance
only flashing via keys not set knox 0x1.... If an update is available otherwise knox trigger set to 1.
If already rooted rom has super su installed, this during first reboot can stop knox triggering(just like for s4 mini).... but so far no rom present.
You can flash original samsung software with odin an dknox will NOT be triggerd.
cya
stiff
So, every people say other thing... Who to belive in?
I am not going to root (was I writing it?), just pures stock ROm from sammobile.
Well, I fill now like before a risk operation
look here,
there is a guide:
http://www.kingoapp.com/help/samsung-knox-counter.htm
I just finished flashing G800FXXU1ANL1_G800FOXX1ANK1_ROM firmware from sammobile via Odin. No issue whatsoever.
Well actually it seems fairly straighfoward to go back to stock, if you have the appropriate stock image to flash with Odin. I'm just used to do the whole "unlock bootloader, flash recovery, flash autoroot/rom/whatever" process on other devices and it feels weird to just load up Odin and do everyhing. So that's an insecurity.
I'm more interested in knowing whether Samsung "knows" that you rooted/unlocked the device, for warranty reasons. If sometime I decide to go back to full stock and at some point I need to return/send the device for some service, I want to know if they can tell whether the device had been previously rooted. On my motorola xt1092 unlocking the bootloader requires some sort of code from Moto itself, so even if you go back totally stock you can't get rid of the "unlocked bootloader" msg, let alone that they have you already registered on their system as having non-valid warranty.
YES. Atm there is no root method that won't trip knox and if knox is 0x1 samsung will always know. Some providers don't care about that and will fix ur phone/tablet. Especially if it don't even boot or some mechanic problem, just flash stock firmware with odin. My personally was very insecure when flashed firmware 5.1.1 then kernel and then root with odin (always used TWRP on S4) but all worked ok, just read the guide, real all post and all will be ok. If u wan't then go go stock just flash the same stock firmware and you will have it stock with no root stock recovery but knox will be 0x1
mk89pwnz said:
YES. Atm there is no root method that won't trip knox and if knox is 0x1 samsung will always know. Some providers don't care about that and will fix ur phone/tablet. Especially if it don't even boot or some mechanic problem, just flash stock firmware with odin. My personally was very insecure when flashed firmware 5.1.1 then kernel and then root with odin (always used TWRP on S4) but all worked ok, just read the guide, real all post and all will be ok. If u wan't then go go stock just flash the same stock firmware and you will have it stock with no root stock recovery but knox will be 0x1
Click to expand...
Click to collapse
Thanks for the info! I found out there was a piece of software called "Triangle Away" which helped reset counter to 0x0 when going back to full stock, but i can't find out if it would work on the Tab S2... http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
kokotron said:
Thanks for the info! I found out there was a piece of software called "Triangle Away" which helped reset counter to 0x0 when going back to full stock, but i can't find out if it would work on the Tab S2... http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Click to expand...
Click to collapse
It was flash counter not knox. Knox is literally impossible to reset. Triangle Away only works on older devices. List can be found here: http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
mk89pwnz said:
YES. Atm there is no root method that won't trip knox and if knox is 0x1 samsung will always know. Some providers don't care about that and will fix ur phone/tablet. Especially if it don't even boot or some mechanic problem, just flash stock firmware with odin. My personally was very insecure when flashed firmware 5.1.1 then kernel and then root with odin (always used TWRP on S4) but all worked ok, just read the guide, real all post and all will be ok. If u wan't then go go stock just flash the same stock firmware and you will have it stock with no root stock recovery but knox will be 0x1
Click to expand...
Click to collapse
Just to reconfirm that, since I was also a little concerned about that (I have a T810 btw, not a T815): While the stock firmware on my device works 'well enough', there are certain things i'd rather it was able to do. Knox however has me holding off (at least until the warranty expires). Does the same apply to the T810? (There is no root method that won't trip knox.)
ATM no. The only way to root Tab s2 is to trip Knox. King root will root your device with no Knox tripping but it will last until you reboot
I was trying to set up my corporate email using knox and it just won't complete the knox installation using mobileiron. After some research, I opened up the Samsung My Knox app and it gives me an error message saying "My KNOX cannot be installed because a custom OS has previously been installed on this device". I have never attempted to root my S5, my knox flag is 0x0 and I am on PA2 I flashed using ODIN. Has anybody seen this problem before? is there a way to fix this problem?
Anyone?
still no luck and have not found anything similar from other forums
yesterday I rebooted my device and to my surprise, during the initial bootscreen, a padlock and the label "Custom" appeared. Funny thing is I have never flashed a custom ROM on my device or attempted to root. I rebooted again and the message did not show up anymore. I think it might have something to do with a flash counter, but I am not sure if it is possible to reset it. Again, my knox flag is 0x0, so I don't know what is going on. Any insight will be helpful.
I think I figured out what went wrong. Seems like when I flashed PA2, the bootloader for some reason did not flash and it stayed on OI5. Once I flashed again the BL file, I am now able to open Knox and my enterprise email.