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

Did This Work For You?

  • Yes (I used a 16GB micro SD card)

    Votes: 100 45.5%

  • No (I used a 16GB micro SD card)

    Votes: 49 22.3%

  • Yes (I used a 32GB or 64GB micro SD card)

    Votes: 50 22.7%

  • No (I used a 32GB or 64GB micro SD card)

    Votes: 21 9.5%
  • Total voters
    220
Search This thread
By:
Advanced…
audit13

audit13

Recognized Contributor
Jun 4, 2012
12,914
5,046
Toronto
Try Odin 3.07 which is what I always use.

When connecting to your computer, any unknown or new devices appear in the device list?

Do you have a screen shot of the download screen on your phone?
 
  • Like
Reactions: mrrocketdog
T

tatungyo

Member
Oct 17, 2014
8
1
audit13 said:
Try Odin 3.07 which is what I always use.

When connecting to your computer, any unknown or new devices appear in the device list?

Do you have a screen shot of the download screen on your phone?
Click to expand...

Yes, my computer does detect the phone now. I tried flashing the stock rom with odin v3.07 and it gives an error saying there is no PIT partiton. (succeed 0/failed 1) Here is a screenshot of the phone, sorry for the terrible quality its from my old iphone 3gs:
2lszolt.jpg
 
mrrocketdog

mrrocketdog

Senior Member
Oct 27, 2013
4,527
2,008
tatungyo said:
Yes, my computer does detect the phone now. I tried flashing the stock rom with odin v3.07 and it gives an error saying there is no PIT partiton. (succeed 0/failed 1) Here is a screenshot of the phone, sorry for the terrible quality its from my old iphone 3gs:
2lszolt.jpg
Click to expand...

dont know if this will help , but...
http://forum.xda-developers.com/showthread.php?t=1848264.

"all i can really do , is stay out of my own way and let the will of heaven be done"
 
samxander

samxander

Member
Aug 22, 2013
24
1
Tagaytay City
help!

im getting this message in odin when trying to flash twrp


<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 /

when trying to flash full stock mjb firmware it says no pit partition even tho i have one..
im doing this because my phone wont boot up..always a message "unable to do normal boot"
cant access recovery.. only unuseful odin now..

---------- Post added at 12:20 PM ---------- Previous post was at 12:12 PM ----------
samxander said:
im getting this message in odin when trying to flash twrp


<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 /

when trying to flash full stock mjb firmware it says no pit partition even tho i have one..
im doing this because my phone wont boot up..always a message "unable to do normal boot" tho odin
says pass still cant access recovery.. only unuseful odin now..
Click to expand...
im on sgh-i747 pre 4.3
 
Last edited:
samxander

samxander

Member
Aug 22, 2013
24
1
Tagaytay City
tried odin 3.10.5.. it says

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) :crying:
 
H

hellosomesh

New member
Nov 25, 2014
1
0
Need NAND BACK up of SGH-I747 with 4.4.2 bootloader

Hi....

I have a bricked SGH-I747. I used SD card method of unbricking it. After several attempts I could boot the phone into download mode using the 4.4.2 bootloader. However, I do not have a 4.4.2 stock firmware to flash using odin. I tried to repartition using D2_USA_ATT_16G.pit. But odin fails to partition EMMC.. My intention was to flash a custom recovery if partitioning is successful and then flash a 4.4.2 custom rom..

I believe that a I747 CPU detects for EMMC first for booting and if it is not present it tries to boot from SD card. And it did successfully in my case. The SD card contains only bootloader infrormation.

I would like to flash entire NAND backup of a working i747 with 4.4.2 ROM on to SD card and try to boot. A back up i747 of stock 4.4.2 is preferable. I request any one with a I747 working on 4.4.2 version to take a NAND backup and share it with me.
 
E

eatkabab

Senior Member
Jan 4, 2007
366
16
I still have a problem but I love you, thank you, you saved my hard brick. Used 16gb C10, U1 SanDisk microSD card. ATT S3 i747 previously broke when flashing 'stock 4.4' through Odin.

