[Q] GT-I9505 Firmware upgrade failed. - Galaxy S 4 Q&A, Help & Troubleshooting

I tried to upgrade my galaxy s4 to android 4.4.2 using odin.
But while performing the process, odin said it failed
now my galaxy says " Firmware upgrade encountered an issue. Please select recovery mode in kies and try again".
i am from Nepal.
Thank you
MODEL: GT-I9505
FCC ID : A3LGTI9505
SSN : -I9505GsMH

With this little information, there is not much we can do. You need to give more details if you want help.
What was the error? What firmware did you try to flash? What steps did you take? Did you try a different usb cable, different ports, different pc etc etc.

Lennyz1988 said:
With this little information, there is not much we can do. You need to give more details if you want help.
What was the error? What firmware did you try to flash? What steps did you take? Did you try a different usb cable, different ports, different pc etc etc.
Click to expand...
Click to collapse
i used odin v3.09.
I tried flashing with the stock firmware but couldnot.
steps i took is shown in attachments.
error in my odin is
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNC4_I9505YXYFNC1_I9505XXUFNC4_HOME.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> 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> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!
yes i tried diffent pcs, and with different cables, and different usb port too..

sakarmaskey said:
i used odin v3.09.
I tried flashing with the stock firmware but couldnot.
steps i took is shown in attachments.
Click to expand...
Click to collapse
Try to flash the same firmware like the pic attached.

Joku1981 said:
Try to flash the same firmware like the pic attached.
Click to expand...
Click to collapse
same problem occured!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNC4_I9505YXYFNC1_I9505XXUFNC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!

Related

Soft Bricked Device; Keep Getting <ID:0/004> Complete(Write) operation failed.

I keep trying to reflash to stock and keep getting this error in ODIN:
<ID:0/004> Complete(Write) operation failed.
I tried running as admin and removing the SD card. No dice. I also tried reflashing a recovery, same error.
I tried following this and still get the same error: http://forum.xda-developers.com/showthread.php?t=2483380
Full error:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<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)
Screen reads in red:
SW REV CHECK FAIL " [aboot]Fused 2 > Binary 1
Whitechapel420 said:
I keep trying to reflash to stock and keep getting this error in ODIN:
<ID:0/004> Complete(Write) operation failed.
I tried running as admin and removing the SD card. No dice. I also tried reflashing a recovery, same error.
I tried following this and still get the same error: http://forum.xda-developers.com/showthread.php?t=2483380
Full error:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<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)
Screen reads in red:
SW REV CHECK FAIL " [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
If you have gone to Kitkat then you can't go back to JB...
Also, there have been people who have trouble flashing carrier roms from the open roms...

Soft Bricked

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

[Q] Odin: Complete(Write) operation failed.

Sold my phone on eBay, I had it rooting running SafeStrap on NB1 firmware. Thought it would be best to flash back to stock before shipping it. Used this ROM. Got various errors before deciding I had to repartition with this PIT file. Since then I have gotten the same error (in the title). Is this fixable or am I completely screwed?
Odin text:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_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> Removed!!
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Click to expand...
Click to collapse
Update: Just tried a USB port on the motherboard rather than the front panel ports and got this:
<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> 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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
Click to expand...
Click to collapse
Is this good or am I even more screwed?
Update 2: Here's what I get when only flashing the MD5 without the PIT:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_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> 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!!
Click to expand...
Click to collapse
Update 3: Was able to flash the MD5 I used in order to root. Tried again to flash the stock MD5 and got about as far as one can hope for but, again, faced the Complete(Write) operation failed.
Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_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> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> NON-HLOS.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.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!!
Click to expand...
Click to collapse
After this point I was again able to restore the ROM I had before. So I'm guessing this points to the problem being within the MD5 I'm attempting to flash?
If you're not already, use the tar from here
http://forum.xda-developers.com/showthread.php?p=50912149
It could be a bad download of the file that is causing the problem. You also should not need the pit file. Use usb 2.0 ports, not 3.0 and try different ports and cable. Odin can be finicky.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you're not already, use the tar from here
http://forum.xda-developers.com/showthread.php?p=50912149
It could be a bad download of the file that is causing the problem. You also should not need the pit file. Use usb 2.0 ports, not 3.0 and try different ports and cable. Odin can be finicky.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I redownloaded the file from that link, used a different USB port, and finally I am successful!
windoge said:
Thanks, I redownloaded the file from that link, used a different USB port, and finally I am successful!
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Nexus 5 using XDA Free mobile app
I tired changing USB ports it worked...
jd1639 said:
If you're not already, use the tar from here
http://forum.xda-developers.com/showthread.php?p=50912149
It could be a bad download of the file that is causing the problem. You also should not need the pit file. Use usb 2.0 ports, not 3.0 and try different ports and cable. Odin can be finicky.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank a lot...
It worked after trying different ports...

[HELP]I Think i bricked my phone. Please help me Out Thanks, [Solved :D]

Hi,
I mistakenly deleted my os and now i can't boot. When i flash it just get stuck. Recover-mode downloading blue bar just move a further and than stop. When i try to run my mobile there is a error message "Firmware Upgrade encountered an issue. Please select recovery mode in kies and try again." I can only open Recovery Mode,
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<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> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> hyp.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help me with this.
Edit: Change the port and it works

Failed root on SM-N910T now stuck at recovery booting

Bought this to make into a rooted note 4. Not my main phone yet, I have an AT&T version.
Attempted to root following the directions on CFROOT, that got me to this point. Now have spent 2 days searching for solutions and trying things. No progress!
In download mode Using Odin 3.9 and 3.10.7 the CFROOT file report success but stuck in recovery booting. Attempting to reinstall the entire firmware Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<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> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Any help would be greatly appreciated!
John
dylistn said:
Bought this to make into a rooted note 4. Not my main phone yet, I have an AT&T version.
Attempted to root following the directions on CFROOT, that got me to this point. Now have spent 2 days searching for solutions and trying things. No progress!
In download mode Using Odin 3.9 and 3.10.7 the CFROOT file report success but stuck in recovery booting. Attempting to reinstall the entire firmware Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<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> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Any help would be greatly appreciated!
John
Click to expand...
Click to collapse
You're in the wrong place. These are the S4 forums, not Note 4.
Anyway, AT&T devices have a locked bootloader and I don't think CF-Auto-Root can root those.
So you may have to find another solution to rooting.
But before that you may have to flash the stock firmware again, as the current one is messed up by the failed root flash.
Thank you
I thought I had the right forum. Can I move this to another forum. Or should I start a new thread and delete this?
dylistn said:
I thought I had the right forum. Can I move this to another forum. Or should I start a new thread and delete this?
Click to expand...
Click to collapse
It can be moved. Select the report option and as a reason select thread moving.

Categories

Resources