I have bought my sgs2 from samsung Romania. They say if i flash any other firmware beside the official one for Romania via Kies, i lose the warranty.
I can hardly help it to stay stock:|. I am looking to root, flash updates, customs roms.
My question is: Can i revert to the stock official XWKE2, unroot, etc just as out of the box, so that the phone can appear untweaked and have the warranty again ? Is there a way the guys at the service find out that the phone was flashed?
Thanks in advance for your answers!
Alekxxx said:
I have bought my sgs2 from samsung Romania. They say if i flash any other firmware beside the official one for Romania via Kies, i lose the warranty.
I can hardly help it to stay stock:|. I am looking to root, flash updates, customs roms.
My question is: Can i revert to the stock official XWKE2, unroot, etc just as out of the box, so that the phone can appear untweaked and have the warranty again ? Is there a way the guys at the service find out that the phone was flashed?
Thanks in advance for your answers!
Click to expand...
Click to collapse
Yes if you have a copy of the original .
jje
how do i find a copy? from where can i download ?
on xda? i'll try a search
http://www.samfirmware.com/WEBPROTECT-i9100.htm
oh and btw,
if you flash a custom binary, it voids your warranty, even if you flash back to stock.
everytime you flash a custom binary, it notes how many times you flashed a custom binary.
if you would send your device back to your carrier, they can easily check if there was a custom binary flashed on your phone.
I would suggest, that you get an USB jig off ebay or somewhere else. with it, you can reset this counter, and you get your warranty back(price is around 8$).
Alekxxx said:
how do i find a copy? from where can i download ?
on xda? i'll try a search
Click to expand...
Click to collapse
DEV section xda branded roms .
jje
Hello there!
I need your help to be sure about some things.
(Oh! Sorry for my bad English, not my native language)
I have a Galaxy S5, I bought this with my country operator. The latest software for the SM-G900F model released by my operator is G900FXXU1ANCE.
I read that Samsung has updated the software with some better and this update is G900FXXU1ANE2.
My questions are:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Thanks in advance for your answers.
gevensa said:
Hello there!
I need your help to be sure about some things.
(Oh! Sorry for my bad English, not my native language)
I have a Galaxy S5, I bought this with my country operator. The latest software for the SM-G900F model released by my operator is G900FXXU1ANCE.
I read that Samsung has updated the software with some better and this update is G900FXXU1ANE2.
My questions are:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Thanks in advance for your answers.
Click to expand...
Click to collapse
First of all flashing official firmware with Odin will NEVER trip KNOX. Don`t know if you can flash an older rom, if the bootloader is the same it should be possible, just try it mate and if it should fail you reflash the rom you have now. You can flash any compatible rom with Odin, also the ones that are not for your region.
gevensa said:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Click to expand...
Click to collapse
Installing this update should not change the Knox bit. It should remain at 0x0 in this situation. Flashing stock firmware will not normally change Knox, although if you try installing a pre KitKat firmware e.g. 4.2.1, may corrupt the bootloader and increment the Knox counter. A power interruption during the flash process may also trip Knox. More commonly, installing a custom kernel or recovery will also trip the Knox counter.
You should be able to revert or downgrade to the earlier firmware in your example. And that won't affect your warranty (or be necessary for warranty purposes). Note though that you cannot downgrade all firmware versions. For example, Samsung introduced the Knox DRM in 4.3 and don't want you downgrading to remove it, consequently you cannot downgrade from 4.3 to 4.2.x (or earlier).
Thanks for your answers.
Another question: I have csc CRM What if I install the csc PHE, I will receive in the future the OTAs to release in Spain?
Sent from my SM-G900F using XDA Free mobile app
gee2012 said:
First of all flashing official firmware with Odin will NEVER trip KNOX. Don`t know if you can flash an older rom, if the bootloader is the same it should be possible, just try it mate and if it should fail you reflash the rom you have now. You can flash any compatible rom with Odin, also the ones that are not for your region.
Click to expand...
Click to collapse
fffft said:
Installing this update should not change the Knox bit. It should remain at 0x0 in this situation. Flashing stock firmware will not normally change Knox, although if you try installing a pre KitKat firmware e.g. 4.2.1, may corrupt the bootloader and increment the Knox counter. A power interruption during the flash process may also trip Knox. More commonly, installing a custom kernel or recovery will also trip the Knox counter.
You should be able to revert or downgrade to the earlier firmware in your example. And that won't affect your warranty (or be necessary for warranty purposes). Note though that you cannot downgrade all firmware versions. For example, Samsung introduced the Knox DRM in 4.3 and don't want you downgrading to remove it, consequently you cannot downgrade from 4.3 to 4.2.x (or earlier).
Click to expand...
Click to collapse
Thanks for your answers!!
Sent from my SM-G900F using XDA
Free mobile app
gee2012 said:
...
You can flash any compatible rom with Odin, also the ones that are not for your region.
Click to expand...
Click to collapse
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
my stock firmware said:
Model: SM-G900F
Model name: GALAXY S5
Country: Czech Republic
Version: Android 4.4.2
Changelist: 1539356
Build date: Thu, 08 May 2014 03:44:41 +0000
Product Code: ETL
PDA: G900FXXU1ANE2
CSC: G900FETL1AND3
MODEM: G900FXXU1ANE2
Click to expand...
Click to collapse
born4trance said:
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
Click to expand...
Click to collapse
Where is your device from, if i may ask? Is it a Dutch device or imported?
I ordered mine from a dutch webshop (i'm also dutch btw) who import their devices from EU countries.
born4trance said:
I ordered mine from a dutch webshop (i'm also dutch btw) who import their devices from EU countries.
Click to expand...
Click to collapse
Yup, saw that. So you can`t flash a Dutch PHN rom to your device? Strange as it its a EU device as you say Have you tried a German DBT rom?
gee2012 said:
Yup, saw that. So you can`t flash a Dutch PHN rom to your device? Strange as it its a EU device as you say Have you tried a German DBT rom?
Click to expand...
Click to collapse
Everything flashes fine, until it encounters hidden.img.ext4
I haven't looked at other firmwares yet but i did notice that the mentioned file's filesize differed from the PHN .tar one.
Its a shame that there are so many differences amongst the same model.
born4trance said:
Correct > FAIL! (Size) @ hidden.img.ext4
I haven't looked at other firmwares yet but i did notice that the file in question differed from the one inside the PHN .tar
Click to expand...
Click to collapse
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.
gee2012 said:
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.
Click to expand...
Click to collapse
I already quoted the firmware i (currently) have, a few posts back
born4trance said:
I already quoted the firmware i (currently) have, a few posts back
Click to expand...
Click to collapse
Sorry for not reading that Usualy it shouldn`t be a problem to flash a different European rom. I got my phone with a TNL (T-Mobile) rom and flashed a PHN rom and it wasn`t a problem for me. I`ll try flashing a DBT rom just to see if it works.
gee2012 said:
Sorry for not reading that Usualy it shouldn`t be a problem to flash a different European rom. I got my phone with a TNL (T-Mobile) rom and flashed a PHN rom and it wasn`t a problem for me. I`ll try flashing a DBT rom just to see if it works.
Click to expand...
Click to collapse
Perhaps it will work for you but not for me Í'm not sure if or when i'll flash another FW, i don't really want to lose/give up towelroot :angel:
gevensa said:
Another question: I have csc CRM What if I install the csc PHE, I will receive in the future the OTAs to release in SpaIn?
Click to expand...
Click to collapse
An OTA update will check your CSC to see if the update should be applied to your system. If you change your CSC from AAA to BBB, you can't expect to receive OTA's for AAA any longer. If your intent in doing this is wanting to receive BBB updates, the CSC change will usually suffice. It's a carrier implementation though and a more conservative carrier could also do secondary checks such as matching the baseband CSC as well.
Also you shouldn't change a CSC unless you are confident that the BBB OTA is compatible with your current firmware.
.
---------- Post added at 11:06 PM ---------- Previous post was at 10:17 PM ----------
born4trance said:
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
Click to expand...
Click to collapse
That doesn't surprise me at all. As I said earlier, you cannot expect to flash any firmware with Odin. It is dismaying how many people state that you can do so when they don't really know that to be true. Or to be more precise, they think they know and want to help someone. But in fact, they don't understand the subject in any depth, have no reasonable basis to believe that they do and good intentions notwithstanding, do a real disservice by spreading dangerously inaccurate information.
To reiterate, you cannot flash any file with Odin. Someone who tells you that you can flash any carrier's S5 firmware onto your S5 is demonstrably wrong. It will work in some cases and they are making a bad assumption that because it worked in one case that it can be universally done. As you found out firsthand, that is not true. Someone who assumes it is universally true and further presents that unfounded assertion as fact isn't exercising sound judgement.
This is an oversimplification, but to give you a rough idea of what is going on.. hidden.img.ext4 contains carrier specific information. And it is partitioned. So if you flash a firmware from another carrier and it happens to be formatted as a larger partition, the flash will corrupt the partition structure, leading to the Odin error writing to hidden.img.ex4 and soft brick your phone.
Long story short, don't blindly believe everyone that makes authoratative statements about what you can safely do. Try to understand the process as much as possible yourself, so that you can spot the worst inconsistencies. And look for a sense of how deep and consistent someone's knowledge of a subject is before taking their advice.
To recover after flashing an incompatible flash from another carrier, you would ideally flash a stock copy of hidden.img.ext4 and the PIT from the original carrier. If you don't care aout Knox, flashing CWM will typically resolve the issue as well. Also if you understand partitioning structures, better informed users can discern in advance if a carrier x firmware can be safely flashed or not.
.
fffft said:
That doesn't surprise me at all. As I said earlier, you cannot expect to flash any firmware with Odin. It is dismaying how many people state that you can do so when they don't really know that to be true. Or to be more precise, they think they know and want to help someone. But in fact, they don't understand the subject in any depth, have no reasonable basis to believe that they do and good intentions notwithstanding, do a real disservice by spreading dangerously inaccurate information.
To reiterate, you cannot flash any file with Odin. Someone who tells you that you can flash any carrier's S5 firmware onto your S5 is demonstrably wrong. It will work in some cases and they are making a bad assumption that because it worked in one case that it can be universally done. As you found out firsthand, that is not true. Someone who assumes it is universally true and further presents that unfounded assertion as fact isn't exercising sound judgement.
This is an oversimplification, but to give you a rough idea of what is going on.. hidden.img.ext4 contains carrier specific information. And it is partitioned. So if you flash a firmware from another carrier and it happens to be formatted as a larger partition, the flash will corrupt the partition structure, leading to the Odin error writing to hidden.img.ex4 and soft brick your phone.
Long story short, don't blindly believe everyone that makes authoratative statements about what you can safely do. Try to understand the process as much as possible yourself, so that you can spot the worst inconsistencies. And look for a sense of how deep and consistent someone's knowledge of a subject is before taking their advice.
To recover after flashing an incompatible flash from another carrier, you would ideally flash a stock copy of hidden.img.ext4 and the PIT from the original carrier. If you don't care out Knox, flashing CWM will typically resolve the issue as well. Also if you understand partitioning structures, better informed users can discern in advance if a carrier x firmware can be safely flashed or not.
Click to expand...
Click to collapse
Wow.. and wow (+thanks )
So (long story short): besides flashing CWM/TWRP/Philz i could flash a .pit from a 16GB S5 (of the same model) that comes with a PHN firmware, and then flash the PHN firmware itself and retain 0x0
born4trance said:
So (long story short): besides flashing CWM/TWRP/Philz i could flash a .pit from a 16GB S5 that has a PHN firmware on it (and retain 0x0)
Click to expand...
Click to collapse
Flashing a custom recovery would increment Knox to 0x1. But it should remain 0x0 if you use the proper PIT corresponding to the new stock firmware. I haven't tested that (as I don't really care about Knox personally) but I don't see any logical reason that Knox would be concerned with that scenario, nor heard of any reports of it happening to anyone.
PHN.. is Netherlands? So assuming that you have say, a 16 GB SM-G900F, you should be able to flash a 900F PHN firmware successfully and safely if you do so in conjunction with a PIT file for a 16 GB PHN 900F. I presume that the flash won't trip Knox either but I have not actually done so personally.
Theoretically the write could still fail on an aboot auth failure but I haven't seen any evidence that carriers are locking down their bootloaders that tightly and don't think that would be a likely impediment.
.
fffft said:
PHN.. is Netherands?
Click to expand...
Click to collapse
Correct: For non branded / SIM-lock free
fffft said:
So assuming that you have say, a 16 GB SM-G900F, you should be able to flash a 900F PHN firmware successfully and safely if you do so in conjunction with a PIT file for a 16 GB PHN 900F. I presume that the flash won't trip Knox either but I have not actually done so personally.
Click to expand...
Click to collapse
I indeed own a SM-G900F and its also important to mention that the partition layout differs between 16GB/32GB models
Now to get ahold of the correct .pit (still looking)
Hello everyone! I've bought a Galaxy S5 some days ago(SM-G900F) but it came with this firmware: KOT49H.G900FFXXU1ANE2,and it is branded by TIM Carrier. Now my question is,I want to un-brand it and install stock OS so I have updates earlier,but I am scared that I could trip KNOX Counter and lose warranty. Anyone has a procedure to do this? Also,will I lose warranty? Thanks in advance,and sorry if this may not be the right section.
Wolf80 said:
Hello everyone! I've bought a Galaxy S5 some days ago(SM-G900F) but it came with this firmware: KOT49H.G900FFXXU1ANE2,and it is branded by TIM Carrier. Now my question is,I want to un-brand it and install stock OS so I have updates earlier,but I am scared that I could trip KNOX Counter and lose warranty. Anyone has a procedure to do this? Also,will I lose warranty? Thanks in advance,and sorry if this may not be the right section.
Click to expand...
Click to collapse
There is always a risk when playing around with the firmware no matter the phone make, model and carrier/network. For what it's worth, I got a second hand branded S5 (SM-G900F) and flashed the unbranded UK (BTU) firmware on it after unlocking it using Odin. Knox still intact on mine as far as I can tell, reading "0x0". You might need to reset it a few times and maybe clear DALVIK/ART cache a few times to get the right CSC to appear on the phone and get OTA updates. But again in my experience everything is still working after debranding.
Wolf80 said:
Hello everyone! I've bought a Galaxy S5 some days ago(SM-G900F) but it came with this firmware: KOT49H.G900FFXXU1ANE2,and it is branded by TIM Carrier. Now my question is,I want to un-brand it and install stock OS so I have updates earlier,but I am scared that I could trip KNOX Counter and lose warranty. Anyone has a procedure to do this? Also,will I lose warranty? Thanks in advance,and sorry if this may not be the right section.
Click to expand...
Click to collapse
Just download the latest stock firmware United Kingdom / Europe (BTU) from Sammobile,, download Odin then use Odin to flash the BTU firmware, Factory Reset the phone after flashing to set the correct CSC and clear the Caches, flashing a stock rom won't trip KNOX. Flashing Custom roms,Custom Recovery, kernels etc will, staying stock wont.
Hi there
My galaxy s5 got into water yesterday so I checked the back of the phone and saw the litmus paper became red, then I thought that now I can finally root my phone without concerning lol ), then I flashed Modem: XXU1ANI1 and intend to flash rom later. But then I told my friend who works at Samsung Services and he checked my phone and said that it has no problem so it is still under warranty. So I want to ask you guys that whether I flashed the modem XXU1ANI1 affect my warranty or later if I can update stock firmware via OTA. Can I flash back to the latest stock modem XXU1ANG3 for G900H Vietnam without tripping knox? or if it has any problem?
Please help me , I really appreciate any help you guys can provide.
phong2503 said:
Hi there
My galaxy s5 got into water yesterday so I checked the back of the phone and saw the litmus paper became red, then I thought that now I can finally root my phone without concerning lol ), then I flashed Modem: XXU1ANI1 and intend to flash rom later. But then I told my friend who works at Samsung Services and he checked my phone and said that it has no problem so it is still under warranty. So I want to ask you guys that whether I flashed the modem XXU1ANI1 affect my warranty or later if I can update stock firmware via OTA. Can I flash back to the latest stock modem XXU1ANG3 for G900H Vietnam without tripping knox? or if it has any problem?
Please help me , I really appreciate any help you guys can provide.
Click to expand...
Click to collapse
Yes, you can flash back to your stock modem without tripping Knox (if it has not been tripped).
To check whether your Knox was tripped or not, you can use Phone INFO ★Samsung★ app and look for the Knox Warranty Void status (under GENERAL INFO section).
Thank you so much