[Q] Software Update for my S5 (SM-G900F) - Galaxy S 5 Q&A, Help & Troubleshooting

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)

Related

[Q] Flashing ROM of Same Region but different Product Code with Odin

Hi all. I wanted to flash a ROM from Same Region (same CSC) but different Product Code with Odin cause I can't already wait for the OTA or kies update for my specific product code.
Question: Will this trip knox flag to 0x1 and/or flash counter?. I think it will not but I am not sure.
lou_pams said:
Hi all. I wanted to flash a ROM from Same Region (same CSC) but different Product Code with Odin cause I can't already wait for the OTA or kies update for my specific product code.
Question: Will this trip knox flag to 0x1 and/or flash counter?. I think it will not but I am not sure.
Click to expand...
Click to collapse
Flashing Stock ROM does not trip KNOX.. However some people have reported that it has tripped for them, It shouldn't but there is a small possibility from what others have said.

Rooted with RDLV, Knox 0x0. But, what now?

I have rooted my Note 3 succesfully with RDLV, without tripping Knox. I am really happy with that.
My phone is branded Vodafone, with CSC N9005VFGBMI1. The latest Firmware for that is MI7.
I have a few questions about this, hope someone can help me with this.
I want to update to N9005XXUDMK2_N9005OXADMK2_BTU.zip. I know it's a different csc, is that possible? (I know I will lose Knox 0x0)
If that is possible, how do I do that?
Thanks!
Pierre118 said:
I have rooted my Note 3 succesfully with RDLV, without tripping Knox. I am really happy with that.
My phone is branded Vodafone, with CSC N9005VFGBMI1. The latest Firmware for that is MI7.
I have a few questions about this, hope someone can help me with this.
I want to update to N9005XXUDMK2_N9005OXADMK2_BTU.zip. I know it's a different csc, is that possible? (I know I will lose Knox 0x0)
If that is possible, how do I do that?
Thanks!
Click to expand...
Click to collapse
Somebody show me the way? Just flash the BTU with Odin? I don't mind tripping knox.
Pierre118 said:
I have rooted my Note 3 succesfully with RDLV, without tripping Knox. I am really happy with that.
My phone is branded Vodafone, with CSC N9005VFGBMI1. The latest Firmware for that is MI7.
I have a few questions about this, hope someone can help me with this.
I want to update to N9005XXUDMK2_N9005OXADMK2_BTU.zip. I know it's a different csc, is that possible? (I know I will lose Knox 0x0)
If that is possible, how do I do that?
Thanks!
Click to expand...
Click to collapse
1. You should read the thread on how to update the system using Mobile Odin PRO without losing knox 0x0. Also keep in mind that you need to stop both ROM and security automatic updates in order to avoid having the knox flag triggered.
2. Also check http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=VOD#firmware
3. If you really want to change CSC away from VOD and for instance to BTU you should probably do that first at MI7 level (from your current MI7 VOD to MI7 BTU) if you want maximum safety and to be able to root again with knox 0x0. You might also need an app to help you checking/changing CSC, look around for threads discussing that specific topic.
Can I safely use a firmware with a CSC N9005VFGDMJ1? Or do I always have to use a firmware of the original CSC? (N9005VFGBMI1)?
Pierre118 said:
Can I safely use a firmware with a CSC N9005VFGDMJ1? Or do I always have to use a firmware of the original CSC? (N9005VFGBMI1)?
Click to expand...
Click to collapse
You do not need to use a firmware with the original CSC, BUT:
- you should try to do as much of the changes as possible on OLDER versions with the old bootloader (so that you can still root and keep knox 0x0)
- writing a ROM with a different CSC will very often NOT change your effective CSC - many ROMs are multi-CSC and you might keep existing CSC on the new ROM; in order to finalize the change you will need to use a program that forces the CSC change (and you will see that the CSC was changed since it will totally wipe the user data in the phone - like a full factory reset)
- you should also be aware that some changes might mess things on your phone, so instead of jumping to the first change you can think-off you should first try to read more around here.
xclub_101 said:
You do not need to use a firmware with the original CSC, BUT:
- you should try to do as much of the changes as possible on OLDER versions with the old bootloader (so that you can still root and keep knox 0x0)
- writing a ROM with a different CSC will very often NOT change your effective CSC - many ROMs are multi-CSC and you might keep existing CSC on the new ROM; in order to finalize the change you will need to use a program that forces the CSC change (and you will see that the CSC was changed since it will totally wipe the user data in the phone - like a full factory reset)
- you should also be aware that some changes might mess things on your phone, so instead of jumping to the first change you can think-off you should first try to read more around here.
Click to expand...
Click to collapse
Thanks for your helpful reply. I will take your advice and will read more around here before I do things I don't understand. I'm rooted now at firmware MI7, with 0x0 Knox. I did a lot of reading before I took that step. I will take time before I do the next one.
Pierre118 said:
Thanks for your helpful reply. I will take your advice and will read more around here before I do things I don't understand. I'm rooted now at firmware MI7, with 0x0 Knox. I did a lot of reading before I took that step. I will take time before I do the next one.
Click to expand...
Click to collapse
Don't forget to disable automatic updates and security updates. Especially read the thread on Mobile Odin PRO and updating while keeping knox 0x0. (CSC is almost irrelevant in most cases - as long as 3G/4G from your provider is correctly detected; if you are rooted with knox 0x0 you will ALWAYS want to update the ROM manually under YOUR control and not when Samsung or your carrier wants to update your phone).
xclub_101 said:
Don't forget to disable automatic updates and security updates. Especially read the thread on Mobile Odin PRO and updating while keeping knox 0x0. (CSC is almost irrelevant in most cases - as long as 3G/4G from your provider is correctly detected; if you are rooted with knox 0x0 you will ALWAYS want to update the ROM manually under YOUR control and not when Samsung or your carrier wants to update your phone).
Click to expand...
Click to collapse
What do you freeze in titanium backup so it won't update.
Dattack said:
What do you freeze in titanium backup so it won't update.
Click to expand...
Click to collapse
Software Update (also Samsung Hub Update, but that is just since I never use the Samsung Hub). Right now I did not freeze the Security Policy Update but I am tempted - but on that I first disabled automatic security updates somewhere in settings.
Pierre118 said:
Can I safely use a firmware with a CSC N9005VFGDMJ1? Or do I always have to use a firmware of the original CSC? (N9005VFGBMI1)?
Click to expand...
Click to collapse
In fact N9005VFGDMJ1 and N9005VFGBMI1 are from the same CSC

