Solved Samsung Bootloop Odin Fail To Flash System.img Fixed With UFi

This topic has been solved

Abdullah

Friend's Martview
Oct 22, 2016
1,422
4,051
Pakistan
PayPal:

Donate money to this user
Samsung G530 Bootloop Odin Fail To Flash System.img Fixed



if your phone is bricked and flashing stock with Odin fail writing system.img to System Partition. And you have tried to do it using all newest Samsung flashing tools
"Odin failed, fash failed in z3x tool pro, flash failed in octopus box, flash failed in Chimera Tool and others" On latest build (the one that has all those crashes) and right at the beginning of the flashing process, the writing of system.img to System partition fails and the device was bricked.
And stuck on Bootloop Or "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Bricked up to the point where a restore using Samsung Switch or Kies was the only apparent solution.
it is a really annoying procedure, you will need your device serial number and a good internet connection. When the download was finished, the software instructed to go into download mode. The installation started and seemed to be doing fine, but sadly the process has failed at 67%.
So to solve this Samsung bootloop problem you need to follow this method hope it will 100% work for you. Thanks

Odin Log:
<ID:0/022> Odin engine v(ID:3.1100)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> aboot.mbn
<ID:0/022> NAND Write Start!!
<ID:0/022> sbl1.mbn
<ID:0/022> rpm.mbn
<ID:0/022> tz.mbn
<ID:0/022> hyp.mbn
<ID:0/022> NON-HLOS.bin
<ID:0/022> sec.dat
<ID:0/022> boot.img
<ID:0/022> recovery.img
<ID:0/022> system.img.ext4
<ID:0/022> FAIL! (Erase)
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
 
Top