Develop Bugs

Why can't a bricked phone be revived?

This is a question for those in the know when it comes to programming.Why isn't there a way to revive a bricked phone? Can't there be some method for a host computer to manually write the radio to the device? How does HTC fix a bricked phone for it to be a refurb?
I'm just very curious about this because I see a few people attempt to update the radio only to lose power and brick their EVO. I have no programming experience so don't know what goes on at the internal component level. Thanks in advance for your input.

It goes back to the old bootstrapping problem when computers were being developed. A computer (in this case, your cell phone) is pretty dumb at the hardware level. All it can do is run programs. That's ALL it can do. It can't even load a program, only run them. Thus the problem. It gets solved by injecting a "bootstrap" program at startup (from the phrase "pull yourself up by your bootstraps") which is a program that runs and gives access to all the I/O, and the computer can then load more programs.
When you update this bootstrapping program, it gets dicey, because if it isn't written right, or if there's a glitch during the update, this most basic of all functions gets corrupted. If the program that tells the phone how to load programs goes away, all the phone can do is... sit there. Like a brick.
Hope this helped!

That helped me, thanks.

Soylent Grin said:
It goes back to the old bootstrapping problem when computers were being developed. A computer (in this case, your cell phone) is pretty dumb at the hardware level. All it can do is run programs. That's ALL it can do. It can't even load a program, only run them. Thus the problem. It gets solved by injecting a "bootstrap" program at startup (from the phrase "pull yourself up by your bootstraps") which is a program that runs and gives access to all the I/O, and the computer can then load more programs.
When you update this bootstrapping program, it gets dicey, because if it isn't written right, or if there's a glitch during the update, this most basic of all functions gets corrupted. If the program that tells the phone how to load programs goes away, all the phone can do is... sit there. Like a brick.
Hope this helped!
Click to expand...
Click to collapse
Thanks for the info. That is interesting. So how does HTC initially put the bootstrap in and/or how do they handle a bricked phone?

Soylent Grin said:
It goes back to the old bootstrapping problem when computers were being developed. A computer (in this case, your cell phone) is pretty dumb at the hardware level. All it can do is run programs. That's ALL it can do. It can't even load a program, only run them. Thus the problem. It gets solved by injecting a "bootstrap" program at startup (from the phrase "pull yourself up by your bootstraps") which is a program that runs and gives access to all the I/O, and the computer can then load more programs.
When you update this bootstrapping program, it gets dicey, because if it isn't written right, or if there's a glitch during the update, this most basic of all functions gets corrupted. If the program that tells the phone how to load programs goes away, all the phone can do is... sit there. Like a brick.
Hope this helped!
Click to expand...
Click to collapse
Thanks good explanation appreciate that.

rafroehlich2 said:
Thanks for the info. That is interesting. So how does HTC initially put the bootstrap in and/or how do they handle a bricked phone?
Click to expand...
Click to collapse
There is probably a JTAG interface somewhere in there. In fact,that's how the original hack of the IPhone was done. (Better ways were since found) Most devices have a quasi standard interface for programming the flash and accessing and the hardware for diagnostics. For instance,linksys routers actually have a spot on the board to solder a header and you can make a cable that connects to the parralel port. Do a google search for "Hairy Dairy Maid Debrick" and you will find it. A similar thing is probobally possible with the Evo (Ive even seen them on Hard Drives and CD Rom drives) The problem is,its not entirely standardized,and it might not even be a connector or pads on the board. It might instead be a matter of knowing where you can connect the leads on the board to something that under the right circumstances BECOMES the JTAG connector. (For instance,a pin that controls something else might be a JTAG interface for the first few hundred milliseconds of start-up,or if a certain other pin of the chip is grounded when the power is applied. It might also be completely internal to the chip,and there be NO connectors on the board (it almost CERTAINLY has the capability,they need it during prototyping) and the chips might be programmed BEFORE they are soldered in. It might take replacing the rom chip to get it to go. There are lots of ifs
Chances are though,the factory has a special cable and a special software program that can reprogram the device. To replicate that might be relatively easy or could be next to impossible but requires a certain degree of knowledge about the hardware. What I suspect is,until someone who has the skills to make such a cable bricks their phone,they wont bother figuring out how to debrick one. In fact,when that person bricks their phone,they will probably take it back to sprint and say "I dont know what happens" In fact,even if its stuck looping in an obviously hacked boot loader he for some odd reason cant undo,hes probably going to send it back to sprint. I know someone who did exactly that to their brand new HP laptop. He found that 15kv from the flyback of an old B&W television applied to the memory slots took care of the looping and Best Buy gave him another one. As he put it "I dont know what happened,but it smells bad and wont boot up"

