Develop Bugs

Phone life after death. Breaking the Jtag taboo.

I had some research yesterday, yet I still can't find a proper answer to most of my questions about the following subject. Hoping some of the experts here can contribute some of their knowledge and hopefully I will edit this thread to a guide, or at least spare others the need for wondering around the web as I did.
Well, Few days ago I turned off my phone, and it wont turn on or response to any physical key combination, usb connection (Except for charging the battery) or even that famous Samsung jig (301KΩ Between pin 4 and 5 on the usb connection). It is not recognizable by any device while connected through usb interface. It is permabricked. The worst thing that can happen to a phone while the hardware is intact.
Although the name indicates otherwise, some things can be done in order to get the device working again.
It is a process in which the phone's main bored is exposed, than a special device (e.g riff box) is connected to certain areas on the pcb that were made that way for the initial configuration of the phone back in the factory. The pinout of the connection varies in each model, but the interface is the same and called "Jtag". Than, that device connects to a pc through usb interface.
So the first step would be to get that device and to connect it to both pc and phone's motherboard through a certain pinout that is mostly hard to get. You'll need a driver for that jtag flashing device and a compiled file which you would like to flash in to your phone. I don't know if that file is specific to each model or to the certain chip the phone is using (Can different models with the same chip be flashed the same way? Reply if you know and I'll edit it here).
By what I know, after flashing that file the phone will be accessible through usb interface for further flashing of the rom.
Alternatively, There are some companies that offer that kind of service. I couldn't find any who work with T989, and prices for that kind of service.
I would like to have as much information as possible and maybe eventually I'll be able to get my phone fixed. In that case I'll add some photos and document the process.

Michael.fri said:
I had some research yesterday, yet I still can't find a proper answer to most of my questions about the following subject. Hoping some of the experts here can contribute some of their knowledge and hopefully I will edit this thread to a guide, or at least spare others the need for wondering around the web as I did.
Well, Few days ago I turned off my phone, and it wont turn on or response to any physical key combination, usb connection (Except for charging the battery) or even that famous Samsung jig (301KΩ Between pin 4 and 5 on the usb connection). It is not recognizable by any device while connected through usb interface. It is permabricked. The worst thing that can happen to a phone while the hardware is intact.
Although the name indicates otherwise, some things can be done in order to get the device working again.
It is a process in which the phone's main bored is exposed, than a special device (e.g riff box) is connected to certain areas on the pcb that were made that way for the initial configuration of the phone back in the factory. The pinout of the connection varies in each model, but the interface is the same and called "Jtag". Than, that device connects to a pc through usb interface.
So the first step would be to get that device and to connect it to both pc and phone's motherboard through a certain pinout that is mostly hard to get. You'll need a driver for that jtag flashing device and a compiled file which you would like to flash in to your phone. I don't know if that file is specific to each model or to the certain chip the phone is using (Can different models with the same chip be flashed the same way? Reply if you know and I'll edit it here).
By what I know, after flashing that file the phone will be accessible through usb interface for further flashing of the rom.
Alternatively, There are some companies that offer that kind of service. I couldn't find any who work with T989, and prices for that kind of service.
I would like to have as much information as possible and maybe eventually I'll be able to get my phone fixed. In that case I'll add some photos and document the process.
Click to expand...
Click to collapse
1st off, it's "taboo" not tabu. Secondly there is already a pretty good amount of threads that have covered this in detail, I'm certain because I have posted in them. Lastly, please SEARCH the existing threads before creating a new one; the answers to all your questions are already there.

1. Thanks, Changed to "Taboo".
2. I searched, I really did. I went all over google with many key words and covered up this forum as well. All I got is some articles about the jtag protocol, which is good for knowledge but too general for the application I need, and some threads in which people writing that their phone is bricked and asks what to do about it. Not a single post is about how to fix that independently, and what does it require. If you could give me link to these threads you say that covers up the subject, I'll delete this thread at once.

