Related
Hello guys,
I’m aware this has been discussed many times before, but this information is "old" most of the times. My Galaxy S4 (i9505) is now running stock Touchwiz Android 4.3 (i9505XXUEMJ7).
What I want to do is the following: flash my phone to a i9505G, but with some research I've found that that isn't possible. Are there any other ways to get the clean i9505G 4.4.2 ROM without any changes (like root) on my i9505? (I know there are much custom ROM's, but if possible I'd like to keep it "stock".)
Since I'm running 4.3 with Knox I'm a little scared about the Knox 0x1 status, is this already "resolved" or will this still be a problem?
Thanks.
Broodplank's AOSP rom is the way to go:
http://forum.xda-developers.com/showthread.php?t=2397511
You still need to flash a custom recovery to flash it, though. I recommend CWM. Simply works.
tsphere said:
Broodplank's AOSP rom is the way to go:
http://forum.xda-developers.com/showthread.php?t=2397511
You still need to flash a custom recovery to flash it, though. I recommend CWM. Simply works.
Click to expand...
Click to collapse
Thanks for your reply. Rooting and flashing a custom recovery shouldn't be a problem, however I'm still a little worried about Knox, there simply isn't a way to reset it after it goes to 0x1?
The HTC One can be "changed" into a HTC One Google Edition: http://forum.xda-developers.com/showthread.php?t=2358781
But as far as I can tell this isn't possible for the Galaxy S4?
As far as i seen, once you flash something with odin, your knox flag gets changed. However it's not clear to me whether it changes the warranty actually...
tsphere said:
As far as i seen, once you flash something with odin, your knox flag gets changed. However it's not clear to me whether it changes the warranty actually...
Click to expand...
Click to collapse
It's not just the warrenty I'm worried about. If I want to sell the phone later I want it to be fully working, I assume with Knox 0x1 Knox isn't working anymore?
JoeyLe said:
Thanks for your reply. Rooting and flashing a custom recovery shouldn't be a problem, however I'm still a little worried about Knox, there simply isn't a way to reset it after it goes to 0x1?
The HTC One can be "changed" into a HTC One Google Edition: http://forum.xda-developers.com/showthread.php?t=2358781
But as far as I can tell this isn't possible for the Galaxy S4?
Click to expand...
Click to collapse
In theory every non G device can be converted into a G device if the hardware model is the same but in practice is not always accomplished 100%. The problem here is Knox, for waht I understand it has 2 layers: The knox bloatware that comes stock on sammys ROM and the off rom portion included in the bootloader. The bootloader is basically what the system loads up first
. so it can't bypassed. So to kkep it simple, if you flash ANYTHING (not sure however if re flashing the stock original ROM activates the flag) on the knox bootloader (AKA: new bootloader) the ''flag'' will change to 0x1, this flag is called eFuse so basically 0x1 means is burned and it can't be changed ANYWAY. If you don't plan to use your phone for work you shouldn't care about the flag.
For more information you can check this thread
http://forum.xda-developers.com/showthread.php?t=2447832
JoeyLe said:
It's not just the warrenty I'm worried about. If I want to sell the phone later I want it to be fully working, I assume with Knox 0x1 Knox isn't working anymore?
Click to expand...
Click to collapse
1. It isn't clear if Knox 0x1 voids warranty or not.
2. If you have Knox 0x1 your phone will work fine, but you won't be able to use Knox security enhancements.
3. You can't convert the 9505 to the 9505G, the Google Play edition has different bootloader, modem and pit partition.
Enviado do meu Xposed Galaxy S4 4G LTE
dclarkg said:
In theory every non G device can be converted into a G device if the hardware model is the same but in practice is not always accomplished 100%. The problem here is Knox, for waht I understand it has 2 layers: The knox bloatware that comes stock on sammys ROM and the off rom portion included in the bootloader. The bootloader is basically what the system loads up first
. so it can't bypassed. So to kkep it simple, if you flash ANYTHING (not sure however if re flashing the stock original ROM activates the flag) on the knox bootloader (AKA: new bootloader) the ''flag'' will change to 0x1, this flag is called eFuse so basically 0x1 means is burned and it can't be changed ANYWAY. If you don't plan to use your phone for work you shouldn't care about the flag.
For more information you can check this thread
http://forum.xda-developers.com/showthread.php?t=2447832
Click to expand...
Click to collapse
Thank you very much! That was very interesting to read. I personally don't care about Knox, all the Samsung bloatware is the main reason I want to have stock Android on my S4.
dandroid13 said:
1. It isn't clear if Knox 0x1 voids warranty or not.
2. If you have Knox 0x1 your phone will work fine, but you won't be able to use Knox security enhancements.
3. You can't convert the 9505 to the 9505G, the Google Play edition has different bootloader, modem and pit partition.
Enviado do meu Xposed Galaxy S4 4G LTE
Click to expand...
Click to collapse
Thanks for the information. I see there are many custom roms which are very close to stock Android, that should be fine as well.
JoeyLe said:
Thanks for the information. I see there are many custom roms which are very close to stock Android, that should be fine as well.
Click to expand...
Click to collapse
Sure, but the 4.4 roms (Google Play) have one main issue, random reboots.
Hey Guys,
I'm using a N9005 as my phone. For syncing "work" email an 3. Party MDM App is required. Because of the bad battery life I rooted the phone (knox 0x1) and installed Greenify and a custom kernel. It worked great but because I did a full wipe I needed to install the MDM App again.
Now I am not able to encrypt the device and the MDM tells me that my phone is compromised. I don't know if it is because of root or the missing encryption, knox 0x1 or the kernel?
Anyone has an idea what I can do now (except flashing stock)?
Is there any chance to get a great battery life again without root?
Thanks.
Alex87142 said:
Hey Guys,
I'm using a N9005 as my phone. For syncing "work" email an 3. Party MDM App is required. Because of the bad battery life I rooted the phone (knox 0x1) and installed Greenify and a custom kernel. It worked great but because I did a full wipe I needed to install the MDM App again.
Now I am not able to encrypt the device and the MDM tells me that my phone is compromised. I don't know if it is because of root or the missing encryption, knox 0x1 or the kernel?
Anyone has an idea what I can do now (except flashing stock)?
Is there any chance to get a great battery life again without root?
Thanks.
Click to expand...
Click to collapse
Revert back to Stock kernel at least, it'll be the kernel that will cause the issue because it isn't signed Official, you don't use the KNOX container so that won't be the issue - Although triggering KNOX does stop the device from being encrypted.. but try changing the kernel and see.. It probably won't work though.
I've attached Stock MK2 kernel if you need it.
radicalisto said:
Revert back to Stock kernel at least, it'll be the kernel that will cause the issue because it isn't signed Official, you don't use the KNOX container so that won't be the issue - Although triggering KNOX does stop the device from being encrypted.. but try changing the kernel and see.. It probably won't work though.
I've attached Stock MK2 kernel if you need it.
Click to expand...
Click to collapse
Thanks. But it didn't help. I flashed the stock kernel. When I try to encrypt, the screen goes black and the phone reboots after approx. 30 sec.
I reinstalled MDM but it still shows "compromised".
Alex87142 said:
Thanks. But it didn't help. I flashed the stock kernel. When I try to encrypt, the screen goes black and the phone reboots after approx. 30 sec.
I reinstalled MDM but it still shows "compromised".
Click to expand...
Click to collapse
That'll be the KNOX effect then. Won't be able to encrypt your device anymore I'm afraid
escarth was
radicalisto said:
That'll be the KNOX effect then. Won't be able to encrypt your device anymore I'm afraid
Click to expand...
Click to collapse
Are you sure? Didn't found anything about that around the web.
I did a backup with TWRP and try if going back to stock (unroot) helps...
Alex87142 said:
Are you sure? Didn't found anything about that around the web.
I did a backup with TWRP and try if going back to stock (unroot) helps...
Click to expand...
Click to collapse
Well when KNOX is tripped you can't encrypt your device, you can try going back to full stock and see, but it doesn't work afaik. Have a gander round the forum you'll see some people posting about it.
radicalisto said:
Well when KNOX is tripped you can't encrypt your device, you can try going back to full stock and see, but it doesn't work afaik. Have a gander round the forum you'll see some people posting about it.
Click to expand...
Click to collapse
Good news. After I was so frustrated I wiped and flashed stock.
Encryption worked!!!!
I installed MDM without any error.
Hopefully everything will work now....
Thank you all.
Can you root again after you have encrypted your phone I was trying to do this the other day but with no luck fort it most of been something to do with Knox ??
Sent from my SM-N9005 using xda app-developers app
Alex87142 said:
Good news. After I was so frustrated I wiped and flashed stock.
Encryption worked!!!!
I installed MDM without any error.
Hopefully everything will work now....
Thank you all.
Click to expand...
Click to collapse
Interesting thar Encryption works after triggering KNOX, some conflicting reports that it does not.. Good to know none the less.
Yes you can root but it will wipe and destroy encryption. Encryption not working after root seems to be a common 4.3 bug.
https://code.google.com/p/android/issues/detail?id=58073
Gesendet von meinem SM-N9005 mit Tapatalk
I have a phone which has a lot of problems after the KitKat update.
Now I want to try to reinstall KitKat. Samsung doesn't provide this, so I want to use ODIN and the firmware from SamMobile.
Does anybody know if I will do this that it will trip the Knox counter?
What if you try to just reset the phone to factory settings? I wouldn't know anything about Knox though. Hope you sort it out. :fingers-crossed:
Cootje_NL said:
I have a phone which has a lot of problems after the KitKat update.
Now I want to try to reinstall KitKat. Samsung doesn't provide this, so I want to use ODIN and the firmware from SamMobile.
Does anybody know if I will do this that it will trip the Knox counter?
Click to expand...
Click to collapse
no it wont
markslo112 said:
What if you try to just reset the phone to factory settings? I wouldn't know anything about Knox though. Hope you sort it out. :fingers-crossed:
Click to expand...
Click to collapse
Tnx for the tip. Already tried that 2 times. No luck
Cootje_NL said:
I have a phone which has a lot of problems after the KitKat update.
Now I want to try to reinstall KitKat. Samsung doesn't provide this, so I want to use ODIN and the firmware from SamMobile.
Does anybody know if I will do this that it will trip the Knox counter?
Click to expand...
Click to collapse
it won't trip Knox, i tried it several times as long as they are official roms
Cootje_NL said:
I have a phone which has a lot of problems after the KitKat update.
Now I want to try to reinstall KitKat. Samsung doesn't provide this, so I want to use ODIN and the firmware from SamMobile.
Does anybody know if I will do this that it will trip the Knox counter?
Click to expand...
Click to collapse
long as they are official samsung roms you be ok....
I reinstalled my firmware and I can confirm that it indeed won't trip Knox.
As it might be useful I also want to share that updating using my Mac (with VMWare for Windows) gave me a lot of troubles. After using a native Windows laptop the update went fine.
Too bad it didn't solve my problem. Going back to the store to claim my warranty.
jaythenut said:
no it wont
Click to expand...
Click to collapse
So forgive me if I'm asking a stupid question here but I thought that if I root my Note 3 I will automatically trip the Knox counter, even before I get anywhere near flashing a new ROM - stock or custom. Is that not true then?
Medical HRH said:
So forgive me if I'm asking a stupid question here but I thought that if I root my Note 3 I will automatically trip the Knox counter, even before I get anywhere near flashing a new ROM - stock or custom. Is that not true then?
Click to expand...
Click to collapse
You won't trip Knox if you install a KK rom but will if you try to flash bak JB.
Any form of rooting will trip Knox. There used to be safe ways that didn't but with the introduction of the newer bootloaders this is no longer guaranteed...
Have you tried backing up any info you want to keep to a pc then factory resetting, I found KK was a b!tch until I reset it due to old JB data scraps causing issues...
ultramag69 said:
You won't trip Knox if you install a KK rom but will if you try to flash bak JB.
Any form of rooting will trip Knox. There used to be safe ways that didn't but with the introduction of the newer bootloaders this is no longer guaranteed...
Have you tried backing up any info you want to keep to a pc then factory resetting, I found KK was a b!tch until I reset it due to old JB data scraps causing issues...
Click to expand...
Click to collapse
I'm on stock 4.3 and not having any issues at the moment - other than my Note 3 not picking up the 4G signal on 3 for some infuriating reason.
So can I flash a stock KK rom without rooting then? I'm probably being thick but thought you had to be rooted to flash any kind of ROM?
Medical HRH said:
I'm on stock 4.3 and not having any issues at the moment - other than my Note 3 not picking up the 4G signal on 3 for some infuriating reason.
So can I flash a stock KK rom without rooting then? I'm probably being thick but thought you had to be rooted to flash any kind of ROM?
Click to expand...
Click to collapse
You have to be rooted to flash the custom roms provided here and that will mostly be thru recovery. It will surely trip knox. To flash stock roms from sammobile you don't need root. That can be done thru odin.
Sent from my SM-N9005 using XDA Premium 4 mobile app
I would suggest however, if you are network locked to unlock 1st... If you need to flash a separate modem afterwards this can trip Knox as you aren't really using a "Stock rom"...
Also make sure re-activation lock is OFF.... If you go to Kitkat and you don't have a KK rom yet you are stuck with a softbricked phone until you do get the KK rom... You can't go back to JB after flashing KK rom due to a new bootloader...
Please can anyone tell me did S3 Neo also has Knox Security, I don't see Knox written anywhere in Odin mode.
Kashmir Hackers said:
Please can anyone tell me did S3 Neo also has Knox Security, I don't see Knox written anywhere in Odin mode.
Click to expand...
Click to collapse
Yes S3 Neo has Knox. You can use this https://play.google.com/store/apps/details?id=com.bryancandi.knoxcheck app to check if you have Knox.
Info :
0x0 Warranty valid/You have knox
0x1 Warranty void/You don't have knox
Sent from my GT-I9301I using XDA Free mobile app
Kashmir Hackers said:
Please can anyone tell me did S3 Neo also has Knox Security, I don't see Knox written anywhere in Odin mode.
Click to expand...
Click to collapse
Software tools say it has. But after flashing different roms and recoveries gazzilion times mine still says 0x0. As you can see from the screenshot even atm I am using cm12.1 with TWRP recovery and it hasnt done anything to the counter. So to be honest I think no matter what you do you can just flash back stock from odin and keep waranty.
xXPR0T0TYPEXx said:
Yes S3 Neo has Knox. You can use this https://play.google.com/store/apps/details?id=com.bryancandi.knoxcheck app to check if you have Knox.
Info :
0x0 Warranty valid/You have knox
0x1 Warranty void/You don't have knox
Sent from my GT-I9301I using XDA Free mobile app
Click to expand...
Click to collapse
Does it really mean we have Knox Security if the app shows 0x0 ???
mandzo said:
Software tools say it has. But after flashing different roms and recoveries gazzilion times mine still says 0x0. As you can see from the screenshot even atm I am using cm12.1 with TWRP recovery and it hasnt done anything to the counter. So to be honest I think no matter what you do you can just flash back stock from odin and keep waranty.
Click to expand...
Click to collapse
Wow, then it is really a good news but can anyone else confirm it....Please
Kashmir Hackers said:
Wow, then it is really a good news but can anyone else confirm it....Please
Click to expand...
Click to collapse
Heres another screenshot from Phone Info app. Now the since this app detects knox warranty void on models like s4, s5 and as far as I know s6, I highly doubt samsung went thru the trouble of putting some undetectable warranty counter and a mid range device such as our S3 neos.
mandzo said:
Heres another screenshot from Phone Info app. Now the since this app detects knox warranty void on models like s4, s5 and as far as I know s6, I highly doubt samsung went thru the trouble of putting some undetectable warranty counter and a mid range device such as our S3 neos.
Click to expand...
Click to collapse
My Phone is just two months old , should I root my mobile because I'm afraid of tripping the knox counter which obviously you can't reset.
Kashmir Hackers said:
My Phone is just two months old , should I root my mobile because I'm afraid of tripping the knox counter which obviously you can't reset.
Click to expand...
Click to collapse
I rooted mine the second day I got it (I got it somewhere around January). So far havent had any problems with it and the knox (if there is one) still says 0x0. That said rooting and flashing custom recovery is still something that may potentialy harm your device so its up to you to decide. Dont take my words as 100% proof everything will be ok. Maybe indeed w8 for a few more ppl to say if they had any problems with knox so far.
Kashmir Hackers said:
Does it really mean we have Knox Security if the app shows 0x0 ???
Click to expand...
Click to collapse
I am not 100% sure mate.
I checked my build.prop file and I found this "ro.config.knox=v00" I don"t know if it means, our phone has knox. I also found an app called "KNOX notification manager" in settings.
Sent from my GT-I9301I using XDA Free mobile app
xXPR0T0TYPEXx said:
I am not 100% sure mate.
I checked my build.prop file and I found this "ro.config.knox=v00" I don"t know if it means, our phone has knox. I also found an app called "KNOX notification manager" in settings.
Sent from my GT-I9301I using XDA Free mobile app
Click to expand...
Click to collapse
Knox isnt only related to warranty btw. It allso has to do with samsung enterprise security crap. Thats why we have some knox apps on our phones.
But again w8 for more reports from ppl who have rooted before you do it just to be safe.
mandzo said:
Knox isnt only related to warranty btw. It allso has to do with samsung enterprise security crap. Thats why we have some knox apps on our phones.
But again w8 for more reports from ppl who have rooted before you do it just to be safe.
Click to expand...
Click to collapse
Hey Buddy guess what? I took the risk and rooted my mobile with Cf Auto Root method and everything went smoothely and when I checked Knox status with apps nothing has changed and in Odin mode also only status has changed to Custom nothing else.
Mission Accomplished
Kashmir Hackers said:
Hey Buddy guess what? I took the risk and rooted my mobile with Cf Auto Root method and everything went smoothely and when I checked Knox status with apps nothing has changed and in Odin mode also only status has changed to Custom nothing else.
Mission Accomplished
Click to expand...
Click to collapse
Glad everything went fine. Enjoy your rooted s3 neo.
mandzo said:
Glad everything went fine. Enjoy your rooted s3 neo.
Click to expand...
Click to collapse
You know what after rooting my mobile the first thing I did is to remove the Knox crap from my mobile, they scared me enough but not anymore:good:
I can confirm that re-flashing a stock rom resets the binary counter to official. Happy rooting!
SpaceDye said:
I can confirm that re-flashing a stock rom resets the binary counter to official. Happy rooting!
Click to expand...
Click to collapse
Happy to hear that , thanks buddy for letting others know.
SpaceDye said:
I can confirm that re-flashing a stock rom resets the binary counter to official. Happy rooting!
Click to expand...
Click to collapse
Does it means I have my warranty back if I reflash official stock rom?
Im thinking about flash CM 12.1 but i still have 1 year and 6 month's warranty.
funchomix said:
Does it means I have my warranty back if I reflash official stock rom?
Im thinking about flash CM 12.1 but i still have 1 year and 6 month's warranty.
Click to expand...
Click to collapse
Yep! Your warranty will not be void as long as your device is running a stock rom when you turn it in. You can check your binary counter by going to download mode.
funchomix said:
Does it means I have my warranty back if I reflash official stock rom?
Im thinking about flash CM 12.1 but i still have 1 year and 6 month's warranty.
Click to expand...
Click to collapse
If you flash CM 12.1 , it will trip the binary counter but you can always reset the binary counter with the help of Triangle Away App by ChainFire. Resetting the binary counter and then flashing the Stock Rom will restore the warranty of your device.
Kashmir Hackers said:
If you flash CM 12.1 , it will trip the binary counter but you can always reset the binary counter with the help of Triangle Away App by ChainFire. Resetting the binary counter and then flashing the Stock Rom will restore the warranty of your device.
Click to expand...
Click to collapse
On this phone KNOX not work and does not tick. 100%
maxxim62 said:
On this phone KNOX not work and does not tick. 100%
Click to expand...
Click to collapse
I'm not talking about Knox Counter but I'm talking about Binary Counter which every Samsung phone already have and keeps track of how many times a custom firmware had been flashed. And as far as Knox Security is concerned there is still no way to reset Knox counter but fortunately S3 NEO don't have it.
Hey Guys,
i am very interested in flashing a custom ROM without tripping Knox. I know that it has to be based on a stock rom and stock kernel but i havent seen anyone tried it.
I appreciate any help
Deathvirus said:
Hey Guys,
i am very interested in flashing a custom ROM without tripping Knox. I know that it has to be based on a stock rom and stock kernel but i havent seen anyone tried it.
I appreciate any help
Click to expand...
Click to collapse
no.
You can try CM13 its not offical but i got weekly/monthly updates
http://forum.xda-developers.com/galaxy-s4/general/rom-cm13-0-galaxy-s4-ve-gt-i9515-t3245133
hanne1989 said:
You can try CM13 its not offical but i got weekly/monthly updates
http://forum.xda-developers.com/galaxy-s4/general/rom-cm13-0-galaxy-s4-ve-gt-i9515-t3245133
Click to expand...
Click to collapse
Did you even read his question?
Lennyz1988 said:
Did you even read his question?
Click to expand...
Click to collapse
Yeah i did but i only give him a tip that he also can you cm13.... We both knows it will tripping KNOX but if he want to test a custom beside the stock he can try to use CM13. En nou gewoon je bek houden
Unless you use the knox apps or are afraid of losing the warranty, then there is no other reason to be afraid of tripping knox.
GDReaper said:
Unless you use the knox apps or are afraid of losing the warranty, then there is no other reason to be afraid of tripping knox.
Click to expand...
Click to collapse
Its the warranty that bothers me because the Device is 2 Weeks old
My device was 1 month old when I first tripped knox.
A new phone is very unlikely to have a hardware failure.
Besides, my warranty was crap. I read it and it stated that it doesn't cover water damage, it doesn't cover a broken screen and a bunch of other stuff. Basically it covered only things that were a result of a manufacturing fault, like the aforementioned hardware fail or a bad battery.