[HOW TO GUIDE] How To Unbrick AT&T I747 and I747M After 4.3 OTA

[theramsey3]

thus far this method will not work for any of your 4.4.2 ota bricks if you flashed the 4.4.2 modem on the mjb bootloader, the only way to fix those bricks is with a new emmc, motherboard or a new phone. Jtag won't save you this time the phone is now a glorious paperweight.

On 4.3 it will not work if you flashed a bootloader for the wrong model(E.G. AT&T I747 bootloader on a Bell I747M)


Read ALL of the first 2 posts,there is useful information and files in post 2.

This works for BOTH AT&T I747 and the I747M The files are located at the bottom of this post in the quote there are also more instructions and files/tools to download in the 2nd post of this thread.


First and foremost I take no credit for any of the work here, other people did most of the leg work. This is a DIRECT copy of -Mr.X-'s post from here namely page 17 that is being used with his permission, I have added to it after having to actually Unbrick my phone lastnight.

Thank you to all who contributed to the things that made this thread possible. -Mr.X-, Loserskater, upndwn4par, enewman17 and all who may have contributed to their work.

So what you have done is hard bricked your I747 AT&T or your I747M by whatever means. Most likely flashing something with a bootloader. Your phone won't do anything at all. You can't get to download mode or recovery mode. Perhaps this method will fix your phone? Give it a try what else do you have to loose? You might save some money on a Jtag?

I take no responsibility for anything that comes of you using this information.

IF YOU BRICKED YOUR PHONE BY FLASHING A DIFFERENT MODELS BOOTLOADER ON IT THIS METHOD WILL NOT WORK FOR YOU. ] YOU WILL NEED A JTAG.(THAT ALSO INCLUDES WHILE TRYING TO UNBRICK USING THIS METHOD.)

Be sure to get all the way to the bottom of the first 2 posts and PLEASE read everything before doing anything.

The Debrick Files are all the way at the bottom in the qoute below by -Mr. X- The Links Are Active.
Be sure to read the second post too. If you need clarification on anything please send me a PM

Here Is The Information You Came Here For HOW TO DEBRICK - Mr. X-'s post from This Is The Thread That The Below Quote Is From

Click below for the quote from where I got most of my information, do not just start doing things after you read the below quote, read the second post too.

How to UNBRICK:

Credit goes to these guys in this thread, I thought i was onto something origional, however after doign some searching i found others have figured this out for a different Variant of the S3

What you did:
Bricked downgrading the bootloader after upgrading to the 4.3 bootloader. The 4.3 bootloader appears to blow efuses that stop previous boot loaders from booting. Now your EMMC has non booting garbage on/in it. YAY! not...

What we are doing:
What we will be doing is writing the Partition layout (Partition.mbn) among other things to the SD so the phone will boot from it after it fails to boot from the EMMC. According to my research the CPU is designed to cascaded from one storage device to the other in the event of failure on the first device. This also means if your EMMC is smoked, you could technically run the whole rom and everything from the sd card, or that's my assumption.

What you need:

- A Micro SD card 16GB or larger. this will no work on smaller cards, i tried a 2GB 4 GB and 8GB for the sake of testing and it fails.

- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.

- The ability to write the dump image to the micro sdcard.

What to do:

First:
I used "Win32DiskImage" Located here But you can also use dd to write the image to your sd card in Linux.

On Windows:
Open Win32DiskImage. Brows to the Debrick dump you have for your device. Select the drive letter if your micro sd in the drop-down, click write. Bam done.

On Linux:
For ease of example, and method. Open Gparted on your Linux install or live cd, check the dev your sd card is in the drop down menu. For example mine was /dev/sdb/ then use "dd if=/path/to/debrick/dump.img of=/dev/sdb/" This method also works. Be careful you are selecting the right dev or you will overwrite another disk on your system. YOU HAVE BEEN WARNED.

Second:
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.

Third:
Odin that thing back to the 4.3 stock rom. Yes you have to. You ain't getting 4.1.2 bootloaders back so dont think about odining that thing either. it wont boot, with out the SD with the 4.3 bootloader on it installed. Odining back is the best thing to do, it will get the right boot loader on your EMMC. If you are feeling adventurous and you had a custom recovery installed. You can boot to recover instead of download from the debricking SD boot, and install a 4.3 flashable zip bootloader there, if all goes well, you wont lose your data and the bootloader will be functional on the EMMC. Either method you choose after its done "flashing" what ever method. remove the sd and verify it boots on its own.
Note: a user stated that he flashed a bootloader via recovery and flashable zip, and he stated it appeared to flash the bootloadeerr to the micro sd. if this happens, ODIN back to the proper rom to get the internal EMMC rebuilt and booting.

