"USB cb wake lock" "vbus_present" etc. battery charging when unplugged.
Hi All,
This is not a question, its something I want to share as I searched a lot and read a lot on this.
After flashing a 300+ roms without a problem, my S2 decided that it was going to suddenly and randomly act up.
The battery acted as if if was charging when unplugged. Betterbattery stats showed "USB cb wake lock" + "vbus_present" using massive amounts of battery.
I flashed a few stock roms, some custom and many kernels with ODIN but nothing fixed it.
Eventually I had 8-9 back ups on my phone and I tried each of these but the error continued in all but one. After days of frustration I was beginning to think it was a hardware USB issue that I need to replace the part. But no, one of the restore fixed it.
It started acting up today but I cleared battery stats and fixed permissions and all is well again.
Not sure why this randomly happened but I wanted to share this as many are of the opinion its always a hardware issue and needs replacing when clearly there are exceptions to this.
If anyone understand why the above worked, I would appreciate comments as there are some very clever people here and I am sure some of you have fixed this issue.
Thanks.
My two cents on how or what is happening, however not on the software side: Some people with the same issue report that cleaning the USB-port with a toothbrush or any soft brush helped, and sometimes the issue appears or disappears randomly. I guess that the USB connector is badly soldered/mounted onto the board. This could explain why the issue comes and goes, because if the connector gets pushed/pulled in the right direction, the port could reconnect.
I had the same issue, the wakelocks, 'charging' written on the lockscreen, and every now and then the 'charger connected' sound. However flashing, batterystats-wiping and whatnot did not help. Only when I exchanged the board in the lower end (where the USB connector is) with one I had lying around the issue disappeared and has in the two months since never reappeared.
If this keeps happening, it could be worth a try, and it is quite easy to do. There is a very nice photo guide on here somewhere on replacing the screen, it explains it all and is no different for the USB-connector. It also is a possibility, if you don't mind the trouble, to reflash to stock and let the phone be repaired at a service centre.
If you need help or the link to the photo guide, I might still have it somewhere.
I hope this helps.
Coirpre said:
My two cents on how or what is happening, however not on the software side: Some people with the same issue report that cleaning the USB-port with a toothbrush or any soft brush helped, and sometimes the issue appears or disappears randomly. I guess that the USB connector is badly soldered/mounted onto the board. This could explain why the issue comes and goes, because if the connector gets pushed/pulled in the right direction, the port could reconnect.
I had the same issue, the wakelocks, 'charging' written on the lockscreen, and every now and then the 'charger connected' sound. However flashing, batterystats-wiping and whatnot did not help. Only when I exchanged the board in the lower end (where the USB connector is) with one I had lying around the issue disappeared and has in the two months since never reappeared.
If this keeps happening, it could be worth a try, and it is quite easy to do. There is a very nice photo guide on here somewhere on replacing the screen, it explains it all and is no different for the USB-connector. It also is a possibility, if you don't mind the trouble, to reflash to stock and let the phone be repaired at a service centre.
If you need help or the link to the photo guide, I might still have it somewhere.
I hope this helps.
Click to expand...
Click to collapse
Very much appreciate your reply and you could be right about the bad soldering issue, I am going to order the part anyway and have it on stand by.
It was strange that all of the roms, kernels and backups did not work except one. I did the port cleaning and all that too but to no avail but it might be all coincidence that it worked with the backup for a finish. which reminds me, I better change my signature
Thanks or your reply and for your offer to help, it is much appreciated. Thankfully its running butter smoothe at present and I wonder if the USB port is susceptible to moisture too, which might be my issue.
Related
Hi all, this is my first post on this forum but I've been reading for a while to educate myself.
I've got a Herm200 that I've been trying to troubleshoot but to no avail. I'm fairly certain that it has a hardware problem but I haven't been able to isolate anything.
Here's whats happening:
Occasionally the screen will come out of stand-by all white. This will also happen randomly if i touch the screen to perform a command. While the screen is operating, sometimes the buttons on the face will stop working, however the buttons across both sides will continue working just fine.
When the screen turns all white a soft, hard, or stand-by cycle will not always bring it back to life. The fact that the hard reset wont always fix the problem makes me think it's a hardware issue since the phone will boot-up with the the all-white screen.
This is incredibly frustrating especially since HTC wont accept any warranty claims in the USA on the Tytn.
At first I thought this might be a problem with the ribon connection between the screen and the base but i haven't been able to confirm or discount anything at this point. I have yet to find a way to consistently reproduce or rectify the problem so it's very hard to troubleshoot.
I pretty much have to take a second phone with me everywhere right now just incase i need to make a call. Please help! Has anyone ever encountered such a problem?
Thank you in advance!
SneezyRobot said:
Occasionally the screen will come out of stand-by all white. This will also happen randomly if i touch the screen to perform a command. While the screen is operating, sometimes the buttons on the face will stop working, however the buttons across both sides will continue working just fine.
Click to expand...
Click to collapse
Hi. This sounds very similar to a problem that I experienced with a HERMES100. I bought the phone off someone on Ebay recently - someone had obviously scrambled the radio on it. I re-flashed it, and it sprang to life. However, after a couple of days, I experienced a problem where occasionally the LCD would stop refreshing, all the pixels faded away leaving only a white screen. Under these circumstances, some of the buttons on the phone stopped working. Turning phone on/off sometimes cured the problem, or it would require the occasional hard reset. This would happen once or twice a day and I suspect thats why someone tried to re-flash the phone.
In the end, out of curiosity I took the entire phone apart, put it all back together again and now there are no more problems!! Totally fixed!
My suspicion is that it was one of the ribbon cable push connectors on the mainboard - possibly not seated properly, or a bit of dirt contaminating the connection. Obviously when I took the phone apart I must have re-seated it.
If you are planning to take your phone apart, please exercise considerable care because some of the parts are very small and easily damaged. I would recommend buying a proper kit to take it apart. I bought mine for about £5 off ebay. Particularly useful are the plastic spoon "wedges" used to gently prise open the case after removing the screens. Don't use a screwdriver - you will scratch the case.
Good luck.
wow... that sounds like exactly what's going on here, I actually even tried to disassemble it lastnight but didnt have the right driver set. thank you for the advice!
I'll look for one of those sets but what would you search for if i needed to find it?
Thanks again, I just got a set off of Ebay. Hopefully it'll be here next week
With any luck it'll be a connection issue.
I have had the exact same problem. Because I got the Tytn through work I made our IT department handle the issue and I am currently waiting for a replacement and to find out what happened.
Yep, it looks like the problems the OP is having are very similar to the problems we've been having over in this thread:
http://forum.xda-developers.com/showthread.php?t=291027
I'm beginning to think it's a hardware problem as well but not entirely sure.
People in the above thread mentioned that using the scroll wheel a while then moving back to use the D pad fixed the problem (very briefly in my case.) Once I use the center D pad button again it locks the hardware buttons under the screen until I make my device sleep and resume.
Somtimes rather than making all the front hardware buttons unresponsive the issue is that once I use the Down Dpad button I can't use the up button. Pressing up will make it go down, as will pressing down (at least that's working ).
Regarding the white screen - this sometimes also occurs. I can force it to white screen by putting a little pressure on the silver panel surrounding the top, right and bottom of the screen (I have an imate jasjam). Randomly when there's no pressure on the rim and I wake it out of standby, it has a white screen that can only be fixed by turning the screen off and on again.
Finally, the LED indicator seems screwy. Sometimes it never flashes. Other times it flashes sporadically (uneven intervals - we're talking maybe a minute between one flash then seconds before another). When I charge it sometimes the LED doesn't come on but nevertheless it charges. Sometimes if the LED is on it never turns green to indicate a full charge. Yet other times it comes on orange, turns green, then never switches off!
Is it possible that
a) The hardware button problems.
b) The white screen problem.
c) The LED problem.
are all related to some kind of connection going loose? Why would the hardware button problem be temporarily fixable with use of the scroll wheel if this were the case?
The other thread has fallen silent. I'm hoping that some of the gurus in here can offer some input here, even if they don't know the answer but can formulate an opinion. I know very little about these devices.
Thanks in advance guys!
PS - don't really know if I should start another thread, I've posted here as it seems like very much the same issue.
Anybody any idea? advice?
I had a similar problem with my HERM100. I didn't mess around with it too much, I just had Cingular replace it out of warranty exchange (thank god those original ROMs are on the wiki ). I did notice however that after doing a master reset, the screen would function again although I haven't messed around with it too much. I got so frustrated with removing the battery for 5 minutes and STILL powering on with a white screen that I just threw it in my back seat until the new one arrived.
I don't have these screen issues. I only have hardware button problems. It's so damn frustrating! I already own a replacement.
I just received a call from my girlfriend. I wasn't able to answer the phone with the buttons, only with a screentap. I also wasn't able to close the call with the hardware button. Since the side buttons work, I went to settings -> phone, closed it, and there we go. The hardware buttons worked again.
Why the heck is this? I truly hope for some wizz out there with some advice, since HTC would only tell me to send it back after replacing it with a new TyTN with same issues.
Regards,
DM.
Anyone anyone?
HELP!!!!
barncourt said:
Hi. This sounds very similar to a problem that I experienced with a HERMES100. I bought the phone off someone on Ebay recently - someone had obviously scrambled the radio on it. I re-flashed it, and it sprang to life. However, after a couple of days, I experienced a problem where occasionally the LCD would stop refreshing, all the pixels faded away leaving only a white screen. Under these circumstances, some of the buttons on the phone stopped working. Turning phone on/off sometimes cured the problem, or it would require the occasional hard reset. This would happen once or twice a day and I suspect thats why someone tried to re-flash the phone.
In the end, out of curiosity I took the entire phone apart, put it all back together again and now there are no more problems!! Totally fixed!
My suspicion is that it was one of the ribbon cable push connectors on the mainboard - possibly not seated properly, or a bit of dirt contaminating the connection. Obviously when I took the phone apart I must have re-seated it.
If you are planning to take your phone apart, please exercise considerable care because some of the parts are very small and easily damaged. I would recommend buying a proper kit to take it apart. I bought mine for about £5 off ebay. Particularly useful are the plastic spoon "wedges" used to gently prise open the case after removing the screens. Don't use a screwdriver - you will scratch the case.
Good luck.
Click to expand...
Click to collapse
This is my first post as I've so far managed to cure all my issues from just reading the forum. However, I am now having a similar problem with the white screen.
I have a cingular 8525. It fell and the following day the call and end buttons remained lit and wouldn't turn off and they also wouldn't work.
I soft reset, nothing, I then removed the battery and when I turned it back on, there was a white screen and the buttons below still don't work.
I have read the other posts on this issue, but I need help on exactly what kit to buy to reconnect the screen cable and instructions on how to do it as I've never taken apart a phone before, although I have dabbled with other electronic devices.
Your help would be much appreciated, as I am in Jamaica and there are no technicians here who I trust to help.
Thanks in advance.
Below are links to 2 kits I'm thinking of getting. Is either one better than the other?
http://www.pdasmart.com/pdaphonehtcmini.htm?gclid=CJrHntO-hosCFQx1VAodaQf6KQ
http://cgi.ebay.com/SCREWDRIVERS-TO...01677255QQcategoryZ108648QQrdZ1QQcmdZViewItem
CINGULAR IN JA said:
This is my first post as I've so far managed to cure all my issues from just reading the forum. However, I am now having a similar problem with the white screen.
I have a cingular 8525. It fell and the following day the call and end buttons remained lit and wouldn't turn off and they also wouldn't work.
I soft reset, nothing, I then removed the battery and when I turned it back on, there was a white screen and the buttons below still don't work.
I have read the other posts on this issue, but I need help on exactly what kit to buy to reconnect the screen cable and instructions on how to do it as I've never taken apart a phone before, although I have dabbled with other electronic devices.
Your help would be much appreciated, as I am in Jamaica and there are no technicians here who I trust to help.
Thanks in advance.
Below are links to 2 kits I'm thinking of getting. Is either one better than the other?
http://www.pdasmart.com/pdaphonehtcmini.htm?gclid=CJrHntO-hosCFQx1VAodaQf6KQ
http://cgi.ebay.com/SCREWDRIVERS-TO...01677255QQcategoryZ108648QQrdZ1QQcmdZViewItem
Click to expand...
Click to collapse
Both kits look ok. PDA one tells you a little more but the basics appear to be in both.
I'm curious though you soft reset and took the battery out, but have you done a HARD reset? I would always try this first before dismantling.
Mike
In my case, they also are always lit up when the screen is also active.
And no matter what ROM version, they occasionally stop responding. Side buttons keep working.
mikechannon said:
Both kits look ok. PDA one tells you a little more but the basics appear to be in both.
I'm curious though you soft reset and took the battery out, but have you done a HARD reset? I would always try this first before dismantling.
Mike
Click to expand...
Click to collapse
Thanks for the response.
I couldn't do a hard reset because the buttons weren't working.
I have made some progress with the phone now. Found a tech guy who looked at it for me. The white screen is gone, but the buttons still stop working from time to time.
All the connections seem ok.
Is there anything else that could cause the buttons to malfunction?
CINGULAR IN JA said:
Thanks for the response.
I couldn't do a hard reset because the buttons weren't working.
I have made some progress with the phone now. Found a tech guy who looked at it for me. The white screen is gone, but the buttons still stop working from time to time.
All the connections seem ok.
Is there anything else that could cause the buttons to malfunction?
Click to expand...
Click to collapse
Nothing obvious.
Have you got applications installed that you have loaded - could be one thats playing up.
Have you now been able to do a hard reset?
If taking device apart and reassembling improved things it does suggest hardware though and might be worth double checking all those multi-connector blocks for good connections - i.e. take them out and in a few times to ensure any oxidation on contacts is removed.
Mike
mikechannon said:
Nothing obvious.
Have you got applications installed that you have loaded - could be one thats playing up.
Have you now been able to do a hard reset?
If taking device apart and reassembling improved things it does suggest hardware though and might be worth double checking all those multi-connector blocks for good connections - i.e. take them out and in a few times to ensure any oxidation on contacts is removed.
Mike
Click to expand...
Click to collapse
Thanks Mike.
I will give that a shot.
I haven't installed any new applications recently, so I don't think it is a software issue.
Thanks again.
CINGULAR IN JA said:
Thanks Mike.
I will give that a shot.
I haven't installed any new applications recently, so I don't think it is a software issue.
Thanks again.
Click to expand...
Click to collapse
If it wouldn't be a software issue, why is it, in my case, instantly resolved when going to settings -> phone with the side buttons?
i had this problem i took it to a guy who fixed the problem he said it was a very small tear in the flex cable which causes this white screen every now ant then and the buton problem , sorry to say its the cable problem and u need a very capable person to fix it or replace it with a new one . its very common problem baised on the guy who fixed it .
dmxl said:
I don't have these screen issues. I only have hardware button problems. It's so damn frustrating! I already own a replacement.
I just received a call from my girlfriend. I wasn't able to answer the phone with the buttons, only with a screentap. I also wasn't able to close the call with the hardware button. Since the side buttons work, I went to settings -> phone, closed it, and there we go. The hardware buttons worked again.
Why the heck is this? I truly hope for some wizz out there with some advice, since HTC would only tell me to send it back after replacing it with a new TyTN with same issues.
Regards,
DM.
Click to expand...
Click to collapse
Exactly what is happening to me, no white screen issues, just screen taps and answering calls, I also have another problem where the PDA will not allow me to open anything, be it the start menu or contacts, it will open and quickly close again. I have had mine swapped through Telstra in Sydney, it worked fine for a while and then the same crap again. These problems started before I even touched the OS, so it must be a build problem. Maybe we should write a joint letter to HTC letting them know that there is a serious problem with their machine.
I have had the same problem, got my Tytn through work so we sent it back to the company that supplied it to us. Got it back yesterday and they had replaced the "switchboard". Not sure what it is but there was the problem. Had white screen and buttons not working.
--- AC adapter was causing that. Solved.
My friend has a u8800 and he was using 2.2.2 official, he was getting random clicks every day. Now we upgraded to b522 and random clicks are still here. He sended me a video about that.
http://www.youtube.com/watch?v=VRiVicEjMpk
What we tried:
*we used b138 without any changes
*we used b522 without any changes
*we factory resetted in b138
*we factory resetted between b138 and b522
*we factory resetted in b522
*we get rid of silicone case (which we suspected)
He is going to give it to KVK service which is the distributor in turkey. What do you think about that? did anyone encountered something like that. My phone and his phone are have atmel also and I don't have something like that.
115 people looked at this but no answers? SHAME ON YOU!
Maybe nobody knows the answer?
Sent from my U8800 using xda premium
If you've cleaned enough the whole area of the phone (especially the edges) and it's still doing it then it's warranty issue due to faulty digitizer.
(You didn't even wait a day before you complained for no answer? Ask XDA for your money back)
yes I didn't waited, also I think maybe nobody knows the answer but some ideas could fix, so I'll say to him to clean edges of screen with a pin. I'll report back soon.
ok i shall wait 12 hours for your report..
I've got the same problem when i use my wall(?) charger, and some times the random clicks stay for a while when i disconnect the charger. For now and on i use the computer or other charger to my phone.. Because this doesn't seem stable at all!
Maybe not help too much. But it can be the problem?
If it is charger specific, either the charger is pumping out voltage that is not properly regulated or it's switching circuit is causing such EMI that the phone's digitizer goes nuts.
I've heard a case of a faulty charger causing such a behavior but the digitizer died not long after and we attributed it to that. If you can try with a couple more wall chargers and keeps happening then it's the digitizer.
Sorry it took more than 12 hours :/
ziuzitsu, you are right. He tried what you said and he gave it to aftersale. I should say that that idea was quite brilliant. Thank you for help. I should say that you really solved. My friend is thanking to you too. He is going to change adapter before his phone come back.
So I have an issue with a 2012 N7, warranty is long gone. I've tried all suggestions from billykxda's thread, but no luck thus far. I've also tried Google's official page on the topic as well.
I've left the device charging for many consecutive hours, both via AC power and USB, and I suspect my issue resides with the LCD screen. Also tried a hard battery pull. It's also important to note that I haven't undertaken any mods on the device at all, i.e. the bootloader is still locked and USB debugging is not enabled yet.
When I plug the device into my PC the Win7 driver notification bubble pops up, usually reporting either an Unknown Device or an "APX drivers not installed" message. I'm unable to get it to boot into Fastboot, Recovery, or Android OS. Plugging/unplugging the device via USB yields these driver messages over and over again, along with the Win7 sound notification, so the device isn't totally dead, but no amount of button combinations or 30-60+ second button holds are getting any response.
Has anyone else experienced these issues before? Do you think my device is totally dead?
AvidPhisherman said:
Has anyone else experienced these issues before?
Click to expand...
Click to collapse
Yes; I am also experiencing similar issues. Unfortunately, I have not reached a solution. I just replaced a broken screen for a friend. Once I got the screen in, I tried turning it on but didn't see anything happen. I began to research and thought I had the dead battery issue that most people get when leaving it unplugged for an extended period of time. I plugged it in using the wall adapter for a few hours, used the power+volume buttons and still didn't get any response. Finally, I decided to charge it with my PC. The PC recognized something was plugged in, installed drivers, and now I have a Nexus 7 in my connected devices list. While connected to my PC, I hold power+volume down and hear the USB disconnect, reconnect, and have an unrecognizable device attached. This leads me to believe that the Nexus 7 is working properly and the screen is not working. I have taken the entire device apart to re-seat all connections 3 different times and still cannot get it to work. I hope someone can shed some light on our issues!
Edit: I forgot to mention, I also tested the battery with a digital multimeter. It reads approximately 3.79 volts DC. I thought it may be important to state this in case the issue is battery related. I'm not certain what the correct value should be for it to work properly.
I am currently trying to diagnose this problem. Yesterday, I hopped on Craigslist and bought a working Nexus 7 for 50$. I am currently taking it apart to rob parts from it and figure out where the problem is. So far I have tested the battery. The battery reads approximately 3.78 volts DC so I can probably rule this out as my problem.
Also, I noticed something strange yesterday. I took the broken Nexus with me when I went to meet up with the man selling the used/working Nexus. While I was outside in very bright sunlight, I pushed the power button on the broken Nexus. I noticed that I could actually see the screen doing something. It was all fuzzy and had lines running every where, but you could in fact see it doing something. I think the replacement screen I received is bad, but I won't know until I start swapping parts.
AvidPhisherman, for now maybe try taking your Nexus out in very bright sunlight and see if you can see the screen do anything when you press the power button. Also, I'm not trying to hijack the thread. It seems that we have very similar issues. I hope to find something that fixes both of our problems.
Success.... kinda. I tried combining the broken Nexus 7 motherboard with the working Nexus 7 screen but it wouldn't fit since one is the 3G model, and the other is the Wifi only model. Next, I put everything back together on the broken N7, but this time I used the LCD ribbon cable from the good N7. Success!!! It powered up, and I can see the screen. My problem now, is that the screen is mostly unresponsive and acts like you are touching it in random spots, when you're not touching it at all. I'm taking it apart to re-seat the connections... again.
__redfox__ said:
Success.... kinda. I tried combining the broken Nexus 7 motherboard with the working Nexus 7 screen but it wouldn't fit since one is the 3G model, and the other is the Wifi only model. Next, I put everything back together on the broken N7, but this time I used the LCD ribbon cable from the good N7. Success!!! It powered up, and I can see the screen. My problem now, is that the screen is mostly unresponsive and acts like you are touching it in random spots, when you're not touching it at all. I'm taking it apart to re-seat the connections... again.
Click to expand...
Click to collapse
Hey redfox thanks for taking in interest in this! You're not hijacking the thread, your posts are very helpful. Good to know I'm not the only one experiencing these issues.
I'm just a hobbyist with an interest in fixing things, although I don't have much experience with DIY fixing. I didn't have a chance to try turning the screen on under direct sunlight, but yesterday I took both my non-working Nexus 7s (the first one I mentioned in my OP, the second one just has a bad/hollowed out USB port) in to a repair shop for a free diagnosis. I'm actually a business user, my company owns the tablets but I'm responsible for maintenance/tech troubleshooting.
Please keep me posted with updates as to how your progress is going. I'll post again once I get a report from the repair shop re: my issues.
Hi,
I have been having the same problem,
I bought my wife a used Nexus 7 and it worked just fine for almost a year then all of the sudden the screen would not function
there would be lines going through it but it remain dark.
thank you for researching the matter i will try to buy the part online and see if i can get it to work now!
if i understand it correctly there is no need for a new mother board but just a new LCD ribbon cable?
godnessy said:
Hi,
I have been having the same problem,
I bought my wife a used Nexus 7 and it worked just fine for almost a year then all of the sudden the screen would not function
there would be lines going through it but it remain dark.
thank you for researching the matter i will try to buy the part online and see if i can get it to work now!
if i understand it correctly there is no need for a new mother board but just a new LCD ribbon cable?
Click to expand...
Click to collapse
I cannot guarantee that it will fix your screen, but it is possible. When I had this one out in the sun, it did the same thing. The screen was super dark, and I could see crazy lines. Hopefully a new ribbon/cable will fix your problem. They are only a few dollars on Amazon.com
godnessy said:
Hi,
I have been having the same problem,
I bought my wife a used Nexus 7 and it worked just fine for almost a year then all of the sudden the screen would not function
there would be lines going through it but it remain dark.
thank you for researching the matter i will try to buy the part online and see if i can get it to work now!
if i understand it correctly there is no need for a new mother board but just a new LCD ribbon cable?
Click to expand...
Click to collapse
__redfox__ said:
I cannot guarantee that it will fix your screen, but it is possible. When I had this one out in the sun, it did the same thing. The screen was super dark, and I could see crazy lines. Hopefully a new ribbon/cable will fix your problem. They are only a few dollars on Amazon.com
Click to expand...
Click to collapse
Hello fellow users! Quick update, I finally heard back from the repair shop.
Bad news - they tried swapping out the screen, then the battery, USB charging port, display cables, etc. etc. and nothing worked. Their diagnosis is that the tablet has a fried motherboard, and they're unable to repair and/or replace it
Good news - it cost me nothing to receive this diagnosis
Hopefully the outlook is not so grim for your respective N7s. Just wanted to post an update as to what I learned from this whole experience.
Hi guys, Reporting in.
Toke a while but i got the part AND found the stupid device!
After ALOT of fiddling, taking apart and putting back again i found out that the problem was the battery!
it looks like it was on its last leg and that caused all the strange screen stuff.
I dont have another battery to replace it so instead i hooked it up straight to a USB cable and into the socket and it works just fine
thanks for the tips and hopefully this helps someone else!
No amount of recalibration would correct my bad battery so I replaced the battery in my Nexus 10 (running lollypop). It was a complete pain to get the thing apart but it wasn't all that complex. I wanted to test it with the back off but the new battery was dead and I figured, “what could I possibly have done wrong anyhow” so I put it all together and charged it. I found out what I could do wrong. Now that I have it back together and fully charged the touch screen doesn't respond hardly at all. Everything else seems fine. I can boot to Android, boot to recovery etc... Like I mentioned above, taking it apart is a PITA and I'd like to only do it one more time and forever be done. I am guessing one of the 3 ribbon cables over the battery is for the touch screen. I'd like to only fiddle with the right cable only. Does anyone know which one specifically affects the screen?
Jerryp7
Did you find out what the problem was with you tablet. I have the same problem. I'm sure its the ribbon cables but I don't see anything out the ordinary. Thanks.
John R.
I had to open it back up (which is what I wanted to avoid because it was such a birch). Everything looked OK but I unplugged and replugged everything and it's been fine ever since. It had to have been one of the ribbon cables.
Replaced battery - now touch screen doesn't work right
Jerryp7
Thanks for the quick reply. I reopened the table and found the locking bar on one of the ribbon cables is broken. Any idea if they can be replaced?
Thanks again.
Regards,
John R.
Success!
Jerryp7
The clamp for the ribbon cable wasn't broken! The movable part had become detached. After many tries I figured how it went back together. I then found that it helps to hold the cable into the connector as you close the clamp.
Murphy's law rules again.
John R.
Glad you solved it. My only suggestion was to form a little plastic hold-down and super glue. If you ever had to do it again you could snip it off.
Jerry
The new battery still didn't correct the problem with the battery quitting at about 25% left. Do you know if there is any else I should try. I was in contact with Google before I replaced the battery and followed several procedures they suggested. Needless to say none of them worked. When I try to wipe the system cache partition I never get the screen that allows me to select the Recover mode. I get a screen with an arrow on the left that says "Start" and a droid in the center with the words "Downloading" under it. I let that run for over an hour but it didn't appear to do anything. If you have any suggestions I would appreciate them. Thanks.
John R.
Not sure. I'm not having any problems. Have you tried recalibrating the battery? I did that before replacing it which naturally didn't help a bad battery. Is you device rooted? I think it has to be to recalibrate. I use skipsoft unified android toolkit and have been for years. Last thing I did was upgraded to the OTA Build LMY49G which breaks root but the toolkit rooted it even thought Mark doesn't have the factory build availiable yet.
My connector broke when I was changing the battery. Anyone know how to fix it? There was little silver pins that came out. Thanks for help in advance.
Sent from my Nexus 7 using Tapatalk
For what it's worth... I had this same problem and was able to fix it fairly easily (if you don't count the PITA of opening the case again). The three cables have to be connected perfectly, which is why they are taped down. The one on the far right (if the device is oriented so the edge with the controls is on top) connects the LCD (it's labeled as such). I have lighted magnifying goggles that I use for many things. I carefully removed the tape (again), opened the locks (again), pulled out the cables, then pushed them gently back in, making sure they were in as far as they could go, all the way across (the goggles make all this very easy to see), and then closed the locks. I did this with all three ribbon cables. I then examined the tape for lint, cleaned off any dirt with 99% isopropyl alcohol and no-lint chamois swabs (just dab it lightly - don't remove all the glue), then pressed the tape down very firmly. When I closed the case again, all was well.
Opening the case isn't nearly as easy as those YouTube videos makes it look. But I'm so glad I did this. It's great to have a working battery again.
Next: Install Android 6!
JohnR0836 said:
Jerry
The new battery still didn't correct the problem with the battery quitting at about 25% left. Do you know if there is any else I should try. I was in contact with Google before I replaced the battery and followed several procedures they suggested. Needless to say none of them worked. When I try to wipe the system cache partition I never get the screen that allows me to select the Recover mode. I get a screen with an arrow on the left that says "Start" and a droid in the center with the words "Downloading" under it. I let that run for over an hour but it didn't appear to do anything. If you have any suggestions I would appreciate them. Thanks.
John R.
Click to expand...
Click to collapse
I have the same problem, replaced the battery tried 2 different recalibrate apps, tried factory reset, cleared cache and battery shuts down at 20% with no warning.
It's the first cable if you have the camera facing upwards. There is the 2 cables that are together, it's the first of those cables that controls touch on the screen. Just make sure it's seated correctly, press down on it some and close the tab and tape it back in place. I know this because I ended up having to take the back off again while the tablet was powered on after I replaced my battery because the screen wasnt working. I checked each cable and that first one was the one that controlled touch. My Nex10 is working as smoothly as it did when I first got it.
Hi,
Yesterday, I used the phone like normal(little bit of listening music and media etc) and drained the battery, so it shut down. Connected the charger fairly later and it started charging. In a few hours switched it on and saw that there was this white stop sign on the notification bar. Figured it might be a matter of a reboot since things like that happen from time to time. When rebooted in the morning the sign was still there.
I tried all the firmwares from Sammobile available for the region and nothing got it away, tried LineageOS and then used SmartSwitch to restore the thing.
I also got to the ServiceMode using dial code:
Code:
*#011#
and it says there that:
Code:
MIPI DEVICE FAIL. DEVICE MID=0x20c, PID=0x008
Googled a bit and it seems that the easiest way to fix this is changing the motherboard.
Some more background if it matters: the device asks for a sim pin and hasn't been dropped. Just happened out of the blue.
Solved
Hi again,
I managed to fix the issue. Seems like this is a common problem but I didn't find anything on why it happens or is, just some sites I personally haven't heard before had some same content how to fix the J500M but the same chip was faulty on the J500FN.
What I did was: re-heat the chip shown on the pictures a bit with a hairdryer that had a really small radius(kinda like put a cone on it because didn't want to heat the whole board up). And that seemed to do it. It probably will break again, since it was and is still faulty and for that reason broke on the first place. Also if you're advanced enough you can try to solder it, but that seems to be for the professionals really.. One little connection in the wrong place and you fry the damn thing!
The safe bet is to replace the motherboard(which I don't currently have money for) but that does the trick for me now. Also if your warranty still lasts you might wanna take it to the Samsung Service shop where they should replace or re-solder the chip safely onto the mainboard for free. Or change it alltogether.
What also sealed the deal for me was that the grille that was on the opposite of the chip what was faulty had this weird burn-mark thingy on it, so thats why the whole thing happened..
The pictures of the faulty component: Thegsmsolution.com
I hope that anyone who struggles in the future with this (or in the past and still hasn't found a way to fix it) can fix it now.