Hi all, I will explain briefly what happens to my S3 (GT-I9300) is "soft brick" enters the "downloads" only. If I want to enter the recovery mode, restarts and freezes once the logo of Samsung.
I tried to make a flash via Odin (1.85, 3.07 version) by following the appropriate steps. A negative result (fails). I read that it could be the file "PITS" I have also tried different and never-ending operation is always the result is "fail". After that I have to turn off the phone by removing the battery, it is the only way to recognize ODIN again.
The end result is always the same:
<ID: 0/005> Added !!
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cord ..
<OSM> Please wait ..
<OSM> I9300UBUGML1_I9300ANCUGMK1_I9300UBUGMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 Sucessfully finished ..
<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> sboot.bin
<ID: 0/005> Write Start NAND !!
<ID: 0/005> Transmission Complete ..
<ID: 0/005> Now Writing .. Please wait about 2 minutes
<ID: 0/005> Receive Response from boot-loader
<ID: 0/005> FAIL!
<OSM> All threads completed. (Succeed 0 / failed 1)
Try flashing bootloader BLFB then try firmware flash with pit. If still the same then your emmc chip is broken.
boomboomer said:
Try flashing bootloader BLFB then try firmware flash with pit. If still the same then your emmc chip is broken.
Click to expand...
Click to collapse
thank you very much I will try and tell you
agus_311 said:
thank you very much I will try and tell you
Click to expand...
Click to collapse
Hi. There was no case, apparently the cell is damaged. Any other suggestions? or is it like a cute paperweights... =(
Thanks
Related
I'm desperated right now. I Tried to install an original 2.3.4 XWKI1 rom, but in odin, with all options right and yellow icon, the update starts but when will start the rom write appear an error and said FAIL! in red upthere.
I Tried another original rom and the same error. I don't khow what to do. Sorry for the english... i know if have other theads about this, but no one solve my problem.
When i start the phone appears: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
But the kies don't recognize the phone
ODIN ERROR:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_JDI_I9100WBKK1_I9100UHKJ1_I9100JDIKK1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sorry if i broken any rules, and HELP ME please!
What model phone have you got?
Eg: I9100
Sent from my GT-I9100 using XDA App
Yeah, GT-I9100
Maybe flashing a firmware with PIT?
with the five files. I Found this in other topic with the same issue:
"I encountered the same problem. And I was able to solved it by flashing it with xxkg6 stock firmware downloaded from sammobile.com.. The file must contain 5 files that includes the pit file. I know most of the thread advised not to touch the pit file but I just did(I took the risk). When I loaded the pit file, it automatically checked the re-partition option.. After 5mins my gs2 has born again.."
If you have Kies loaded at same time/in background close it. You cant flash via ODIN while Kies is running.
i killed all running process from kies... i'll try with a firmware with PIT and check re-partition (XXKG6)
rffslow said:
and check re-partition
Click to expand...
Click to collapse
I wouldn't do that if i were you.
peachpuff said:
I wouldn't do that if i were you.
Click to expand...
Click to collapse
why? i don't see any other solution... i don't know what to do so
phone was havaing problem of null imei and was not accepting code *#7284# so i flashed it
now having an other problem of phone not starting in normal mode
tryed tto many version but nothing changed
always reboot on recovery menu
i've try with theses versions
Code:
I9300XXEMC2_I9300VFGEMD1_SFR_4.1.2.zip
Code:
I9300XXALEF_I9300XEFALE1_XEF.zip
Code:
recovery-cwmtouch-6.0.3.2-GTI9300.tar
RR_JB_V3.1.4_AOKP_4.2.1_I9300.zip
Code:
CODE_I9300XXBLH1_928452_REV00_user_low_ship.tar.md5
MODEM_I9300XXLH1_REV02_REV04_CL1172449.tar.md5
CSC_OXE_I9300OXEBLF1_CL777132_REV00_user_low_ship.tar.md5
Code:
CODE_I9300XXEMA2_836582_REV00_user_low_ship.tar.md5
MODEM_I9300XXELLA_REV02_REV04_CL1214143.tar.md5
CSC_WIN_I9300WINEMA1_811450_REV00_user_low_ship.tar.md5
flashed with odin & nspro
Code:
Initialising connection...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun
Reading PIT from device...
PIT read successfully
Uploading BOOTLOADER
BOOTLOADER upload successful
Uploading CACHE
CACHE upload successful
Uploading HIDDEN
HIDDEN upload successful
Uploading RADIO
RADIO upload successful
Uploading RECOVERY
RECOVERY upload successful
Uploading SYSTEM
SYSTEM upload successful
Uploading TZSW
TZSW upload successful
Uploading BOOT
BOOT upload successful
Ending session...
Rebooting device...
Press NEXT to continue...
corrupted efs. restore it or replace the motherboard
Glebun said:
corrupted efs. restore it or replace the motherboard
Click to expand...
Click to collapse
it's possible to repair efs using microbox or nspro or any other samsung box
my problem is phone not booting into normal mode
because of the corrupted efs
Glebun said:
because of the corrupted efs
Click to expand...
Click to collapse
phone fixed by flashing only one file
efs still corrupted but now phone is booting into normal mode
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> _______________I9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> _____.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
cool
Hello. I have a problem. I have a samsung galaxy s6 unit g925x demo edge. I wanted to write it soft 1 g925f a file from which the normal S6 edge. When I included the phone in bootloader mode and tried to write it with a soft by Odin to the odinie jump out the mistake .... Here below you log oo Odin:
<ID: 0/004> Added !!
<OSM> Enter CS for MD5 ..
<OSM> Binary Check MD5 .. Do not disconnect the cable ..
<OSM> Please wait ..
<OSM> Checking successfully completed MD5 ..
<OSM> Leave CS ..
<ID: 0/004> Odin engine v (ID: 3.1100) ..
<ID: 0/004> Analysis file ..
<ID: 0/004> SetupConnection ..
<ID: 0/004> Initialzation ..
<ID: 0/004> Download PIT for mapping ..
<ID: 0/004> Firmware start the update ..
<ID: 0/004> SingleDownload.
<ID: 0/004> boot.img
<ID: 0/004> NAND Record start !!
<ID: 0/004> cache.img
<ID: 0/004> cm.bin
<ID: 0/004> FAIL!
<ID: 0/004>
<ID: 0/004> Complete (Write) operation failed.
<OSM> All threads completed. (Good luck 0 / failed: 1)
Now when I try to turn the phone to either stands on logu galaxy s6 demo unit edge OR appears: An error occurred while updating the device software.Use function of the emergency recovery intelligent software switch. When you want to write it by an intelligent software switch to show that the ten model or g925x demo NO Support scales This program ...
I do not know what to do Help please. I count on it
Personal speech.
Would help to solve the problem I'm going through.
Was using the ROM "cm-13.0-20160901-UNOFFICIAL-Temasek-i9305" and did the usual procedure (already done several times this process), however an hour to another cell restarted and was caught in the BOOT screen ..
I entered the TWRP mode and received a "No OS installed" message.
Based on that, I tried to install the ROM again, but the TWRP can not read the micro sd and not the internal memory.
From that, I tried to return to original ROM, however I am getting this fault message on ODIN:
<OSM> Enter CS is MD5 ..
<OSM> Binary Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> Checking MD5 finished sucessfully ..
<OSM> Leave CS ..
<ID: 0/005> Added !!
<ID: 0/005> Odin engine v (ID: 3.1100) ..
<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> SingleDownload.
<ID: 0/005> tz.img
<ID: 0/005> NAND Write Start !!
<ID: 0/005> FAIL!
<ID: 0/005>
<ID: 0/005> Complete (Write) operation failed.
<OSM> All completed threads. (0 succeed / failed 1)
I've used the version of ODIN (3:07, 3:10, 3:12) all display the same error.
I also noticed that when you enter the TWRP and access any folder, I get the message in the log:
unable to mount the store
Failed to mount (invalid argument)
Try rooting my Samsung j7 Prime SM-G610M device with CF-Auto-Root. The case is that under the CF-Auto-Root corresponding to version 8.1.0 Oreo of my Mobile with the same number of compilation, but when flashing from Odin, it tells me everything is correct, but it restarts, I verify with Root Checker that I have rooted, but he says no. Below I leave the log generated by Odin to review.
Code:
<ID: 0/005> Added !!
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> Checking MD5 finished Successfully ..
<OSM> Leave CS ..
<ID: 0/005> Odin engine v (ID: 3.1203) ..
<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> SingleDownload.
<ID: 0/005> recovery.img
<ID: 0/005> cache.img
<ID: 0/005> RQT_CLOSE !!
<ID: 0/005> RES OK!
<ID: 0/005> Removed !!
<ID: 0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID: 0/004> Added !!
<ID: 0/004> Removed !!
<ID: 0/004> Added !!
<ID: 0/004> Removed !!
[/ code]
Forgive my English, I'm from Argentina and use the Google translator ...