yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] justforgot:
Can't do anything? can't get to recovery mode or download mode.

Plug in device to laptop or wallcharge without battery led turns on and laptop recogonize the device as qualcomm hs-usb qdloader 9008 in device manager.

Tell me what i can do? i've tried almost all the .img for tmobile it doesn't work. My device is T999L s3. Help me out please as this is not my device.
[T-Mobile, Samsung Galaxy SIII] Tmobilefan906:
Sorry to say, but I think it's bricked. I had the same issue.
[T-Mobile, Samsung Galaxy SIII] sfelix7:
debrick files

The copy website is no longer available since May 1st 2016. please update ur links. thanks

I have a S3 T999L. I Flashed stock 4.3 using odin3 in download mode but same problem stuck on tmo 4g lte screen
[T-Mobile, Samsung Galaxy SIII] justforgot:
Did you ever get to fix your device or found out what you needed to do to fix your device? as this is not my device i need answers.

Appreciate all your help :)
[T-Mobile, Samsung Galaxy SIII] Tmobilefan906:
No I didn't I tried flashing firmware and recoveries to no avail
[T-Mobile, Samsung Galaxy SIII] justforgot:
I been just getting to a point where i'm only finding possible solutions is jig or jtag

Me have none of those two.
[T-Mobile, Samsung Galaxy SIII] Tmobilefan906:
Try the latter jig
[T-Mobile, Samsung Galaxy SIII] justforgot:
i ordered it. let's see if that works if not i give up on this phone. :(
[T-Mobile, Samsung Galaxy SIII] Tmobilefan906:
If u can get it into download with the jig, all is not lost.
[T-Mobile, Samsung Galaxy SIII] justforgot:
That's what i'm hoping somehow if i can get to download mode. i'm good but i think it might not work. but let's not lose all hopes.
[T-Mobile, Samsung Galaxy SIII] yahanna:
My Galaxy S3 can't charge anymore. Would this method fix it?
[T-Mobile, Samsung Galaxy SIII] karandeepgiddha:
The copy link for the image doesn't work, please can you send an updated link?

Thank You
[T-Mobile, Samsung Galaxy SIII] gaudence:
someone should have the debrick.img for s3 slim g3812b, i need very, am without phone to use. please. great work.
[T-Mobile, Samsung Galaxy SIII] rohailadnan:
Debrick image links not working
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
I have updated all of the links to direct to a backup that I had on dropbox that I did not know I had.
[T-Mobile, Samsung Galaxy SIII] smtariq:
I have samsung note 10.1 n8000 and tab p1000

my p1000 is brick( not going on download mode like totaly dead)

this method and debrick image work on it? if not so plz help me out m new over here
[T-Mobile, Samsung Galaxy SIII] IronRoo:
looks like you might have missed the link just above "here is a flashable zip" it's pointing to copy.com. I got the file from your OP that was pointing to dropbox anyhow.

Thanks for your work!
[T-Mobile, Samsung Galaxy SIII] khat17:
Hi all. Firstly, thanks for this thread. It's been a big help in trying to get my wife's phone back up. However I'm stuck and need a little help.

I always try to ensure that we both have the same type of device. This way I can troubleshoot hers (or mine) easily. She was running AOKP while I am on StockROMLite v2.0 - but I was running AOKP for a while with no problems. One day her phone decided to no longer turn on. It was running quite fine and she just placed it on charge the night before, but it never came back on.

I used the instructions here and got it this far:

I got the debrick image from this thread. I got the PIT files from this thread and I also extracted one from my phone and tried. When I use the one from my phone I get the "Secure Check Fail" error. When I use the PIT files from the thread mentioned before, I get the "PIT Fail: Total Sectors (0)" message. Any help would be greatly appreciated. Oh - and using a jig doesn't work with it.

I'm wondering if I should flash the original stock ROM to my phone before trying to get the PIT? Dunno. Thanks in advance.
[T-Mobile, Samsung Galaxy SIII] rothmasloly:
Still on the Matter t999 dead for ^ 6 months... I need your say

:confused: My Initial plan is to Update My T-Mobile Galaxy S3 T999 to Android 5.1.1 CyanogenMod 12.1 ...

Fisrtly, am sorry if am wrong ... My t999 is dead about 6 months ago... here its goes... I tried to changed the stock recovery to custom recovery using Rom manager , I flashed twrp recovery Galaxy S III (Intl) (i9300) and again without switching off , I then reliased I flashed wrong model immediately I flashed back my own model Galaxy S III (T-Mobile) (d2tmo) twrp and then switched off but its black screen since then….