[Q] Downgrading Galaxy Note 3 SM-N9005 from 4.4.2→4.3 without E-Fuse/Guarantee Loss

[Q] Downgrading Galaxy Note 3 SM-N9005 from 4.4.2→4.3 without E-Fuse/Guarantee Loss
Hello everybody.
Is there any way to downgrade the Galaxy Note 3 SM-N9005 from 4.4.2 to 4.3, without triggering the E-Fuse-Chip to short-circuit which causes feautre-loss and guarantee loss?
It's OK, if the Guarantee is just TEMPORAIRLY disabled, while the downgrade is in progress
But after the downgrade, the device should be like a new one.
I also don't want any damage on my device like lower processing power, guarantee loss, heat problems or compatibility problems.
Also, i've already backed all data up, so backup isn't really needed.
Please don't ask me, why i want to take this downgrade. KitKat has so many unknown software disadvantages, and compatibility problems and it's too bogus.
If you know, how to do this, but you don't think, that a downgrade is not needed, please post it yet.
Short Story
The Shop, where the Note 3 is bought from mentioned this device to have Android 4.3 Jelly Bean, but i was shocked/disappointed, after i saw KitKat.​
The KitKat-Wafer is quite tasty, but the Android-Operation-System is quite bitter.
I really appreciate any help you can provide.
Far as I know flashing an official binary will not trip your Knox. Don't know about KK to JB downgrades because the bootloader can not be flashing back to JB after KK has been applied.
AO7 said:
Far as I know flashing an official binary will not trip your Knox. Don't know about KK to JB downgrades because the bootloader can not be flashing back to JB after KK has been applied.
Click to expand...
Click to collapse
Thank you very much for answering.
So, i just have to start ODIN, and let's/here we go?
Right?
What i understand
So that means:
Download ODIN
Install ODIN
Download Firmware
Connect Note 3 to PC
[*]Let's go (Load Firmware on Note 3)
Will the downgrade be sucessfully?
No Guarantee Loss
[*]No eFuse-Trigger
No Feature Loss
No Other Problems
Temporaire guarantee loss is OK, if it can be restored.
But i don't want to Trigger the EFuse-Short Circuit.
Missing
Step 1 download and install Samsung/ Kies USB drivers .
Open Odin put relevant files in correct box.
Connect phone to PC
Make sure correct boxes ticked in Odin .
Hit start button
No Guarantee Loss >>> No not 100% possible .
Knox Triggered by custom rom / kernel/ recovery not by stock rom .
Really would not downgrade as i don't see you as understanding the basics .
Is your EFS folder backed up is question 1 as a downgrade may lose your IMEI .
Hannah Stern said:
What i understand
So that means:
Download ODIN
Install ODIN
Download Firmware
Connect Note 3 to PC
[*]Let's go (Load Firmware on Note 3)
Will the downgrade be sucessfully?
No Guarantee Loss
[*]No eFuse-Trigger
No Feature Loss
No Other Problems
Temporaire guarantee loss is OK, if it can be restored.
But i don't want to Trigger the EFuse-Short Circuit.
Click to expand...
Click to collapse
I'm gonna agree with the poster above Hannah. It looks like you don't really understand what you are doing.
Here's a very quick rundown:
1. Get the Samsung phone drivers
2. Get Odin 3.09
3. Get EFS professional and make several EFS backups of all partitions
4. If your phone is carrier branded only download stock firmware specifically for your carrier brand. Otherwise any region stock firmware should work. Do not use Hong Kong FW unless your phone is from HK. for safety, stick to firmware of your approximate geographical area to avoid possible issues with modems.
5. Read, read, and read as many threads on this forum as you can.
6. There are a bunch of steps after this which i won't all type out. Refer to point 5...
JJEgan said:
Missing
Step 1 download and install Samsung/ Kies USB drivers .
Open Odin put relevant files in correct box.
Connect phone to PC
Make sure correct boxes ticked in Odin .
Hit start button
No Guarantee Loss >>> No not 100% possible .
Knox Triggered by custom rom / kernel/ recovery not by stock rom .
Really would not downgrade as i don't see you as understanding the basics .
Is your EFS folder backed up is question 1 as a downgrade may lose your IMEI .
Click to expand...
Click to collapse
OK, Understood
AO7 said:
I'm gonna agree with the poster above Hannah. It looks like you don't really understand what you are doing.
Here's a very quick rundown:
1. Get the Samsung phone drivers
2. Get Odin 3.09
3. Get EFS professional and make several EFS backups of all partitions
4. If your phone is carrier branded only download stock firmware specifically for your carrier brand. Otherwise any region stock firmware should work. Do not use Hong Kong FW unless your phone is from HK. for safety, stick to firmware of your approximate geographical area to avoid possible issues with modems.
5. Read, read, and read as many threads on this forum as you can.
6. There are a bunch of steps after this which i won't all type out. Refer to point 5...
Click to expand...
Click to collapse
OK, Thanks very much.
I've got a German SM-N9005
What is the Newest Baseband Version with Android 4.3?
I think, it is:
PDA: N9005XXUDMJ7
CSC: N9005OXADMJ4
Or is MK2 newer?
Hannah Stern said:
I've got a German SM-N9005
What is the Newest Baseband Version with Android 4.3?
I think, it is:
PDA: N9005XXUDMJ7
CSC: N9005OXADMJ4
Or is MK2 newer?
Click to expand...
Click to collapse
Very basic Samsung FW decoder:
Device identifer - region code - FW identificator ( The lower the letter in the alphabet the newer the software)
N9005 - XXU - MJ7
This is the last 4.3 FW for DBT (Generic Germany)
http://samsung-updates.com/details/22095/Galaxy_Note_3_Snapdragon/SM-N9005/DBT/N9005XXUDMK2.html
AO7 said:
It looks like you don't really understand what you are doing.
Click to expand...
Click to collapse
That's why i was asking.
>>> But thank you very much for letting me know, which is the lastest 4.3-JB-Firmware for the Galaxy Note 3 and telling me, how Samsung's Firmware Codes work.
I owe you something for that great post...
The only problems are the upload sites:
Both pages Suck
UL.TO - Dead Link
RapidGator - Struggle to Download
But i managed it to download that file.
Thank you very much @AO7. The world needs more people like you.
Baseband is Modem and not always updated at the same time as firmware updated .
@JJEgan
 @AO7
