Samsung Galaxy A7(2018) stuck at Android Recovery after booting!!

I followed all the steps as advised, including choosing the Home CSC file over the CSC file. But unfortunately nothing happened. for a split second, a screen appears saying "erasing" but after that the phone reboots and after 4-5 mins, returns to the Android Recovery Mode.
 
Then probably going need to try without Home CSC so can factory reset and see if it can reset the phone
 
<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/014> Added!!
<ID:0/014> Odin engine v(ID:3.1301)..
<ID:0/014> File analysis..
<ID:0/014> skip file list for home binary
<ID:0/014> param.bin
<ID:0/014> userdata.img
<ID:0/014> Home Binary Download
<ID:0/014> Total Binary size: 4430 M
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> NAND Write Start!!
<ID:0/014> SingleDownload.
<ID:0/014> sboot.bin
<ID:0/014> cm.bin
<ID:0/014> boot.img
<ID:0/014> recovery.img
<ID:0/014> system.img
<ID:0/014> vendor.img
<ID:0/014> modem.bin
<ID:0/014> Transmission Complete..
<ID:0/014> Now Writing.. Please wait about 2 minutes
<ID:0/014> Receive Response from boot-loader
<ID:0/014> modem_debug.bin
<ID:0/014> Transmission Complete..
<ID:0/014> Now Writing.. Please wait about 2 minutes
<ID:0/014> Receive Response from boot-loader
<ID:0/014> cache.img
<ID:0/014> odm.img
<ID:0/014> hidden.img
<ID:0/014> RQT_CLOSE !!
<ID:0/014> RES OK !!
<ID:0/014> Removed!!
<ID:0/014> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Added!!

The Odin log
 
<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/014> Added!!
<ID:0/014> Odin engine v(ID:3.1301)..
<ID:0/014> File analysis..
<ID:0/014> skip file list for home binary
<ID:0/014> param.bin
<ID:0/014> userdata.img
<ID:0/014> Home Binary Download
<ID:0/014> Total Binary size: 4430 M
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> NAND Write Start!!
<ID:0/014> SingleDownload.
<ID:0/014> sboot.bin
<ID:0/014> cm.bin
<ID:0/014> boot.img
<ID:0/014> recovery.img
<ID:0/014> system.img
<ID:0/014> vendor.img
<ID:0/014> modem.bin
<ID:0/014> Transmission Complete..
<ID:0/014> Now Writing.. Please wait about 2 minutes
<ID:0/014> Receive Response from boot-loader
<ID:0/014> modem_debug.bin
<ID:0/014> Transmission Complete..
<ID:0/014> Now Writing.. Please wait about 2 minutes
<ID:0/014> Receive Response from boot-loader
<ID:0/014> cache.img
<ID:0/014> odm.img
<ID:0/014> hidden.img
<ID:0/014> RQT_CLOSE !!
<ID:0/014> RES OK !!
<ID:0/014> Removed!!
<ID:0/014> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Added!!

The Odin log
Is the phone in download mode? And connection shows in the top left corner of Odin COM and highlighted?
 
is it advisable to flash it with an older version of the firmware as recently I had installed the latest firmware which was out on September 2022. so may be the recent firmware may have something to do with the issue?
 

Trending Posts

Members online

Forum statistics

Threads
956,464
Messages
6,968,366
Members
3,163,553
Latest member
braindefender