Windows still recognise it as- RELINK HS-USB QDLoader 9008 (COM95)

Please help me its urgent… In my case I think I replaced stock recovery with wrong twrp recovery gt-i9300 s3 intl/twice. I need NEW T999_Partial_Sys_Dump_for_debrick pls for my own case. For- s3 T999 v4.1.2 jb , 4.1.1 JB , 4.0.4 ICS OR STEPS TO DO SO , USING WINDOWS OPERATING SYSTEM

PS: I noticed that when you extract debrick_SGH-T999, u get (in d image attach)

But the recovery is zero in size. Can anyone shed light on it ?

Thanks in advance Gurus in the house. :confused: :crying:
[T-Mobile, Samsung Galaxy SIII] khat17:
Good night. Firstly, I'd say try and find a recovery or debrick image for your model and put on the SD card as instructed. If someone already has that image available - use the methods described to put the image on an SD card and see if it will boot. If you manage to get it up then you're fine. I assume you've also already tried to place the phone in download mode and recovery mode. Silly questions but.................have you also tried to do a battery pull/drain for 5 minutes then boot the phone again? Trying both recovery and download mode? Have you tried using a jig for your model?
[T-Mobile, Samsung Galaxy SIII] cdurex:
Hi everyone!

I was wondering if we could create like a new thread with a list of debrick img for different phones.

Is this posible?

Will this method work for every phone?

And using the files from here; modified for every other phone obviously http://xdaforums.com/showpost.php?p=45725480&postcount=45 to create de img for each device.

Thanks for the reply in advanced.
[T-Mobile, Samsung Galaxy SIII] khat17:
*BUMP*

Still waiting on any reply that may help with this issue.

[MENTION=2981952]cdurex[/MENTION] - This seems like a good idea to me at least - but it's a matter of whether or not the method works for all phones. There may be some modifications needed to get it to work. This thread is for the S3 but mine is the S4 Mini Duos. Still got it to the place in the quoted post above though. Just stuck from there.
[T-Mobile, Samsung Galaxy SIII] khat17:
*BUMP*

Still waiting on any reply that may help with this issue. Just go to the page before this to see how far I got using these instructions on my wife's S4 mini. I'm stuck though, and need some more assistance. Anyone?
[T-Mobile, Samsung Galaxy SIII] khat17:
*BUMP*

Think this may be my last attempt here. Will post the info in the appropriate thread (S4 Mini Duos). Maybe I'll have better luck if I put it where persons might actually be looking for things for the specific device. If it's been an inconvenience for me to have my info in this S3 thread then I apologize. I'll wait a bit and *hopefully* someone will reply here all the same.
[T-Mobile, Samsung Galaxy SIII] crutchcorn:
I'm following the directions fairly well (I think) and am not able to get anything but QHUSB mode. Is it necisary to have 16GB on the SD card? That could be my problem

---------- Post added at 02:06 PM ---------- Previous post was at 01:54 PM ----------

To answer my own question:

Yes. You NEED at 16GB SD card. Reason? The files that you're flashing to the SD card total up to ~15.7GBs. Even if the tool you're using gives you the "flash successful" message, it did not do it properly
[T-Mobile, Samsung Galaxy SIII] progamer00:
Question? = Yes. But I bought a 16GB SD card and it only gave me about 14.4 GB memory space. It's normally the same with most of the SD card, you will only get less then 15GB of memory in a 16 GB SD card.

I've tried to use the De-brick.img with 16GB SD card and my phone did not boot. So I was wondering If I should try using the 32GB SD card ???
[T-Mobile, Samsung Galaxy SIII] khat17:
The debrick image that I have for the phone I have was less than 1GB. Maybe it's because it's the wrong one for the phone I'm using. But I suggest trying a different SD card and some other stuff.

To clarify why your media devices have less space than stated - 1MB = 1024 Bytes in IT generally, but the manufacturers use 1MB = 1000 Bytes. See article in blog link below for more clarification.

http://blog.forret.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/

But basically, ensure your media that you're going to use (SD card) is larger than the file that you're going to use (DEBRICK.IMG). If it copies to the device then theoretically there should be enough space. If the device is defective or there was some error during the copy process, you may have a case where there's a corrupted or incomplete file on the SD.

