I have an unlocked Verizon S5 that I want to put the Official T-Mobile firmware on. I can use it on T-Mobile fine ( I have a T-Mobile SIM and set up the APN etc.... but I want to reflash it with the latest T-Mobile firmware. ( G900TUVU1DOB1 )
My problem is that using any version of Odin fails.
Verizon Info:
Model: SM-G900V
Android: 4.4.4
Baseband: G900VVRU1ANK2
Build Number: KTU84P
HW Version: G900V.05
Phone Screen Shows:
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
UDC START
SECURE CHECK FAIL : abort
Odin Log Reports:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900TUVU1DOB1_G900TTMB1DOB1_G900TUVU1DOB1_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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
How can I convert this to a T-Mobile S5?
Related
As described in Chainfire's goole+ post I tried to reroot my GS4 again after it upgraded to MH5 (DBT version).
And it failed to flash with Odin, this is the log from Odin, the result in Odin is a red square with FAIL as message:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
The cf autoroot I use is indeed with a timestamp of 05 september.
My phone gives these messages
ODIN MODE
Then a few white text lines:
Product name: GT-I9505
Current binary: Samsung official
System status: official
KNOX Kernel lock: 0x0
KNOX Warranty void: 0x0
CSB-Config-LSB: 0x30
Then a line in grey:
Write protection: enable
then 2 final lines in red:
start: [224,1440]
bar: [240,1440]
On the rest of the screen is still mentions Downloading, do not turn off target!!
Any idea on what is causing this problem ?
gerritcap said:
As described in Chainfire's goole+ post I tried to reroot my GS4 again after it upgraded to MH5 (DBT version).
And it failed to flash with Odin, this is the log from Odin, the result in Odin is a red square with FAIL as message:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
The cf autoroot I use is indeed with a timestamp of 05 september.
My phone gives these messages
ODIN MODE
Then a few white text lines:
Product name: GT-I9505
Current binary: Samsung official
System status: official
KNOX Kernel lock: 0x0
KNOX Warranty void: 0x0
CSB-Config-LSB: 0x30
Then a line in grey:
Write protection: enable
then 2 final lines in red:
start: [224,1440]
bar: [240,1440]
On the rest of the screen is still mentions Downloading, do not turn off target!!
Any idea on what is causing this problem ?
Click to expand...
Click to collapse
make sure you read other posts about rooting as you will void your warranty as Knox void warranty will show 0x1. so if you want to void your device flash at your own risk. hope this helps you out. if id have known i would void my warranty i would not have rooted my device
So, I was trying to flash my custom rom to my SCH-i545 (Verizon S4) and now it's stuck in download mode!
It's an NC5 and android 4.4.2 (I think) . Pretty much every forum i visited said to use TWRP and Safestrap, but after flashing the custom recovery and rebooting, it would not leave download mode. Tried flashing a custom recovery with odin, and it fails.
Phone output:
Could not do normal boot.
PRODUCT NAME: SCH-i545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB:0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224,1440]
SW REV. CHECK FAIL : fused : 6, Binary : 1
Odin output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> NON-HLOS.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried the recovery mode combo at least 20 times, to no avail. Any help for this noob?
Nevermind, i'm an idiot. I had the wrong .tar.md5
I've tried to downgrade my S5 to kitkat with Odin. It fails and Odin says this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANE9_G900VVZW1ANE9_G900VVRU1ANE9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On my download screen, it says :
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECUREDOWNLOAD : ENABLE
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Maybe my bootloader is locked? Can that prevent me from downgrading? I'm kind of new at flashing so... Any help would be great. Thanks!
I'll assume the last 3 characters of your build number are OE1, OG5, or OK3. Am I right? If so, then you can't downgrade.
deleted5 said:
I've tried to downgrade my S5 to kitkat with Odin. It fails and Odin says this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANE9_G900VVZW1ANE9_G900VVRU1ANE9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On my download screen, it says :
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECUREDOWNLOAD : ENABLE
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Maybe my bootloader is locked? Can that prevent me from downgrading? I'm kind of new at flashing so... Any help would be great. Thanks!
Click to expand...
Click to collapse
if you werent rooted before you upgraded to lollipop then you cant downgrade or root because of the locked bootloader
First Of All Sorry, My English Is A Little Bad, I Speak Spanish But I`m Doing The Best That I Can...
I Have An S5 (G900P) And I`m Trying To Install A Stock Rom (OA6) Via Odin But Appears An Error
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And On My Cellphone
Odin Mode
Product Name: G900P
Current Binary: Custom
System Status: Custom
Reactivation Lock (KK): Off
Knox Warranty Void: 0x1 (4)
Qualcomm Secureboot: Enable (CSB)
Rp Swrev: s1, T3, R1, A3, P1
Secure Download: Enable
UDC Start
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
Does Anyone Knows How Can I Fix This Problem?
What firmware was it on originally?
justinxfan said:
What firmware was it on originally?
Click to expand...
Click to collapse
OK4, but i tried to install it and either i can`t
I took this Galaxy S5 from my friend to fix as it was boot looping on him. A factory reset in recovery didn't help at all.
He told me he got the device second hand but here is the confusing bit. The model on the battery sticker states it's a G900F, the about device screen shows it's a G900F. However download modes is showing it's a G900A. Furthermore the device is running the firmware for the united arab emirates, my friend being from the UK. I have tried various firmwares however all fail in odin with the same problem:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
About System:
Model Number - SM-G900F
Android Version - 4.4.2
Baseband Version - G900FZHU1ANG1
...
Build number - KOT49H.G900FZHU1ANG1
...
Click to expand...
Click to collapse
Download Mode:
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
UDC START
Click to expand...
Click to collapse
Thanks.
If Download mode states G900A, then the phone is a G900A
All the other model versions, Settings > About, Phone info, stickers, etc, can all be changed, and often are changed to say G900F to sell the phone quicker as it is the more popular model
AT&T lock their bootloaders, you could try flashing a newer version of Android, 5.0 >
Or try KIES firmware recovery
Here is a 5.0 one click firmware recovery to try too
Code:
http://downloadmirror.co/android/KR/Copy-of-G900AUCU3BOC4-OneClick.zip