Still have a problem though. Was previously on 4.4.2 and I found this cache of 4.4.2 bootloader, modem, ROM: https://www.androidfilehost.com/?w=files&flid=15759

I was able to load up the bootloader and that allowed me to then boot into at least recovery without the debrick card. The modem also loaded up okay but I cannot get the ROM to load. I had to use a custom 4.4.x kernal since that link didn't have an explicitly separate kernal (I expect it's built into the ROM file) I've tried this stock one as well as CM11. Any ideas?

Error message: "error executing updater binary in zip..."

I would like to try to Odin back to 4.3 but I read all this stuff about how once you go to 4.4 you cannot go back...maybe would want to try to load up all the separate files but the only files in the OP are for the i747M and I feel like that will brick my i747 if I even try. I can't find a good stock 4.4 source to Odin...obviously the one source I had didn't work so I don't trust anything that's not XDA. All help HUGELY appreciated and again, THANK YOU!




PS
Also, you don't need two microSD cards, you just pop out the card once booted into recovery, format it to fat32, load up your files and plug it back in. You then go to mounts and uncheck and recheck the microSD. You can't uncheck the microSD before popping out the card however. It won't let you re-check/mount the card if you do.


UPDATE:
updated to TWRP 2.8.5 and now get the following error: assert failed: getprop...
 
Last edited:
D

dawgdoc

Senior Member
Nov 27, 2013
1,033
570
eatkabab said:
ATT S3 i747 previously broke when flashing 'stock 4.4' through Odin.

Still have a problem though. Was previously on 4.4.2 and I found this cache of 4.4.2 bootloader, modem, ROM: https://www.androidfilehost.com/?w=files&flid=15759

I was able to load up the bootloader and that allowed me to then boot into at least recovery without the debrick card. The modem also loaded up okay but I cannot get the ROM to load. I had to use a custom 4.4.x kernal since that link didn't have an explicitly separate kernal (I expect it's built into the ROM file) I've tried this stock one as well as CM11. Any ideas?

Error message: "error executing updater binary in zip..."

I would like to try to Odin back to 4.3 but I read all this stuff about how once you go to 4.4 you cannot go back...maybe would want to try to load up all the separate files but the only files in the OP are for the i747M and I feel like that will brick my i747 if I even try. I can't find a good stock 4.4 source to Odin...obviously the one source I had didn't work so I don't trust anything that's not XDA. All help HUGELY appreciated and again, THANK YOU!
-----
UPDATE:
updated to TWRP 2.8.5 and now get the following error: assert failed: getprop...
Click to expand...

Definintely do not try to Odin back to 4.3 if you installed any 4.4.x bootloader and modem.
Before doing anything else let's be absolutely certain of the bootloader and modem your phone is running on. (I was not certain what you used based on the link you provided. There are a number of debrick images, bootloaders, and stock ROM dumps on that page.) Since you have TWRP installed you can use the terminal emulator built into it. Run these commands for a definitive answer.
Code: 
getprop ro.bootloader
Code: 
getprop | grep version.baseband
Was the error message you received from attempting to install CM11, a 4.3 ROM, or some other ROM? Specifiy the ROM that gave the message, please. I would expect that message from trying to install a ROM that was built before the release of your installed bootloader.

BTW: AT&T did not release any complete 4.4 ROMs compatible with Odin. Most of the Stock 4.4.x ROMs in the forum are from XDA folks who captured the images from OTA prior to flashing and then built them as Recovery flashable zips. But, for the i747M there may be Odin flashable 4.4.x series Stock ROM. That could be the root of the issue.
 
  • Like
Reactions: eatkabab
E

eatkabab

