I have what I assume to be a hardware problem here.
I have a i9505 motherboard that won't display any image or accept touch input. I've tried it another phone (where it didn't work either), and tried the motherboard from that phone in both (and that worked in both phones). So far as I can tell the problem is with the motherboard, not the screen.
I'm pretty sure the motherboard's not completely dead, as it makes the startup sound, I can flash an image via Odin, been able to get into ADB both in Philz Touch and Android proper (although can't authorise the connection there), can access files on it when connected to a Windows PC, etc.
Does anyone know where the problem could lie? I'm assuming I should just throw the motherboard away, but would be great if there's some way to fix this. Throwing it away would leave me with a working case/screen I can't use.
Thanks.
Related
If anyone can offer any advise/assistance, it would be greatly appreciated!!
I have 2 AT&T branded 8525 phones. Both have issues and I assumed I could make one good working phone from them.
Phone 1 had a touchscreen issue. It is not responsive what-so-ever. I tried the credit card trick, cleaning out the edges, hard reset, soft reset, etc... nothing seems to make it respond at all. Reflashed the ROM, but of course I am stuck at the "Touch Screen to Begin" screen.
Phone 2 works just fine, but when plugging in the mini usb charger the screen starts to fade to white (with many vertical lines appearing...but eventually the screen goes to white). If you wiggle the charger, it will clear up, but then go back to the fading white screen. If you leave it long enough on the white screen, it will lock up.
So I thought I could take the known good LCD from phone 2 and put it in phone 1. Yesterday I took both phones apart to do this. I placed the good LCD in the phone that had the possibly bad LCD. Put it all back together and found the touchscreen still does not work . So perhaps the LCD was fine and it was something else. I then decided to just take the motherboard from phone 2 and put it in phone 1 along with the LCD I just replaced (effictively moving the lcd and motherboard over to a new case). Same issue... touchscreen does not work. I assume moving the parts around eliminates a loose connection of some sort. I did make sure the ribbon cables were properly aligned and secured well. I am guessing something is wrong on the motherboard.
Does anyone have an idea of what could be wrong to prevent the touchscreen from working?
Oh...moving both the motherboard and lcd with the whitescreen issue(phone 2) over to the other phone (phone 1) casing didn't change anything at all either...so I assume that is not a connection issue with the cables. I also looked closely at the mini USB connector on the motherboard to see if there was bad solder or something that was making it act up. I am guessing bad hardware in both phones, but was hoping I could somehow make one of these phones work and junk the other. Sounds like I may have to junk both as the cost of parts is probably is silly.
Thanks for any help!!
Eric
Well I have an issue with my S4 GT-i9505, when it starts up it makes all the right noises and lights up the LEDs but the screen is black and lifeless. I installed Kies and it installed a firmware update, I had already done a factory reset using instructions dealing with no screen access. I have taken it to a non samsung service centre in melbourne and they said it was the motherboard, they claim to have tried several other screens and they didnt work so assumed it is the motherboard, but it is able to be found by PC and Kies and has upgraded to the latest firmware. So i dont think it is the motherboard, still the screen remains blank.
Does anyone know what causes this and if changing the motherboard or is there a graphics card that may fix this.
[?] on board etc
motherboard
Well i found a shop with a test motherboard who slipped it in and the phone worked fine. So now i have to find a motherboard.
Guys, care to help me out here? I have this i9505 in front of me. It was brought to me because it would randomly stop playing audio. I noticed that this audio issue only happens after the device wakes up from sleep. No sound at all after wake up from sleep. And Video Playback (SdCard and YouTube) stutter goes along with the problem. Here's what I did to get rid of this issue:
- Factory reset in Samsung Stock Recovery; didn't help.
- Flash stock tar.gz via Odin; didn't help. (Yes, I used the correct one matching my model)
- Flash CM to rule out issues with Samsung specific software/drivers; didn't help
So I concluded that there must be a hardware issue. Since the device looked pretty worn out and sticky, I though maybe dust or something else like a liquid could've destroyed the internals. I dissassembled it but to my surprise it looked very clean. So I reassembled it. Plot twist; now it wouldn't boot anymore. It passes the Samsung splash screen and gets into the Bootanimation. But within seconds into it, it reboots. This goes on and on and on unless I take out the battery. I know what you're thinking, but listen; I disassembled/reassembled almost 70 devices, almost half of which iPhones (Yes, I keep track of it, since I charge people for my work) and chances that I messed up something are very low. Not saying impossible, but you get the point. I exclusively change parts. Dispalys, middle frames, backcovers, batteries, microphones, cameras, microsd/sim trays, you name it*. Anyway.
Now, no matter what I do, I can't boot into the OS. Download Mode, Recovery, be it stock TWRP or CWM just work fine. When I format the internal storage via TWRP/CWM and boot up the device on stock, no folders are created on it. But when I flash a custom ROM, be it TW, CM or AOSP/A, I sometimes get into the OS and the standard Android folder structure is created. But the device is then pretty much unresponsive. I can barely navigate the OS before it shuts down again.
What could be the issue here? What could I have damaged during reassembly to cause these issues? But on the other hand, the S4 has a fairly simple architecture and I use an ESD pad, ESD wrist straps and only use plastic tools to pry off connectors. I even watch the humidity in my room for the record.
I gave this guy a replacement Nexus 5 already after he brought his S4 to me. That's what I usually do when I can't tell how long a "repair" could take. If it turns out that I caused the problem, of course he'll get to keep the device.
EDIT: I forgot. I have some spare parts for the i9505 and replaced one at a time to rule out malfunctioning hardware. So far I replaced every part except mainboard (Sim/SdCard Slot), Display and any cable connected to these two parts only to end up with the same problem.
nitrous² said:
Guys, care to help me out here? I have this i9505 in front of me. It was brought to me because it would randomly stop playing audio. I noticed that this audio issue only happens after the device wakes up from sleep. No sound at all after wake up from sleep. And Video Playback (SdCard and YouTube) stutter goes along with the problem. Here's what I did to get rid of this issue:
- Factory reset in Samsung Stock Recovery; didn't help.
- Flash stock tar.gz via Odin; didn't help. (Yes, I used the correct one matching my model)
- Flash CM to rule out issues with Samsung specific software/drivers; didn't help
So I concluded that there must be a hardware issue. Since the device looked pretty worn out and sticky, I though maybe dust or something else like a liquid could've destroyed the internals. I dissassembled it but to my surprise it looked very clean. So I reassembled it. Plot twist; now it wouldn't boot anymore. It passes the Samsung splash screen and gets into the Bootanimation. But within seconds into it, it reboots. This goes on and on and on unless I take out the battery. I know what you're thinking, but listen; I disassembled/reassembled almost 70 devices, almost half of which iPhones (Yes, I keep track of it, since I charge people for my work) and chances that I messed up something are very low. Not saying impossible, but you get the point. I exclusively change parts. Dispalys, middle frames, backcovers, batteries, microphones, cameras, microsd/sim trays, you name it*. Anyway.
Now, no matter what I do, I can't boot into the OS. Download Mode, Recovery, be it stock TWRP or CWM just work fine. When I format the internal storage via TWRP/CWM and boot up the device on stock, no folders are created on it. But when I flash a custom ROM, be it TW, CM or AOSP/A, I sometimes get into the OS and the standard Android folder structure is created. But the device is then pretty much unresponsive. I can barely navigate the OS before it shuts down again.
What could be the issue here? What could I have damaged during reassembly to cause these issues? But on the other hand, the S4 has a fairly simple architecture and I use an ESD pad, ESD wrist straps and only use plastic tools to pry off connectors. I even watch the humidity in my room for the record.
I gave this guy a replacement Nexus 5 already after he brought his S4 to me. That's what I usually do when I can't tell how long a "repair" could take. If it turns out that I caused the problem, of course he'll get to keep the device.
EDIT: I forgot. I have some spare parts for the i9505 and replaced one at a time to rule out malfunctioning hardware. So far I replaced every part except mainboard (Sim/SdCard Slot), Display and any cable connected to these two parts only to end up with the same problem.
Click to expand...
Click to collapse
It's clearly hardware damage. Some component on your motherboard. The audio problem is/was also hardware related. No software would cause that. My conclusion based on your info is that the motherboard already was damaged. Sound problems are usually a damaged motherboard. So the disassembly probably made it worse. Just bad luck. Maybe reheating/reflowing the audio chip will fix it. If not then buy a new motherboard and charge him that.
Yeah, was also thinking about a reflow. But it's strange that everything works. Download mode, recovery and I can mount and access every partition in TWRP/CWM. Let's see. I'm not sure if I'm gonna charge him. It sounds obvious on first sight that I caused it, sure. But I haven't given up hope yet.
Gesendet von meinem LG-H815 mit Tapatalk
I have a Galaxy S5 that belongs to my brother which has a cracked screen. It powers on fine and recently factory resetting itself but can't see the screen. I'm trying to recover photos from the device of my brothers son during the first year of his life. The photos are very important to him and I'm trying my best to recover them.
I'm using MobileEdit Forensics and other recovery software but having problems connecting to the device. I'm thinking it's because of USB debugging isn't enabled. Is there a command of the line code I can run to enable it?
Would replacing the screen be any benefit to me? Am I taking the right approach?
Thanks in advance for any help given.
Do you know if touching any part of the screen has any effect (even of you can't see what touching it does)?
Replacing the screen is an option, but it's an expensive option if there are other things that might/could work instead.
The reason I asked about whether the screen is still responsive is because if it is, you can simply get an MHL adapter from somewhere like ebay and use it to connect your device to a TV so that whatever is on the phone screen (even if you can't see it) will be on the TV screen. Then you can perform the retrieval from the phone by looking at the TV screen.
The MHL adapter I got to use with my phone cost me £5.
The galaxy s5 don't have a digitizer so probably if the screen is dead,then the touch function is too(as I know from my brothers note 3 witch has the same mechanism for the screen).
You said you did a factory reset on the phone.. If you did, wouldn't those pictures be deleted?
A good option is to try Samsung back up (I think it backs up pictures too) or other back up software the phone may have..
Another thing to try is if the phone have adb enabled then you could unlock it by:
Powering it on
Let it auto connect of to a wifi you have already given the password for it when the phone was workings (if WiFi was enabled last time the phone worked)
Log it to Samsung website and apply the'unlock my phone' option
Then connect it to the PC and obtain the pictures...
Tryed to see if the pictures are located in the SD card?
If nothing of this works then the only solutions remaining are repairing the screen or get it to a data recovery company..
Hope I helped you and good luck with it
Uh...The S5 *does* have a digitizer....In exactly the same way that *every* other touchscreen device ever produced does.
keithross39 said:
Uh...The S5 *does* have a digitizer....In exactly the same way that *every* other touchscreen device ever produced does.
Click to expand...
Click to collapse
It doesn't.. It reads touch events directly from the amoled screen.. The digitizer is just a glass for the s5.. It does nothing, the phone can work too if you just remove the glass and it reads touches normally
The digitizer is the part of the screen that tells the device *where* the screen was touched ie the 'grid reference' of the interaction. If the S5 doesn't have a digitizer, what replaces it...without the digitizer how is the S5 going to know what to do when you touch the glass at a specific point...which app/function is being selected at any given location on the display if the device can't tell the location of the touch?
---------- Post added at 09:01 PM ---------- Previous post was at 08:51 PM ----------
The digitizer part of the screen exists...pure and simple. It is usually bonded to the underside of the outer glass panel.
If as you say, the touch works without the glass, then it's built into the amoled display....but it *is* present and a part of the screen, regardless of what part of the screen module it's built into.
That *may* well have implications for the touch functionality.
If it's just the 'backlighting' that has failed, but the touch functionality remains, then connecting the device to a TV via MHL should work.
If the screen is totally dead, an MHL connection will be pointless, and a new screen is probably the only option. But as has already been mentioned, if a factory reset has been performed, the chances are that what you are trying to recover has already been erased.
Hello, guys.
Several days ago I bought HD2 with cracked screen, also stuck in Android bootloop (some Cyanogenmod ROM)
I don't even planned to make it work normally, planned to use it as spare parts for another HD2, but after reflash to a stock 3.14 - it booted up normally.
But Wi-Fi is dead, it simply doesn't turn on.
Link to a video:
youtu.be/4QglUj_CIvI
Anyway, I will replace display module as soon as it arrive to me.
So, does anyone have suggestions? Something tells me, it's a HW problem, not SW. Now device is dissasembled.
And there is no visible damage near Broadcom chip or somewhere else. No corrosion, no cracks, no overheating marks. Nothing.
Bluetooth is working normally, despite it's the same IC.
Any help is appreciated...
nearnull said:
Hello, guys.
Several days ago I bought HD2 with cracked screen, also stuck in Android bootloop (some Cyanogenmod ROM)
I don't even planned to make it work normally, planned to use it as spare parts for another HD2, but after reflash to a stock 3.14 - it booted up normally.
But Wi-Fi is dead, it simply doesn't turn on.
Link to a video:
youtu.be/4QglUj_CIvI
Anyway, I will replace display module as soon as it arrive to me.
So, does anyone have suggestions? Something tells me, it's a HW problem, not SW. Now device is dissasembled.
And there is no visible damage near Broadcom chip or somewhere else. No corrosion, no cracks, no overheating marks. Nothing.
Bluetooth is working normally, despite it's the same IC.
Any help is appreciated...
Click to expand...
Click to collapse
could be something regarding to your wifi antenna in your housing, the connector to it, or coaxial cable to the mainboard