Related
hello folks,
i've searched the forum and couldn't find an explicit answer for my question.
i have i9500 and i'm upgrading it's firmware to the lastest available on weekly bases, i use odin and just flash the newer firmware over the existing one, without wipe and it all seems to work just fine as it is.
now, i know for a fact that my bootloader is KNOX enabled and my KNOX flag is 0x0 (active warranty)
my question is - can (not should - bat CAN) i flash custom roms? i mean, i don't care about warrany or KNOX flag 0x1, just want to know if i can grab PAC i.e and follow the regular installation instruction without hard-bricking my device?
i would very appreciate any certified answer.
regards
There are some ROMs that u can flash without void ur warranty and u will have android 4.3. Anyway If u dont care about warranty only u have to:
1. Download correct Rom for ur device (.tar file)
2. Open Odin and flash it
OR
1. Download correct Rom for u device (.zip file)
2. Open custom recovery, wipe all and install the ROM
3. Enjoy
re: KNOX
eviatar said:
hello folks,
i've searched the forum and couldn't find an explicit answer for my question.
i have i9500 and i'm upgrading it's firmware to the lastest available on weekly bases, i use odin and just flash the newer firmware over the existing one, without wipe and it all seems to work just fine as it is.
now, i know for a fact that my bootloader is KNOX enabled and my KNOX flag is 0x0 (active warranty)
my question is - can (not should - bat CAN) i flash custom roms? i mean, i don't care about warrany or KNOX flag 0x1, just want to know if i can grab PAC i.e and follow the regular installation instruction without hard-bricking my device?
i would very appreciate any certified answer.
regards
Click to expand...
Click to collapse
Ok, here are the prerequisites for not getting the KNOX POX:
#1: Don't allow the flashing of the OTA update
#2: Don't Odin flash the official stock TAR firmware. (SamMobile or elsewhere)
#3: Don't Odin flash the 4.3 NON-HLOS.BIN
#4: Don't Odin flash any bootloaders
If you have NOT done either one of those four things you will NOT catch the KNOX.
You can Odin flash the 4.3 MODEM but it is completely optional.
See which one has the best signal for you.
( or keep the exisiting MODEM which is already in your phones.)
The phone will work just find with either the 4.3 modem or your existing one.
You can flash any cwm/twrp flashable 4.3 or 4.2.2 zip file stock or custom roms.
If you follow these rules above you will not loose audio, signal or wifi and you will not catch KNOX POX.
Now that's not too difficult to understand right? LOL
eviatar said:
hello folks,
i've searched the forum and couldn't find an explicit answer for my question.
i have i9500 and i'm upgrading it's firmware to the lastest available on weekly bases, i use odin and just flash the newer firmware over the existing one, without wipe and it all seems to work just fine as it is.
now, i know for a fact that my bootloader is KNOX enabled and my KNOX flag is 0x0 (active warranty)
my question is - can (not should - bat CAN) i flash custom roms? i mean, i don't care about warrany or KNOX flag 0x1, just want to know if i can grab PAC i.e and follow the regular installation instruction without hard-bricking my device?
i would very appreciate any certified answer.
regards
Click to expand...
Click to collapse
Yes, you can, but only custom roms based on 4.3 bootloader.
Enviado desde mi GT-P7510 usando Tapatalk 2
i have a galaxy s4 i9500 with android 4.2.2 and i read that if i update to 4.3 i will get a security feature called KNOX which tracks your custon kernel flashes and cannot be reset. and also you can't flash back to 4.2.2. is that true?
if it is so:
1.what will happen if you'll try to flash 4.2.2 with odin?
2.what other disadvantages KNOX have?
3.shoiuld i really care about KNOX if my phone's warranty is already void?
4.can KNOX harm my device by any way?
please answer the question by order!
i am thankful for any help i can get in this forum and appriciate everyone who answers my questions beacause i wanna know if i should update or not.
P.S.:if i have 4.2.2 can i install cyanogenmod 11 (unofficial) or i need to update to 4.3 to do that?
Knox doesn't track custom kernel flashes specifically, it detects if you flash anything non-samsung (whether it's cf-autoroot, custom recovery or whatnot). It just says knox 0x0 or 0x1, if it's 0x1 your warranty is void. There is another counter detecting number of flashes, but that can be reset with TriangleAway. Knox cannot be reset. EDiT: TriangleAway only works on i9505, sorry.
1. If you don't have a knox-enabled bootloader you can flash an older rom version. Boot into recovery mode, if you see a knox counter there you cannot flash older firmwares than the one you already have (on i9505 there was one knox-enabled fw before 4.3). If you don't see anything knox related you can flash what you want, but once you flash a knox enabled rom you cannot downgrade to older official samsung roms.
2. Besides not being able to reset the knox counter there isn't really anything special. Atleast none that I have noticed. SuperSU asks if you want do disable knox-features upon first run.
3. No, then it doesn't really matter. Unless you really want to flash an older firmware from samsung.
4. No, it's a samsung feature.
If I were you I'd flash official 4.3 builds anyway, as they're generally much faster and much more stable, atleast for me on i9505. And the improvements outweigh the downsides of knox. 4.3 feature list: http://www.sammobile.com/2013/10/18...al-android-4-3-update-for-galaxy-s4-gt-i9500/
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)
Hi,
was realesed in Portugal the first Android 5.0 Lollipop rom Portugal (Vodafone) (TCL) for the model SM-G900F with the PDA G900FXXU1BNL9.
Can I flash this stock rom on my phone ?
If not can I flash other stock ROMs?
Will this trip the Knox flash to 0x1?
How can i flash it?
This are my phone references:
SM-G900F
Portugal(TPH) - TPH
PDA: G900FXXU1ANJ1
CSC: G900FOXX1ANJ1
MODEM: G900FXXU1ANJ1
Version: Android 4.4.2
Yes you can, it should work fine
bloodrain954 said:
Yes you can, it should work fine
Click to expand...
Click to collapse
Bit will it trio knox?
How can i flash?
Stock ROM will not trip KNOX
Flash using ODIN
bloodrain954 said:
Yes you can, it should work fine
Click to expand...
Click to collapse
*Detection* said:
Stock ROM will not trip KNOX
Flash using ODIN
Click to expand...
Click to collapse
But wich stock ROM are sutible for my phone?
I am a newbie, i dont really underatand much..
Can you point any tutorials por somethings here i can learn how to do it please?
In this thread it says:
" Even if you flash a KNOX-enabled firmware via odin (e.g. the latest fw) knox will be set to 0x1"
http://forum.xda-developers.com/showthread.php?t=2595889
What should i belive?
You should not flash anything yet, you should spend a few days reading threads from the beginning until you understand exactly what to do
All the info you need has been posted in many threads here, start reading until you know exactly what you're doing, and you understand the difference between a KNOX enabled ROM and a stock ROM
*Detection* said:
You should not flash anything yet, you should spend a few days reading threads from the beginning until you understand exactly what to do
All the info you need has been posted in many threads here, start reading until you know exactly what you're doing, and you understand the difference between a KNOX enabled ROM and a stock ROM
Click to expand...
Click to collapse
Thats exactly what i am doing bit i AM going crazy because some people say that flash ROMs with Odin activate the knox flag, and others say the oposit. So i dont really know what to belive ir what to do
Flash custom ROM / Recovery = KNOX 0x1
Flash stock = KNOX 0x0
I sucessfully installed Lollipop on my Galaxy S5! I installed the Spain no carrier version!
Just one more question, when the ROM that my phone came with gets out, should I install her or not?
Can i replace one rom for another?
Hi, i know there is another thread but i think is not the same problem.
In "About Device" my S5 show SM-G900F branded for United Arab Emirates (XSG - G900FXXU1POEC) but in "Download Mode" the screen info show me different version of galaxy S5..... SM-G9006V wich is from China.....wtf?
Is something like that legit?
My question is if i want to flash new firmware for XSG ( G900FXXU1POI1 ) will it work or i brick device / or trip Knox?
The firmware for SM-G9006V use different CSC and if i try to flash this will triping KNOX waranty, is corect?
INFO
-I forgot to mention that sees no new firmware via Kies, OTA or Smart Switch although there are two firmware already released.
-When i try "Firmware upgrade and initialization" in Kies 3 after type of Model name field -SM-G900F and serial number
its say my serial number is wrong but when type in Model name field SM-G9006V and serial the procedure want to continue wich meant is OK.
The System operational you need to download the exact one that is described on Download Mode.
The Download mode is the real one.
If you want to flash only the modem/CSC you can flash the G900F.
But the Kernel and the Bootloader i think you need to flash the G9006V.
if you flash an Firmware differently from your download mode you can brick your device (Soft-Brick, not Hard-Brick)
If you bought it from someone, you can easily edit on config to show anything you want on About Device.
Hi, thanks for answer, but its something i dont get it.
How they manage to do some thing, flashing G9006V firmware and after that flashing G900F XSG firmware ( AP-CP-CSC) without triger the Knox.
Anyway, Is there an easier way to flash the latest update for the UAE of September 2015 and to keep the same configuration, the bootloader from G9006V,
XSG G900F kernel and CSC from UAE without enable Knox or brick my phone.
cryogent said:
Hi, thanks for answer, but its something i dont get it.
How they manage to do some thing, flashing G9006V firmware and after that flashing G900F XSG firmware ( AP-CP-CSC) without triger the Knox.
Anyway, Is there an easier way to flash the latest update for the UAE of September 2015 and to keep the same configuration, the bootloader from G9006V,
XSG G900F kernel and CSC from UAE without enable Knox or brick my phone.
Click to expand...
Click to collapse
As far as I know only custom kernels and custom recoveries trigger Knox. Technically custom non touchwiz roms also will I believe, but since you flash them from recovery that's a little implied, not 100% sure on that though, someone correct me if I'm wrong.
Sent from my SAMSUNG-SM-G900A using Tapatalk
To flash anything you need to root. therefore you are going to trigger the knox.
I BELIEVE that you can only flash original firmware TOUCH WIZ without root
DBlackFireD said:
To flash anything you need to root. therefore you are going to trigger the knox.
I BELIEVE that you can only flash original firmware TOUCH WIZ without root
Click to expand...
Click to collapse
Rooting does not trigger Knox.
Sent from my SAMSUNG-SM-G900A using Tapatalk
The only root method that WON'T trip knox is towelroot, and that method won't work on anything other than KitKat.
CF Root WILL trip knox.
TWRP WILL trip knox.
So for most people rooting will trip knox
http://i.imgur.com/rVnFwJM.jpg
I would like to point out that using apps such as kingoroot allow one click roots that won't trip Knox. After the build.prop is modified they can just unroot and it'll be like nothing happened
justinxfan said:
I would like to point out that using apps such as kingoroot allow one click roots that won't trip Knox. After the build.prop is modified they can just unroot and it'll be like nothing happened
Click to expand...
Click to collapse
Point noted....I have no experience of those root methods....
The methods I mentioned are the main methods (with dedicated threads) to be found/mentioned on XDA........
http://i.imgur.com/rVnFwJM.jpg
Thank you all for your help but leave this thread because I gave the phone back and chose another producer.
The problem could not be solved by those at the store because all the phones were lot of the same trouble.
Sorry I can not help you with other information in the future.
Thank
Sent from my XT1063 using Tapatalk