Senior Member
Jan 4, 2007
366
16
dawgdoc said:
Definintely do not try to Odin back to 4.3 if you installed any 4.4.x bootloader and modem.
Before doing anything else let's be absolutely certain of the bootloader and modem your phone is running on. (I was not certain what you used based on the link you provided. There are a number of debrick images, bootloaders, and stock ROM dumps on that page.) Since you have TWRP installed you can use the terminal emulator built into it. Run these commands for a definitive answer.
Code: 
getprop ro.bootloader
Code: 
getprop | grep version.baseband
Was the error message you received from attempting to install CM11, a 4.3 ROM, or some other ROM? Specifiy the ROM that gave the message, please. I would expect that message from trying to install a ROM that was built before the release of your installed bootloader.

BTW: AT&T did not release any complete 4.4 ROMs compatible with Odin. Most of the Stock 4.4.x ROMs in the forum are from XDA folks who captured the images from OTA prior to flashing and then built them as Recovery flashable zips. But, for the i747M there may be Odin flashable 4.4.x series Stock ROM. That could be the root of the issue.
Click to expand...

First off, huge thank you for assistance with this old device.
I looked for the terminal emulator and I thought I clearly remembered that it was built into TWRP but it seems it doesn't exist. I can't get to any terminal. I can however tell you that this was the bootloader file that fixed the hard brick once flashed: d2att_I747UCUFNE4_bootloader_modem_4.4.2_7-29-14.zip

After that, per the OP instructions, I went ahead and also flashed this modem: I747UCUFNE4_ModemBaseband.zip

Given that I was previously on CM11/4.4.x, I attempted to flash I747UCUFNE4_Stock_Rooted_Odex.zip with no luck, then the latest CM11 nightly for the S3. I'm not planning on going back to 4.3 given all the warnings everywhere.

