Unable to Flash Galaxy S5

[AJMacca]

Hi folks, (newbie here, so not sure what I'm doing here, (or with my Phone).

According to the info in About Device, I have an S5 (SM-G900F), Build No: G900FXXU1ANE2, Baseband V: G900AUCU2AND3
I've been trying' to 'Return to Stock', (Alliance ROM on Phone when I bought it, practically brand new).

Have read shed loads of tutorials on flashing the device with the use of ODIN and Firmware based on above Build No, but ODIN fails every time, exceptionally quickly, (like 3 seconds in).

I decided to give KIES a go, but KIES will not even attempt anything unless I put the device in as SM-G900A, then it will offer to download and install Firmware G900UACU1ANCE (ATT), but even that fails early during download. (Incidentally, when in Download Mode, the top of the Screen displays ODIN Mode, then Product Name: SM-G900A. In Download Mode, info also says: Reactivation Lock (kk): Off KNOX Warranty Void: 0x0 Secure Check Fail: [aboot] (sometimes with Fixed 2 > Binary 1 after [aboot].

KIES says the following F/W is installed: G900FXXU1ANE2/G900FOXU1ANE2/G900AUCU2AND3/G900FXXU1ANE2 (BTU)
The back of my phone does have an AT&T logo on it, (I assume therefore my phone is AT&T International version, hence the ATT Firmware suggestion in KIES? Would the locked Bootloader therefore stop me from flashing the ROM on it and returning to stock?

Thanks for any assistance/answers folks, Andy

 

[ironass]

Hi folks, (newbie here, so not sure what I'm doing here, (or with my Phone).

According to the info in About Device, I have an S5 (SM-G900F), Build No: G900FXXU1ANE2, Baseband V: G900AUCU2AND3
I've been trying' to 'Return to Stock', (Alliance ROM on Phone when I bought it, practically brand new).

Have read shed loads of tutorials on flashing the device with the use of ODIN and Firmware based on above Build No, but ODIN fails every time, exceptionally quickly, (like 3 seconds in).

I decided to give KIES a go, but KIES will not even attempt anything unless I put the device in as SM-G900A, then it will offer to download and install Firmware G900UACU1ANCE (ATT), but even that fails early during download. (Incidentally, when in Download Mode, the top of the Screen displays ODIN Mode, then Product Name: SM-G900A. In Download Mode, info also says: Reactivation Lock (kk): Off KNOX Warranty Void: 0x0 Secure Check Fail: [aboot] (sometimes with Fixed 2 > Binary 1 after [aboot].

KIES says the following F/W is installed: G900FXXU1ANE2/G900FOXU1ANE2/G900AUCU2AND3/G900FXXU1ANE2 (BTU)
The back of my phone does have an AT&T logo on it, (I assume therefore my phone is AT&T International version, hence the ATT Firmware suggestion in KIES? Would the locked Bootloader therefore stop me from flashing the ROM on it and returning to stock?

Thanks for any assistance/answers folks, Andy

Hello and welcome to Android Central AJMacca!

WOW!

It looks as though someone has done some very heavy duty modding to get Alliance ROM v4 for KitKat, NE2, to work on the AT&T carrier minority variant, G900A. This would seem to include flashing a stock G900F KitKat firmware to it after, possibly, altering the .PIT file/s. This would account for Kies not being able to upgrade it and Odin not being able to flash it as it is now neither a G900A or a G900F and the CSC codes and Product codes will not match. See 40 Galaxy S5 models - Dummies Guide for details of the models mentioned and CSC codes. Unfortunately, without knowing how or which mods were used to enable Alliance ROM v4 to run on a G900A, I cannot comment further. Perhaps you could ask on the Alliance ROM forum...

[ROM][G900F][NE2] AllianceROM v4 | AllianceROM

 

[AJMacca]

I will check it out. Thanks or at least pointing me in a new direction, (who ever you are? No user/name attached to the reply)

 

[AJMacca]

Re: Your advice

Hi AJMacca! I do not usually reply to PM's, preferring instead to reply on the open forum, so that others may benefit from the Q&A. .PIT files are both firmware and model sensitive and should only be used with great care as they can brick your phone. The G900F .PIT file will not be suitable if your model is indeed the AT&T G900A, if I remember correctly. First, you will need to determine exactly which model of Galaxy S5 you have. Phone INFO ★Samsung★ is useful for this. Then it is a case of reverse engineering whatever was done by the previous owner. I, from your previous information, I am only guessing what has been done.

Above is further info from User: ironass... (included to assist others with similar problems).

 

[AJMacca]

Hi folks. Some more info about my Phone. Phone INFO reports the following details:

Phone Model: SM-G900F
Phone Type: klte
Product Name: kltexx
Product Code: SM-G900AZWABTU
Original CSC Code: BTU
F/Ware's CSC Code: BTU
Active CSC Code: BTU
CSC Country: UK & IRE / GB
Mobile Operator: O2 - UK / 23410
Bootloader Version: G900AUCU2AND3
Baseband Version: G900AUCU2AND3
PDA Version: G900FXXU1ANE2
CSC Version: G900FOXA1ANE2
Kernel Version: 3.4.0-964333 dpi SWDD5009 #1 32-bit
Root Existence: Yes
Build Number: G900FXXU1ANE2
Build Fingerprint: samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANE2:user/release-keys
Build Description: kltexx-user 4.4.2 KOT49H G900FXXU1ANE2 release-keys
Build Date: Thu May 8 12:44 KST 2014
Changelist 1539356

I have received an Email from the retailer, and he states that the Handset was never opened or tampered with. Prior to purchase. (I couldn't remember if I

purchased it as brand new, I recall it was fairly cheap though. AT&T wouldn't dump a ROM on it would they?)

Hope this information helps someone come up with a solution, to either help me get the right Firmware, remove Alliance ROM, or upgrade to Lollipop. Thanks

for any help guys, Andy

 

[ironass]

Hi folks. Some more info about my Phone. Phone INFO reports the following details:

Phone Model: SM-G900F
Phone Type: klte
Product Name: kltexx
Product Code: SM-G900AZWABTU
Original CSC Code: BTU
F/Ware's CSC Code: BTU
Active CSC Code: BTU
CSC Country: UK & IRE / GB
Mobile Operator: O2 - UK / 23410
Bootloader Version: G900AUCU2AND3
Baseband Version: G900AUCU2AND3
PDA Version: G900FXXU1ANE2
CSC Version: G900FOXA1ANE2
Kernel Version: 3.4.0-964333 dpi SWDD5009 #1 32-bit
Root Existence: Yes
Build Number: G900FXXU1ANE2
Build Fingerprint: samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANE2:user/release-keys
Build Description: kltexx-user 4.4.2 KOT49H G900FXXU1ANE2 release-keys
Build Date: Thu May 8 12:44 KST 2014
Changelist 1539356

I have received an Email from the retailer, and he states that the Handset was never opened or tampered with. Prior to purchase. (I couldn't remember if I

purchased it as brand new, I recall it was fairly cheap though. AT&T wouldn't dump a ROM on it would they?)

Hope this information helps someone come up with a solution, to either help me get the right Firmware, remove Alliance ROM, or upgrade to Lollipop. Thanks

for any help guys, Andy

Everything about the above indicates that you have an unbranded U.K. model, G900F, on Product code BTU and running stock KitKat, NE2, firmware. Nothing about it shows AT&T or a locked bootloader!!!

I am confused!!!

In post #1 you say you bought it as, "practically new", and on Alliance ROM which means the phone must have been opened, tampered with, rooted and a custom ROM flashed to it prior to sale! Aso, you said it had an AT&T logo on the back?

 

[AJMacca]

The retailer has confirmed the Phone was brand new when purchased, and not tampered with in any way by them. Yes, there is an AT&T logo on the battery cover.
I too am confused, and I am a qualified Network Systems Engineer, so deal with many a confusing situation, but this has got me stumped. So, reverting to question, can I 'flash' the .PIT file to resolve. I have SM-G900_pit_16GB.zip file to use? (My S5 is a 16GB version).

 

[ironass]

The retailer has confirmed the Phone was brand new when purchased, and not tampered with in any way by them. Yes, there is an AT&T logo on the battery cover.
I too am confused, and I am a qualified Network Systems Engineer, so deal with many a confusing situation, but this has got me stumped. So, reverting to question, can I 'flash' the .PIT file to resolve. I have SM-G900_pit_16GB.zip file to use? (My S5 is a 16GB version).

With a custom Alliance ROM installed on it, then whatever model of Samsung Galaxy S5 you may have, is most definitely NOT brand new or un-tampered with. Send it back and demand a refund!

 

[AJMacca]

I have had it since last September, and therefore they can argue I have tampered with it in that time, (besides, the Phone functions normally, I just wanted to put Lollipop on it. Quick thought. The required Firmware, (to return-to-stock), should match the Build No. G900FXXU1ANE2? I will also post the details shown when I try to flash with G900FXXU1ANE2 Firmware, through ODIN.

 

[AJMacca]

This is what ODIN returns:

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANE2_G900FOXA1ANE2_G900FXXU1ANE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I have also followed ODIN Instruction Guides to the letter, set up USB Debugging on device etc

 

[ironass]

I have had it since last September, and therefore they can argue I have tampered with it in that time, (besides, the Phone functions normally, I just wanted to put Lollipop on it. Quick thought. The required Firmware, (to return-to-stock), should match the Build No. G900FXXU1ANE2? I will also post the details shown when I try to flash with G900FXXU1ANE2 Firmware, through ODIN.

"If", as it would seem, your phone is the International model, G900F, on Product code BTU with just Alliance ROM v4 flashed to it, then you need to unroot using the SuperSU app installed... Settings > Full unroot... and then flash the latest, stock, Samsung BTU firmware, below, by following the instructions and video contained in the links of #1.11 of 40 Galaxy S5 models - Dummies Guide

Model SM-G900F
Model name GALAXY S5
Country United Kingdom
Version Android 5.0
Changelist 4920185
Build date Fri, 15 May 2015 07:45:20 +0000
Product code BTU
PDA G900FXXU1BOE5
CSC G900FOXA1BOE5

 

[AJMacca]

Will give that a 'whirl' and confirm the outcome .

 

[AJMacca]

I note that in the Dummies Guide, the link to the ODIN 3.10.6 shows ODIN 3.10.6, (as it should). On the Options Tab, the Re-Partition option is checked. Is this meant to be? (I thought all other Guides say to make sure that option is not checked?

 

[ironass]

I note that in the Dummies Guide, the link to the ODIN 3.10.6 shows ODIN 3.10.6, (as it should). On the Options Tab, the Re-Partition option is checked. Is this meant to be? (I thought all other Guides say to make sure that option is not checked?

Where does it show Re-Partition checked?

 

[AJMacca]

in Dummies Guide section 1.11, I clicked link to ODIN. Web page opens, and the first Screen Shot, on left hand side of image

 

[ironass]

in Dummies Guide section 1.11, I clicked link to ODIN. Web page opens, and the first Screen Shot, on left hand side of image

That is the download page showing what it can do and is accompanied by the warning, "Do not use this tab. This tab is for engineers. The device will be changed with the pit in CSC file".

The video, albeit for the Odin v3.0.9 does not show Re-Partition ticked. Never, ever, tick Re-Partition or attempt to flash .PIT files unless you know exactly what you are doing as they can, "brick", your handset. Hence the warning in the latest version of Odin.

 

[AJMacca]

NO worries.

 

[AJMacca]

Tried the Firmware you mentioned above, (G900FXXU1BOE5). I followed the Guide, Unrooted the Device with SuperSU, (checked with Phone INFO and confirmed Unrooted). Have followed every detail, and ODIN still fails in a couple of seconds. Here is ODIN output:

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

There is only the single .tar.md5 file when I unzip the Firmware once, (as per instructions). Surely, this would therefore suggest that either; A) the Phone is not the G900F, or B) the Bootloader is locked?

 

[AJMacca]

A useful reply from someone in Alliance ROM forum:

So you indeed have a G900a.

However pit's or anything like like that were never altered. The rom that is running is the international version which runs fine on US models.

To get back to bone stock what you should do is look on xda developers in the section for your phone (ATT S5 G900A) and find the latest full odin tar. The other one you were trying to flash failed because I assume you tried the g900f odin tar which will not pass the sw check on the G900A locked bootloader. There is some trickery involved getting custom roms on these devices. But nothing as serious as you suspect.
I think you will find what you need here, (I can't post links yet). Guess it was both A) and B) above then. What a 'mare!!!

 

[AJMacca]

Have done some more research, by checking my IMEI No on two Sites, and both confirm the Phone as a G900A. I have been directed to a link on XDA, where I have d/loaded Firmware with BL, AP, CP & CSC files, (but they are for AT&T. May try to flash' tomorrow. Was wondering, if do 'flash', and all goes well, will my Phone still be ok to work in the UK, or will I need to find a further CSC Firmware for BTU, and 'flash a CSC Firmware on its own afterwards