Another thing brought up in a different thread was how a member tried using Class10 cards in his handset and things didn't work until he used a lower class device. Just something to bear in mind if you have other issues.

Something else to do is use a program like TeraCopy to help ensure the file copies with no errors. If you want to do it manually, after copying the file check the MD5/CRC/SHA of the original and compare with the copy on the SD.

Hope this helps your situation.
[T-Mobile, Samsung Galaxy SIII] DrGit:
eMMC sudden death is a sometimes software-induced, but not soft-repairable, hardware failure, and this SD boot method will not fix a dead chip. Unfortunately, short of desoldering and replacing the chip, I think you're out of luck.
[T-Mobile, Samsung Galaxy SIII] khat17:
Thanks for that. Since then I've replaced her phone so all is good now. Maybe I'll try to reflow the chip and see if it will work.
[T-Mobile, Samsung Galaxy SIII] carcomp:
Will this work if you've done something stupid like flash an international rom for i9300 over the top of cyanogenmod on a T999L? Thats exactly what I did. Facepalm. I've written the image, I've put the sdcard in my phone, and it just sits there. ODIN can't see it. I can see it with QPST or whatever that tool is that looks at the qualcomm chip.
[T-Mobile, Samsung Galaxy SIII] IronRoo:
it's been known to work when an international version has being flashed in error

eg (last comment)

https://xdaforums.com/showthread.php?t=2345860&page=3

but I don't know how different the two phones you mention are, so maybe not in your case, but some people have had to repeat the whole process a few times before it's worked or use a different sd card.
[T-Mobile, Samsung Galaxy SIII] carcomp:
I'm using Linux to create the .img. It completes the dd task, but parted print doesn't show 23 partitions, only an error saying the disk has no name. I am just going from memory. Is it super important to use a 16gb card? Trying with 8gb. Now. I have an 8 and a 128gb card. If I could just get the image on it correctly. Using 32 bit Linux ubuntu 16 on VMware workstation
[T-Mobile, Samsung Galaxy SIII] carcomp:
Some time has passed and I decided to give it another try. I set up a proper Lubuntu linux machine, and created the 23 partition sdcard. The card is a 16gb SanDisk Ultra PLUS Class 10 card. I'm pretty sure i've tried every combination of putting in the battery, the cord, and the memory card, as well as every combination of buttons. Phone still just sits there dead. I can get the red light when i plug in without the battery. I've tried the 'bang the phone on the table for the power button' thing, but i'm 99% sure the button is fine. The phone hardly has any use. I've tried the T999L image, as well as one of the NOT FOR 4.3 images for a T999. (FYI My phone is a tmobile T999L).

I've also tried writing the sdcard using a micro to mini sdcard adapter as well as a usb to sdcard adapter.

Also, I noticed that when i have the SD card in the phone, the computer won't recognize it / initialize the qualcomm COM port. If i take the SD card out, its alright again.

History:

I had installed CyanogenMod 13 or 14 (something pretty recent) on the device. I had clockworkmod recovery on it, but honestly I didn't know how to use it. I do think though, that before I flashed anything I created a nandroid backup, if that matters.

Anyway, it was running slowly, so I thought I'd try something else. I googled "best galaxy s3 Roms" and found the Omega Rom here https://xdaforums.com/galaxy-s3/development/rom-omega-v58v50-14-34-1-2omega-t1663656,

Sadly, I didn't notice it was an international I9300 rom. My phone has been bricked ever since. I have since replaced the phone, but I'd like to give it to my 10yo daughter to use since she is just getting into social networking with her friends. She doesn't need to have the latest phone. The s3 is good enough for now.

Another idea was to see if odin can see the phone, but i've always thought that if the phone is black-screened, odin can't do anything with it.

Does anyone still feel like assisting?
[T-Mobile, Samsung Galaxy SIII] kethujaa:
please i need T-Mobile SGH-T999L V4.0 Debrick file plz help me someone
[T-Mobile, Samsung Galaxy SIII] Alexander7000:
help!

never worked for me, in 2018 with 4 s3 phones with hard brick in t999, t999v, t999n or t999L ... I thank the effort, so I wonder if anyone could guide me that I have successfully achieved ???
[T-Mobile, Samsung Galaxy SIII] mach1monorail:
Will this solution erase any data (photos, videos, contacts, text messages) stored on the phone's internal memory or only on the SD card? Ideally would like to find a way to get all my data off of the internal memory and then ditch the phone altogether. If anyone has any suggestions on how to do this, I'd be super grateful.
[T-Mobile, Samsung Galaxy SIII] droiduzr2:
I hope you can help me, assuming you are still on this board.