Michael.fri said:
1. Thanks, Changed to "Taboo".
2. I searched, I really did. I went all over google with many key words and covered up this forum as well. All I got is some articles about the jtag protocol, which is good for knowledge but too general for the application I need, and some threads in which people writing that their phone is bricked and asks what to do about it. Not a single post is about how to fix that independently, and what does it require. If you could give me link to these threads you say that covers up the subject, I'll delete this thread at once.
Click to expand...
Click to collapse
don't pay attention to that guy he like to troll every where he goes. Try to google search for mobile tech or Adam Outler, and check if he get the Jtag service for our phone. If I'm not wrong the charge for the Vibrant was $50.00 plus shipping and handling. I hope you can fix your phone.
Sent from my SGH-T989 using xda premium

Do you know what caused the brick?
Sent from my SGH-T989 using xda premium

Searched, and yet no result. Sending the phone to the U.S is quite risky. I have no idea how they're intended to pack it before sending it back. I would rather doing this in Israel.
I saw on ebay several devices associated with Jtag. the price starts from 10$ for a simple usb dongle, through 30$ devices, which is the price of most of the jtag devices I found, to the 150$ riff box that is associated with phone unbricking.
By what I know Jtag is a simple serial protocol. I just need sort of "bridge" to translate the logic 1's and 0's with the right voltage level and certain clock speed to a usb interface or even RS232. How expensive can that be?
I also contacted several ebay sellers which offer a jtag repair service. they all answered this model is not supported.
I would go to Samsung labs in Israel and see what they can do to get it working.
I just thought to invest 20$, get that sort of device and to get it done by my own.
Another issue is the pinout. The pinoput of the Jtag connection is not shown in any website, so I have no way of knowing how to connect on this specific PCB.
Last thing I need is that new bootloader I can flash, and a software to flash it through. Where can I download it?
About the reason for bricking the phone, I have no Idea. As I said, last time I've installed new rom was more than a week prior to the incident. I've used some overclocking app mostly to underclock my phone, cause it drained the battery like hell before, even while it was running on stock and after changing the rom several times.
I also used some usb otg device which worked normally, but was not plugged to the device even few hours before it was bricked.

Hopefully we can figure out the cause of these permabricks so we can prevent it from happening to more people.
Sent from my SGH-T989 using xda premium

I gotta say, this is quite alarming. That the phone can just hard brick itself like this spontaneously.
I've had some scary experiences with the phone myself. Like a couple of random reboots that required the long power press for the phone to power back on. At least it always came back on.
I'm also from Israel myself so a similar scenario can bring me to the same situation as you.
Good luck with getting any kind of solution.
Sent from my SGH-T989 using xda premium

parusia said:
don't pay attention to that guy he like to troll every where he goes. Try to google search for mobile tech or Adam Outler, and check if he get the Jtag service for our phone. If I'm not wrong the charge for the Vibrant was $50.00 plus shipping and handling. I hope you can fix your phone.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Troll for advising to follow the posted rules of membership ? WOW

I just contacted Adam and still no jtag for this device .
Sent from my Galaxy Nexus using XDA App

did you look for a service manual?
- the manual may cover schematics for jtag device.

Been flashing phones since the Razr and never bricked a phone I couldn't repair myself. That is until I tried to flash my GSII back to stock through odin. Sent it to Samsung and they had to replace motherboard. Now I'm a little nervous about using odin.

reocej said:
Been flashing phones since the Razr and never bricked a phone I couldn't repair myself. That is until I tried to flash my GSII back to stock through odin. Sent it to Samsung and they had to replace motherboard. Now I'm a little nervous about using odin.
Click to expand...
Click to collapse
I recommend splurging on the $2-3 for a jig, I have had moments where I thought I was SOL & the jig saved my arse.

Michael.fri said:
Last thing I need is that new bootloader I can flash, and a software to flash it through. Where can I download it?
Click to expand...
Click to collapse
Did you solve your problem?

