I just recently replaced my screen/lcd/digitizer on my phone and my microphone no longer works. The microphone flex cable seems to be in good condition as the vibration still works. I'm stumped. I hate to go back to my buddies old phone.
outcold32 said:
I just recently replaced my screen/lcd/digitizer on my phone and my microphone no longer works. The microphone flex cable seems to be in good condition as the vibration still works. I'm stumped. I hate to go back to my buddies old phone.
Click to expand...
Click to collapse
If you're s-off you can RUU to rule out software but it's nearly impossible to tell online what would be causing it software wise. Even if the flex cable looks fine, it can still be damaged. Also, the cable could come loose while putting it back together. These are things we cannot tell from miles away though.
exad said:
If you're s-off you can RUU to rule out software but it's nearly impossible to tell online what would be causing it software wise. Even if the flex cable looks fine, it can still be damaged. Also, the cable could come loose while putting it back together. These are things we cannot tell from miles away though.
Click to expand...
Click to collapse
Unfortunately, my phone is s-on. If it is the flex cable, then shouldn't my soft buttons not light up as they are the same flex cable?
outcold32 said:
Unfortunately, my phone is s-on. If it is the flex cable, then shouldn't my soft buttons not light up as they are the same flex cable?
Click to expand...
Click to collapse
That is not necessarily the case. I would S-OFF and RUU though if you want to rule out software.
I have the same problem as the OP. No mic after screen replacement. Unfortunately, I replaced the screen, went S-OFF and to RUU 3.18 all in one fell swoop so I'm not certain if it's a hardware or software problem.
Update: After replacing the Nav Light/Microphone flex, works fine. (AT&T version)
Got from PhonePartsUSA, part number FLX-HTC-276
Related
Hi,
My phone has a problem, i hope someone can help me, it started about a month ago,
When i slide the keyboard the screen would freeze, the image would freeze or sometimes it would become like this:
http://www.esato.com/board/img.php?id=140762 ( this is not my phone its just a pic i found)
This problem would be solved it i gently slide the keyboard back in, the screen would be back to normal, sometimes i had to slide it out and it
alot of time to make it work.
Well, today i woke up, with the screen of my phone all messed up ( like in the picture), i slide it out and in alot of times but no luck.
I turned my phone off, when i turned it on, the screen doesnt lighted up or showed something, the phone just vibrates, i took off the battery and tried again but no luck.
I read somewhere that i could be the flex cable, so i ordered one, but its gonna take some time to arrive.
Anyone had this problem before that can help me?
I didn't encounter such problems on MT4GS yet. But being a slider phone enthusiast I could 100% say it's a flex cable thing since I encountered that problem more than a dozen times already on other phones(nokia).
Riyal said:
I didn't encounter such problems on MT4GS yet. But being a slider phone enthusiast I could 100% say it's a flex cable thing since I encountered that problem more than a dozen times already on other phones(nokia).
Click to expand...
Click to collapse
Thanks for the info , when my new flex cable arrive i'll let everybody know what was the problem.
ShadyGame said:
Thanks for the info , when my new flex cable arrive i'll let everybody know what was the problem.
Click to expand...
Click to collapse
I would strongly recommend that you get a cable with the speaker already soldered in place....
+1 to that, get as much pre assembled as possible, this is about the most pain in the butt phone I've ever had the pleasure to disassemble. Read the last few posts here!
http://forum.xda-developers.com/showthread.php?p=35109055
Sent from my HTC Vision using xda premium
GoPadge said:
I would strongly recommend that you get a cable with the speaker already soldered in place....
Click to expand...
Click to collapse
is this one okay?
http://www.ebay.com/itm/121037327256?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
ShadyGame said:
is this one okay?
http://www.ebay.com/itm/121037327256?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
Click to expand...
Click to collapse
Yup. That one has the speaker, it's the black bar at the top with the silver sticker.
GoPadge said:
Yup. That one has the speaker, it's the black bar at the top with the silver sticker.
Click to expand...
Click to collapse
Nice, that the one i ordered, thanks for your help, ill report later how everything went when i receive the flex cable
I know this thread is from quite a while ago, but how did everything go? I'm having a similar issue.
GoPadge said:
I would strongly recommend that you get a cable with the speaker already soldered in place....
Click to expand...
Click to collapse
thanks for this bit of advice.
Disassembling the front of the phone is a pain. I'm a fan of spending $40 on ebay on a broken phone (where the screen still works just fine) and swapping out the fronts. That will get you a new flex cable as well. Otherwise, you risk having to get a new flex cable *and* a new LCD.
Agreed. First time disassembling front I was scared not to OVERheat phone internals. I ripped in half trackpad ribbon, damaged lcd back cover and got a lot of problems from it.
Then I bought broken phone with good front, but dead LCD. Second time I just lost it, I heated phone so hard that I got burns on my fingers, but it was worth it, LCD glue came off soo nice.
So better to overheat, then underheat when disassembling front LCD.
My nexus was working fine, I received a call, answer it, after the call my nexus screen was unresponsive. After that the screen only shows a colored noise.
I thought it was the screen, but I replaced with a broken glass (working) screen a it have the same symptom. The problem seems to be a hardware one, I hard reset it, disconnect everything, replaced the usb board, but it looks is the main board the problem or (2 bad screens?)
Does anyone have seen this?
I attached a pic of the problem.
I would definitely say its a problem are you on stock are you rooted?
Sent from my Nexus 5 using Tapatalk
Pretty sure it's the display ribbon port or cable. I've seen this a few times in the last couple of months.
spinninbsod said:
I would definitely say its a problem are you on stock are you rooted?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm rooted on android L, but it doesn't seem to be software because as soon as I turn on the phone it shows the noise instead of the Google logo and android animation
Sandman-007 said:
Pretty sure it's the display ribbon port or cable. I've seen this a few times in the last couple of months.
Click to expand...
Click to collapse
What you call the display ribbon? The one that connect to the usb board on the bottom of the battery? Can it be replaced?
2fastkuztoms said:
I'm rooted on android L, but it doesn't seem to be software because as soon as I turn on the phone it shows the noise instead of the Google logo and android animation
What you call the display ribbon? The one that connect to the usb board on the bottom of the battery? Can it be replaced?
Click to expand...
Click to collapse
No the ribbon cable from the motherboard to the LCD. Yes it can be replaced.
Either the screen or flex cable. In extremely rare cases it could even be the motherboard.
Lethargy said:
Either the screen or flex cable. In extremely rare cases it could even be the motherboard.
Click to expand...
Click to collapse
I suspect a bad ground or something related with the cable. When I touch the cable the screen start working. Ordered the flex cable, let see if it fix it, i let you know.
2fastkuztoms said:
I suspect a bad ground or something related with the cable. When I touch the cable the screen start working. Ordered the flex cable, let see if it fix it, i let you know.
Click to expand...
Click to collapse
I've actually seen this happen when a device overheats (I'm looking at you Droid Razr >.>)
Custom Kernels sometimes have this issue as well.
However, if it's constant, a hardware issue is more likely, I'm just giving out a possible idea.
Beauenheim said:
I've actually seen this happen when a device overheats (I'm looking at you Droid Razr >.>)
Custom Kernels sometimes have this issue as well.
However, if it's constant, a hardware issue is more likely, I'm just giving out a possible idea.
Click to expand...
Click to collapse
About 5 or so people have had such issue. None were because of custom kernels (and I don't think overheating either). Either a replacement screen or flex cable fixed it for them. Hardware issue, happens.
Thanks to all.
Todays update:
The flex cable arrived today, installed it, assembled the rest of the phone and bingo! Phone is working fine!!!
Happy again with my nexus, i was almost convinced to jump to the g3 but I really love my red nexus.
I had the same issue reported here: http://forum.xda-developers.com/google-nexus-5/help/hbo-screen-death-t2811070
FlexCable was broken
Cheers
Tom
Hello,
I've had recently broke my XT925 and have question if it’s possible to bring it back to life...
Well from the beginning... I've had glass smashed and during tearing screen from the glass I damaged it, so I've ordered new screen with glass and digitizer. When it arrived, after putting it all together it appears that screen doesn't respond on any touch. My friend read somewhere that it could be solved by flashing the phone again(now I don't know is it truth, and right now it feels like one of the smallest problem I have).
I flashed my Milestone 2 and Droid 4 before so I didn't suspect it be so troubling now.
Because my Motorola had been updated to 4.4.2 and I couldn't find firmware in that version I've decided to downgrade the version to 4.1.2. I found some video with how to modify XML file to be flashable. Unfortunately the video is in foreign to me language (Spanish I guess) and at the time I don't realize, that phone has to be unlocked to do that.
It, start to flash, but when it gets to "boot" it stop saying that it can't be downgraded. So right now My XT925 starts to AP Flash mod with text Flash Failure. I'm able to get to recovery mode and from there try to update phone but like in AP Flash it just don't want to flash Android 4.1.2.
Is there any way to bring it back to life?
I'm guessing that it should run if I could flash files for 4.4.2 but I don't know from where I can get them...
Please tell me do I have nice looking brick or there is a hope for my phone?
Phone is locked, has no other then stock tools installed, and it had system version 180.46.117.XT925.CCE-Retail.en.EU before I started to mess with it.
I tried flash it with 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml. When it begin starting in AP Flash mode I have removed every line that cause stopping the process (technically everything except "partition", "tz", "boot" and "system" is loaded from 4.1.2) so now its very messy. Right now I don't know what I was hoping for. What's done is done, so now I can only hope that it can be fixed.
If its even fixable, there is no way to fix it without the stock kk fxz, unless you can get it unlocked using Moto's site.
Sent from my G3 Rockin Cyanogen
Thank you for your reply.
I'll try unlocking by web when I get home. I'm only hoping that it can be done without working properly touch screen, or buy connect keyboard via OTG. Otherwise I'm doomed...
Why the F would reflashing after changing the screen and/or digitizer magically bring back the touchscreen functionality to life ?
No touchscreen only means the digitizer was not installed properly, that's all. Open the phone again and check all flex cables and connection, they are really tricky to put back in connectors properly. (pro tip, use some very small pliers to manipulate flex cables and put them back in their connectors)
Unlocking does not require any touchscreen functionality though, it's just a matter of keyboard input from your computer. Just unlock, downgrade properly to say 4.1.2, and when you're done see if the touchscreen work. And when you find out it doesn't, tear the phone apart again and double-check all flex cables connectors on the motherboard
It works!! Thank you very much!!
At first I have problems to find the fastboot.exe in the downloaded SDK directory (for those who also have problems with finding that file it is in 'sdk\platform-tools' folder). The process of unlocking is very easy so I have no problem with that . After unlocking phone flash correctly.
CoinCoin88 said:
Why the F would reflashing after changing the screen and/or digitizer magically bring back the touchscreen functionality to life ?
No touchscreen only means the digitizer was not installed properly, that's all. Open the phone again and check all flex cables and connection, they are really tricky to put back in connectors properly. (pro tip, use some very small pliers to manipulate flex cables and put them back in their connectors)
Unlocking does not require any touchscreen functionality though, it's just a matter of keyboard input from your computer. Just unlock, downgrade properly to say 4.1.2, and when you're done see if the touchscreen work. And when you find out it doesn't, tear the phone apart again and double-check all flex cables connectors on the motherboard
Click to expand...
Click to collapse
Apparently when you have KitKat update it's necessary to flash phone again after replacing the screen and/or digitizer. After flashing digitizer is working properly. I didn't need to open the phone and correct any flex cables (there is only one common to the screen and digitizer so if that was wrongly connected probably I won't be seeing anything). To be honest I don't think that will work without opening the phone. I instinctively unlocked the phone and started to choose the language. Then I realized that I can do it. I'm really glad that the phone is working correctly.
Once again thank you very much for your help.
M_Kwiatkowski said:
It works!! Thank you very much!!
At first I have problems to find the fastboot.exe in the downloaded SDK directory (for those who also have problems with finding that file it is in 'sdk\platform-tools' folder). The process of unlocking is very easy so I have no problem with that . After unlocking phone flash correctly.
Apparently when you have KitKat update it's necessary to flash phone again after replacing the screen and/or digitizer. After flashing digitizer is working properly. I didn't need to open the phone and correct any flex cables (there is only one common to the screen and digitizer so if that was wrongly connected probably I won't be seeing anything). To be honest I don't think that will work without opening the phone. I instinctively unlocked the phone and started to choose the language. Then I realized that I can do it. I'm really glad that the phone is working correctly.
Once again thank you very much for your help.
Click to expand...
Click to collapse
Well, I'll be damned, it's the first time I hear of such behaviour, and i've ripped apart a long list of devices before my razr... Sometimes to replace the screen, sometimes to replace the battery, sometimes just for fun... and I've never seen that before.
(Although IIRC there are two flex cables going from the front assembly to the motherboard in the xt925 and not just one, but I don't remember which one is for what)
edit: OK just found out lcd and digitizer are glued together in most recent phones, including xt925, so there's probably only one flex cable for the whole assembly. They other one was probably for the led I guess...)
CoinCoin88 said:
Well, I'll be damned, it's the first time I hear of such behaviour, and i've ripped apart a long list of devices before my razr... Sometimes to replace the screen, sometimes to replace the battery, sometimes just for fun... and I've never seen that before.
(Although IIRC there are two flex cables going from the front assembly to the motherboard in the xt925 and not just one, but I don't remember which one is for what)
edit: OK just found out lcd and digitizer are glued together in most recent phones, including xt925, so there's probably only one flex cable for the whole assembly. They other one was probably for the led I guess...)
Click to expand...
Click to collapse
The second one is for front camera, speaker and light sensor. I don't count that one because is actually separate part from the screen witch is screwed to the front frame of the phone. To be clear I had problems with that cable and I had to put it few times before camera and sensor start work correctly. That is why I paid special attention to the good fitting of these cables to the motherboard. That was before I smashed software by trying downgrade locked phone so I was pretty sure that it was fitted correctly.
Now my Motorola still works fine. After replacing the screen it actually lived longer in one piece then when I bought it. I scratched the screen next day from purchase... then it fell of my hands few times(usually with the help of other people)... That is why I decided to change glass and front frame... and then during the peel-off old glass from screen I broke the screen... It all happened in period shorter than two months... I'm guessing this particular XT925 is very unlucky... or... it's just unlucky to have me as the owner...
I'm very careful with carrying it with me now, so I don't have to replace the screen again... it cost alto... :|
Well, at least now I know how to bring it safely back to life. And I must admit that my friends are quite impressed that I managed get it work again.
I bought my brother a second-hand M8. It had a cracked screen but it was really cheap. I put the new screen in and a new SIM card reader. Everything worked fine for months and out of the blue the screen stopped responding to touch. Everything else worked fine as far as I could tell. Even in TWRP touch was gone so I figured maybe it was a cheap screen or something like that. I took it apart and the backlight was falling apart. Ordered a new screen that had the frame with it to save time on reassembly and because the old one was a little tweaked. Same problem, ran the RUU from Windows, ran different RUU's from several threads via Fastboot. Ran the latest firmware package on Santods thread and still nothing. It has to be the motherboard at this point right? The display and digitizer cables go right into the motherboard and the only cable that looks replaceable goes up int the daughter board with the cameras and top speaker assembly. Am I missing something or should I just scrap this mess?
lightweaponx said:
I bought my brother a second-hand M8. It had a cracked screen but it was really cheap. I put the new screen in and a new SIM card reader. Everything worked fine for months and out of the blue the screen stopped responding to touch. Everything else worked fine as far as I could tell. Even in TWRP touch was gone so I figured maybe it was a cheap screen or something like that. I took it apart and the backlight was falling apart. Ordered a new screen that had the frame with it to save time on reassembly and because the old one was a little tweaked. Same problem, ran the RUU from Windows, ran different RUU's from several threads via Fastboot. Ran the latest firmware package on Santods thread and still nothing. It has to be the motherboard at this point right? The display and digitizer cables go right into the motherboard and the only cable that looks replaceable goes up int the daughter board with the cameras and top speaker assembly. Am I missing something or should I just scrap this mess?
Click to expand...
Click to collapse
When I swapped out the battery in mine the screen was unresponsive and it was becaus a ribbon cable was misaligned in the connector. I cannot rememer Which one it was but I hope this helps.
bug6810 said:
When I swapped out the battery in mine the screen was unresponsive and it was becaus a ribbon cable was misaligned in the connector. I cannot rememer Which one it was but I hope this helps.
Click to expand...
Click to collapse
I checked all of the ribbon cables multiple times and sadly that had no effect. Thank you for trying though!
lightweaponx said:
I checked all of the ribbon cables multiple times and sadly that had no effect. Thank you for trying though!
Click to expand...
Click to collapse
No problem and good luck!
Title explains all. I'm in a tight bind with money too..
I want to believe I can just reflash stock via odin and it will come back. Or is there something else I can do to make this work?
It sense touch 10% of the time, but it's never enough to unlock my phone or do anything with it.
Edit: the new screen worked perfectly before I did the operation. Don't know what went wrong. I didn't scratch or bend anything to my knowledge. The process took about 10 minutes and went really smooth.
kanzenmuketsu said:
Title explains all. I'm in a tight bind with money too..
I want to believe I can just reflash stock via odin and it will come back. Or is there something else I can do to make this work?
It sense touch 10% of the time, but it's never enough to unlock my phone or do anything with it.
Edit: the new screen worked perfectly before I did the operation. Don't know what went wrong. I didn't scratch or bend anything to my knowledge. The process took about 10 minutes and went really smooth.
Click to expand...
Click to collapse
Hello, I repair cellphones for a living. And it depends on a lot of things. My guesses are three things. From most likely to least likely.
1. You said that everything was working fine before you changed ROMS, it could be an incompatibly issue between the screen and the software. A lot of aftermarket screens are mostly compatible with stock, a lot have compatibility with custom ROM. It could be an issue solely on the software and not related to the screen.
2. There isn't a solid connection on the LCD connector, that usually happens with during installation, sometimes if the device is set down hard or dropped knocking the connection loose.
3. It's a defective screen. It happens sometimes. It's not uncommon for a screen to appear fine but after a few hours it acts up. It could have just been a coincidence that you noticed or went defective when you flashed (not saying flashing is responsible for this scenario).
Flash back to stock and then you'll have a great chance of to see which out of the 3 are responsible. Cheers.
I repair iphones, android devices, laptops, ect.
Sent from SM-G900Pkltespr
There are only 2 flex cables on the S5 LCD. Make sure the primary (top flex) is seated correctly, then the easiest thing to check before taking the screen back off is the flex under the battery cover. You will see a little screw near the lower right of the battery with a little cover. Pull up that cover while the battery is out and make sure that cable is seated correctly. If both flex cables are seated correctly then it can only be 1 of 2 things IMHO, the screen you purchased is defective or you bent some pins on the mobo where the flex cables attach. I don't think it's a rom issue.