I have a Tab 8.9 LTE T957 D (Telus in Canada says ATT on the back cover also).

I messed it up and flashed the wrong file.

I can't get into download mode.

It's a black screen. I do not have an external sdcard therefore I can't do the sd debrick.img trick.

I do get it showing up in Windows 10 as Qualcom QDLoader9008.

I think it can be fixed.

It does who up in Odin but it will just sit there saying setting up connection (something like that). It just wont write the file.

I am familiar with Miflasher and Qflash.

I guess I just don't have the right xml files (package) for this unit.

How do I fix this given what I have to work with? I can setum a Linux Virtual Box if needed.

HAte to see this tablet go to waste. It has some life.
[T-Mobile, Samsung Galaxy SIII] Bleiz07:
Please, I need the debrick file for galaxy s3 SGH- T999N

---------- Post added at 08:14 AM ---------- Previous post was at 08:09 AM ----------

do you have the T999N debrick image? So you can send it to me please
[T-Mobile, Samsung Galaxy SIII] carlos1984:
Hi all would this method work for debricking a sm 377w tablet . It is hard bricked no download no recovery no power.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Okay, I'll see what I can get done and what I can find for you. I've got a lot of work to get done today so I'm out of IRC for the day until this evening
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I can't remember if it was already discussed or not, but I'm pretty sure there will be certain situations where this will not work.

If I'm understanding correctly, this will basically allow you to boot download mode so you can Odin the correct firmware back onto the device. So if a brick was caused by flashing over a partition like EFS, or param, or persist, for example, it is not included on the official firmware, so it will remain bricked.

Just a theory, but it seems logical. I do believe most bricks should be fixable by this, just not all.

What do you guys think?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
In case it doesn't work for some reason, [MENTION=4712945]GenericAsianGuy[/MENTION] used the recovery script I posted to get what you need. He posted here: http://xdaforums.com/showthread.php?p=45768559
[T-Mobile, Samsung Galaxy SIII] cy_mpak:
we are using byte-to-byte copy of working phone. so even if some parts are missing in official fw, we still get them.

similar procedure for i9300 require "special" plug in connector (Jig/Power Key/USB/Anyway-Jig/etc or 300k resistor at ID & GND) and short resistor R313 to boot from SD. i am not sure if in some cases this is also require on t999(v)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I'm still unsure about that. The reason I specifically mentioned a few of those partitions was because they are not included in the dumps being used to create this fix, or in the official firmware.

So if a brick was caused by overwriting the "param" partition for example, I'm not seeing how this would fix that since param is not included in the image or the firmware. The same is true for several other partitions as well.
[T-Mobile, Samsung Galaxy SIII] cy_mpak:
This is what I have in the image and on SD:

# parted /dev/sdb print

Model: Generic Ultra HS-SD/MMC (scsi)

Disk /dev/sdb: 16.0GB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Disk Flags:

Number Start End Size File system Name Flags

1 4194kB 67.1MB 62.9MB modem

2 67.1MB 67.2MB 131kB sbl1

3 67.2MB 67.5MB 262kB sbl2

4 67.5MB 68.0MB 524kB sbl3

5 68.0MB 70.1MB 2097kB aboot

6 70.1MB 70.6MB 524kB rpm

7 70.6MB 81.1MB 10.5MB boot

8 81.1MB 81.7MB 524kB tz

9 81.7MB 82.2MB 524kB pad

10 82.2MB 92.7MB 10.5MB param

11 92.7MB 107MB 14.3MB ext4 efs

12 107MB 110MB 3146kB modemst1

13 110MB 113MB 3146kB modemst2

14 113MB 1686MB 1573MB ext4 system

15 1686MB 14.8GB 13.1GB userdata

16 14.8GB 14.8GB 8389kB persist

17 14.8GB 15.7GB 881MB cache

18 15.7GB 15.7GB 10.5MB recovery

19 15.7GB 15.7GB 10.5MB fota

20 15.7GB 15.7GB 6291kB backup

21 15.7GB 15.7GB 3146kB fsg

22 15.7GB 15.7GB 8192B ssd

23 15.7GB 15.8GB 5243kB grow