I was looking at using QPST
QPST is a program often frowned upon here at xda. It is commonly used to flash phones, and has little to do with android coding. The software is made for Qualcomm (or by them) and this device has a chip from them in it. This has tools for building and installing bootloaders and partition tables. Our device after a hard brick (and still serviceable by JTAGing) has a com port open still and if you load the driver in windows you will see a port number as others here on XDA have said. The driver allows ODIN to see the device but not connect. QPST does connect, but I have not attempted to flash anything to it since I have not built any files to load. I'm kind of stuck creating the needed xml that makes the partition table and headers and file that are to be loaded to partitions. This is really a softbrick, in my opion, but nobody has the knowledge for this level of building and coding, with this tool, here at XDA. If somebody does, it may make those selling JTAG services mad, but that would mean we could fix our phones on our own. On my own, I'm a few weeks away from this solution, with some help from people here that know how to write xml for partition tables and can help me locate files for a build, I can generate the files, test them, make a write up and post the solution in just a few days.
By the way, this is a multi-device solution in the long run. We get one fixed and we can start on the others with this same issue, where the only life left in the device is the Qualcomm download mode driver showing in windows device manager.

Michael.fri said:
I had some research yesterday, yet I still can't find a proper answer to most of my questions about the following subject. Hoping some of the experts here can contribute some of their knowledge and hopefully I will edit this thread to a guide, or at least spare others the need for wondering around the web as I did.
Well, Few days ago I turned off my phone, and it wont turn on or response to any physical key combination, usb connection (Except for charging the battery) or even that famous Samsung jig (301KΩ Between pin 4 and 5 on the usb connection). It is not recognizable by any device while connected through usb interface. It is permabricked. The worst thing that can happen to a phone while the hardware is intact.
Although the name indicates otherwise, some things can be done in order to get the device working again.
It is a process in which the phone's main bored is exposed, than a special device (e.g riff box) is connected to certain areas on the pcb that were made that way for the initial configuration of the phone back in the factory. The pinout of the connection varies in each model, but the interface is the same and called "Jtag". Than, that device connects to a pc through usb interface.
So the first step would be to get that device and to connect it to both pc and phone's motherboard through a certain pinout that is mostly hard to get. You'll need a driver for that jtag flashing device and a compiled file which you would like to flash in to your phone. I don't know if that file is specific to each model or to the certain chip the phone is using (Can different models with the same chip be flashed the same way? Reply if you know and I'll edit it here).
By what I know, after flashing that file the phone will be accessible through usb interface for further flashing of the rom.
Alternatively, There are some companies that offer that kind of service. I couldn't find any who work with T989, and prices for that kind of service.
I would like to have as much information as possible and maybe eventually I'll be able to get my phone fixed. In that case I'll add some photos and document the process.
Click to expand...
Click to collapse
Mobile Tech offers the JTag service. There is even a discount for XDA members. They offer the service for all variants of the S2
Here you go!
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/

daxxone said:
QPST is a program often frowned upon here at xda. It is commonly used to flash phones, and has little to do with android coding. The software is made for Qualcomm (or by them) and this device has a chip from them in it.*snip* On my own, I'm a few weeks away from this solution, with some help from people here that know how to write xml for partition tables and can help me locate files for a build, I can generate the files, test them, make a write up and post the solution in just a few days..
Click to expand...
Click to collapse
Any word on a fix using QPST?

Samsung has my hard bricked phone...

I'm watching the repair process online at their tracker thing and the last comment says "replaced PBA". Anyone know what that means? Obviously they're fixing it which is fantastical. This is just my own curiosity wanting to know...

google much?
http://www.youtube.com/watch?v=EhLPyC23jBI

My gosh, why can't people just answer without smart remarks.
Sent from my SAMSUNG-SGH-I747 using xda premium

PBA = That's basically the main board that makes the device work. Mine was replaced by Samsung as well after a hard brick.
Next time read more and be careful on what you flash on your device, these things seems to be very weak and fragile.
Good luck and I hope this answer your question.:good:

llanero75 said:
PBA = That's basically the main board that makes the device work. Mine was replaced by Samsung as well after a hard brick.
Next time read more and be careful on what you flash on your device, these things seems to be very weak and fragile.
Good luck and I hope this answer your question.:good:
Click to expand...
Click to collapse
These devices aren't anything near fragile. They can actually take a huge beating when it comes to flashing. But... If anyone were to flash something for say an i9300 to this device it would need to be repaired. Which should be expected. That's why flashing device specific is very important. Thread titles and forum names are cool to handle that though.

Potential Brick, Unsure How To Proceed

Hello all.
I am an HTC guy through and through and have never owned a Samsung device. I'm familiar with HTC's S-OFF/HBOOT/bootloader stuff, but I'm not really all that clear on how it works for Samsung devices. I promise I've tried to do some reading before hand before coming to you, including looking at other threads, but they don't seem to be the issue I'm having.
I'm trying to help a friend out who has an AT&T GS3 that I unlocked for him and put an AOSP ROM on it a few months ago (don't worry, I made damn sure it was the AT&T version and no other carrier/international ROM).
He came to me today telling me that his phone suddenly turned off, and was not turning on again. I figure it's probably just a corrupted partition, something that I could fix with a reflash or something like that.
However, when I look at it, it seems to be something potentially worse. The phone did nothing with the battery in, so I took it out and put it back in. The phone very briefly vibrates, the Samsung logo shows for about 1.5 - 2 seconds at most, and then the screen goes dark.
When I try to enter Download Mode, I'm able to get to the custom software "warning" page, where I press Volume Up, and it shows me Download Mode and "Waiting" (as I expect it to) but then the screen just goes black again after about a second or two.
It's roughly the same with Recovery Mode, I can catch a glimpse of what looks like CWM (but I'm not entirely sure) and then the screen goes black.
If I choose to forgo the battery altogether, and I plug it in straight to the wall, the red LED on the top right lights up for again maybe 3 - 4 seconds at most, the light goes away, and the phone briefly vibrates, shows me the Samsung logo, and then goes dark.
I'm confused. I don't know if it's a brick, but then again, to me as an HTC user, "brick" means Qualcomm USB Download mode. I've also read about this infamous Samsung Sudden Death Syndrome that struck some of the 16 GB models that Samsung sold (and yes, you guessed it, this is the white 16GB model).
I don't really know what other troubleshooting options there are (but as I said before, I'm an HTC guy). If any of you have any sort of advice I would love to hear it.
Thank you for your time.

I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.

xBeerdroiDx said:
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
Click to expand...
Click to collapse
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.

Yeah, the biggest problem is that once you get into recovery or download mode, the device reboots/loops. This eliminates the possibility of any kind of flashing or wiping.

You might have a bad motherboard. If I was you I'd take it to att for a replacement. BTW if he doesn't have insurance for the phone they do have open enrollment , I'd wait a day or two after enrolling to submit a claim.
Wish you the best.
Sent from my SGH-I747 using xda app-developers app

LiquidSolstice said:
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Click to expand...
Click to collapse
It's a realllly long shot but he could contact mobile tech videos and tell them his issue and see if a jtag repair would help. If it's hardware of course he is out of luck but it's worth a shot and a lot cheaper.

[Q] Bricked T999

I have a GS3 that was rooted with a CM rom. I was using it the other day and the screen just suddenly went black. I tried rebooting it and popping out the battery, but to no avail. I can't boot it into download or recovery mode either.
When I put in the battery, the phone vibrates but nothing else. When I plug in the USB cable with no battery, it vibrates and the LED comes on for a few seconds before flickering off.
My first priority is data recovery, I've been a bad boy and haven't backed up my data for a while. My second priority is making it so they can't tell I have a flashed ROM when I send it out for warranty service, though AFAIK, this may be a nonissue.
I tried to make a 300k jig, and it didn't work (assuming I got the pins right).

Have you tried KAsp3rd's debrick method?
Stickies in development.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Have you tried KAsp3rd's debrick method?
Stickies in development.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I'm not stuck in QHSUSB-DLOAD as far as I can tell. Would it still be effective?