pflatlyne said:
There is probably a JTAG interface somewhere in there. In fact,that's how the original hack of the IPhone was done. (Better ways were since found) Most devices have a quasi standard interface for programming the flash and accessing and the hardware for diagnostics. For instance,linksys routers actually have a spot on the board to solder a header and you can make a cable that connects to the parralel port. Do a google search for "Hairy Dairy Maid Debrick" and you will find it. A similar thing is probobally possible with the Evo (Ive even seen them on Hard Drives and CD Rom drives) The problem is,its not entirely standardized,and it might not even be a connector or pads on the board. It might instead be a matter of knowing where you can connect the leads on the board to something that under the right circumstances BECOMES the JTAG connector. (For instance,a pin that controls something else might be a JTAG interface for the first few hundred milliseconds of start-up,or if a certain other pin of the chip is grounded when the power is applied. It might also be completely internal to the chip,and there be NO connectors on the board (it almost CERTAINLY has the capability,they need it during prototyping) and the chips might be programmed BEFORE they are soldered in. It might take replacing the rom chip to get it to go. There are lots of ifs
Chances are though,the factory has a special cable and a special software program that can reprogram the device. To replicate that might be relatively easy or could be next to impossible but requires a certain degree of knowledge about the hardware. What I suspect is,until someone who has the skills to make such a cable bricks their phone,they wont bother figuring out how to debrick one. In fact,when that person bricks their phone,they will probably take it back to sprint and say "I dont know what happens" In fact,even if its stuck looping in an obviously hacked boot loader he for some odd reason cant undo,hes probably going to send it back to sprint. I know someone who did exactly that to their brand new HP laptop. He found that 15kv from the flyback of an old B&W television applied to the memory slots took care of the looping and Best Buy gave him another one. As he put it "I dont know what happened,but it smells bad and wont boot up"
Click to expand...
Click to collapse
Wow. Thanks for the detailed answer. Too bad this isn't a standardized item. I hope eventually things progress enough where this isn't even a thought. Thanks again for the good response.
Sent from my PC36100

rafroehlich2 said:
Wow. Thanks for the detailed answer. Too bad this isn't a standardized item. I hope eventually things progress enough where this isn't even a thought. Thanks again for the good response.
Sent from my PC36100
Click to expand...
Click to collapse
Yea,it would be nice if it were. Its kinda sorta quasi standard,so it HAS been done in some cases where its necessary,but often there are easier ways around it. Personally, I have allways thought that its a pretty stupid thing to make a piece of equipment that can fail due to a bad flash. The people who designed many of the flash memory chips seemed to agree,and they added something called a "boot block" to many,but the way its implemented,when its implemented doesn't fully protect you from a bad flash. Its even worse now that everything is in ball grid array chips soldered down to the board.

[Q] How to Brick your EVO

What I would like to compile is a list of things one could do to brick there phone. One way is if you lose your RSA private keys, what else can cause you to walk around with a paper weight?