so param is included in debrick image. And yes, it's missing from odin images
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
That could possibly happen on the other hand if it is recoverable through JTAG then we should be able to do the same with this method.
[T-Mobile, Samsung Galaxy SIII] buidoitieutu:
is there a way to do this on window yet? I dont know how to use Ubuntu and it doesnt seem to recognize my sd card.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I believe that's just the partition table. There's no way all of that can possibly fit in a 128mb img file.

[MENTION=3505796]KAsp3rd[/MENTION]

I was under the impression that the image was only of the first 7 partitions? (Up through the boot partition)

But looking at the table there it appears to have the first 13 and a small chunk of 14 (/system).

Is that correct?
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
I had tried using an image with just the first 70.6M for the L and the V with no success in either when it came to light that the regular t999 used a full 128M to boot for the one that I used. At some point today I am going to brick my S3 again and try some things using smaller sizes of images so that all can be verified on size. And you are correct that its just the partition table. And not actually all of the partitions.
[T-Mobile, Samsung Galaxy SIII] cy_mpak:
that image contains full partition table and 128M of data. so technically image is missing actual data from partitions 14 to 23.

we have to boot into download mode - rest of data is not needed
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ok, gotcha. Thanks for confirming all of that!

Lol! Never thought I'd see a post that includes the statement "I am going to brick my S3 again and try some things"!!! Too cool! :cowboy:

Right, which brings me back to my original point. If a user flashes something that overwrites one of those partitions that are not in the image, and it results in a bricked device, this method will not be able to fix it. And don't get me wrong, I am not trying to dumb down the importance of this at all! But it is likely that at some point, something like this will come up and people would be wondering why, after trying 10 times, they cannot get this to work! Im simply pointing it out now since it popped into my head.

Now, I do believe that it can be fixed in this situation! But this method, as is, on its own will not be enough. My theory is that if someone holds onto a FULL dump for each model, they would be able to create an Odin flashable file to restore whichever partition got flashed. This would best be done on a case by case basis though.

The main issue I see with this is that someone from each model will have to trust someone else to hold onto their full dump and keep it from being publicly available. The reason I say this is because the NV data is spread out over several of those partitions, and if you happen to restore the one which holds the IMEI, it may change it to the same as the donor device. (If they ran the NV backup, this should not be an issue, unless they restore the partition that holds the part of the backup that contains the IMEI!) Hopefully it would see the incorrect one as corrupt and attempt to restore it in the first case. To avoid the second case, we may want to recommend re-running the nv backup after unbricking.

Anyway, I went further than I planned there, but i believe it is still good to know info as for what to look out for in certain, unique situations. If you guys think we should put out a request for it, I already have a script that will dump every partition individually. I just modified it to make the one I posted before.

What does everyone think of all of this? Like I said, its just a theory as I have never seen this attempted. But from my understanding of everything, it seems to me a fairly sound theory. I welcome your scrutiny of it!
[T-Mobile, Samsung Galaxy SIII] cy_mpak:
Analogy example.

In the past we used 1.44Mb floppy disks. Bootable disk had MBR (sector 0), then 2 files in the beginning of the disk - io.sys, msdos.sys. And command processor command.com anywhere on the disk. So if you make a sector by sector (starting from 0) copy of about 200k into image and put that image on another floppy, you can boot OS. You will also have FAT with pointers to files, which will be missing from disk 2. However you can BOOT.

Same here - we only copy data we need to boot into download mode - we don't care about system, cache or even recovery.

I suspect that for t999v procedure to fallback to sd-boot require some additional steps, similar to i9300 (i.e.resistor between pins 4 and 5 and short resistor r313 to force boot from sd)
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Video posted in 2nd post for those that want/need it. Included instructions for returning your sdcard back to normal as well.
[T-Mobile, Samsung Galaxy SIII] kimdoocheol:
I followed the instructions and got an SD w/ 23 different partitions on it.

I think what caused my brick was this http://xdaforums.com/showthread.php?t=2240832, as I also flashed ACID mod, but it failed and so did the devil kernel. I've never had a problem with ACID and have had it on this device before, so I really doubt it was that, and i'm almost positive it was because of the dk because another member in that thread flashed it on their vzw variant and had the same issue, although i'm unsure if it was a successful flash or what.

Anyways, the battery i'm using right now I am not quite sure if it is charged or not. I will get it in my external charger tomorrow and see what happens. I was wondering, does the device always boot? or is there a chance that it doesn't boot but can still go into download mode or become responsive in ODIN?