It might be useful to know that what I was previously on CM11 and was trying flash Lollipop/CM12 which is when I first ran into issues. I gave it 20min to boot and figured it wasn't going to boot so I went back to load the nandroid but it seems I had cleared one step too many and had no nandroid. So I simply googled for a stock Odin flashable 4.4 ROM which is when I hard bricked it...likely because it was an i747M ROM as you specified and I came to the same conclusion. This is my back up phone and I was going to use it but I wanted Lollipop since my newer phone has it. When I last updated the S3 to CM12 successfully I told myself I'd never flash it again because it works 100% and it's just a back up. But I couldn't resist :(

At this point, it loads up into TWRP and Download mode fine.

This is the error when attempting to flash CM11 or I747UCUFNE4_Stock_Rooted_Odex.zip: E: Error executing updater binary in zip...
I haven't tried other ROM's but I consider CM ROM's pretty standard and I've never had an issue with them so unlikely another custom ROM would work over CM.


UPDATE:
Figured out how to get to the terminal...
getprop ro.bootloader gives me: I747UCUFNE4
getprop | grep version.baseband yields: no response from the phone. Just shows what I typed...


UPDATE 2:
So I believe this may be a similar 'you can flash up but can't flash back' kinda things. Given that the bootloader and modem I currently have on there is compatible with the Lollipop ROM's, I attempted to flash the latest CM12 from here: http://forum.xda-developers.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854

It successfully flashed so I went ahead and flashed the appropriate Gapps and recommended SU update, wiping cache and delvik between zip files. All went through fine. I've been waiting about 5min now for it to boot...all I see is the CM man with the evil eyes and "Samsung Galaxy SIII" above him.


UPDATE3:
Waited about 12min, nothing happened, held power till turned off, ejected microSD, booted into TWRP, wiped cache and delvik again, factory reset, reboot and WOW! It worked! "Android is updating... installing app XX of 105"

PS:
The link to the GAPPS is broken on the more up to date 5.0.2 page by matrixzone. I used the GAPPS file found on an older CM12 thread here: http://forum.xda-developers.com/galaxy-s3-att/orig-development/rom-cm12-d2att-alpha-builds-t2959561
Seems to have worked.
 
Last edited:
D

dawgdoc

Senior Member
Nov 27, 2013
1,033
570
@eatkabab

You put a lot of work into that. I am glad to see you have it working.

If you have any reception issues you may need to reflash the modem. The only reason I mention this is because you didn't get a return from that second command.
 
  • Like
Reactions: eatkabab
E

eatkabab

Senior Member
Jan 4, 2007
366
16
dawgdoc said:
@eatkabab

You put a lot of work into that. I am glad to see you have it working.

If you have any reception issues you may need to reflash the modem. The only reason I mention this is because you didn't get a return from that second command.
Click to expand...

Reception is spot on. This ~3yr old phone performs as well as my 10mo old OnePlus. In fact, the touch screen is way more responsive and accurate too! I'm switching back to the S3 to send the OnePlus back to the factory so they can shove it.

I usually work pretty quickly when I run into a problem. These days I have plenty else to do so it's like 20min here 15min there. It was all the OP that made this possible however. That and my rather extensive history of reading XDA and following instructions very closely that allowed me to adapt the OP instructions to my unique situation with Lollipop. Now I know, don't update anything that you don't have the stock stock super stock Odin flashable ROM for. I consider myself extremely lucky that the 4.4 bootloader and modem just happen to be compatible with 5.0. Otherwise I'd be completely lost as I've never downgraded back a version of Android...well I have on the OnePlus but it was just between CM11 and CM12 which I assume all code is far more updated to be able to handle a slightly broader range of compatibility. Not to mention it's all so new and there are only two versions that run on the OnePlus.

All that being said, I still don't understand why you cannot downgrade. As stated and evidenced, the bootloarder, modem, even kernel (which is usually built into the ROM anyways) is compatible with both 4.4 and 5.0. What about the higher ROM breaks things such that it no longer allows one step back to work? Is there any real way to reverse it? For future knowledge...so I'm more careful about what I'm doing.

The past year or two I've flashed so many friends and friends of friends phones willy nilly that I began to feel invincible. Of course I would stay well within what's available for all those and only push my own phones far ahead, but still. This is the first ever hard brick I've ran into and I'm so so so thankful for XDA and everyone here.
 
Last edited:
D

dawgdoc

Senior Member
Nov 27, 2013
1,033
570
eatkabab said:
All that being said, I still don't understand why you cannot downgrade. As stated and evidenced, the bootloarder, modem, even kernel (which is usually built into the ROM anyways) is compatible with both 4.4 and 5.0. What about the higher ROM breaks things such that it no longer allows one step back to work? Is there any real way to reverse it? For future knowledge...so I'm more careful about what I'm doing.
Click to expand...

I'm not sure what happened to you originally. Not being able to downgrade bootloaders started with the MJB (Android 4.3) release. I believe not being able to have a modem version different from the bootloader version started with the NE4 release, but it could have been the MJB release. Funny thing is that you can downgrade the MJ2 bootloader, it is the leaked Android 4.3 bootloader. I am actually running the MJ2 bootloader and MJB modem. I have been doing so successfully for many months.

Generally the NE4 and NJ1, the most recent bootloaders released for the i747 by AT&T, should be safe with all of the current Lollipop ROMs. I guess it is feasible that an updater-script of a ROM would only allow the NJ1 bootloader, I just haven't read of one yet. For now there should be no issues downgrading from Lollipop to KitKat if you do not try to change bootloaders and modems. The caveat is that it may require wiping /system and very possibly the internal sdcard due to changes in the partition layout. I have read of several having troubles until they did so.
 
E

eatkabab

Senior Member
Jan 4, 2007
366
16
dawgdoc said:
Generally the NE4 and NJ1, the most recent bootloaders released for the i747 by AT&T, should be safe with all of the current Lollipop ROMs. I guess it is feasible that an updater-script of a ROM would only allow the NJ1 bootloader, I just haven't read of one yet. For now there should be no issues downgrading from Lollipop to KitKat if you do not try to change bootloaders and modems. The caveat is that it may require wiping /system and very possibly the internal sdcard due to changes in the partition layout. I have read of several having troubles until they did so.
Click to expand...

Interesting. I assume this information pertains to the S3 only, with every other device having their own oddities. I didn't try, but would you think a different custom recovery might have allowed me to install the 4.4 ROM? If I tried to do it right now, it most likely wouldn't work. I sort of want to kick back to 4.4 since it had a fully functional camera and YouTube however it is nice to have Lollipop.

Every time I run into problems, one of the biggest issues is actually finding the files I need. I can understand the ROM's, bootloaders and other phone related things, but I'm just baffled by the lack of flashable recovery files. Every custom recovery out there should have links for an Odin flashable, zip flashable, img and app installable available for every device. Additionally, it would be nice if CM started putting out Odin flashable ROM's as well. Just to give us an alternate to stock factory crap that is usually broken by ATT anyways.
 
D

dawgdoc

Senior Member
Nov 27, 2013
1,033
570
eatkabab said:
Interesting. I assume this information pertains to the S3 only, with every other device having their own oddities. I didn't try, but would you think a different custom recovery might have allowed me to install the 4.4 ROM? If I tried to do it right now, it most likely wouldn't work. I sort of want to kick back to 4.4 since it had a fully functional camera and YouTube however it is nice to have Lollipop.

Every time I run into problems, one of the biggest issues is actually finding the files I need. I can understand the ROM's, bootloaders and other phone related things, but I'm just baffled by the lack of flashable recovery files. Every custom recovery out there should have links for an Odin flashable, zip flashable, img and app installable available for every device. Additionally, it would be nice if CM started putting out Odin flashable ROM's as well. Just to give us an alternate to stock factory crap that is usually broken by ATT anyways.
Click to expand...

It probably is only the SGS3, but then I only tend to read about a few devices: the SGS3, Samsung GalaxyS (Captivate), and some low volume Intel tablets (mine is an Acer A1-830).

I would have thought TWRP 2.8.5.x would have worked fine. Or was it that you had to upgrade to it before you resolved your problems? The other recovery that I see people using successfully is Philz_Touch It has files in three formats: .zip, .tar.md5, and .zip.md5.
 
E

eatkabab

Senior Member
Jan 4, 2007
366
16
I forgot about the stupid batt drain issue of this phone. First time I've returned to it after a year. Any specific issue found that solves the ~10% batt drain/hr on standby? If I remember correctly, it used to be that some flashes worked alright some didn't and nobody had really isolated any particular reason for it.
 
S

spac3c4t512

Member
Aug 16, 2014
13
1
Smithville
Hey guys, I'm curious about the possibilities of downgrading from 4.3. I get the impression that under some circumstances it may actually be possible. If so I'm hoping that I fall into the lucky SOB category. I received an S3 i747 that was still on stock 4.1.1 LK3. Unfortunately I got some files mixed up and flashed a ROM for the international S3 and the only method that finally got it running again was this one. I do have a backup from before the brick when I was running the 4.4.4 Pac Man ROM, but still on the LK3 bootloader. Can I downgrade from the MJB 4.3 using that backup or will I just end up with another brick? Thanks for any help that anyone can offer.
 
D

dawgdoc

Senior Member
Nov 27, 2013
1,033
570
spac3c4t512 said:
Hey guys, I'm curious about the possibilities of downgrading from 4.3. I get the impression that under some circumstances it may actually be possible. If so I'm hoping that I fall into the lucky SOB category. I received an S3 i747 that was still on stock 4.1.1 LK3. Unfortunately I got some files mixed up and flashed a ROM for the international S3 and the only method that finally got it running again was this one. I do have a backup from before the brick when I was running the 4.4.4 Pac Man ROM, but still on the LK3 bootloader. Can I downgrade from the MJB 4.3 using that backup or will I just end up with another brick? Thanks for any help that anyone can offer.
Click to expand...

If you are saying that you are now on the MJB 4.3 bootloader, then you should not try to downgrade it. That is what I continually read.
 
S

spac3c4t512

Member
Aug 16, 2014
13
1
Smithville
audit13 said:
Did the international ROM you flashed include a bootloader?

When you talk about an mjb backup, are you referring to a nandroid backup?
Click to expand...

I dont know if it included a bootloader but i think this was the one I flashed. SmartROM+v0.8.1+Repack.

And I'm currently on the mjb bootloader. The backup I have is a twrp backup from before i flashed this rom. At the time i made the backup I was on the lk3 bootloader. Also, I'm fairly certain i have another nandroid backup on my other external hdd if that does me any good at all.
 
You must log in or register to reply here.

Similar threads

amzi
i747 and i747m?
Replies
1
Views
1K
Dankest
Dankest
niceppl
does anyone have a jtag dump of i747 or i747m?
Replies
2
Views
594
AxAtAx
AxAtAx
F
[Q] AT&T i747 android 4.3 [How to root?]
Replies
9
Views
3K
F
Farahjr
T
How to Manual unlock AT&T S3 I747 4.4.2?
Replies
3
Views
4K
audit13
audit13
rileyfallan
[Q] Unroot 4.3 after ota update sgh-i747
Replies
17
Views
2K
rileyfallan
rileyfallan

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 39
    theramsey3
    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.

    -Mr. X- said:
    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.
    Click to expand...
    View
    29
    theramsey3
    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.


    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
    View
    4
    DocHoliday77
    DocHoliday77
    Tips for Debricking!

    Hey guys. I have posted much of this in enewman's thread, but thought it would be best to have it here. I have been helping members to debrick their devices in the T-Mobile S3 forums ever since the method was discovered. There are a few tips I have which may or may not have been mentioned before, and may or may not make a difference here. I believe everything should apply though because our devices are very similar to each other.

    The first, and most important thing IMO, is DON'T GIVE UP! At least not right away! We have seen many people who were unable to restore their device the first time they tried. Quite a few had to run through the instructions of partitioning the sdcard several times before it finally worked. No clue as to why this happens, I just know it does happen. (I actually know from experience on that!)

    We also recommend using a 16GB or 32 GB, Class 6 or better sdcard. (I personally do not recommend using some cheapo generic. Its up to you if you want or need to try with one, but they often do not actually have the advertised available storage.) (I personally always use Samsung brand sdcards from Authorized Dealers....not just for the debrick process, but for my everyday use I feel they are hard to beat.) Any name brand should be sufficient though. Just beware of all the fakes out there!
    I know I've seen it mentioned that the 32GB card will not work for you guys. But it has for T999 users before. Still the 16GB is the better choice here. (I have also theorized that if you have a 32GB model, it might actually be best to try with a 32GB card if available.) In the end though, as long as it is at least 16GB, try what you have before spending money on something else. You never know, you might actually get lucky! Some manufacturers, for example, have Class 4 cards that will actually reach Class 6 r/w speeds.

    I also suggest taking a look at the T-Mobile thread, stickied in Development. Some of the information there could be of use as well.
    [HOWTO] UnBrick T-Mobile S III QHSUSB_DLOAD w/Video Walkthrough In particular, we recommend using a different method for partitioning your sdcard. We have found many have had little success using the Windows method. Instead, people seem to have a much higher success rate when using the Linux LiveCD or VM method. (I will post the instructions for both below). There are also links to video tutorials for those who prefer to watch it being done before trying it themselves.

    For the KK bricks that have happened in the last 24 hours, I would be very surprised if this is unable to fix these devices. Especially for those who bricked by flashing the 4.4.2 modem while on 4.3 firmware. These debrick.img's include the first chunk of data from the main partition, mmcblk0. The modem is on the first partition of this, mmcblk0p1, so when you use the debrick.img, it should boot up using the modem included in that img. So if you are still on 4.3 firmware but bricked by flashing the modem, you should be able to use either the 4.3 or 4.4.2 debrick.img. Your choice. Id recommend using the 4.3 version for now, at least until we verify this is working for 4.4.2. It also means that if 4.3 does not seem to be working for you, you have a second choice to fall back on and try again. (More a psychological thing IMO, but anything that keeps you motivated to keep at it is a good thing! Having a second option can help people to feel like there is still hope if the first is not working!)
    If you do end up using a 4.4.2 debrick.img, just remember you will ONLY be able to flash 4.4.2 firmware to fix the device. Just like if you were flashing normally with Odin, it will see you are booted up using 4.4.2 firmware, and it will fail the SW Rev. Check if you try to flash anything older.

    So anyway, sorry for such a long post guys! Just trying to cover all the bases. I know some has probably already been discussed, but it doesn't hurt to revisit it if it has.

    The following instructions will tell you how to partition your sdcard with the debrick.img using the Linux LiveCD! I just double checked and saw that this is mentioned in the OP but I missed it before. Still, incase it helps anyone I will post what we have for our instructions from T-Mobile.

    What you need:
    • Bricked SGH-I747/I747M
    • 16GB or 32GB microSD card (all data will be erased from this sdcard)
    • microSD card reader
    • Linux Live Disc
    • A debrick.img for your device and firmware (I can host and try to help organize all of these for each model/carrier if you guys like)
    • The correct build of stock firmware for your device. (Best to match the firmware build with that of the debrick.img)

    • Boot your Linux OS
    • Download the debrick image (Make absolutely sure you get the correct one!!! If you are not certain, ASK!)
    • Open terminal on your Linux OS
    • Insert your microSD card into the reader
    • Plug your microSD card reader into your computer
    • Enter the following in the Terminal

      Code: 
      dmesg | tail

      You should see something that mentions where it is mounted via /sdX (X = variable. Mine always said sdb.)

      Code: 
      dd if=/path_to_debrick.img of=/dev/sdX

      Don't forget, X is variable representing the microSD card ignoring the partition numbers as they should be overwritten.
      I had to do this a couple times for the image to actually take

    • To check if the sdcard was partitioned correctly, enter this:

      Code: 
      parted /dev/sdX print

      If you see an Error about the GPT table being corrupt you can type "OK" and then you will be given an option to Fix/Ignore; type "Ignore".
      It should show approximately 23 partitions (IIRC)

    Now that you have created your debrick sdcard, here is how you use it!

    • remove the microSD card from the reader
    • remove the battery, sim and external microSD card from your device
    • insert your debrick microSD into your phone
    • insert the battery and down your power button (at this point your phone might actually boot completely and you can recovery any software/data you want)

      If you have Odin flashable firmware for your device, next do this. Otherwise, follow the instructions in your OP for using a second sdcard.
    • reboot into Download mode either via adb or Volume Down + Home + Power
    • Once the device is booted into bootloader remove the microSD card.
    • Flash your firmware via Odin like usual, and make sure you UNCHECK partition! (Should be unchecked by default already, but just in case....)

    Note: If you do not remove the sdcard after booting into Download Mode, the flash from Odin will fail!

    I do hope this helps some of you. I am going to try to create a stock NE4 firmware for use with Odin. If successful, you will not have to use the 2 sdcard method anymore! I hope....!

    If I have gotten anything wrong, or something does not quite fit for your devices here, please let me know! And I do hope no one minds me posting this. I now know the OP mentioned using Linux, but didn't see much info on it. That and I have heard lots of folks talking about using the Windows method, which we found to be unreliable, so I figured a more detailed guide on this method might prove useful.

    If I can do anything else to help, please feel free to ask! And GOOD LUCK!!!!!! :fingers-crossed:
    :cowboy:
    View
    3
    I
    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. :eek:
    View
    3
    DocHoliday77
    DocHoliday77
    OK, since we have had no confirmation of either the 80mb or 128mb debrick.img's working, I have made a few more scripts that will create new ones of different sizes.

    T999_Partial_Sys_Dump_for_debrick-256.zip
    This will create a 256mb image

    T999_Partial_Sys_Dump_for_debrick-512.zip
    This will create a 512mb image

    T999_Partial_Sys_Dump_for_debrick-1580.zip
    This will create a 1.58gb image


    Note: Before uploading for people to test them, zip them up and it will significantly reduce the file size you have to upload.

    Remember to make sure you have enough free space before running the scripts!

    We will do our best to figure this out guys! I know it sucks to have such a nice paperweight....
    View

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone