I have an SCH-i545 S4. It was running Jelly Bean 4.3 at the time rooted using Super SU and still have TWRP recovery.
I was trying to install the new lollipop update manually and forgot to switch from stock to a ROM slot in TWRP recovery and wiped the stock ROM.
I try to use Odin to flash stock firmware and revert to unrooted, but I get the following error: (I am able to get phone into download Odin mode)
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<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)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Using Odin 3.09 and trying to flash :
ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar
Not sure if I'm using the wrong stock firmware and Odin version.
Let me know what I'm doing wrong thank you!
You can't flash older firmwares.
Odin 3.09 worked fine for me in the past, buy it doesn't hurt to try a different version.
Also, use the back USB ports if you have a pc.
Try different USB cables and windows versions too. Odin is quite picky.
My setup was Windows 7 x64 Pro with Odin 3.09. Using the back USB and original cable I never had an issue flashing stuff with Odin.
GDReaper said:
You can't flash older firmwares.
Odin 3.09 worked fine for me in the past, buy it doesn't hurt to try a different version.
Also, use the back USB ports if you have a pc.
Try different USB cables and windows versions too. Odin is quite picky.
My setup was Windows 7 x64 Pro with Odin 3.09. Using the back USB and original cable I never had an issue flashing stuff with Odin.
Click to expand...
Click to collapse
So I should be flashing the latest lollipop firmware vs. the older kit kat or jellybean?
odin is failing when flashing aboot.mbn because the rom has a bootloader that is older than the bootloader on the phone.
Flashing a stock LP or kk should work if the phone was running a stock 4.3 rom.
audit13 said:
odin is failing when flashing aboot.mbn because the rom has a bootloader that is older than the bootloader on the phone.
Flashing a stock LP or kk should work if the phone was running a stock 4.3 rom.
Click to expand...
Click to collapse
Alright I tried what you said and started to flash the following file: I545VRUGOC1_I545VZWGOC1_VZW
Here is the data from Odin 3.09 and the process failed again:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUGOC1_I545VZWGOC1_I545VRUGOC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any suggestions? Working with Windows 10 and original samsung cord.
Strange. Boot into recovery and look at the second or third line for the recovery version on the phone.
audit13 said:
Strange. Boot into recovery and look at the second or third line for the recovery version on the phone.
Click to expand...
Click to collapse
So booting into download gives the following:
Odin Mode
Product name: SCH-I545
Current Binary: Samsung Official
System Status: Custom
Reactivation Lock: Off
CSB-CONFIG-LSB: 0x30
Secure Download: Enabled
Write Protection: Enabled
eMMC Burst Mode enabled
Can the phone be booted into recovery?
audit13 said:
Can the phone be booted into recovery?
Click to expand...
Click to collapse
Trying... Maybe not anymore???... Giving me the software update fail screen
Sounds reasonable since recovery is probably gone.
This is the verizon version of the phone? Have you tried using the original USB cable as previously suggested, a different USB port, or operating system?
audit13 said:
Sounds reasonable since recovery is probably gone.
This is the verizon version of the phone? Have you tried using the original USB cable as previously suggested, a different USB port, or operating system?
Click to expand...
Click to collapse
Just got his while trying this OS on a different USB port.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
angelfury126 said:
Just got his while trying this OS on a different USB port.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Just got it to PASS!!!! YES!!!. Plugged into the back usb ports.
Now the problem is it won't boot up... Thoughts?
It is completely dead? Did you get the firmware from sammobile.com?
audit13 said:
It is completely dead? Did you get the firmware from sammobile.com?
Click to expand...
Click to collapse
Don't think so. I'll download and try again.
All official firmware is on sammobile.com.
The phone will go to download mode?
audit13 said:
All official firmware is on sammobile.com.
The phone will go to download mode?
Click to expand...
Click to collapse
Yes.
angelfury126 said:
Just got it to PASS!!!! YES!!!. Plugged into the back usb ports.
Now the problem is it won't boot up... Thoughts?
Click to expand...
Click to collapse
I told you right from the beginning to use the back USB ports.
Anyway, did you wipe before flashing the firmware? Cuz Odin will not do it for you.
have you tried flashing different versions of the rom?
When flashing, did you try unchecking everything except f.reset time? When it finishes flashing, power off the phone by removing the USB cable and then the battery. Replace the battery and boot directly to recovery to perform a factory wipe, then reboot to the rom.
audit13 said:
power off the phone by removing the USB cable and then the battery.
Click to expand...
Click to collapse
Or you can just hold the power button for a couple of seconds until it turns off
That will work too but I find removing the battery to be easier for me.
Related
Hi all,
Phone is soft bricked, I cant access the recovery, but can access the odin download mode.
The phone came with I337mvluamg1 firmware, Although when i try to reflash the phone with the stock firmware odin fails..
Im using Odin 3.07
And the I337MVLUAMG1 firmware from sammobile but i get this message from odin
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMG1_I337MOYAAMG1_I337MVLUAMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is day 4 with the phone soft bricked and it just wont budge, ive tried multiple different firmware versions, even back tracking. but nothing.
Any tips? suggestions?
Thanks
sdawg1010 said:
Hi all,
Phone is soft bricked, I cant access the recovery, but can access the odin download mode.
The phone came with I337mvluamg1 firmware, Although when i try to reflash the phone with the stock firmware odin fails..
Im using Odin 3.07
And the I337MVLUAMG1 firmware from sammobile but i get this message from odin
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMG1_I337MOYAAMG1_I337MVLUAMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is day 4 with the phone soft bricked and it just wont budge, ive tried multiple different firmware versions, even back tracking. but nothing.
Any tips? suggestions?
Thanks
Click to expand...
Click to collapse
Im now getting a pass from I337MVLUAMDJ in odin, but the phone still wont boot to recovery or the OS
Odin back to stock. Don't use what's in my description.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Make sure your trying to flash the same version of firmware.... if the phone was originally on 4.3 you can't flash back to 4.2. You can go up versions but not down... if the bootloader is 4.3 you can't get to 4.2
I tried flashing the stock firmware but it failed, but when i use a version above stock i get a pass from odin, the phone resets but when boots, gets stuck on the samsung galaxy s4 screen, and wont boot to recovery..or the OS....
sdawg1010 said:
I tried flashing the stock firmware but it failed, but when i use a version above stock i get a pass from odin, the phone resets but when boots, gets stuck on the samsung galaxy s4 screen, and wont boot to recovery..or the OS....
Click to expand...
Click to collapse
You need to keep trying to get into recovery. When you do, do a factory reset
Sent from my Nexus 5
hello everyone
i rooted my s4 a while back, then unrooted by flashing XSA-I9505XXUEMK9-20131212101727 through odin
then i decided to root it again, it worked but this time the wifi stopped working so i flashed XSA-I9505XXUEMK9-20131212101727 (same firmware) again, except everytime i do it, odin gives me a fail
i used a pit file to flash with XSA-I9505XXUEMK9-20131212101727 (same firmware again), except during the middle of this process, the connection between my cable and phone broke
tried pit + XSA-I9505XXUEMK9-20131212101727 (same thing) on odin 3.09 after the first attempt, it gives me a fail and this
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_HOME.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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
right now, when i try to boot my phone, it gives me "firmware upgrade encountered an issue. please select recovery mode in kies and try again", though i can't do anything in kies
all i can access is download mode, recovery mode doesn't work either (it never did, even when my phone was fine)
please help
chilifourloko said:
hello everyone
i rooted my s4 a while back, then unrooted by flashing XSA-I9505XXUEMK9-20131212101727 through odin
then i decided to root it again, it worked but this time the wifi stopped working so i flashed XSA-I9505XXUEMK9-20131212101727 (same firmware) again, except everytime i do it, odin gives me a fail
i used a pit file to flash with XSA-I9505XXUEMK9-20131212101727 (same firmware again), except during the middle of this process, the connection between my cable and phone broke
tried pit + XSA-I9505XXUEMK9-20131212101727 (same thing) on odin 3.09 after the first attempt, it gives me a fail and this
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_HOME.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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
right now, when i try to boot my phone, it gives me "firmware upgrade encountered an issue. please select recovery mode in kies and try again", though i can't do anything in kies
all i can access is download mode, recovery mode doesn't work either (it never did, even when my phone was fine)
please help
Click to expand...
Click to collapse
Although this message your phone is in download mode
change usb port and try again
try different port
Fixed it somehow........
actually disregard all that, i flashed the pit file by itself in odin 3.09 and everything works again O_O
i'm missing an app which is weird...
i still can't reflash XSA-I9505XXUEMK9-20131212101727 through odin though, it still gives me a fail, which ends up ruining everything again, so i reflash the pit and now this happens
i did a factory reset, now samsung keyboard keeps crashing and the menu and back button do nothing
wth is happening ._.
chilifourloko said:
i still can't reflash XSA-I9505XXUEMK9-20131212101727 through odin though, it still gives me a fail, which ends up ruining everything again, so i reflash the pit and now this happens
i did a factory reset, now samsung keyboard keeps crashing and the menu and back button do nothing
wth is happening ._.
Click to expand...
Click to collapse
maybe wrong or corrupt firmware file try another
pda4g said:
maybe wrong or corrupt firmware file try another
Click to expand...
Click to collapse
which firmware should i use
does it matter ?
chilifourloko said:
which firmware should i use
does it matter ?
Click to expand...
Click to collapse
download firmware for your country
Your file may be damaged
download new
pda4g said:
download firmware for your country
Your file may be damaged
download new
Click to expand...
Click to collapse
redownloaded firmware, stopped antivirus and all kies processes, changed usb ports to one of the back ones, reflashed firmware from ~80 percent battery aaaaaaaaaaaaand...
IT WORKS !!!!!!!!!!!!!!!!!!!!!!!!!!!!
HALLELUJAH
chilifourloko said:
redownloaded firmware, stopped antivirus and all kies processes, changed usb ports to one of the back ones, reflashed firmware from ~80 percent battery aaaaaaaaaaaaand...
IT WORKS !!!!!!!!!!!!!!!!!!!!!!!!!!!!
HALLELUJAH
Click to expand...
Click to collapse
ok Good luck!
So I went from Hyper RLS16 MJ7 to MK2 using odin, then used VZW OTA to go to NC5. Rooted, Installed Safestrap, then installed Hyperdrive RLS17 (on stock slot per sbreens instructions). For some reason I was having some weird Quirks and decided to try to flash NC5 in odin again using surges file, It started to flash (full wipe method with PIT file) and failed, so now I have the problem where it starts to flash, fails, the I jut re-partition and am able to get back into download mode, but Its gets up to ABOOT in odin, then fails. Here is the messages in odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
If anyone has any ideas, please let me know, I have tried going back to MK2, but I am assuming its locked out because it fails instantly.
Let me know if there is more info needed.
Verizon SCH-I545 Galaxy S4 NC5 baseband.
bradbb2009 said:
Let me know if there is more info needed.
Verizon SCH-I545 Galaxy S4 NC5 baseband.
Click to expand...
Click to collapse
Nope. No more info needed. you have to follow two easy steps to repair:
1. go here;
2. Ask your question in Q&A section.
sorry, but you posted in wrong S4 thread:highfive:
hi there i have a live demo unit set with snapdragon chipset i updated my bootloader which i cant downgrade and now i am getting bootloop so i flashed some 4.4.2 rom which didnt worked though and now i am going back to stock rom N9005XXUGNG1_N9005DBTGNG1_DBT [Germany] using odin and it gives me error
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005DBTGNG1_N9005XXUGNG1_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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Help me what should i do and when i install twrp and clear cache i manage to boot somehow but i keep giving me error samsung keyboards stops working
or you root, install recovery and flash custom rom
or you do odin again and maybe change version 3.09 or older
or you root, install recovery and flash custom rom
or you do odin again and maybe change version 3.09 or older
Click to expand...
Click to collapse
tried changing odin version 3.07 still the same
now dowloading poland stock rom
is there any way to fix samsung keyboard has stopped workig every 2 sec
cybertron_001 said:
tried changing odin version 3.07 still the same
now dowloading poland stock rom
is there any way to fix samsung keyboard has stopped workig every 2 sec
Click to expand...
Click to collapse
Try this
http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
I had some issues in the past with kitkat and flashing roms so i ran across this. It helped me.
Hello,
I've been trying to upload the Telus Andorid 6.0.1 to my Samsung S5 and have been unsuccessful. I continually get "Complete(Write) operation failed".
I have tried versions of Odin 3.09, 3.11 and 3.12 to no success.
I have ensured the driver of the S5 is on the computer (Windows 7, latest patches).
I have used multiple cables (OEM) and ports (front and rear).
I am in download mode (power, volume down, and home button).
Finally, Kies has been fully removed.
Here is what I'm trying to install: G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3_HOME.tar.md5.
Here is a snapshot of the log.
<ID:0/014> Added!!
<ID:0/014> Odin engine v(ID:3.1101)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> aboot.mbn
<ID:0/014> NAND Write Start!!
<ID:0/014> sbl1.mbn
<ID:0/014> rpm.mbn
<ID:0/014> tz.mbn
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm doing all of this because my stock phone is bootlooping. I tried a new battery and it did not resolve my issues. Any help would be appreciated as I've searched this site and others for multiple hours and I'm now stuck on the firmware update screen telling me to recover using Kies (not the logo). It automatically starts there.
Thank you.
Hi
You're sure to put the phone in download mode?
grandshervee said:
Hello,
I've been trying to upload the Telus Andorid 6.0.1 to my Samsung S5 and have been unsuccessful. I continually get "Complete(Write) operation failed".
I have tried versions of Odin 3.09, 3.11 and 3.12 to no success.
I have ensured the driver of the S5 is on the computer (Windows 7, latest patches).
I have used multiple cables (OEM) and ports (front and rear).
Finally, Kies has been fully removed.
Here is what I'm trying to install: G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3_HOME.tar.md5.
Here is a snapshot of the log.
<ID:0/014> Added!!
<ID:0/014> Odin engine v(ID:3.1101)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> aboot.mbn
<ID:0/014> NAND Write Start!!
<ID:0/014> sbl1.mbn
<ID:0/014> rpm.mbn
<ID:0/014> tz.mbn
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm doing all of this because my stock phone is bootlooping. I tried a new battery and it did not resolve my issues. Any help would be appreciated as I've searched this site and others for multiple hours and I'm not stuck on the firmware update screen (not the logo). It automatically starts there.
Thank you.
Click to expand...
Click to collapse
Sent from my SM-G532F using Tapatalk
merwan said:
Hi
You're sure to put the phone in download mode?
Click to expand...
Click to collapse
Hi, yes I'm in download mode (power, volume down and home button).
Also, I noticed I miswrote something and have corrected it. I meant to write:
I'm NOW stuck on the firmware update screen telling me to recover using Kies (not the logo).
grandshervee said:
Hi, yes I'm in download mode (power, volume down and home button).
Also, I noticed I miswrote something and have corrected it. I meant to write:
I'm NOW stuck on the firmware update screen telling me to recover using Kies (not the logo).
Click to expand...
Click to collapse
Try to redownload the md5 file
Change USB port. And if u another 2.0 cable to. Somwnthing it happend dont worried
I have tried all of these files and get the same error for each. brand new S5 USB 3 cable and different port too.
G900W8VLU1DPD3_G900W8OYA1DPD3_G900W8VLU1DPD3_HOME.tar
G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3_HOME.tar
G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3_HOME.tar - same file as above but from a different download site.
What is the line after:
<ID:0/007> tz.mbn
that causes it to fail?
Don’t use the usb 3 cable, the old HTC and BlackBerry cables are the best as theyre 21 pin connectors. Where are you downloading the tarball from? Sammobile.com/firmwares is the only truly reputable place altho there are many sites that have them as well, but if youre having trouble flashing them, get a tarball from the source directly. I agree with a previous post, try a different port, different cable and fresh download. One of those is bound to work.
Sorry for such a late reply. I am still unsuccessful with the S5. Redownloaded from Sammobile
G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3
I loaded a Note 4 with Odin 3.12, a micro-USB cable, and this specific USB port and it woudln't work with the S5. Is it possible that there is internal hardware damage shorting something?
grandshervee said:
Sorry for such a late reply. I am still unsuccessful with the S5. Redownloaded from Sammobile
G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3
I loaded a Note 4 with Odin 3.12, a micro-USB cable, and this specific USB port and it woudln't work with the S5. Is it possible that there is internal hardware damage shorting something?
Click to expand...
Click to collapse
i guess its possible, but id try a different odin version before i jumped to that conclusion
Ok, so somehow I got the phone to boot up and go through the setup menus, then it failed.
It then rebooted and displayed
Set Warranty Bit : kernel
I now ran ODIN again.
This was on the phone
Product Name: SM-G900W8
Current Binary: Custom
System Status: Official
Reactivation Lock(KK): OFF
Knox Warranty Void: 0x1 (1)
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
UDC Start
Secure Check Fail : aboot
and this was the output within odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
try with different odin version, like 3.11, also reinstall drivers or flash using another pc
Just rebooted phone and got this.
Recovery Booting.....
Set Warranty Bit : recovery
Also, tried with 3.11, no success. Drivers have been reinstalled twice over.
now it hangs at tz.mbn before failing.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1101)..
<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> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
grandshervee said:
Just rebooted phone and got this.
Recovery Booting.....
Set Warranty Bit : recovery
Also, tried with 3.11, no success. Drivers have been reinstalled twice over.
now it hangs at tz.mbn before failing.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1101)..
<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> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
ive had that error a few times before when using the stock samsung cable. do you have another cable? preferably an old school blackberry or htc one. The older cables from those manufacturers seems to have always worked best for me and others