Could be. It basically allows you to boot download mode from the sdcard. From there you Odin flash the firmware and hopefully that would fix it. But if it's a hardware failure, which it could be per your description, I doubt anything will work.
Sent from my SGH-T999 using Tapatalk

New update. I figured out that the 300k ohm resistor trick DOES work, but only for like three seconds. Meaning that they'll be able to see the custom binary count, but (as far as I know) I can't reset it to 0.
The weird part is that it only works if I plug the usb jig into the phone before putting the battery in, if I put the battery in first, it doesn't work. It almost seems like it constantly thinks the power button is being pressed or something.
I guess I'm opening it up and looking for a short. The power button operates normally tactile-y speaking.
EDIT: new new update. I wasn't able to find anything physical when I looked at the pcb. But I verified my theory, somewhat. When I hold home and volume up/down (without touching the power button) when I put the battery in, it boots into download mode for a second before shutting down.
It's not behaving exactly like it would if it was only that though, because I tried holding the power button down on the t999l I got as a replacement, while inserting the battery, and the boot screen shows up for a few, where a boot screen never shows up on the bad phone.
DOUBLE EDIT: can I swap that pcb with the one from the t999l, or are they too dissimilar? Would I be able to swap it with one from another t999, or does the board that has the power switch also have the onboard storage?
TRIPLE EDIT: I answered my own question, the eMMC and the power switch are on the same board. But if the fault is caused by something else (e.g. a camera), would I be able to plug all the other hardware from the t999l into the t999, or can I just boot up the t999 without most of the hardware connected as a test?

I would not risk going through all that trouble. Not quite sure why you would honestly. You got a T999L right? Warranty replacement I assume? It's a superior device so why my not just use it as is?
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
I would not risk going through all that trouble. Not quite sure why you would honestly. You got a T999L right? Warranty replacement I assume? It's a superior device so why my not just use it as is?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
1. I really want my data back.
2. I risk getting charged for out of warranty if they see it was rooted and flashed.
3. I'm going to sell it anyways, I got a note 3 because the S3 was on backorder and I couldn't do my job without a smartphone.

1. I'm sorry to say, but plan on this not being possible.
2. If it won't boot there is little chance you'd have to worry about it. They aren't going to go to extraordinary measures to check k the counter. Many people have claimed they sent a dead device back and never got charged, even though the counter had been tripped.
If you damage the good hardware you won't have much to sell.
I don't understand why you'd be willing to attempt to Frankenstein the two devices, but not at least attempt the debrick method I mentioned.
Also, you should be aware, even if it's something else, not a bad chip, it probably won't work. Much of the hardware is in fact different between the two. Different camera, different radios, different SoC....
I wish you luck if you decide to try this, but imo you are taking an awful big risk to try something that probably won't work anyway.
If your data is really that important maybe you should look into a data recovery service.
And in the future, back up back up back up!
Good luck whatever you decide. Let us know what happens.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
1. I'm sorry to say, but plan on this not being possible.
2. If it won't boot there is little chance you'd have to worry about it. They aren't going to go to extraordinary measures to check k the counter. Many people have claimed they sent a dead device back and never got charged, even though the counter had been tripped.
If you damage the good hardware you won't have much to sell.
I don't understand why you'd be willing to attempt to Frankenstein the two devices, but not at least attempt the debrick method I mentioned.
Also, you should be aware, even if it's something else, not a bad chip, it probably won't work. Much of the hardware is in fact different between the two. Different camera, different radios, different SoC....
I wish you luck if you decide to try this, but imo you are taking an awful big risk to try something that probably won't work anyway.
If your data is really that important maybe you should look into a data recovery service.
And in the future, back up back up back up!
Good luck whatever you decide. Let us know what happens.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Reading through the whole thread, I am going to agree with the Doc. Why would you go to all that trouble ? Nobody is going to be able to salvage that data, let alone snoop in it. You are best move on rather than Creating that Frankenstein Monster as Doc aptly put it.

