Related
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.
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,
Captivate Glide i927 replaced cracked screen
I replaced the cracked screen assembly and installed a new ribbon. The lower lights (home, search, back button etc) work and also the keyboard lights. The ATT chime sound works too but the display does not light up when powered on.
Connected the phone after replacing ribbon/ screen to the comp for Kies to back up and it is saying the phone is locked. It is the lock code that you set to keep others from accessing. Since the display does not light, the correct code can not be placed in. Can someone please place a picture of the unlock screen mode here? The display touch pad works so if the position of the numbers can be acquired, this may help me to get the phone files accessed and reset hoping to get the display working.
The phone is not rooted and upgraded to the ICS as of October 2012.
Up $86 for the ribbon and new screen and the repair shops want $100 plus the cost of possible parts needed. Would like to try my best so this route can be avoided.
Cheers,
Robert
By now the phone SIM is locked out. I believe there is a way to reboot the phone through a computer?
mer80cedes said:
By now the phone SIM is locked out. I believe there is a way to reboot the phone through a computer?
Click to expand...
Click to collapse
The only way I can think of is rebooting via adb. If you're not rooted (the "reboot" command in shell requires root, i don't know if "adb reboot" wants it), or haven't even turned on USB Debugging at all, then you're doomed.
However, since Odin-ing is not that hard (only requires several key pressing), you could try Odin in a custom recovery (or not, if you already have one), back your system up to external SD in tar or other formats, and then extract the data you want from the backed-up packages (I've done this with tar packages). If you ever need the screenshot of a particular version of recovery, ask again in this thread and I think we'll be more active (and easier) to help.
Sent from Samsung Captivate Glide @ CM10.1.2
AndyYan said:
The only way I can think of is rebooting via adb. If you're not rooted (the "reboot" command in shell requires root, i don't know if "adb reboot" wants it), or haven't even turned on USB Debugging at all, then you're doomed.
However, since Odin-ing is not that hard (only requires several key pressing), you could try Odin in a custom recovery (or not, if you already have one), back your system up to external SD in tar or other formats, and then extract the data you want from the backed-up packages (I've done this with tar packages). If you ever need the screenshot of a particular version of recovery, ask again in this thread and I think we'll be more active (and easier) to help.
Sent from Samsung Captivate Glide @ CM10.1.2
Click to expand...
Click to collapse
Thank you AndYan.
This Captivate has only been upgraded to the Sandwich version. Non-rooted nor modified in any other way. The only reason to remove the files is due to it having solar cell module prototype designs and concepts on it (Reason why it can not be shipped out for professional repairs). Since most of the information was wrote on paper, it's best to just wipe the phone out completely to get it back to working condition for use again.
This is quite interesting learning about programming and such since I have never done this before. Just like building cars, took many many years to do and this programming is just another cool thing to learn about
It takes a special knowledge and experience to understand the programming of Odin and phones which I do not comprehend, I will be destroying the motherboard with a hammer and tossing it out. It is way too much to understand how to set coding and such. Best off investing in another phone and moving on.
The parts that will be saved if anyone can use will be the ribbon strip and also brand new display screen.
Paid $86 for the display and will sell for $75 free shipping with insurance.
Ribbon strip will be $20 free shipping with insurance. If both are wanted $95 free shipping.
Since I do love the Captivate so much another will be purchased.
mer80cedes said:
It takes a special knowledge and experience to understand the programming of Odin and phones which I do not comprehend, I will be destroying the motherboard with a hammer and tossing it out. It is way too much to understand how to set coding and such. Best off investing in another phone and moving on.
The parts that will be saved if anyone can use will be the ribbon strip and also brand new display screen.
Paid $86 for the display and will sell for $75 free shipping with insurance.
Ribbon strip will be $20 free shipping with insurance. If both are wanted $95 free shipping.
Since I do love the Captivate so much another will be purchased.
Click to expand...
Click to collapse
You mean you smashed your Glide?! God, I just had mine 5 days ago. Anyway, hope my tip still helps when you're in any smaller trouble next time.
AndyYan said:
You mean you smashed your Glide?! God, I just had mine 5 days ago. Anyway, hope my tip still helps when you're in any smaller trouble next time.
Click to expand...
Click to collapse
No way lol! Only the mother board will be smashed to save the data on it from being used again. All of the other parts will be saved since another Captivate will be getting purchased.
mer80cedes said:
No way lol! Only the mother board will be smashed to save the data on it from being used again. All of the other parts will be saved since another Captivate will be getting purchased.
Click to expand...
Click to collapse
That's still sad to see. Why not just solder off the storage chip, somehow destroy it, and find a similar model chip to replace it?
EDIT: I guess the Samsung-proprietary partition table and some data on special partitions like EFS are not reconstructible on a blank new chip. Then you did the easiest choice possible.
Sent from Google Nexus 4 @ CM10.2
Is it cool for someone to take a photo of their Captivate i927 when it is at the display for the personal unlock code (PIN). It will make a good reference point enough to possibly use my touch screen to unlock my cell to reboot. Just have to get the location of the numbers and also the OK button.
After many hours research (great learning experience), the phone was done on master reset without needing to see the screen. At least now it can be sent out to get repaired without the personal information being potentially taken by another.
Done
mer80cedes said:
After many hours research (great learning experience), the phone was done on master reset without needing to see the screen. At least now it can be sent out to get repaired without the personal information being potentially taken by another.
Done
Click to expand...
Click to collapse
Woohoo, so no need to smash anything? You did an awesome deed to keep a nice phone alive
A friend recently sent me her "retired" Galaxy Note II. She replaced it because at some point the screen stopped turning on altogether, but she still wanted me to see if I can salvage it somehow. I've tried, with no luck, and searches on the topic don't seem to suggest any solutions other than the fact that it may be a hardware issue. While I can accept this possibility, I'm really hoping that it is not the case because at this point I don't think it would be worth investing the time and money to buy the parts, learn how to replace them, and attempt it. If anyone has any ideas I'd be very grateful. Here are the symptoms:
The display NEVER turns on. It is in a constant state of pitch black.
The sounds are working fine. When I get an email, for example, it notifies me.
The hardware button works
The software buttons do not work
Upon connecting the device to a monitor, keyboard and mouse, the monitor works, however the keyboard and mouse do not. (I use the same monitor, keyboard and mouse with my Galaxy S4 and they all work fine.)
Touch interaction with the screen is working properly. Using the monitor, I am able to use the device, but it is very tricky, as it is simply a matter of trial and error. I tap on a black screen and have to look on the monitor to see if I hit my target.
The device is on the stock TouchWiz that came with it, and is not rooted. Since I am pretty sure that doing any mods without a working display would be more difficult than I could tolerate, I opted to take an OTA instead, despite the fact that it may make rooting and flashing ROM's impossible in the future. I hope I didn't screw myself by doing that but I had to make an executive decision. Here is what I've tried so far:
Factory reset
Update to the latest software (Android 4.3)
Pulled battery, held power button for 10 seconds while battery was out, replaced battery and powered device on.
I'd greatly appreciate any suggestions. Ideally, here is what I'd like to happen: get the display to turn on and restore functionality to the software buttons. This may not be possible without replacing some hardware components, which as I mentioned is not an option, but if it is I'd really like to give it a shot. Thanks in advance for any suggestions.
My initial guess would be a digitizer failure...
A phone drop or water damage can easily render a phone dead...
You have the option of replacing the screen and digitizer at a cost of about $225.00 for the needed parts...but it's still no guarantee that the fix would be 100% successful...
My honest opinion is this...
Given the unknown history of the device...you are taking an expensive chance in attempting a repair...
And given the age of the device....the repair if performed by a qualified repair service would push the cost very near to the overall value of the device...
For the same dollars spent...you can obtain any number of working devices and save yourself the hassle...and the unknowns associated with a repair that will likely work...but again may not...
You are of course free to attempt the repair...but....
The skill level needed to perform a "proper" repair of the device is high...and you would need to study up on the process extensively before cracking open that case...
If I were in your situation...the choice would be to sell the device for parts....and put that cash back into a working device...
Others will chime in I'm sure with their recommendations....but I would choose to move on...g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
gregsarg said:
My initial guess would be a digitizer failure...
A phone drop or water damage can easily render a phone dead...
You have the option of replacing the screen and digitizer at a cost of about $225.00 for the needed parts...but it's still no guarantee that the fix would be 100% successful...
My honest opinion is this...
Given the unknown history of the device...you are taking an expensive chance in attempting a repair...
And given the age of the device....the repair if performed by a qualified repair service would push the cost very near to the overall value of the device...
For the same dollars spent...you can obtain any number of working devices and save yourself the hassle...and the unknowns associated with a repair that will likely work...but again may not...
You are of course free to attempt the repair...but....
The skill level needed to perform a "proper" repair of the device is high...and you would need to study up on the process extensively before cracking open that case...
If I were in your situation...the choice would be to sell the device for parts....and put that cash back into a working device...
Others will chime in I'm sure with their recommendations....but I would choose to move on...g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
Thanks for the reply, and sorry I didn't see it sooner (I always forget to subscribe to threads). I figured this was probably not a fixable problem (at least not easily/economically fixable). But I wanted to see if there were any quick fixes I could try, and it sounds like there aren't. With that said, if anyone does want it for parts I'd let it go for a reasonable price (considering the damage and lack of functionality) through Swappa. (Sorry if I'm not supposed to make these kinds of offers here, if that is the case I'll gladly remove it.)
Hi all, I have a problem with my stock T-Mobile US S9. A few months ago this weird thing happened where if I turned on my screen immediately after it turned itself off, only the top few lines would be visible. The whole screen would take input, but you could only see a little below the status bar, maybe. If I waited a bit and then turned the screen on, it would work normally, with the whole screen visible and looking fine.
It's gotten progressively worse to the point where this happens most of the time I turn the screen on. However, I've found two workarounds:
1) My Always On Display is set to turn on when I tap the phone. If I do that, the AOD works as normal, and if I then turn on the phone screen the phone screen works fine. This only works when Always on display is set to turn on on tap. It does not work if AOD is set to always be on.
2) If, when my screen is glitching out I hold the screen up to a reeaally bright light (like inches from a lightbulb), the rest of the screen turns on. It's weirdly green tinted and kind of stuttery.
Turning off automatic brightness does not fix this issue. If tried booting in safe mode and even factory resetting the phone. Issue still persists, including on screens like when the phone enters recovery mode.
The fact that I can get the screen working normally using workaround #1 makes me think this is a software issue, but the fact that it happens on the recovery screen makes me think it's pretty low-level. Any ideas? Anyone else had a similar issue?
I gave Samsung tech support a call and the level 1 tech I spoke with seemed to think that it was a software issue and that I should bring it in to be looked at by a technician. I'm in Maine at the moment and there's no Samsung or UBreakIFix stores within two hours, so she suggested taking it to Best Buy to look at. Not amazingly helpful or surprising.
If it's a software issue though... I mean this is my fourth Android phone and I've rooted and flashed ROMs on all the previous phones anyway. I don't want to lose Samsung Pay, so I'd rather not unlock the bootloader, but is there a way to flash the stock operating system or something? The exact model number is SM-G960U
It's a firmware or hardware issue not software as a reload* would have fixed it.
The firmware has been corrupted (needs reflashed) or there's been a hardware failure.
Best to send it in for repair or take it the a Samsung Experience Center as they can reflash the stock rom and have advanced diagnostic tools.
*make sure all system apks are running on factory load and have not been updated after the reload.
Updates, destroyers of worlds...
blackhawk said:
It's a firmware or hardware issue not software as a reload* would have fixed it.
The firmware has been corrupted (needs reflashed) or there's been a hardware failure.
Best to send it in for repair or take it the a Samsung Experience Center as they can reflash the stock rom and have advanced diagnostic tools.
Click to expand...
Click to collapse
If that’s really necessary I’ll do it. But the closest place is out of state and when I called them said it would take 4 hours just to do a diagnostic. That plus the round trip... if there’s a way I can save some time, I’d like to.
For example, if one possibility is a stock firmware reflash, that’s something I’ve never done before on a Samsung device, but not very different from things I feel comfortable doing. I've flashed roms and rooted many android devices in the past. From a preliminary search , it looks like there's even a leaked tool online to do so from Samsung called Odin and that I just need to find the latest SM-G960U image with the right "csc" code for my carrier (I think TMB for T Mobile US). What would be even better is if one of those diagnostic tools you mentioned leaked the same way that Odin did.
Any recommendations on either diagnostic software or firmware reflashing? Or would you strongly advise leaving that kind of thing alone? I would like to still use things like Samsung Pay at the end of all this.
jptiger said:
If that’s really necessary I’ll do it. But the closest place is out of state and when I called them said it would take 4 hours just to do a diagnostic. That plus the round trip... if there’s a way I can save some time, I’d like to.
For example, if one possibility is a stock firmware reflash, that’s something I’ve never done before on a Samsung device, but not very different from things I feel comfortable doing. I've flashed roms and rooted many android devices in the past. From a preliminary search , it looks like there's even a leaked tool online to do so from Samsung called Odin and that I just need to find the latest SM-G960U image with the right "csc" code for my carrier (I think TMB for T Mobile US). What would be even better is if one of those diagnostic tools you mentioned leaked the same way that Odin did.
Any recommendations on either diagnostic software or firmware reflashing? Or would you strongly advise leaving that kind of thing alone? I would like to still use things like Samsung Pay at the end of all this.
Click to expand...
Click to collapse
If it's under warranty let Samsung deal with it. A good tech with experience is invaluable.
Rather then waste time the extra ride might end up being the easiest solution. You could also next or 2nd day it to the center and back, make sure it's insured and packaged well.
blackhawk said:
If it's under warranty let Samsung deal with it. A good tech with experience is invaluable.
Rather then waste time the extra ride might end up being the easiest solution. You could also next or 2nd day it to the center and back, make sure it's insured and packaged well.
Click to expand...
Click to collapse
That makes complete sense for something under warranty, but unfortunately my phone isn't. The S9 is about three years old now, and the Samsung rep was quick to tell me that the device was no longer covered. It looks like a mail-in repair service would cost about $175, which I'm theoretically willing to pay, but not if I can just handle on my own for free.
jptiger said:
That makes complete sense for something under warranty, but unfortunately my phone isn't. The S9 is about three years old now, and the Samsung rep was quick to tell me that the device was no longer covered. It looks like a mail-in repair service would cost about $175, which I'm theoretically willing to pay, but not if I can just handle on my own for free.
Click to expand...
Click to collapse
In that case you have nothing to lose by reflashing it. Hopefully that gets it.
Otherwise it be hardware... probably a good chance this actually the cause.
The good news is the 9's are available for a couple hundred in good condition if need be.
I was considering getting the 9 as a second phone (have the 10+) as the 10+'s haven't come down much in price.
Samsung current lineup sucks.
Huh. Well, before reflashing, I tried something I found other people suggesting for a related problem: https://eu.community.samsung.com/t5...t-bars-black-screen-issue/td-p/1745470/page/7
It's an app called OLED Saver. It's not perfect, the screen still has an odd green tint to it unless I use one of the tricks I was describing above. But I no longer have the issue where most of the screen isn't visible.
I might try reflashing anyway, will post results if I do.
Yeah, no joy. Reflashed by downloading the latest firmware using Frija for SM-G960U with TMB as the CSC, and flashed using Odin v3.13.3. If anything the problem is slightly worse now, but OLED Saver still mostly seems to fix it. I guess it's just a hardware issue with a weird software workaround...
Same type of brightness problem here as you describe, on my new S9 (G960U) - - Model starqltesq - CSS XAA
The product is under guarantee, but as it is imported from Hongkong to France, I don't have accesss to the Samsung local representatives and have probably to send it back to Hongkong ...
I will keep you updated if I learn something about the problem and the solution ....
Wiping the cache partition stopped this happening for me for around 24 hours but it came back this morning. On the Note9 forums someone posted that setting animations to .5 in dev options fixes this. I will try it.
Bhonka said:
Wiping the cache partition stopped this happening for me for around 24 hours but it came back this morning. On the Note9 forums someone posted that setting animations to .5 in dev options fixes this. I will try it.
Click to expand...
Click to collapse
Disable animations instead. It wastes resources. Personally I like seeing a fast, snappy OS do it's thing with no middle man needed. Lol, you end up waiting for the animations rather than the OS.
I've heard of people flashing custom roms and that resolved the issue permenetly, but can't find anyone willing to give some real feedback. I posted a topic asking this question, but haven't gotten any replies..
Not very helpful, but a work around could be to use Screen Filter
I temporary fixing my S9+ green screen issue by uninstalling the NFC module.
Unfortunately, this option make us cant charging the phone.
Maybe some one expert in hardware mod can do better.
Eve&Me said:
I temporary fixing my S9+ green screen issue by uninstalling the NFC module.
Unfortunately, this option make us cant charging the phone.
Maybe some one expert in hardware mod can do better.
Click to expand...
Click to collapse
Hey could you explain what exactly did you uninstall and how?
After uninstalling it wireless charing stopped working or what did you mean by cant charge the phone?
Did it fully resolve the green screen issue?
Some people noticed that problem after upgrade Android 9 to 10.
At this moment we have some facts:
1) OLED saver temporary solves problem
2) disconnect NFC module solves problem, some people on xda and on the yt confirm that
3) heating back cover using heat gun can help - I Discovered that some weeks ago
Interesting comment from the yt:
Sour Words
Sorry to say this, but green screen issue is a hardware fault not something an update can fix. One of the updates from Samsung is causing the CPU to over heat and in return permanently damaging the oled screen. Not only that but also compromising the battery as well. The only fix is the replacement of both the oled screen and battery. This repair is entirely the fault of Samsung due to a faulty update that over works the CPU capacity. Therefore my advice is for you to return your device back to Samsung and lodge an assessment request. They charge a small fee for the assessment, but the entire repair should be compensated by Samsung. Be firm and keep the pressure via emailing them to insist on Samsung covering the repair costs. My Note 9 is almost 3 years old when green screen issue happened. They fixed the entire thing free of charge. But I kept firm and didn't let them bully me into charging me for the repairs, which was their fault in the first place. I must admit, my phone despite its age, is in perfect condition. Not a scratch on it. Which I know contributed winning my argument for the repairs. So if you have psychical damage, I doubt you will have a chance. Good luck to all who will give this successful method a go.
Click to expand...
Click to collapse
mreminemfan4ewver said:
Hey could you explain what exactly did you uninstall and how?
After uninstalling it wireless charing stopped working or what did you mean by cant charge the phone?
Did it fully resolve the green screen issue?
Click to expand...
Click to collapse
When we disassembly NFC Module, the phone will give LOW TEMPERATURE warning. And make us cant charge the phone