I'm trapped.
Is there any way to
Root without triggering EFuse
or EFS-Backup without root?
Here's my thread about EFuse. (This text is the link itself)
Hannah Stern said:
@JJEgan
@AO7
I'm trapped.
Is there any way to
Root without triggering EFuse
or EFS-Backup without root?
Here's my thread about EFuse. (This text is the link itself)
Click to expand...
Click to collapse
I use EFS Backup Pro to backup my modem and EFS partitions but that requires root. TWRP also has the ability to backup the modem partition, but flashing a custom recovery will trigger knox 0x1.
I've tripped my knox over a year ago so I don't keep up with how to root the phone while keeping knox 0x0. A quick google gave me this post but I have not tried it myself.
If you manage to root your phone and keep it 0x0 than technically I imagine you can backup your EFS. The question is it's still worthwhile to go to all this trouble. The N9005 is approaching its' second birthday. In my personal case, since I don't care for extended warranties on electronics, my legal basic warranty already expired some time ago anyway.
there might be some obscure proprietary Samsung features that depend on Knox. But other than those, I see no real point in trying to keep your phone 0x0.
AO7 said:
I use EFS Backup Pro to backup my modem and EFS partitions but that requires root. TWRP also has the ability to backup the modem partition, but flashing a custom recovery will trigger knox 0x1.
I've tripped my knox over a year ago so I don't keep up with how to root the phone while keeping knox 0x0. A quick google gave me this post but I have not tried it myself.
If you manage to root your phone and keep it 0x0 than technically I imagine you can backup your EFS. The question is it's still worthwhile to go to all this trouble. The N9005 is approaching its' second birthday. In my personal case, since I don't care for extended warranties on electronics, my legal basic warranty already expired some time ago anyway.
there might be some obscure proprietary Samsung features that depend on Knox. But other than those, I see no real point in trying to keep your phone 0x0.
Click to expand...
Click to collapse
EFS backup always shows up an error while starting up. Then it closes itself.
EFS and EFuse...:crying:
does anyone here still have that jelly bean file?
pottylotty said:
does anyone here still have that jelly bean file?
Click to expand...
Click to collapse
What JB file ???

