Trying 2 Install Firmware after accidentally dropping phone in water - Galaxy S6 Q&A, Help & Troubleshooting

Ok so Im Useing New firmware 2 Install The Firmware Stock but now it shows me this error (OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/004> param.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<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!!

Try to use newest Odin 3.12.7 and newest Samsung USB Drivers. Also download one more time right latest firmware for your model (the best way to get it is SamFirm). HERE you found all and some info. Try like that.
EDIT:
I didn't saw your another thread HERE: https://forum.xda-developers.com/galaxy-s6/help/plz-help-trying-to-reinstall-stock-t3671080/
If there was connection with water can be hardware issue like broken motherboard etc... So...

Thank U
rifek4 said:
Try to use newest Odin 3.12.7 and newest Samsung USB Drivers. Also download one more time right latest firmware for your model (the best way to get it is SamFirm).
EDIT:
I didn't saw your another thread HERE: https://forum.xda-developers.com/galaxy-s6/help/plz-help-trying-to-reinstall-stock-t3671080/
If there was connection with water can be hardware issue like broken motherboard etc... So...
Click to expand...
Click to collapse
Yea I Might Just Buy A Galaxy S8 But Thank U

Related

Plz Help Trying To Reinstall Stock Firmware But Getting Error (odin)

Hi ive recently Dropped My Phone in water on a accident When i tried to turn on my phone all it would show was the galaxy s6 Boot Logo Then Shut off So i tried to reinstall the Firmware But i keep getting this error from odin Its a Cricket Galaxy S6 And the model number is SM-G920AZ (ID:0/003> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You're trying to flash wrong or old firmware.
forumber2 said:
You're trying to flash wrong or old firmware.
Click to expand...
Click to collapse
MMM I See ill see if i can find newer firmware then
This Happends
forumber2 said:
You're trying to flash wrong or old firmware.
Click to expand...
Click to collapse
Ok It Goes To system.img now then stops (OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/004> param.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<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!!

GALAXY S7 reboot while wipe in twrp

Hi guys,
I need help. My phone suddenly turned off and when I tried to switch it on, I got bootloop. When I enter twrp and choose wipe, my phone reboots. I installed a new version of twrp, but it doesn`t help. I tried to install custom roms, but around 60-70% reboot. Does anybody know how to fix?
Galaxy S7, G930FD
LineageOS 14.1
TWRP 3.1.1.0
thanks in advance
Flash stock
*Detection* said:
Flash stock
Click to expand...
Click to collapse
I got fail
<ID:0/004> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4071 M
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
That happen to me, only fixed by flashing just AP file on Odin, I was on Oreo stock and tried to root and this happen.
j0shyc0re said:
That happen to me, only fixed by flashing just AP file on Odin, I was on Oreo stock and tried to root and this happen.
Click to expand...
Click to collapse
Ok,
I got fail, but the process of installing the firmware is still on. How can I stop it?
Just disconnect the USB cable.

stuck on sboot.bin when try to flash stock firmware SM-G955FD

First I got stuck in the "custom binary blocked FRP lock". and when i try to flash stock firmware, odin fails with some sboot.bin error...please help me someone
<ID:0/003> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
assassin410 said:
First I got stuck in the "custom binary blocked FRP lock". and when i try to flash stock firmware, odin fails with some sboot.bin error...please help me someone
<ID:0/003> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Stuck at the same issue, the problem probably is that the bootloader is the newest V3 version, which is not Downgradeable for now.
RapsodyR55 said:
Stuck at the same issue, the problem probably is that the bootloader is the newest V3 version, which is not Downgradeable for now.
Click to expand...
Click to collapse
I got the same problem, so do we have to wait for a new Odin Version?
I am also stuck at this situation. Completed the rooting process on my S8 950FD after installing some custom apps, it force reboot and is stuck in a boot loop with (only official release binaries are allowed to be flashed). I then try to flash it back to stock firmware but was successful, and had the same log messages as thread starter.
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I use:
Odin3 v3.13.1
Samsung firmware: Galaxy S8 SM-G950FD 8.0.0 June 15, 18 Singapore (XSP) G950FXXU2CREH
Stuck here as well!

Help Installed Lineage on Samsung S7 not edge cant restor back to stock OS

Device info : Samsung s7 (not Edge) SM-G930W8 build G930W8VLU3CRE3 Canadian version for Rogers.
So I recently installed Lineage 15 Android 8.0 and rooted. Its super glitchy and I want to restore to a Stock Android 8.0.
I downloaded stock firmware, then open Oden and reboot my phone into download. I locate the BL, AP, CP, CSC home and click start in Oden.
Odin immediately says RESET, then PASS! My phone reboots and instead of loading a stock 8.0 OS it loads Lineage!!! I cant get past this. Can some one help?
Here is the odin log.
<ID:0/004> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> sboot.bin.lz4
<ID:0/004> param.bin.lz4
<ID:0/004> cm.bin.lz4
<ID:0/004> boot.img.lz4
<ID:0/004> recovery.img.lz4
<ID:0/004> system.img.lz4
<ID:0/004> modem.bin.lz4
<ID:0/004> modem_debug.bin.lz4
<ID:0/004> cache.img.lz4
<ID:0/004> hidden.img.lz4
<ID:0/004> Home Binary Download
<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> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I fixed the problem. I was using the wrong version of Odin. I was able to install android 8.0 Oreo using Odin verison 3.13.1. I then got stuck on the boot screen during my first boot. Using the Voumue up + down + home + power butts I did a forced reboot. Then Using vomume up + home + Power I went into recover my and did the following. Wipe data / factory reset Wipe cache partition. Reboot the phone and it now works. I thought I would post this info incase some one runs into this problem.

Trying to fix S7 Edge (SM-G935F) with stock OS (never rooted) stuck in boot loop

Hi,
I was in the situation as I described earlier in the noob thread https://forum.xda-developers.com/t/help-thread-ask-any-question-noob-friendly.2257421/post-85728889
Meanwhile I kept reading a trying to make my phone start again. So I tried to to flash my phone to stock to fix it.
As I wrote in the above post I have a Galaxy S7 edge (SM-G935F) so I downloaded the latest from the Netherlands (where the phone is from) and Vodafone (my original provider) from Sammobile:
I tried to use this one: https://www.sammobile.com/samsung/g...e/SM-G935F/VDF/download/G935FXXU8ETI2/607496/
I think that's correct right?
However the following happened:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> modem_debug.bin
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 4319 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So it doesn't seem to get passed boot.img?
Afterwards the behaviour was different and its asking me to try emergency recovery with Samsung Switch (which does not even list my phone). I can still get in download mode in the phone though and try flashing again but I only get the same results (or an outright reject if I try slightly older firmwares).
Is there anything I can do now or is my phone broken?
Do you have solve the problem? because I have the same problem

Categories

Resources