The frankenphone would only have been for if the phone didn't work without the camera/speaker/etc connected. However when I disconnect everything from the main board except for the screen, I get the same behavior. So I guess the only thing I would want to test would be the touchscreen. I can't find any info on if the t999l touchscreen is compatible with the t999 board, but if anyone knows, that would be great.
I'm still going to try the microsd card debrick method, I was concentrating on the usb jig last night since that got me further than anything else so far.
As to why, I have pictures and whatnot on the phone that I want to save, as well as a bunch of work crap that will take me dozens of hours to recreate, plus a bunch of other personal stuff. If I can't get it, then I can't get it, but I want to exhaust my resources (within reason) before giving up.

dubloe7 said:
I'm still going to try the microsd card debrick method, I was concentrating on the usb jig last night since that got me further than anything else so far.
As to why, I have pictures and whatnot on the phone that I want to save, as well as a bunch of work crap that will take me dozens of hours to recreate, plus a bunch of other personal stuff. If I can't get it, then I can't get it, but I want to exhaust my resources (within reason) before giving up.
Click to expand...
Click to collapse
Try JTAG instead of this if sdcard doesn't work. Most of t999l hardware is supposed to be identical. Since partition are potentially different. So phone may not boot. But you might be able to do adb. Good luck.

Actually it's the other way around. Partition layout is the same (though firmware incompatible) and hardware is definitely different.
Sent from my SGH-T999 using Tapatalk

SD card didn't work, looking for jtag instructions.
EDIT: The more I look, the more it looks like a faulty power switch. Unfortunately, it doesn't look like I have a way to short the power switch or something in a way that doesn't void the warranty...
Any help on this is appreciated.

Well, I think I'm completely screwed now.
I found this, http://androidforums.com/samsung-ga...-help-black-screen-vibrating.html#post5262715 and somehow managed to lift the freaking solder pads.
What do you think the chances that they won't charge me a couple hundred dollars for "out of warranty service" are?
EDIT: good news: Confirmed that the cable that I lifted the solder pads on, which I assume is an antenna, probably isn't the problem (unplugged it on the t999l, and it works fine).
bad news: I also confirmed the power switch itself isn't the problem either. The left and right hand side aren't connected (according to my multimeter) when the button isn't pressed, but they are when it is.
Another edit: I unconfirmed the power switch part. It looks like the button only needs the slightest contact in order to short. I removed the power button from the case, surprisingly difficult since I saw people complaining about it falling out. Now the difficult part is making it think the switch is closed for long enough to not turn it on, but not long enough to turn it back off. I've gotten it to the boot logo, but I haven't gotten it to fully boot.
Yet another EDIT: the only way I can get it to turn on long enough to see the boot logo is by smacking it in my hand after it turns on, which seems to interrupt the constant button press signal. From the metering on the switch, it seems that even less contact is needed to turn on the phone than to signal the multimeter. Any suggestions as to somewhere to cut the power switch signal other than the power switch?

Hard Brick I747: yes, there are options

The definition of "Hard Brick" is a phone that cannot be booted into any mode (including download, recovery). Worse case is a phone that does not respond to the buttons at all (power, menu, home, back, and volume). I have searched through all XDA forums and keyworded the net for hours, convinced that there had to be a free or cheep way to unbrick my hard bricked I747. I found leaked instructions that outlined how to bridge a specific (very small) transistor (named R313) inside the phone in order to trigger "SD Card Mode." The SD card was prepared to reinstall boot img and stalk ROM prior to triggering SD Card Mode. However, after opening my phone I found that the phone used to illustrate and show where the R313 transistor was located was designed totally different than my model. There was no way to know where the R313 was. Evidently, the S3 design can differ depending on carrier or maybe time purchased.
So, if it is unlikely for most of us that we will be able to find and bridge the R313 transistor, then there are only two other solutions that I was able to find. TJig, which is about $60, or send phone to Samsung for warranty service (if still under warranty). My phone is still under warranty and I just sent my phone in to Samsung. The question remains, "will Samsung be able to see if a hard bricked phone is customized or has a flash count?" or do they even look. If phone hard bricked, one can boot the phone into download mode with the right equipment. Download mode reveals the flash count. If Samsung checks flash count, then I assume TJig may be my only option. Or maybe Samsung will offer to unbrick my "out of warranty" phone for less than the price of a TJig. Hard to say. I will post my results when I get them.
If you are out of warranty, you may try calling around to service providers. The S3 is still the most popular phone on the planet; there is a good chance that a serve provider somewhere has a TJig and would charge you $20 or so to fix your phone with it.
Please add to this post if you can contribute. Especially if you have gone the warranty route and can report what happened.