flashing a radio image from another phone, especially GSM. It will actually fry the circuits. Saw someone do that in the Hero forums (didn't check what hero a rom was for and literally toasted it. Completely dead.) I don't think there are that many other ways to truly brick the phone beyond repair. There are plenty of ways to soft brick, but generally if the phone turns on, there is at least some way to fix it, though it might be out of reach for less technical users.

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?

Is it possible to recover data from a truly bricked phone?

I used these searches before compiling this thread;
"how to recover data from a bricked SGN"
"data extraction from a SGN that will not boot"
"removing the HD from samsung galaxy nexus"
These searches did not yield results that replicate my situation. The only search that resulted in many entries were for people with "bricked phones" that (at least somewhat) responded to input. I associate the term "bricked" with a phone that does not respond to input, or show any indication of getting power.
My phone is a Samsung Galaxy Nexus on verizon wireless. It has been rooted and is running a custom ROM by...AOKP i think. I had some assistance each time I rooted and updated my ROM.
Here is my problem, what caused it,my troubleshooting steps, and what I'm trying to do. My phone was partially submerged in water for an unknown amount of time. The battery and SIM were removed and kept in a water proof container within an hour of submersion. The water damage indicator stickers (on both the battery and the phone have not been triggered). About 24hrs later, the phone was placed in a zip lock bag with 4 desiccant silica gel packs where it will remain for the next 24. Per vzw's tech support, I tried to power the phone on using the charger and the battery removed. No change. Verizon was not advised of the partial submersion, only the non triggered water damage stickers. This phone is under warranty and a replacement has been shipped. I confirmed that my contacts are backed up to google.
The reason for this post is, I have close to 30GB of pictures and videos that I stored on this device's "internal SD" that I want to recover. Looking through the searches I mentioned above, it sounds like this isn't so much a separate card, but more of a partition on the phone's HD. I have been told by vzw that neither their branch office tech support, nor their recovery/diagnostic team that analyzes returned phones has the capability to remove and return this data.
If someone here has hardware experience with cracking open a SGN and swapping the "internal SD card" I would greatly appreciate any information available for this task.

if it cant turn on, you cant retrieve data.

Zepius said:
if it cant turn on, you cant retrieve data.
Click to expand...
Click to collapse
Well..OK. I'm not ready to give up just yet. When my desktop PC's power supply failed, the PC was unusable, and didn't indicate power. I swapped that out and it now it works fine. This seems like it could be a similar situation. I at least want to exhaust every option I have before throwing in the towel.
Those 30GB contain hundreds of pictures of the first 2 years of my kid's life.
It seems to me that data recovery should still be possible if an replacement power source is utilized. Maybe more than just the power source has failed. Maybe every other hardware component in my wet phone has failed. But maybe, that "internal SD" is recoverable.
If anyone here knows what the "internal SD" looks like, and has successfully swapped one, I'll risk it. I know I can't trust vzw with such a task.
I realize this is a developers forum, and I'm asking for hardware failure advice. If anyone can refer me to a different forum that is more specialized to my specific task, I'll gladly take my trouble there.
Thanks for reading,
Jef

you're assuming 1 thing. the nand that houses the storage is in good health. When water is introduced, you have the unknown factors of what it does to circuitry.
im sure there is a ifixit teardown showing where the nand is. The problem is its soldered to the mainboard of the phone. You might be able to unsolder it, but thats a stretch.

Zepius said:
you're assuming 1 thing. the nand that houses the storage is in good health. When water is introduced, you have the unknown factors of what it does to circuitry.
im sure there is a ifixit teardown showing where the nand is. The problem is its soldered to the mainboard of the phone. You might be able to unsolder it, but thats a stretch.
Click to expand...
Click to collapse
Thank you very much Zepius. I googled "ifixit teardown samsung galaxy nexus" which lead me to a page (that I'm not able to paste here as a new user).
which is exactly what I was looking for. I wouldn't go so far as to say that I'm assuming the nand is in good health, just wishful thinking.

Anncoco - sorry, I don't remember what I did with this. It's been about 4 years, and this was 3 phones ago. I think I had some of the photos backed up somewhere else, enough that I never went to the trouble to disassemble the Nexus. From my notes - I remember the phone did not indicate it was getting power when plugged in.

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.