Related
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?
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.
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Top5a said:
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Click to expand...
Click to collapse
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
thorur said:
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
Click to expand...
Click to collapse
Did it die closely after the unlocking/flashing? Or a long time after? Or was the unlocking/flashing an attempt to save the phone? Ever get it fixed? I'm so anxious!
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
Well, thanks for the input! Makes me feel a better hopefully the emmc isn't completely fried. I just really want my files, and am continually irritated at myself for having been so stupid to not make backups.. although I have phones from 10+ years ago that have never completely died in such an unexpected manner. It's quite the agonizing wait for a JTAG programmer to come in the mail. If I can manage to get it to boot from SD, which I haven't been able to do so far, do you think it's logical for me to simply reflash the bootloader/CWM, then attempt boot? It shouldn't erase files, right?
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
I've also searched everywhere for a debrick image for 4.1.1 AT&T... anyone know where I can get one? All I can find are ones for 4.1.3 =\
EXACT same problem here, let me know if you find anything
(Btw, my phone also had the "power button stuck down" issue, but your phone will vibrate when you put the battery in if this is the issue.)
If I'm not mistaken you will be able to Odin to 4.1.1 while using the 4.3 SD card debrick (again this is just guessing)
Sent from my ATT Samsung Galaxy SIII using TapaTalk
I've tried the SD card debricks for 4.3, and still nothing happens. Yea, I also don't get vibrate. As a long shot, I actually installed the qualcomm drivers and ran the qdload.sh script to attempt to send a signal which kicks the phone out of that mode (works on some... I want to say, HTC, phones), but, yea, I think the emmc just failed somehow. I'm hoping that the failure is just in the bootloader segment, and that by jtag reflashing the bootloader area, I should be able to boot. Either that, or even if one of the memory sectors died, hopefully it's not the one with my data partition. I still can't believe this ! Out of all the electronics I've ever used, aside from a hard drive or two, I've never had something like a phone just kick the bucket with no warning. gha !
Also, thanks for all the tips and stuff, guys and gals. Tell me if you figure out anything, and I'll let you know if I get it fixed with jtag.
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
ZOMG SO RUDE > haha, j/k ;P Yea, no problem, dude/dudette! I know how it feels reading threads with no followup... I'm actually surprised that people have come out of the proverbial woodwork mentioning having similar problems to me ! It really sucks spending inordinate amounts of time reading threads and not arriving at a definitive conclusion... so, yea, I especially want to let people know if there is a fix, and/or how I did it.
So, with regard to what you said about the snapdragons not failing... yea. This is rekking my mind, tbh, because I've just never had a device insta-fail on me like this (aside from some old computer hard drives that were server backed up, but yea that's essentially par for the course on that medium [yay for S.M.A.R.T.]). Especially a device that I'd only had for less than 2 years, and though my GS3 has heavy usage, I treat it very well (no drops, water, etc.)... so, yea.
Also, a minority of people with whom I have spoken via the æther have also experienced similar emmc failures on i747s, as well ! Which I was not expecting. It's still insane, though, to believe that, out of such a small percentage of phones that could potentially experience SDS, and then which ones actually do experience it... and then to not even have an i9000 and /still/ experience it on an i747... I feel as though I've won the lotto. Except ****ty.
I'm waiting on parts to come in, then surgery will commence.
Did you try going into download mode? If you can so that then the phone is fine. Another thing is try reflashing stock Odin which will erase msgs and stuff but not music or pics unless u tick "repartition".
Sent from my SGH-I747M using Tapatalk
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [Samsung I747 V1.0.5095.46594]
Connecting to the dead body...OK
Detected dead body ID: 0xhexhereisOK[redacted] - CORRECT!
Set I/O Voltage reads as 1.81V, TCK Frequency is 1 MHz
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0100 (000000, 0x000400000000 Bytes = 16.00 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (000000, 0x000000080000 Bytes = 0.50 MB)
No Resurrection Data is available for the eMMC Chip with Capacity = 16.00GB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x0003AB3FBE00
Had to reduce the speed to that 2MHz/1MHz to get communication to work. So, 0x51 is a DCC power failure problem... but it is able to detect the initialized chips. So.. not really sure how to proceed at this point. I haven't checked the signal quality on my NRST line, which apparently can cause problems. Some people have increased the voltage from 1.8 to say 1.9, but doing something like that requires me to actually make my own resurrection file, which I haven't had the time to do yet.
Anyone seen a problem with something like this before?
The 000000 is somewhat unsettling, as the chip is apparently supposed to report some ID#? Although, the failures that I'm getting don't seem to be the typical ones that happen when the emmc becomes completely toasted.
Oh, yea... I can't seem to figure out wth is up with --> WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Like..... ??? I think I'm using the most up to date resurrector?!
EDIT: Dumping out the entire contents of the emmc (haven't had errors so far, but it will take a while at 1 MHz), into a bin file (this avoids the bad sectors in the bootloader).
Does anyone know what to do with the resultant *.bin file? I think that if I got another surrogate GS3, I'd be able to write that onto the phone, essentially cloning my dead phone. I'd like to avoid having to do that, though -- does anyone know how to write one of DCC bin jtag file dumps into a readable file system?
I'm having trouble searching through the forum because of the multiple types of bricks people are facing.
I simply restarted my phone today and it will now simply not boot/charge/go into recovery/does not get to logo.
It acts very much like the Sudden Death Syndrome which my previous handset had suffered from, but I checked this one when I got it (2-3 years ago, can't even recall when) and it had the corrected eMMC or whatever it was called.
It's what the community would consider a hard brick, since it's impossible to interact with it from the outside. I've been reading as many threads as possible to find something similar, but was unsuccessful.
I have however stumbled upon the UnBrickable SD mod that works on Exynos 4412 chips, which my device has. I can't however find a thread about it specifically for the Note 2 for the life of me.
There is one for the Note 3 here for example: http://forum.xda-developers.com/showthread.php?t=2476353
Can anyone point me in the right direction? This seems like the correct solution for me, but I can't find any more info on it and it was extremely sudden too, since it was working fine before the reboot of death.
Thanks for any help!
I'm guessing there's no such thing for the Note 2 then? Not sure what to think - it is an older device after all.
Hi everyone, long time XDA lurker, first time poster here. Hope I'm in the right spot.
I have a 3XL that bricked overnight similar to what I've seen on other posts (for example: https://forum.xda-developers.com/t/...Rj7bE_8k87pI2zaSnIskWwmvsbMpMeVBlmWrHPsqhUY0c)
Long story short, can't get it to boot, isn't recognized by fastboot/adb. I started following this guide https://www.thecustomdroid.com/qpst-flash-tool-download-usage-guide/ and my phone is recognized, but like one user in the xda post (above), I don't know where to get the raw firmware file that I need to move forward (need elf or mbn file with maybe some xml files?). I've been searching high and low and this is where I'm stuck. I've seen some mentions about needing to get these files from someone who actually has a working 3 XL, but I'm not sure if that's the only option. Does anyone have any insight that could help me move forward?
And on that note, if I manage to recover the phone using this method, will it be recovered right back in the state it was, or will it be freshly formatted? Again, I've read lots on this, but I can't seem to get a straight answer. To be honest, while getting the phone working again would be amazing, my priority is recovering the data from the phone, so if this QPST recovery will only end up giving me back a naked phone, then I'm open to alternatives.
Any help is appreciated! Thanks!
Currently in the exact same boat as you, unfortunately...
I'm also mostly interested in just getting to my data, although having a working phone again would be nice.
I can get the serial port to show up in qpst but I'm pretty much at a stand still from there, can't get anything else to work.
Have you had any luck??
I'm in the same position as you guys, pixel 3 XL bricked, bootloader locked, no recovery just Fastboot Mode (With OEM Locked, any command wil not work there.. thank u so much Verizon), I was looking and this seems to be the only way but I can not find any dump from a pixel 3 xl working to flash in EDL Mode, if you guys can find something let me know, I'm gonna try to find it on my side too
Unfortunately I never found a solution. QPST recognized the phone, but could never successfully connect to it. While Googling the issue, I noticed that this has happened to a number of other people too, and it often seems to coincide with updates, so it could be linked although good luck getting Google to admit to that.
I ended up swapping the phone out for an S21. This is the first phone that has even bricked itself so bad that I couldn't recover anything from it, and seeing how it has happened on many generations of the Pixel line, I wasn't very tempted to get another one unfortunately.
Chiming in with a similar story to the rest of you folks.
I'm an experienced user that knows his way around adb/fastboot and flashing custom ROMS and whatnot, but in this case I have a completely stock Pixel 3XL that I woke up to find in this hard bricked EDL state. I am up-to-date with any and all updates for the OS and I usually pull those down on release day or very shortly after. No idea what update could have caused this, but in my case, I am overseas with a bricked cell phone - SUCKS.
Hopefully the QPST files can be located so that we can recover from this bull****.
I know some people with a working 3 XL. Are there instructions on how to extract the necessary files from a working phone to flash through QPST on the bricked phone?
I just ordered a 3 XL for my daughter and I'm getting scared seeing these stories. Is it just aged hardware related? Or is it update related? It's weird that it seems to be happening over the last few months on the 3 series which makes me think its either related to an update that rolled out or just mileage until failure of the chips?
I have had for two years a used one year old 3XL and had no problems. If someone has instructions, I would be glad to extract what is needed. At this phase it has only been unlocked to use DNS66 though I consistently ROM'd all my earlier phones. Age related ;-)