Hard Bricked Galaxy S3 SPH-L710

[jazzytrashglam]

I've read a number of forum posts about how to unbrick a hardbricked galaxy S3 and followed them all and even tried countless times the same method as is suggested, yet I can't get my phone to boot at all. Anyone out there have any advice? I rooted my phone just fine and then flashed Android_Revolution_HD-SGS3_53.0.zip onto it through clockwork mod. Everything appeared to be installing fine and when it came time to reboot, clockwork mod notified me that something appeared wrong in my boot file and I may lose root priveledges. It then asked if I wanted clockwork mod to fix it and I unfortunately said yes. The screen immediately went pitch black and nothing I have tried gets it to show any signs of life.

I have a 64 GB micro SD that I've used with the command

sudo dd if=Desktop/debrick_sph_l710.img of=/dev/mmcblk0

I then check it with

sudo fdisk -l /dev/mmcblk0

and get

GPT PMBR size mismatch (30777343 != 122241023) will be corrected by w(rite).
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/mmcblk0: 58.3 GiB, 62587404288 bytes, 122241024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 98101B32-BBE2-4BF2-A06E-2BB33D000C20

Device             Start      End  Sectors  Size Type
/dev/mmcblk0p1      8192   131071   122880   60M Microsoft basic data
/dev/mmcblk0p2    131072   131327      256  128K unknown
/dev/mmcblk0p3    131328   131839      512  256K unknown
/dev/mmcblk0p4    131840   132863     1024  512K unknown
/dev/mmcblk0p5    132864   136959     4096    2M unknown
/dev/mmcblk0p6    136960   137983     1024  512K unknown
/dev/mmcblk0p7    137984   158463    20480   10M unknown
/dev/mmcblk0p8    158464   159487     1024  512K unknown
/dev/mmcblk0p9    159488   160511     1024  512K unknown
/dev/mmcblk0p10   160512   180991    20480   10M Linux filesystem
/dev/mmcblk0p11   180992   208895    27904 13.6M Linux filesystem
/dev/mmcblk0p12   208896   215039     6144    3M unknown
/dev/mmcblk0p13   215040   221183     6144    3M unknown
/dev/mmcblk0p14   221184  3293183  3072000  1.5G Linux filesystem
/dev/mmcblk0p15  3293184 28958719 25665536 12.2G Linux filesystem
/dev/mmcblk0p16 28958720 28975103    16384    8M Linux filesystem
/dev/mmcblk0p17 28975104 30695423  1720320  840M Linux filesystem
/dev/mmcblk0p18 30695424 30715903    20480   10M unknown
/dev/mmcblk0p19 30715904 30736383    20480   10M unknown
/dev/mmcblk0p20 30736384 30748671    12288    6M Linux filesystem
/dev/mmcblk0p21 30748672 30754815     6144    3M unknown
/dev/mmcblk0p22 30754816 30754831       16    8K unknown
/dev/mmcblk0p23 30754832 30765071    10240    5M Linux filesystem

The phone acts no differently with the flashed sd card than it does without it. Is the only way to fix it with a JTAG?

 

[hilla_killa]

U need 16gb sd card, debrick image for your phone. Then you can boot into download mode and flash in odin! Get a high quality 16gb card

 

[jazzytrashglam]

U need 16gb sd card, debrick image for your phone. Then you can boot into download mode and flash in odin! Get a high quality 16gb card

I'm using a 32 GB SanDisk micro sd, could it just be that all the debrick images I've used are just the wrong ones?

 

[hilla_killa]

Its possible but i think if your phone is 16gb than you need 16gb sd