Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,730,397 Members 47,050 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Software Update for my S5 (SM-G900F)

Tip us?
 
gee2012
Old
#11  
gee2012's Avatar
Recognized Contributor
Thanks Meter 2802
Posts: 7,704
Join Date: Jul 2010
Location: Heerlen
Quote:
Originally Posted by born4trance View Post
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
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.
USE Search: /this thread /all threads/Google before posting your question, you`re most likely not the first one having this issue
 
born4trance
Old
(Last edited by born4trance; 13th July 2014 at 08:40 PM.)
#12  
born4trance's Avatar
Member
Thanks Meter 10
Posts: 87
Join Date: Jan 2008
Location: Rotterdam(ned)
Quote:
Originally Posted by gee2012 View Post
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.
I already quoted the firmware i (currently) have, a few posts back
OnePlus One (Sandstone Black 64GB) Order Status: Shipment Pending

- REQuest: A .pit for a 16GB SM-G900F, to be used with a PHN firmware (non-branded)
- Don't flash the .pit i posted on XDA! (read why and also read this)

- Want to view/read my posts? Click here
- My (Semi) Portable Minecraft Launcher: http://web.minecraftnoob.com
 
gee2012
Old
#13  
gee2012's Avatar
Recognized Contributor
Thanks Meter 2802
Posts: 7,704
Join Date: Jul 2010
Location: Heerlen
Quote:
Originally Posted by born4trance View Post
I already quoted the firmware i (currently) have, a few posts back
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.
USE Search: /this thread /all threads/Google before posting your question, you`re most likely not the first one having this issue
 
born4trance
Old
(Last edited by born4trance; 13th July 2014 at 08:53 PM.)
#14  
born4trance's Avatar
Member
Thanks Meter 10
Posts: 87
Join Date: Jan 2008
Location: Rotterdam(ned)
Quote:
Originally Posted by gee2012 View Post
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.
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
OnePlus One (Sandstone Black 64GB) Order Status: Shipment Pending

- REQuest: A .pit for a 16GB SM-G900F, to be used with a PHN firmware (non-branded)
- Don't flash the .pit i posted on XDA! (read why and also read this)

- Want to view/read my posts? Click here
- My (Semi) Portable Minecraft Launcher: http://web.minecraftnoob.com
 
fffft
Old
(Last edited by fffft; 14th July 2014 at 11:06 AM.)
#15  
fffft's Avatar
Senior Member
Thanks Meter 193
Posts: 611
Join Date: Jul 2013
Quote:
Originally Posted by gevensa View Post
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?
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 ----------

Quote:
Originally Posted by born4trance View Post
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".

So there are some exceptions =/

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.

.
The Following 2 Users Say Thank You to fffft For This Useful Post: [ Click to Expand ]
 
born4trance
Old
(Last edited by born4trance; 14th July 2014 at 09:20 AM.)
#16  
born4trance's Avatar
Member
Thanks Meter 10
Posts: 87
Join Date: Jan 2008
Location: Rotterdam(ned)
 

Quote:
Originally Posted by fffft View Post
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.


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
OnePlus One (Sandstone Black 64GB) Order Status: Shipment Pending

- REQuest: A .pit for a 16GB SM-G900F, to be used with a PHN firmware (non-branded)
- Don't flash the .pit i posted on XDA! (read why and also read this)

- Want to view/read my posts? Click here
- My (Semi) Portable Minecraft Launcher: http://web.minecraftnoob.com
 
fffft
Old
(Last edited by fffft; 14th July 2014 at 11:07 AM.)
#17  
fffft's Avatar
Senior Member
Thanks Meter 193
Posts: 611
Join Date: Jul 2013
Quote:
Originally Posted by born4trance View Post
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)

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.

.
The Following User Says Thank You to fffft For This Useful Post: [ Click to Expand ]
 
born4trance
Old
(Last edited by born4trance; 14th July 2014 at 10:18 AM.)
#18  
born4trance's Avatar
Member
Thanks Meter 10
Posts: 87
Join Date: Jan 2008
Location: Rotterdam(ned)
Quote:
Originally Posted by fffft View Post
PHN.. is Netherands?
Correct: For non branded / SIM-lock free

Quote:
Originally Posted by fffft View Post
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.
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)
OnePlus One (Sandstone Black 64GB) Order Status: Shipment Pending

- REQuest: A .pit for a 16GB SM-G900F, to be used with a PHN firmware (non-branded)
- Don't flash the .pit i posted on XDA! (read why and also read this)

- Want to view/read my posts? Click here
- My (Semi) Portable Minecraft Launcher: http://web.minecraftnoob.com

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes