Bricked SPH-L720 after modem firmware upgrade attempt. Help! - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

Phone: SPH-L720
Baseband: L720VPUAMDL
OS: PAC-ROM 5.1.1
Attempted to update the modem from MDL to OK3 with only the modem.bin and NON-HLOS.bin file via Odin 3.10.7. The upgrade failed. Now the phone fails to boot and displays the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". ODin was run "as administrator" and I have swapped cables and USB ports. The phone will go into download mode and display the follow screen:
PRODUCT NAME: SPH-L720
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: Custom
KNOX KEARNEL LOCK: 0xfffffffC
KNOX WARRANTY VOID: 0xFFFFFFFC
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
I attempted to reload the factory image L720vpumdl and it failed with a missing PIT partition error. see below.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
I attempted again with the same image and added a L72016GB pit file.
With PIt file added:
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
If anyone has any suggestion or a known solution I would apreciate it. I do have access to another SPH-L720 but it baseband is on NAE.
Thanks

leapcad said:
Phone: SPH-L720
Baseband: L720VPUAMDL
OS: PAC-ROM 5.1.1
Attempted to update the modem from MDL to OK3 with only the modem.bin and NON-HLOS.bin file via Odin 3.10.7. The upgrade failed. Now the phone fails to boot and displays the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". ODin was run "as administrator" and I have swapped cables and USB ports. The phone will go into download mode and display the follow screen:
PRODUCT NAME: SPH-L720
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: Custom
KNOX KEARNEL LOCK: 0xfffffffC
KNOX WARRANTY VOID: 0xFFFFFFFC
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
I attempted to reload the factory image L720vpumdl and it failed with a missing PIT partition error. see below.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
I attempted again with the same image and added a L72016GB pit file.
With PIt file added:
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
If anyone has any suggestion or a known solution I would apreciate it. I do have access to another SPH-L720 but it baseband is on NAE.
Thanks
Click to expand...
Click to collapse
Try the full OK3 tar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
Try the full OK3 tar
Click to expand...
Click to collapse
Tried the full ok3 tar file ( L720VPUGOK3_L720SPTGOK3_L720VPUGOK3_HOME.tar.md5). It ran much longer but soon failed also. Posted results below.
The phone screen added 2 lines in red at the bottom. Start [224, 1440] Bar [224, 1440]
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!

leapcad said:
Tried the full ok3 tar file ( L720VPUGOK3_L720SPTGOK3_L720VPUGOK3_HOME.tar.md5). It ran much longer but soon failed also. Posted results below.
The phone screen added 2 lines in red at the bottom. Start [224, 1440] Bar [224, 1440]
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
Can you get into Recovery and flash a ROM? If not, can you flash a recovery in Odin?

bilgerryan said:
Can you get into Recovery and flash a ROM? If not, can you flash a recovery in Odin?
Click to expand...
Click to collapse
The phone had TWRP 3.0.2 before the mishap but that would not load. I went back into Download mode and reloaded TWRP 2.8.4.0 via Odin and that was successful. When I attempted to boot the phone it went into (boot loop) and was stuck on the Samsung Galaxy S4 boot screen. I went back into recovery and did a factory wipe. TWRP complained at the very end it was unable to mount /system. I went into advanced wipe and selected system. The wipe/format of /system came back clean. I then did a nandroid restore and rebooted. We are finally up and running.! :good:
Thanks bilgerryan for your assistance.!!!
TWRP 2.8.4.0 load:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

leapcad said:
The phone had TWRP 3.0.2 before the mishap but that would not load. I went back into Download mode and reloaded TWRP 2.8.4.0 via Odin and that was successful. When I attempted to boot the phone it went into (boot loop) and was stuck on the Samsung Galaxy S4 boot screen. I went back into recovery and did a factory wipe. TWRP complained at the very end it was unable to mount /system. I went into advanced wipe and selected system. The wipe/format of /system came back clean. I then did a nandroid restore and rebooted. We are finally up and running.! :good:
Thanks bilgerryan for your assistance.!!!
TWRP 2.8.4.0 load:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Cool, glad you got it back up and running.

Related

[Q] Hard to unbrick

Hey guys...
I need a little help from professionnals...I wanted to try a Cyanogen rom, the 10.1.3, a stable one, on my S4. So I downloaded it, I rooted my phone with cf-autoroot with Odin, intalled CWM Recovery. Then I did all the wipes and flashed the cyanogenmod.
Guess what, it didn't work The flash worked well but next infinite bootloop on the boot animation of cyanogen...So I tryied to go back to recovery, mount USB and flash an another rom of cyanogen. And the results was worse, the flash did'nt work at all, if I remember "failed to mount /system" or something similar. And when I tried to restard the phone, nothing happened.
So I wanted to go back to the stock rom to repair this mess. => Download mode then under PDA, my tar.md5 files. Didn't work. I also tried with a PIT file, same result.
I changed my usb cable, the version of Odin, the usb port.
Here's what Odin give :
<ID:0/003> Added!!
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I don't know what to do, I tried a lot of things beside all of this. Any ideas ?
THX
Try install STOCK ROM with older ODIN (click here), no the newest version
What stock rom are you trying to flash?
Thanks, but no change...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Lennyz1988 said:
What stock rom are you trying to flash?
Click to expand...
Click to collapse
This is I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME, official for Europe, 4.3
BeamGG said:
This is I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME, official for Europe, 4.3
Click to expand...
Click to collapse
if you have the secured bootloader (knox warranty void 0x0 in download mode) that means you can not flash old firmware such as MGA. you can flash firmwares MH?, MI? or MJ?.
I9505XXUBMGA = 4.2.2.
Thats probably why the flashing fails.
Lennyz1988 said:
I9505XXUBMGA = 4.2.2.
Thats probably why the flashing fails.
Click to expand...
Click to collapse
I'm such an idiot...I hasd chosen the wrong file...I'm trying with the MJ5 now, I'll let you know
EDIT : Indeed it goes further, but not at the end :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT : I changed the usb port and re-installed the drivers, worked...finally, thx guys !
BeamGG said:
I'm such an idiot...I hasd chosen the wrong file...I'm trying with the MJ5 now, I'll let you know
EDIT : Indeed it goes further, but not at the end :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT : I changed the usb port and re-installed the drivers, worked...finally, thx guys !
Click to expand...
Click to collapse
Only changing usb port and reinstalling solved it?
I have the same issue with ODIN3 3.07.
need4steer said:
Only changing usb port and reinstalling solved it?
I have the same issue with ODIN3 3.07.
Click to expand...
Click to collapse
Hey man,
Sorry for this late answer. Yes, as I said, I only changed the usb port et reinstalling drivers...did it work for you ?
BeamGG said:
Hey man,
Sorry for this late answer. Yes, as I said, I only changed the usb port et reinstalling drivers...did it work for you ?
Click to expand...
Click to collapse
Unfortunately no. Apparently the tar.md5 file I was trying to flash was the problem. The developer released a newer version of it which was flashed okay. Thanks a lot anyway!
need4steer said:
Unfortunately no. Apparently the tar.md5 file I was trying to flash was the problem. The developer released a newer version of it which was flashed okay. Thanks a lot anyway!
Click to expand...
Click to collapse
Cool, you are welcome ! :good:

Problem while attempting to room Galaxy S4 I337 ATT