If it does, do a dance or something.

Here is a flashable Bootloader for the i747M 4.3

Here is a debrick Dump from a I747M from the UEMK5 4.3 that works

Broken link I will update IF/AFTER it is fixed is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)

This one is for AT&T phones.
Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.

 

[theramsey3]

The 16GB SD card is going to get formatted and partitioned if you have valuable data on it do a back up of it... You have been warned.MAKE SURE YOU USE THE CORRECT FILES FOR YOUR PHONE FAILURE TO DO SO WILL RESULT IN YOUR PHONE NEEDING TO BE JTAG'ED

YOU HAVE BEEN WARNED REPEATEDLY DO NOT FLASH THE WRONG BOOTLOADERS

Requirements(carrier specific)

For The AT&T SGH-I747

you will need two micro SD cards one 16GB (I read in a similar thread that the SD card must be 16GB no smaller and no larger if you get one bigger to work please let me know) and one 1GB or larger. You will need Odin v3.09(what I used), Samsung kies3 (you need the USB drivers it installs, a working custom recovery either CWM or TWRP(I prefer TWRP) and some patients.

For The SGH-I747M

you will need a 16GB micro SD card to put the debrick files on, Odin v3.09, Samsung kies3, the correct firmware TAR file for your phone and some patients.

If you need some of the things mentioned in the requirements please click under "Tools You May Need And File Downloads For AT&T and the SGH-I747M" .

You Need to Identify Your Phone Model Correctly and download the appropriate debrick file From the quote by -Mr. X- in the post above to place on your 16GB Micro SD Card with the Win32DiskImager (available for download below).

How to put the Debrick file on your SD card

Flash this Debrick file to your 16GB Micro SD card with Win32DiskImager (available below) by
*Insert your Micro SD card into your computer (backup any information you may have on it we are going to ERASE, FORMAT and PARTITION it.)
*Open win32DiskImager
*Navigate to the location where you downloaded the correct Debrick file
*Select your Debrick file by double clicking on it
*In the upper right corner of Win32DiskImager you should make sure that the drive letter assigned to your sd card is selected.
***Which ever drive that is listed will be erased, formatted, partitioned and have a small amount of data written to it***
*Click write in the bottom right hand side

You now have your debrick card

For the SGH-I747M
You need to put the Debrick SD card in the Phone, Pull and Replace the Battery, Put the Phone in download mode and flash your carrier specific 4.3 firmware (instructions and downloads Below) Via ODIN. Reboot the phone allow it to boot up, get in the phone, reboot without the debrick sd card in it, if it won't boot on its own see the link below.

If you are on AT&T
You will need to copy all of the files you are going to flash (you can download them below) onto your 1GB or larger SD card. You then Need Put your Debrick SD card in the Phone, Remove and reinstall the battery,Put the Phone in Recovery Mode (Must Be Either TWRP or CWM Instructions and TWRP Download Below), Dismount the Debrick SD card, Insert your SD card with your Bootloaders, ROM, kernel, and Modem into the Phone, Mount the SD card, Flash your files one at a time, wipe the cache and dalvik between each file, Once you are done reboot the system, You Might have to put the debrick SD back in and do another battery pull, boot up the phone, after you get in the phone reboot it without the Debrick SD card in. If it will not Boot on its own see the link below.

AFTER YOU FLASH IT MAY APPEAR THAT THE PHONE FREEZES ON THE BOOT SCREEN BE PATIENT 4.3 TAKES A LONG TIME TO BOOT THE FIRST TIME A ROM IS INSTALLED.


Tools You May Need And File Downloads For AT&T and the SGH-I747M

Here is a flashable Bootloader for the i747M 4.3

Here is a debrick Dump from a I747M from the UEMK5 4.3 that works

Broken link I will update IF/AFTER it is fixed is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)

Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.

Debrick file mirrors use only if the links ^^^above don't work please.

AT&T debrick file Use this ONLY if you are on AT&T and after you have been on the 4.3 bootloaders

SGH - I747M debrick fileUse this ONLY if you have an SGH-I747M that was on the 4.3 bootloaders.

