SPH-L710 Repair Error
 

Connecting to Target...
JTAG device: MSM8960.
CPU IDCODE : 0x4F1F0F0F Mfg.: 0x787, Part: 0xf1f0, Ver.: 0x4
CPU Manufacturer: Samsung , CPU Name: ARM7GEN
JTAG device: MSM8960.
CPU IDCODE : 0x406B10E1 Mfg.: 0x070, Part: 0x06b1, Ver.: 0x4
CPU Manufacturer: QUALCOMM , CPU Name: MSM8960
Halting CPU...
Initialize hardware...
Starting target communication...
Detecting emmc memory parameters of bank (0) ...
EMMC #0 : ID : 0x00000015 Name : MAG4FB Size : 14.7 G , (30777344) Blocks
EMMC #1 : ID : 0x00000015 Name : MAG4FB Size : 2.0 M , (4096) Blocks
eMMC flash device(s) found, Device ID : 0x00150000
NAND Writing GPT, PIT, MD5...
Packet length too large: 0xFFFFFFFF
Unknown DCC answer /PROTOCOL/
Failed writing file GPT.BIN to eMMC flash 0 at offset 0x000F0000

Is this a bad EMMC that needs replacing since repair via this box or RIFF fails, i can get RIFF to complete sometimes, but usually fails, and EasyJtag fails at 23% when writing the GPT.BIN to eMMC each time. Im guessing only way to repair this is to replace eMMC? I dont have a eMMC pinout for this device or i would try eMMC tool for repair.

Ok, now i managed to get it to complete:

Connecting to Target...
JTAG device: MSM8960.
CPU IDCODE : 0x4F1F0F0F Mfg.: 0x787, Part: 0xf1f0, Ver.: 0x4
CPU Manufacturer: Samsung , CPU Name: ARM7GEN
JTAG device: MSM8960.
CPU IDCODE : 0x406B10E1 Mfg.: 0x070, Part: 0x06b1, Ver.: 0x4
CPU Manufacturer: QUALCOMM , CPU Name: MSM8960
Halting CPU...
Initialize hardware...
Starting target communication...
Detecting emmc memory parameters of bank (0) ...
EMMC #0 : ID : 0x00000015 Name : MAG4FB Size : 14.7 G , (30777344) Blocks
EMMC #1 : ID : 0x00000015 Name : MAG4FB Size : 2.0 M , (4096) Blocks
eMMC flash device(s) found, Device ID : 0x00150000
NAND Writing GPT, PIT, MD5...
eMMC Write OK! Elapsed time: 19.370108s (211.460 KiB/s)
NAND Writing SBL1...
eMMC Write OK! Elapsed time: 1.199069s (106.749 KiB/s)
NAND Writing SBL2...
eMMC Write OK! Elapsed time: 2.095120s (122.189 KiB/s)
NAND Writing SBL3...
eMMC Write OK! Elapsed time: 4.437254s (115.387 KiB/s)
NAND Writing ABOOT...
eMMC Write OK! Elapsed time: 10.615607s (84.404 KiB/s)
NAND Writing RPM...
eMMC Write OK! Elapsed time: 3.059175s (167.365 KiB/s)
NAND Writing TZ...
eMMC Write OK! Elapsed time: 3.488200s (146.781 KiB/s)
All Done.

But it will not stay in download mode, turns off moments after getting into download mode. Same with recovery or even trying to let the phone boot. I assume this has to be eMMC issue, i cant think of anything else that may be causing it. Any insight/help will be much appreciated!

It finally allowed EFS to be written, now its staying in DL mode, waiting for fresh copy of firmware to download, will try reloading with Odin after and post results. Still not sure what was causing this phone to act like this. ive done at least 10-20 of these minimum and never experinced this before. Least it seems to be working now, as stated, will post final results after firmware downloads (super slow server).

Ok, flashed stock via odin, and it now boots up, but has no IMEI, MEID, SN, and SPC readers and 16 digit passwords dont work, so i cant try a ##786#, which probably wouldnt fix it anyhow. So im now stuck with a phone with no way for customer to connect to the network due to these being all blank.

Any one have any ideas? Ive tried everything i can think of. Wish customer could have brought me a phone ic ould do a EFS backup on lol. They may be out of luck?

Ok, after bouncing back and forth between easyjtag and the other box, ive managed to get the phones IMEI & MEID restored. Apparently when i flashed the stock odin firmware, it didnt flash the modem. I reflashed the firmware 3 or 4 times, it finally took and now i have the phone in working order & have a happy customer.

Weird that the modem didnt stick the first few times, ive never had that happen before, anyone else?

Hello, share how you restored MEID and IMEI. EasyJTAG are boot repair solution we don't support IMEI operation at this moment.

Modem was null, flashed the modem from STOCK and this repaired the IMEI

As Spagman stated, restoring the modem fixed this. Though if it hadnt, i would have used CDMA Workshop or DFS as both will write IMEI and ESN/MEID on this model.

Now, im waiting on a power button as apparently this one has a power button issue which may have been half my issues with the "failing" i was getting lol. In fact, im almost certain this is what was causing the failure.

(oops, quoted wrong post lol) also, i have Samsung Tool activated on the easyjtag box, i use it often, love the product guys :)

How did you manage to complete? having the same error with a SGH i747, please

I removed the faulty power button that I as causing the issues and replaced it. Was causing the phone to power cycle during repair which caused the repair to fail. After I removed the button and used tweezers to power it on, it repaired just fine. I replaced the button and all has been well with it since (customer visits often).

thanks, but i have 3 i747 with the same GPT. BIN error, could it be the power button too? currently using a 4.8v usb power supply cable only. any recommendations?

It's possible, but I think my situation was somewhat unique and I doubt many have encountered it due to the same reasons I did. My only guess if your power source is good and not losing power for some reason during repair, is a bad emmc which I think I first thought might have been my problem. Wish I had more ideas or insight on this to provide.