yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] srnoth:
This one was from the original 4.3 (MK4) which it shipped with. I am on NC1 now, will try to pull an unbrick.img of that one when I get a chance.

In my case, I had actually created an unbrick.img before I started messing with bootloaders, hoping that I'd be able to debrick if necessary. But when it didn't work, I read somewhere (can't remember if it was in this thread) that this method only works when you brick the phone with a previous bootloader from the same version. In my case I tried a bootloader from a different D2 variation, so JTAG was the only option.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
As of 4.3 you have to use a debrick image from the same build you are on. Meaning the MK4 img will not work if trying to restore a device that has been updated to NC1.

Im not sure either way about flashing another models bootloader, but it does make sense that this wouldn't work in that case.
[T-Mobile, Samsung Galaxy SIII] pedroisweird:
What does it mean if the phone starts to boot up but then immediately shuts back off after a second or two? I can't stay in download mode long enough to run Odin...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You probably have the common "sticky power button" issue. You can try fiddling with it, some have had some success, but inevitably you'll need to replace the button most likely.
[T-Mobile, Samsung Galaxy SIII] twolves14:
If I was on a 4.4 ROM and used ODIN to flash 4.1.2 (UVDMD5), resulting in a brick, do I use the debrick for 4.3+ or for before 4.3?

Also, can someone point me to the best ODIN guide to use? It seems like this thread: (http://xdaforums.com/showthread.php?t=2603334) is outdated and that PIT should not be checked, etc. From my understanding, I should be able to just flash "root66 T999-UVUENC2" to get to the latest stock, rooted firmware.

Thank you.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Just follow this guide. Unless uou get some sort of pit nit found error. Correct on using that root66 method.

As far as what image to use, if you had ever fully updated to 4.3 via ota or odin, you must use the 4.3 image. If flashing 4.1.2 bricked it you probably need to use the 4.3 image. If in doubt, just use that anyway, then flash the root66 NC2 firmware when you get into download mode.
[T-Mobile, Samsung Galaxy SIII] pedroisweird:
You were right!! OMG!! I had given up on this phone lol. Now I have a nice backup to my S4 :)
[T-Mobile, Samsung Galaxy SIII] kusakhan:
i try different SD card but not work ...SGH T999L debrick 4.3 image
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ive got a copy of another you can try. Just need to upload it first.
[T-Mobile, Samsung Galaxy SIII] kusakhan:
ok i wait....
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sorry, I had two other large uploads running so wanted to wait till at least one was done. Fell asleep! Ill get it up here in 10-15 min.

---------- Post added at 10:48 AM ---------- Previous post was at 10:09 AM ----------

Ok, here you go! Good Luck! I hope it works for you!

http://d-h.st/xc9
[T-Mobile, Samsung Galaxy SIII] kusakhan:
Not Work i try perviousily bricked i use class 10 show memory 31.2 gb and this card show 29.4....i install wrong modem file then bricked ....
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Hopefully at some point someone will maje another T999L image then. Not sure what to tell you till then. Ive asked numerous times for someone to step in and create a new one, but am always ignored... (except the guy who made this one. Sorry it didn't work)
[T-Mobile, Samsung Galaxy SIII] kusakhan:
hopefully anyone can update.....ok i waited...
[T-Mobile, Samsung Galaxy SIII] srnoth:
T999L

Hey guys. I finally got some time to work on this. At the advice of [MENTION=4081205]DocHoliday77[/MENTION] I decided to revert back to the previous 4.3 on T999L (MK4) using ODIN and create a debrick.img for that version. I am not sure if the bootloader changed between versions, but I know the modem did, so maybe this one will work for guys who bricked while on MK4, not NC1.

[MENTION=5462055]kusakhan[/MENTION] let me know if this one works.

https://drive.google.com/file/d/0BwGnS-RKXQLZUkpjaGFTNjhSaVU/edit?usp=sharing

( [MENTION=4081205]DocHoliday77[/MENTION] please feel free to host this one as well if you want :cool:)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You rock man! Thank you for continuing to try and help with this!

To determine your bootloader version, from terminal emulator enter this:

getprop ro.bootloader
[T-Mobile, Samsung Galaxy SIII] kusakhan:
I try this one

my bad luck not work......:crying: thanks for effort
[T-Mobile, Samsung Galaxy SIII] :
You're missing a debrick image for the T999N? (MetroPCS-T-Mobile) I think I can get a debrick image if my sister lets me grab her S3 for a few minutes this afternoon.

--It's for 4.3. with the latest baseband, whatever that might be.
[T-Mobile, Samsung Galaxy SIII] boys501:
hi i have a t999 motherboard dead can i replace it with the i9300 motherboard

in my contery there is only the i9300 motherboard
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I dont think it will fit quite right. I could be wrong, but im pretty sure I heard that somewhere. The motherboard is slightly different as I understand it.
[T-Mobile, Samsung Galaxy SIII] kusakhan:
sgh i747 board support sgh t999l
[T-Mobile, Samsung Galaxy SIII] rookiegenius:
hey guys, my phone has the exact symptom for this :(

My question is I have the original tmo S3 bought last summer. Recently I flashed to 4.4.2 kitkat. Can I use the debrick image posted? I'm quite confused. Thanks a lot.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Use the same or newer firmware as what you are currently running. Rom doesnt matter.
[T-Mobile, Samsung Galaxy SIII] rookiegenius:
This is what Im confused. So the image posted is either not 4.3 or 4.3 while I was running 4.4.2 before hard brick. Does it mean this is no use for me?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
There is no 4.4.2 firmware available for this device. So you only had a 4.4.2 rom which has no bearing on what image you need to use.
[T-Mobile, Samsung Galaxy SIII] bigpappapuff:
k guys i brough my phone back to life with this method now if some one can help my usb port is not working it only charges is their any way i can sync with odin from the mother board ((((help)))))
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Try different cables and usb ports. This often solves lots of issues. Otherwise you may need to replace the part.
[T-Mobile, Samsung Galaxy SIII] cloudi602:
I have a Window 7pc i try and it fail when i try to odin it back to stock.

Odin read it ok and everything but when flashing it failed. So i try it on my window 8 pc and it went throught and it work phone now revived.

My question is how come it didn't work on my window 7? I'm just curious

+rep for this method
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you had kies installed on the computer it often causes odin to fail.
[T-Mobile, Samsung Galaxy SIII] cloudi602:
thank you, that is probably why i have it installed
[T-Mobile, Samsung Galaxy SIII] kevin2005:
I just gave life from dead phone .. thank you. I used the windows method and worked like a champ.
[T-Mobile, Samsung Galaxy SIII] twolves14:
I'm getting a Pit Not Found Error. So I'm trying to repartition it, but I still get:

<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

Or am I getting this error because I'm in Boot Recovery Mode? I can't get into Download mode, unless it's the same thing. ADB won't pick up the phone.

Here is a picture of what I'm doing on ODIN. At first I tried only the PDA with re-partition unchecked. Then I tried just the partition file and re-partition checked (got the error message above). Now I'm trying this, but it fails after getting stuck at SetupConnection.

<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

And this is my phone's screen while I'm trying to flash:

http://i.imgur.com/pbxgE3t.jpg
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You cant use odin in recovery. Only in Download Mode. Thats probably why it cant get the pit. What happens when you try to boot to download mode?
[T-Mobile, Samsung Galaxy SIII] HermitDash:
I'm having the same issue.

I can't boot into download mode no matter what I try. Be it the 3 button combo or a JIG I have. All I can get to is Boot Recovery Mode then it'll goto Odin
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Just to be sure, you are using Volume Down + Home + Power to try and boot Download mode? And you can boot recovery, but it sounds like you have the stock recovery installed, correct? I'm guessing you cannot boot normally? Still have to ask to be sure. What firmware build are you on? How did the device get to this state? When you plug into the computer, what does it show is connected in Device Manger? Have you tried this debrick method? Or just the jig? A situation like this requires you give us a lot more information before we can offer any decent advice.
[T-Mobile, Samsung Galaxy SIII] HermitDash:
Yes, it doesn't boot into download mode at all. I even used a Jig while trying to power up and it doesn't go anywhere except the "Boot Recovery Mode" screen. Stock recovery is installed, that would be correct. In similarity to symptoms I basically have what twolves14 has in regards to flashing via Odin.

Cannot boot normally and was on Build 4.3 Stock. It got there because of an attempt to flash backwards to a older bootloader resulting in the hardbrick. When it's plugged into the computer it shows QHSUSB_DLOAD. I used this debrick method before because I have two phones and I've recovered my other phone without any problems. Tried to use the Jig to force download mode, didn't work; Tried to get into recovery using three button trick also didn't work. If you need any other information just ask away and I'll describe as much as I can.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Can you be a little more specific about the boot recovery mode? Ive seen this mentioned before, but in stock recovery, it says Android System Recovery at the top, and in Download Mode it says Odin Mode if I remember right. Is it one if these you are talking about? I just don't recall ever seeing "Boot Recovery Mode" anywhere. (Maybe I just never noticed?)

Just to be clear again, you are getting to this mode by using the debrick sdcard right? I have no idea if this would work (probably not), but maybe if someone created a 4.3 debrick.img using an insecure kernel and maybe a custom recovery it might allow you to use adb to manually write the correct partitions back to the device.

Before trying something like that though, have you attempted to redo the debrick method from the beginning a few times? Several people found it wouldnt work the first few attempts, but eventually would.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
From what it sounds like, if you are booting into recovery and using the debrick sdcard then the reason nothing is working is because the sd card is still in the phone.

What you need to do is either boot into recovery then reboot to download mode. Once in download mode remove the sd card then flash stock with odin
[T-Mobile, Samsung Galaxy SIII] HermitDash:
Here's what I mean by Boot Recovery mode:

With the Debrick card in there it will only boot to this screen. It will not boot to Download mode, nor will it boot to the stock recovery or custom recovery.

I know that this thread is for the T-Mobile Debrick but it works the same for the AT&T because I've done it.

Also Doc could you please explain the adb method further? I'm kinda doubting it will work because adb does not detect the device when plugged in as well.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Have you tried flashing your firmware via Odin while booted to that screen? (Dont forget to take the sdcard out before doing so). That is basically download mode, but with the extra info on the screen.

Adb won't work unless you have an insecure kernel, and since you're booting from the debrick.img, that would need to have been installed on the device it was created with. (Note that doing that will trip that warranty bit)
[T-Mobile, Samsung Galaxy SIII] :
Raw version unzipped: https://mega.co.nz/#!4xR2hCaL!f-jvViGSQEW3SXuLcvYeaYY2w7wIzUaztfwlCH_spt4

I found this laying around on my EXTSD. To think...I never got it uploaded. Anyways, I think it is for T999N (MetroPCS) 4.3..?

Zipped version: https://mega.co.nz/#!ExISHJjR!1bIhKuX1Xm7Uqt58j2IbP6m9h96I2avStQZVBlSRbkg
[T-Mobile, Samsung Galaxy SIII] imadsen:
Thanks for this thread! I have no idea why it's not stickied. I searched for hours to find the youtube video and I've been a member here for awhile. This thread saved my phone from complete loss.

I still can't boot the S3 to any mode without the SD card though, and I think it's because I upgraded to 4.3 on the T999L. I couldn't get the wifi to work on 4.3, so I went searching for a modem and eventually hard bricked my S3 because I put the wrong modem on the device. This unbrick method has enabled me to at least boot in recovery and download mode. I was able to odin back to 4.1.2 (T999LUVAMB7). I've attempted everything I can think of and everything I've read besides buying another phone to fix the bootloader. No luck yet.

Is there any chance someone could create a 4.3 T999L debrick image? Thanks for all the help! Even if I never fix this phone for good, maybe my experience can help someone else free up that SD card.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Actually, this thread is stickied! When you flashed the firmware with odin did you first take out the sd card? If not try again but remove the sd after booting download mode but before flashing.

It kinda depends on what bricked it too though. Exactly what modem did you flash?
[T-Mobile, Samsung Galaxy SIII] HermitDash:
Yes I've tried flashing a 4.3 Stock Firmware via odin.

ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

That's what I got from just plain flashing the PDA tar file.

And this is what I got afterwards adding a PIT file while ticking Re-Partition

<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

It's the same even if I untick Re-Partition (The MicroSD card was not in the phone while all this was happening)

Now what was it about the insecure kernal dump that I could make? Because I have a second phone that I could do a dump from that's the same i747

Thanks for the advice so far!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Basically, flash an insecure kernel to the device. Then create a debrick.img from there and use it in your dead s3. If it works you should be able to dump the data partition using the dd command.

Another thought i cant remember if it was mentioned already, can you flash cwm or twrp recovery while in Download Mode? If you can, maybe you could boot to that recovery after and try to restore from there. (You could also try making a debrick.img from a device that already has a custom recovery. No idea if that might work though.)
[T-Mobile, Samsung Galaxy SIII] HermitDash:
I would just use the script from the OP correct?

I can't flash CWM or TWRP while in Download mode it shows the same no PIT partition error. If I get a custom recovery to work this thing would liveeeee D;

Anyway my last hope is to just make that last debrick img. Then I give up xD
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yup, flashing the script will crate a new debrick.img you can try.

Good luck!
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
The pit partition missing I think you need to PM [MENTION=4081205]DocHoliday77[/MENTION] to see if he has a PIT for your device. I do not have any PIT layouts anywhere.

And just for future reference, you never want to tick Re-Partition unless told to do so (You end up without a PIT Partition)
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Thanks for this. I'll get it added to the OP sometime this week when I am at home.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
All our PIT files are in a thread in the General section. When using this, check repartition, select the pit file, and also select your firmware in the AP/PDA section of Odin.
[T-Mobile, Samsung Galaxy SIII] kusakhan:
how to solution of 4.3 brick SGH-T999L
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Someone else who has the T999L running stock 4.3 firmware will need to create and upload a debrick.img. All the ones we've tried didn't work for you, so until someone makes another for you to try, theres just no way to fix a T999L running 4.3.

---------- Post added at 09:07 AM ---------- Previous post was at 09:04 AM ----------

Here is the thread containing all our PIT files.

http://xdaforums.com/showthread.php?t=1848267

[MENTION=3505796]KAsp3rd[/MENTION]. Would you mind adding the link in your OP? I think it'll come in handy for some people using this process.

---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------

@kusakhan

Didn't you brick by flashing a modem from a different device? Can you post a link to the modem that bricked you?

I have a feeling that it bricked by writing that modem to a partition not covered by the debrick.img. if we know which partition was overwritten, maybe we could come up with an alternative.

I do think at this point you should really consider a jtag service though. There's no guarantee we will be able to fix it here, and youve been waiting for a solution an awful long time!
[T-Mobile, Samsung Galaxy SIII] srnoth:
Hey guys I forgot to mention that I couple days ago I got a private message indicating the debrick.img that I posted worked successfully for a T999L user.

I think it would be safe to add it to the OP now. Specifically [MENTION=5462055]kusakhan[/MENTION] I'm pretty sure you flashed a modem from a different device and messed it up that way. That's what happened to mine, and the debrick.img method did not work for me... only JTAG.:(
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
I'll get it added to the op tomorrow in the AM
[T-Mobile, Samsung Galaxy SIII] kusakhan:
actually i installed 4.3 firmware T999L and i downgrade to 4.1.2 with cwm zip file ....my phone are not show basebend version I write 4.1.2 T999 UVDMD5 Modem then my phone are bricked

---------- Post added at 09:46 AM ---------- Previous post was at 09:36 AM ----------

Kindly Sir tell how to proceed with pit file....
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
To use the PIT file, flash your firmware in odin like you normally would, but check repartition, and click the PIT button and select the PIT file for your device. PIT files are in a thread in General.
[T-Mobile, Samsung Galaxy SIII] kusakhan:
bricked phone flashed pit file
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Im sorry but I dont understand what you mean by this.....?
[T-Mobile, Samsung Galaxy SIII] kusakhan:
Actually i say My phone Are bricked show QHSUSB_DLOAD and Can i nstalled Pit file....
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you can get to download mode using this debrick method you can then flash using the PIT file. Otherwise, no, there is no other way that I know of.
[T-Mobile, Samsung Galaxy SIII] kusakhan:
http://xdaforums.com/showthread.php?t=2282603

i use this file and my phone are briked
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ok. This debrick method should work for you then. Which carrier is your T999V from?

Im going to be making a new script based on commands KAsp3rd has worked up. Im doing it to help folks in the AT&T forums, but it might help you as well.

Once its ready ill post it and you can try again when someone creates a new debrick.img using it.

It is possible though, that yours may not be fixable except by a jtag service.

You flashed a full firmware from a different device, so it may end up conflicting with the img on the sdcard. I dont know for certain, but its certainly a possibility.
[T-Mobile, Samsung Galaxy SIII] kusakhan:
I use T-Mobile SGH-T999L and i use this modem file on http://xdaforums.com/show....php?t=2282603

and my phone are briked

and i several img use mk4 nc1 but not hopefull....
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
We've got a new way to create the debrick.img files. Ill post it shortly. Maybe this new method will produce one that works for you. Lets hope...!
[T-Mobile, Samsung Galaxy SIII] microchip88:
Will the new method work for SM-G7102 galaxy grand 2..
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No Idea. I don't even know if this ever worked for it. If not, then no it won't.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
New Debrick Script

Hey guys!

This was primarily done in attempt at finding a way to fix AT&T bricks related to the 4.4.2 firmware. But I believe this is probably a better way of creating the debrick.img than our previous script that was flashed in custom recovery.

This is different in a couple of ways. First, it is not flashed in recovery. So we can use it to create debrick.img's that include the stock recovery. It also uses the S3's default block size. This probably wouldn't have any bearing on whether or not it works, but just covering all the bases we can think of! Finally, it uses gzip to automatically compress the image into a .gz archive. This saves space during creation, and makes uploading and downloading much easier. The 128MB debrick.img should be roughly 33.75MB with this method.

Note: Windows users, use 7zip or WinRAR to extract the debrick.img from the debrick.gz.

Instructions:

For the best chance of positive results, please only run this on a fully stock, rooted build.

Download

Create_Debrick_Img_128MB.zip

to your device.

Extract and copy the debrick folder to /data. The path MUST be /data/debrick.

Change permissions on the folder and its contents to rwxr-xr-x (chmod 0755 I think)

Run Create_Debrick_Image.sh (choose Execute if prompted)

Wait a couple of minutes for it to complete and you will find a 33.75MB debrick.gz file on the root of your internal sdcard.

Upload this to your preferred file sharing site and post the link for others to try.

Thats it!

When a debrick.img is confirmed to be working, [MENTION=3505796]KAsp3rd[/MENTION] or myself will host the file indefinitely, and link to it in the OP.

Now we just need to get some new debrick.img's from each model!

If you guys have not done so yet, make sure you thank KAsp3rd for all his outstanding work in this thread! While this new script was a collaborative effort, the majority of it was done by him!

Hopefully this method can help produce images that will work for those of you who have had problems previously! :fingers-crossed:

Good Luck!!!

Doc :cowboy:
[T-Mobile, Samsung Galaxy SIII] kusakhan:
Anyone can post new method debrick image for SGH-T999L 4.3 ......
[T-Mobile, Samsung Galaxy SIII] serio22:
Just quoting you here to continue the conversation in this thread..

Did you set the permissions exactly as doc started?
[T-Mobile, Samsung Galaxy SIII] :
Do I have to have a stock recovery or stock anything? I have my hands on a L w/4.3 baseband and would like to contribute.
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
Yes. I even re did everything and same result.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
I'll look over everything when I get a chance.
[T-Mobile, Samsung Galaxy SIII] serio22:
Did you try this app? https://play.google.com/store/apps/details?id=com.snclabs.scriptrunner
[T-Mobile, Samsung Galaxy SIII] :
I ls-ed into the dir and ran the command myself and it seems to have worked.

Will upload later..

Edit: its more than 33MB...