Win32 Disk Imager (used to write the debrick file to the sd)
Samsunk Kies

Go Here For Odin Pick Whichever One You Want To Use I Used 3.09

Do Not worry about downloading or installing root or KnoxRemover or SuperSU from the thread below yet focus on the task at hand you need to get your phone booting first then concern yourself with other goodies. You need TWRP and possibly ODIN if you want to take it from there. There are instructions in that thread on the installation of TWRP Skip the rest for now.
Go Here For TWRP Custom Recovery There Is Also A Link To ODIN There

Partition Wizard Free (There is a link with instructions below)
With AT&T you will have to download 4.3 bootloaders, a 4.3 rom, a 4.3 kernel and a 4.3 modem. I will post links to Threads where I retreived mine at and possibly a mirror download link with appropriate permissions.

AT&T info and link to roms, bootloader, kernel and modem I used to recover. Click below.

I got everything I flashed from here

Lately I have been running Looserskaters S3Rx, it is very stable and very functional Here is a link to it, I highly recommend it http://forum.xda-developers.com/showthread.php?t=2252932 I am not going to intentionally brick my phone again to test if you can flash this directly from a hardbrick so if anyone is successful or unsuccessful please let me know so I can update this thread.

Use this bootloader for the AT&T i747 ONLY https://www.dropbox.com/s/vbyeorrxapwrots/d2att_I747UCUEMJB_bootloader.zip the one in the tread where I got mine hasn't been working so use this bootloader it is the same one just hosted by a different person.

DO not use these files if you are not on AT&T you will simply be wasting your time by bricking your phone again. AND requiring a Jtag.

For the kernel I flashed the one in the middle d2att_Kernel_Stock_init.d_4.3_MJB_v1.0.zip which belongs to upndwn4par. I used loserskater's rom, bootloader and modem everything I used was linked in that thread. With proper permissions I would like to mirror those links as I know they work well.

This will have you rooted from jump Street. You might have to download supersu from the play store. I didn't have to. But YMMV.

Firmware downloadsFOR SGH-I747M USERS ONLY make sure you download the correct file. These are the TAR files that the I747M users can flash via the PDA button in ODIN
By clicking the button below to reveal links you acknowledge you are going to download the correct file.

WWW.Sammobile.COM (when I was still able to this was the site I downloaded my firmwares from)

If You Need Instructions For Download Mode, Recovery Mode or How to Flash TWRP Click Below

If You Need To Install TWRP Click Below For Instructions

If you don't already have a custom recovery installed on the phone.
* You will need to write your debrick file to your 16GB SD card and insert it into the phone,
* Perform a battery pull
*Reinsert the battery
*Access download mode
*Flash the TWRP file with ODIN
***Click Below For Instructions***

*First to access download mode (you should already have your Debrick SD card in your phone.)
*hold vol down, the home button and the power button for 4 seconds.
*The phone should vibrate.
*Release the power button followed by the remaining two.
*You may or may not have to have the USB cable plugged into your computer to do this? If it wont work with the cable plugged in unplug it and vise versa.
*When the warning screen pops up you need to press the correct button to continue.

***Follow the remaining Instructions EXACTLY***
*Now (if you havent done so yet) open ODIN on your pc (Kies MUST BE CLOSED)
*Click the PDA button, (In ODIN 3.09 it says AP)
*Navigate to where you downloaded the TWRP file,
*Select that file, Double Click To Select
### MAKE SURE that you do NOT have anything besides auto reboot checked ###
*** Once you are sure you have followed the direction ***EXACTLY*** click below to reveal the rest

Now That you are 100% Certain you have nothing more than auto reboot checked,
go to the bottom and click start.
it should write some files and say PASS and all threads finished (1 succeeded/ 0 failed).

you now have TWRP installed you can follow the rest of the guide.

If You Need Instructions To Access Download Mode Click Below.

*First to access download mode (you should already have your Debrick SD card in your phone and your battery removed.)
*Reinsert the battery
*Hold vol down, the home button and the power button for 4 seconds.
*The phone should vibrate.
*Release the power button followed by the remaining two.
*You may or may not have to have the USB cable plugged into your computer to do this? If it wont work with the cable plugged in unplug it and vise versa.
*When the warning screen pops up you need to press the correct button to continue.

If You Need Instructions To Access Recovery Mode Click Below

*First to access recovery mode (you should already have your Debrick SD card in your phone and the battery out.)
*Reinsert the battery
*Hold vol up, the home button and the power button for 4 seconds.
*The phone should vibrate.
*Release the power button followed by the remaining two.
*You may or may not have to have the USB cable plugged into your computer to do this? If it wont work with the cable plugged in unplug it and vise versa.

Your phone won't boot without the debrick SD card? Click below.

If you are on AT&T
When I first got mine booting again it would only boot with the micro SD card that has the .IMG file on it in the phone and only after a battery pull. What I did was boot back to recovery, remove my SD card and I had a spare SD card I used to flash the files with, I inserted it told TWRP to mount the new SD card, flashed the bootloader again and it seems to have cured my phones malfunctions. It now boots on its own like nothing ever happened. It may not happen like this for you???]

For the SGH-I747M
You have Two choices either flash the bootloader only via the 2 sd card method outlined for AT&T which requires flashing Custom recovery and VOIDING YOUR WARRANTYor you can reflash with odin and possibly try a factory reset in the samsung stock 3e recovery.

If your phone is booting now don't play with the bootloaders any more.

Make a nandroid backup of your phone if you are going to follow the instructions below.

You assume all risk associated with such...

Do you want to be able to use wifi, bluetooth or USB tethering? Click below. But read everything carefully before you do anything.

I contacted enewman17 and inquired about the link below \/ \/ \/ he advised me that it should be flashable via custom recovery to any AT&T I747 on 4.3 regardless of rom or kernel and possibly without root. He also said he thinks it may work on the I747M also.

If any I747M users flash it and are successful or unsuccessful please let me know so I can post whether this is effective for that as well.

http://forum.xda-developers.com/showpost.php?p=46804681&postcount=5 I flashed enewman17's tether hack with bluetooth enabled from there ^^^which allows wifi tethering through the roms native tethering app without the carrier getting their hands in your pocket.

Do you need instructions to install the above file? Click below

To install this you need to
*download this file^^^
*move it to your SD card
*put the SD card by k into the phone
*turn the phone off
*boot into recovery
*select install
*navigate to the location of the file ^^^
*select the correct file
*write the file to the phone
*clear the cache and wipe the dalvik
*reboot and enjoy, make sure you thank enewman17 for his fantastic work.

It works flawlessly for me buy your results may vary?

DO you want to get your 16GB micro SD card back to a use able state so you can store data on it again? Click below for details.

If you want to restore your sd card to a useable state after you get everything running again I used http://www.partitionwizard.com/free-partition-manager.html, After you install it and open it Insert your SD card into your computer and select the drive letter assigned to your SD card tell the partition wizard to delete all partitions then in the top left corner click apply. You now have a completly blank unformatted SD card. Now Insert it into your phone the phone will give you a notification that the sd card is unformatted and give you an option to format it. you now have a blank formatted SD card you can use again.

More to come in the near future.

Sent from my SAMSUNG-SGH-I747 using xda app-developers app

 

[iMackshun]

Amazing! Thanks you!

This worked perfectly! I almost lost hope, but this has restored my faith in Android. So, does this mean that this is the end of Custom Roms that run versions <Android 4.3? That would be a shame...Is it the Android 4.3 update that caused all of this, or just Samsung's update?(Google or Samsung) I really loved custom roms of 4.1.2 and there were some things that I was able to do there that were ruined because of the update. It wasn't quite nice for Samsung to do this to those great devs.

 

[BaSingSe]

Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.

Sent from my SAMSUNG-SGH-I747 using xda app-developers app

This is interesting. If the other poster is correct, the phone's CPU will try to boot like the computer CPU, from boot device #1, to #2, #3, etc. In this case, the internal ROM is #1 device and the SD would be #2 root device.

If this is the case, then why do we need the SD card to hold the same bootloader? If the phone is totally hard-bricked, then it should just by-pass the internal ROM completely and boot through the SD directly. Then the phone should be able to boot from 4.1.2 or any older ROM.

So if the SD card has to have the same bootloader as the internal ROM, it means the phone still boots off the ROM bootloader, then continue to boot off the SD card since the internal ROM does not have the valid ROM to continue.

In my case, I have a really hard-bricked phone. I do not even know the original ROM version. I do not think its bootloader is locked. But the previous owner flashed with a wrong ROM from a different phone.

So I'd like to know from the folks who successfully fixed the hard-bricked phones with this method: Do you have to use the debrick.img from the existing bootloader, or you can use any generic debrick.img?

 