I hard bricked my S3 by flashing LK3 bootloader, and I sent my phone to following ebay JTAG service, he is really helpful.
http://www.ebay.com/usr/patrickwalls
If anyone there hard bricked his phone like me and do not feel comfortable with SD card method, I would recommend him.
floykoe said:
The definition of "Hard Brick" is a phone that cannot be booted into any mode (including download, recovery). Worse case is a phone that does not respond to the buttons at all (power, menu, home, back, and volume). I have searched through all XDA forums and keyworded the net for hours, convinced that there had to be a free or cheep way to unbrick my hard bricked I747. I found leaked instructions that outlined how to bridge a specific (very small) transistor (named R313) inside the phone in order to trigger "SD Card Mode." The SD card was prepared to reinstall boot img and stalk ROM prior to triggering SD Card Mode. However, after opening my phone I found that the phone used to illustrate and show where the R313 transistor was located was designed totally different than my model. There was no way to know where the R313 was. Evidently, the S3 design can differ depending on carrier or maybe time purchased.
So, if it is unlikely for most of us that we will be able to find and bridge the R313 transistor, then there are only two other solutions that I was able to find. TJig, which is about $60, or send phone to Samsung for warranty service (if still under warranty). My phone is still under warranty and I just sent my phone in to Samsung. The question remains, "will Samsung be able to see if a hard bricked phone is customized or has a flash count?" or do they even look. If phone hard bricked, one can boot the phone into download mode with the right equipment. Download mode reveals the flash count. If Samsung checks flash count, then I assume TJig may be my only option. Or maybe Samsung will offer to unbrick my "out of warranty" phone for less than the price of a TJig. Hard to say. I will post my results when I get them.
If you are out of warranty, you may try calling around to service providers. The S3 is still the most popular phone on the planet; there is a good chance that a serve provider somewhere has a TJig and would charge you $20 or so to fix your phone with it.
Please add to this post if you can contribute. Especially if you have gone the warranty route and can report what happened.
Click to expand...
Click to collapse

OK, so I sent in my bricked S3 (out of warrantee due to multiple flashes) to Samsung's Warrantee Service Department in Texas. They replaced something and sent it to QC, who put there stamp of approval on it and sent it to shipping. It is now on it's way back to me via 2 day air UPS. So I guess know one noticed the flash count or modified status. It is being sent back to me a warrantee S3.
I can't wait to brake the warrantee again
Results may very, but if your phone is with-in the warrantee window it can't hirt to try warrantee repair. You may know that you broke the warrantee, but they might be to busy to notice. They do pay for shipping both ways. Service is fast. All I had to pay for was the packaging materials.
The EBAY service mentioned above also looks lioke a good deal, for those of you with no warrantee. Check it out.
Sent from my GT-N7105 using xda app-developers app

Uhhh......how many flashes before it's bricked? Just wondering, I've been getting carried away latley. Thanks
Sent from my SGH-I747 using xda app-developers app

simpson173 said:
Uhhh......how many flashes before it's bricked? Just wondering, I've been getting carried away latley. Thanks
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
LOL, I am up over 200 flashes on my note II, but my daughter's S3 bricked when Iflashed an international kernal to an AT&T specific ROM. I guess that is a no no. There are certain things that will brick your phone; as long as you don't do those things, you can flash 5 times a day if you want. The important thing is to read all threads and ask questions before you flash. However, even the experienced and careful flashercan make a mistake. It is important to know what to do if this happens to you.