Phone: Galaxy S4 I337 AT&T with latest update, 4.4.3
What I did before I began the process:
1) Enable debugging mode on the phone
2) Installed latest Samsung Drivers
3) Used original USB Samsung cable
What I did: Download and ran Root and Recovery for ATT-TMO GS4-CASUAL-R527b and in doing so, processed failed.
Here is what looks like now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Following step, to correct the problem, was I download the firmware that came with the phone, I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar. Zip file in size of 1.59GB and I used different version of Odin, including 1.85, 3.04, 3.05 and 3.07 with no success to fix the problem I caused in the first place.
This is what phone looks like -
This is what Odin looks like when it attempted to process the file above, I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I would like to get my phone back running again. Can someone please guide me, if it possible to get it back to stock firmware. Please understand that I searched the forum and Google for all possible solutions, as well as YouTube videos. I am clearly not experience in rooting phone and this was my first attempt.
Thank you for all the help.
Remember that the phone has a locked boot loader which prevents stock recovery and kernel from being replaced. Also, the boot loader itself cannot be downgraded.
You were on KitKat which means you had firmware ending with NB1 or NC1. Trying g to flash the MDL files was trying to downgrade boot loader and hence the issue.
http://forum.xda-developers.com/showthread.php?t=2616221
Read the return to stock section of the above thread. Download and flash the NB1 firmware. There are 2 versions of which you can use either.
Method to update to latest NC1 is also given in the thread.
The only working recovery we have is safestrap. All custom ROM flashing happens with this.
Almost..but failed.
So I checked out the post you replayed and I did the following -
1) Downloaded I337UCUFNB1_4.4_Stock_Odin_tar from here
2) Used Odin v3.9.3 and here is the following result:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.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> 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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
File tar.md5 comes very close to completing and stop; and I get a FAIL!
On the phone I get the following:
START [224, 1440]
BAR [240, 1440]
selchi said:
So I checked out the post you replayed and I did the following -
1) Downloaded I337UCUFNB1_4.4_Stock_Odin_tar from here
2) Used Odin v3.9.3 and here is the following result:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.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> 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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
File tar.md5 comes very close to completing and stop; and I get a FAIL!
On the phone I get the following:
START [224, 1440]
BAR [240, 1440]
Click to expand...
Click to collapse
just keep trying, that happens from time to time...its usually a faultt usb port or cord, so try differnt ports or buy a new cord, ome time I was stuck with a bad cord and literally kept trying for 2-3 hours before it finally completed the odin flash
Sent from my SAMSUNG-SGH-I337 using Tapatalk

[HELP] S6 Edge Plus (SM-G9287C) CUSTOM BINARY (SYSTEM) BLOCKED BY FRP LOCK

I'm trying to reflashed my stock ROM. But it always fail and it says "Custom Binary(System) Blocked by FRP Lock"
I'm currently using Nougat 7.0
Here's my ODIN Log:
<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..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help. Thanks!
cdegudy said:
I'm trying to reflashed my stock ROM. But it always fail and it says "Custom Binary(System) Blocked by FRP Lock"
I'm currently using Nougat 7.0
Here's my ODIN Log:
<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..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help. Thanks!
Click to expand...
Click to collapse
Help please. Thanks!
cdegudy said:
Help please. Thanks!
Click to expand...
Click to collapse
If you have twrp recovery just reboot into it and go to wipe>advanced wipe>and select dalvik/ART cache, system, data, internal storage(if you want), cache. Done finished wipe and swipe into reboot system and you got a message it's no os in your phone just keep reboot it. When the screen become blank keep press hold down power button+home+volume down to into download and that you will reflashed your stock rom with succeed it.
(sorry my bad english)
cdegudy said:
I'm trying to reflashed my stock ROM. But it always fail and it says "Custom Binary(System) Blocked by FRP Lock"
I'm currently using Nougat 7.0
Here's my ODIN Log:
<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..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help. Thanks!
Click to expand...
Click to collapse
Are you trying to flash marshmallow or nougat ?
Google fpr lock lol. You need to remove all your google accounts from device pre flash to disengage the device protection implemented in 5.0 by google.

NEED HELP: S6 EDGE+ SM-G9287C STUCK (Error while updating software)

I hope you guys can help me.
So I tried going around my phone's system. I flashed using ODIN at first, then I got stuck on the "NO COMMAND ERROR". I put my phone again on Download Mode, but this time I got prompted this message, "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.", which I did, but it always says "SM-G9287C does not support initializing."
What could have I done wrong? Please help.
I tried using ODIN again, and I got this:
<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..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3957 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3957 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) - and it took me back to Smart Switch blah blah message
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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..

Need debrick help: accidentally checked repartition in Odin on Core Prime (G360H/DS)

My G360H/DS is stuck in a boot loop. I get the boot splash
Stock Recovery and TWRP both show errors mounting /cache/System/data etc .... so I'm guessing I really killed the partition table. However, I can still get into Download Mode, so I'm really hoping there is a chance to save my phone!
after retry flashing now Odin fails at system.img .. please help me
<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> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 873 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Categories

Resources