[theramsey3]

This is interesting. If the other poster is correct, the phone's CPU will try to boot like the computer CPU, from boot device #1, to #2, #3, etc. In this case, the internal ROM is #1 device and the SD would be #2 root device.

If this is the case, then why do we need the SD card to hold the same bootloader? If the phone is totally hard-bricked, then it should just by-pass the internal ROM completely and boot through the SD directly. Then the phone should be able to boot from 4.1.2 or any older ROM.

So if the SD card has to have the same bootloader as the internal ROM, it means the phone still boots off the ROM bootloader, then continue to boot off the SD card since the internal ROM does not have the valid ROM to continue.

In my case, I have a really hard-bricked phone. I do not even know the original ROM version. I do not think its bootloader is locked. But the previous owner flashed with a wrong ROM from a different phone.

So I'd like to know from the folks who successfully fixed the hard-bricked phones with this method: Do you have to use the debrick.img from the existing bootloader, or you can use any generic debrick.img?

To be quite honest I have no clue if that would work? I am pretty sure if you left your debrick sd card in the phone you could do it like that but then you loose the ability to have expandable storage. Or atleast have to keep your boot.img sd card with you all the time incase you need to reboot the phone.

 

[BaSingSe]

How this works is that: the phone can not boot from the internal bootloader/ROM. So it tries to boot off the SD card. The SD should not have to have the same 4.3 bootloader (technically). From the old/original thread (Sprint), even very old generic ROM should do it. But after you get to download mode, you'll have to flash the same 4.3 ROM (or whatever your last bootloader-locked ROM is). Or you get the same hard-bricked phone since the 4.3 bootloader can't be written over.

But again, I have a hard bricked phone someone flashed with a wrong S3 ROM, something like a GTI9300 ROM onto a Verison S3 phone. And I still can't get the phone to make any move, even after the following the exact instruction many times.

I really hope if someone DOES get this work with a really hard-bricked phone, provide some details, so we can understand this better.

A hard-bricked phone means, if you remove the battery and connect AC, the red light would turn on. Other than that, no boot, no sound, no vibrate, no download mode, no recovery. The phone would be totally dead, other than the red light.

To be quite honest I have no clue if that would work? I am pretty sure if you left your debrick sd card in the phone you could do it like that but then you loose the ability to have expandable storage. Or atleast have to keep your boot.img sd card with you all the time incase you need to reboot the phone.

 

[theramsey3]

How this works is that: the phone can not boot from the internal bootloader/ROM. So it tries to boot off the SD card. The SD should not have to have the same 4.3 bootloader (technically). From the old/original thread (Sprint), even very old generic ROM should do it. But after you get to download mode, you'll have to flash the same 4.3 ROM (or whatever your last bootloader-locked ROM is). Or you get the same hard-bricked phone since the 4.3 bootloader can't be written over.

But again, I have a hard bricked phone someone flashed with a wrong S3 ROM, something like a GTI9300 ROM onto a Verison S3 phone. And I still can't get the phone to make any move, even after the following the exact instruction many times.

I really hope if someone DOES get this work with a really hard-bricked phone, provide some details, so we can understand this better.

A hard-bricked phone means, if you remove the battery and connect AC, the red light would turn on. Other than that, no boot, no sound, no vibrate, no download mode, no recovery. The phone would be totally dead, other than the red light.

Mine was truley Hard Bricked The only response it would give is The red light with the charger plugged in and battery removed. also the QHUSB_DL message on the computer when connected. I recovered from it and created this How To Guide to try to help others.

Mine was recovered from the Debrick file that actually came off of my phone with the help of -Mr.X- to tell me the command lines to type to get the file extracted from my phone the day prior to me bricking my phone(which did not happen on purpose).

Never thought I would need it then 18 hours later I bricked my phone, and found out this is a Viable way to recover from it.

Perhaps your phone needs to be JTAG'ed?

 

[BaSingSe]

- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.

What did you mean by stating that? So your phone was running CM 10.2?

 

[theramsey3]

What did you mean by stating that? So your phone was running CM 10.2?

You're Qouting -Mr.X-'s post from a different thread. I didn't write that part of it. and explained such in the very begining of this thread.

Everything that is grayed out was written by him everything in white was written by me.

 

[FULLTIMEIT]

Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)

Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?

---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------

Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)

Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?

 

[theramsey3]

Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)

Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?

---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------

Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)

Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?

DO you mean these Debrick.img files that are in the first post?

