I tryede to install Nougat on SM-G935F, after i flashed the bootloader my phone keep rebooting when im trying to flash in odin can anyone tell my what do do?? is the phone destroide?
in ODIN
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_G935FXXS1APG3_CL8252943_QB10235864_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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..
Then the phone reboots an samsung galaxy start screen shows, the phone is not able to boot in recovery mode, only download mode
Related
Please Help!
I am stuck in download mode with Odin 3! My Samsung Captivate i896 is plugged into the computer and Odin is running but it looks like Odin may have frozen. I am trying to flash Gingerbread 2.3.3 Rogers Stock Rom as my phone is soft bricked.
Here are the steps so far:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I896UXKH2-HOMEBINARY.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!!
Please help me!
how long have you wait for??
My phone is in the download mode however everytime I try to use Odin, it won't get past factoryfs.rfs.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.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> factoryfs.rfs
This morning I tried it on my friend's laptop and it only went through half of factoryfs.rfs and it would just be stuck. My carrier is Rogers and I've been using GTG_ultimate_unbrick. I've also tried using heindell as well. On Heindell it says that Kernels can not be uploaded. Can anyone help me with this problem?
crazyshin said:
My phone is in the download mode however everytime I try to use Odin, it won't get past factoryfs.rfs.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.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> factoryfs.rfs
This morning I tried it on my friend's laptop and it only went through half of factoryfs.rfs and it would just be stuck. My carrier is Rogers and I've been using GTG_ultimate_unbrick. I've also tried using heindell as well. On Heindell it says that Kernels can not be uploaded. Can anyone help me with this problem?
Click to expand...
Click to collapse
different usb cord
I got through the factory.rfs but now I'm stuck on the boot logo
crazyshin said:
I got through the factory.rfs but now I'm stuck on the boot logo
Click to expand...
Click to collapse
3 fingers into recovery; factory reset, reboot?
@crazyshin -
What ROM were you running before attempting your first ODIN flash?
What ODIN package are you attempting to install (provide link if possible)?
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
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.
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.