Difference between model number and about device

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

Can i flash my samsung s10 plus with different region stock os using odin without bre

I bought my mobile from UAE and am using it in india. When i compare my s10 plus with s10 indian variant , s10 front camera quality far beter than my s10 plus.so i m planning to flash indian region os using odin and have some doubt on this. Please some one clear my doubts
1. Will knox service get tripped, if i flash indian os using odin.?
2. Is this issue occurs due to different region os or hardware fault
3. If knox gets tripped, will it be fixed later ?
Thanks
Doesnt trip knox if you flash a stock firmware
Player04 said:
Doesnt trip knox if you flash a stock firmware
Click to expand...
Click to collapse
Thanks for your reply, will i get OTA updates after installed my region firmware.?
Anyone please respond my question..am getting different answer from different tech sites. Some people are saying flash different region rom will affect the knox. Some of us telling, it wont. Please confirm it.
saravanan vs said:
Thanks for your reply, will i get OTA updates after installed my region firmware.?
Click to expand...
Click to collapse
Yes you will get OTA after flashing a stock firmware using Odin
Use the main CSC file (not the HOME-CSC) if changing region
I always enable OEM Unlock in developer options before attempting to change CSC with Odin (disable OEM Unlock again after you have completed flash to enable full security)
You can only flash a firmware file that matches your model Variant
E.g. you cannot flash 975F firmware to an 975U model etc
Finally be aware your phone will be wiped after the flash completes so backup everything before you start. Good luck
Thanks a lot for your reply. And i am not get your points about CSC...can you please explain little more
saravanan vs said:
Thanks a lot for your reply. And i am not get your points about CSC...can you please explain little more
Click to expand...
Click to collapse
Firmware for Odin flash contains 2 CSC files. The HOME_CSC file will NOT erase your device, the CSC one will. However as you are changing CSC code it is best to use the normal CSC file and allow your device data to be erased as it’s not a good idea to mix data and settings between different firmware
Hope this helps and good luck
Thanks for your reply

Resources