Here is a debrick Dump from a I747M from the UEMK5 4.3 that works
Here is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)

Sent from my SAMSUNG-SGH-I747 using xda app-developers app

 

[FULLTIMEIT]

DO you mean these Debrick.img files that are in the first post?


Sent from my SAMSUNG-SGH-I747 using xda app-developers app

o man my bad lol tired pretty hard to look for the link too...thanks!

 

[dragonslayer73]

Followed instructions still can not get phone into download mode.
I only have a 64 GB SD card could that be the problem?

Also I get no red light and no vibe.
When phone is plugged in Linux sees it as qhsusb_dload

Sent from my GT-N8013 using Tapatalk 4

 

[theramsey3]

Followed instructions still can not get phone into download mode.
I only have a 64 GB SD card could that be the problem?

Also I get no red light and no vibe.
When phone is plugged in Linux sees it as qhsusb_dload

Sent from my GT-N8013 using Tapatalk 4

I could only get my phone to respond to button inputs to get into recovery if; I pulled the battery out with the USB cable unplugged, put the battery back in, plug the USB cable back in, then used the button combination. Otherwise it was a dead phone that did nothing.

Sent from my SAMSUNG-SGH-I747 using xda app-developers app

 

[FULLTIMEIT]

Hi Op, tried to 4.3 file, didnt work for me , I can have red light on when plug in PC with no battery. using a 32 GB class 10 card , wrote the image a few times stil not getting the download mode...also tried to pull battery before combo thing...

Wanna try the 4.1.2 img..but the link is broken?

 

[dragonslayer73]

I could only get my phone to respond to button inputs to get into recovery if I pulled the battery out with the USB cable unplugged put the battery back in then used the button combination. Otherwise it was a dead phone that did nothing.

Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Tried button combos still nothing plugged into PC and not plugged in

Sent from my GT-N8013 using Tapatalk 4

 

[theramsey3]

Read some of this thread which is where -Mr.X- gave credit to in his post. The op of that thread says you may have to try writing the file to the SD card several times and try booting to recovery or download mode several times to be successful.

There is also a post near the end of it that says the SD card must be exactly 16GB. Is that a fact? I don't know? The one I used was and the process worked for me.

If you guys are on AT&T make sure you are using the correct files.

If you guys have the Canadian I747M make sure you use the right file.

That link is messed up its not mine I will contact the rightful owner of it and request that he fix it if possible.

I did not create any part of this process I simply used some information that helped me Unbrick my phone with permission to write a how to guide. Perhaps the size of your SD cards are making a difference here??? I did observe when I was repartitioning my SD card to be able to use it for storage again that when you write the .IMG file to it, it creates several partitions on the SD card to look just like the internal storage of the phone. So if you're using a larger card than the phones internal storage perhaps that is conflicting with the process?

I was using my daily driver 16GB card that I normally keep in my phone for storage.

I am no developer just a concerned SGH-I747 owner. I became really concerned after I bricked my phone the night before last night at about 11pm I finally got it to boot again at about 8am.

This method has been proven to work on many different variants of the galaxy s3. Sprint, T mobile, the Canadian I747M, my phone (AT&T I747) and maybe others as well?

I personally debricked my phone with this method. The author of the post I quoted in the op who wrote all the files says he debricked an I747M with this method.

As with all things though perhaps it doesn't work in all situations?

Sent from my SAMSUNG-SGH-I747 using xda app-developers app

 

[dragonslayer73]

I have the i747 not i747m what debrick image should I use?

Sent from my GT-N8013 using Tapatalk 4

 

[ttreakle1]

Unbricked and now hard bricked again

I used the debrick-SGH-I747U-CUEMJB3.img on my hard bricked (no signs of life except for red charging light when plugged into charger) At&T i747 that had the ota 4.3 update and was able to get into download mode ! from there I flashed TWRP through Odin and from there I flashed the I747UCUEMJ2 rom and it booted right up and was happy ! but then I went back into TWRP and decided to flash boot_CWM_I747MVLUEMK5 and when it was done flashing it said succeeded so I hit reboot then after that my phone was dead again and the sdcard debrick imgae no longer works..........any ideas?

 

[theramsey3]

I have the i747 not i747m what debrick image should I use?

Sent from my GT-N8013 using Tapatalk 4

This is the one you should be using for an AT&T phone

Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.

Sent from my SAMSUNG-SGH-I747 using xda app-developers app