Reflow Main Board @home - Verizon LG G2

I was given this Verizon G2. The complaint was random reboots resulting in getting stuck at LG logo at boot. I Googled and found out that the internal SD card solder connection to the main board goes bad. So, I tried a standard conventional oven @ home reflow of the main board. I removed the G2 main board and baked it in the oven at 380° for 8 mins. I am typing this post from the phone. It successfully rebooted on the first try after reassembly. It has been up running CyanogenMod 12.1 (flashed before bake) for about 10 mins. I booted it and went straight to chrome and xda.com. I'll be back later. I'm gonna go make some calls and play games and see if I still get a reboot.
Update 1: I'm an hour or two in now and have made a 20+ minute phone call while using a Bluetooth headset and still using other apps like social media and reddit.
Update 2 -Final update: Since I got zero replies on this, I'll assume no one cares. If anyone does, the phone is still working. I've been using it as my daily driver for like 3 or 4 days now. I'm gonna keep using it for another couple weeks until my tax return gets in and I can buy an unlocked D851.
.........The End........

I say FASCINATING! How do you get it apart to get the main board out? Mine never gets LTE anymore, which sounds to me like an antenna came disconnected. Heating up the antenna connections might be worth a shot.

fatboyRICH said:
I was given this Verizon G2. The complaint was random reboots resulting in getting stuck at LG logo at boot. I Googled and found out that the internal SD card solder connection to the main board goes bad. So, I tried a standard conventional oven @ home reflow of the main board. I removed the G2 main board and baked it in the oven at 380° for 8 mins. I am typing this post from the phone. It successfully rebooted on the first try after reassembly. It has been up running CyanogenMod 12.1 (flashed before bake) for about 10 mins. I booted it and went straight to chrome and xda.com. I'll be back later. I'm gonna go make some calls and play games and see if I still get a reboot.
Update 1: I'm an hour or two in now and have made a 20+ minute phone call while using a Bluetooth headset and still using other apps like social media and reddit.
Update 2 -Final update: Since I got zero replies on this, I'll assume no one cares. If anyone does, the phone is still working. I've been using it as my daily driver for like 3 or 4 days now. I'm gonna keep using it for another couple weeks until my tax return gets in and I can buy an unlocked D851.
.........The End........
Click to expand...
Click to collapse
You will never be able to truly reflow any electronic devices in your typical household oven as they do not get hot enough. Standard leadfree reflow temperatures peak around 500F, after a ramp up and ramp down time that prevents thermal stresses from destroying the parts. Even with the proper equipment, reflowing BGA/CSP parts is difficult without removing the parts first and then re-balling them as the flux has already been cured during the initial solder process.
I would seriously caution anyone from attempting this without the proper tools and knowledge as you could permanently damage any one of a number of components - I've seen IC packages literally explode after absorbed moisture in the device's resin packaging vaporized by ramping too fast.
T

I care Rich, I care. I loved my G2 but it crapped out on me at school one day. No warning just froze and shut down. Got it back up long enough at one point to pull whatever data I could from it. I ended up getting an S6 Active after jumping between a few crap phones, and the G2 sat in a drawer until tonight when I was looking for some standoff screws in the drawer, and I saw my old flame. The pain from losing her never really went away, and for some reason, I think because I recently did a bit of soldering on a RPi, I thought what if I tried to re-flow this thing? What do I have to lose at this point. Googled g2 mainboard reflow, and your post lit up my life. I baked at 380F for some amount of time re-assembled and I have my G2 again! I may have tried it eventually, but your post inspired me to tear that **** out and turn on the oven right away. I mean, obviously I'm not going to ditch my S6 for the G2, but I'm happy to have it back. Maybe I'll use it for things. Thank you, Rich.

I care!
Mine stopped working.
Was getting pretty hot on a regular basis.
When plugged-in, no lights, just heating up.
Read about "solder re-flow" - don't know how to.

Related

Dead

Hello,
Yesterday my Diamond had died I think
It was frozen and I did a soft reset, screen stays black and nothing happend anymore.
Pulled out the battery, put it back in, and try to turn it back on. It vibrates after a few seconds but the screen stays black.
every help would be great!
Greetings!
Michiel
It might be low on battery so have you tried recharging it?
when i connect it to the power cable nothing happens, the enter button isn't lighting up.
when i connect it to my pc I can browse to the internal storage normally, but it won't charge the battery.
now I'm really confused...
Take out your battery and sim card and leave it out for about 20 minutes and then put it back. During this time, also have your device plugged in (without the battery).
Reflash Everthing
I've pulled out the battery + sim for more than 30 minutes, reloaded the official HTC rom and still the screen is black.
It starts up, vibrates, makes the start sound but the screen remans black.
Now I want to put the orginal HTC SPL back on it, but it doesn't completes the procedure.
Anyone? thnx again!
I got exactly same problem
this has happened to me twice during the past year. the screen was black, although it did vibrate when I turned it on. both times it fixed by itself overnight, very strange.
what I saw is that both times it happened after a long ride with the car, I suspected that due to the prolonged exposure to air conditioning, when I took it out it condensed on the warm motherboard (it was used as a GPS) and some shortcircuit occured.
Unfortunately, 3 weeks ago, again after a long trip with the car, when I took it out it 'died' in 5 minutes (with 100% battery), did not even vibrate anymore when powered on, and never woke up eversince. It is now in service since the 15th of August, with a status on the website of the official HTC service company in Romania (Cirma Electronics) of: "waiting for spare parts" for 5 days...
My guess is that either the MB or the screen fried because of a design issue which caused the condensed vapors to form on some contacts inside...
It sounds as if the device is 100% operational with the exception that the LCD is out. Correct? Or, have you experienced other problems? Try powering up you Diam, then shine a flashlight directly at the screen. If you can see your interface then you have a dead backlight & need a new LCD. If you do not see the image then the LCD itself is defective {Apparently a common problem} & you'll need a new LCD. Either way you should contact HTC service as you have a 2 YR warranty.
@ cocomic: Where is Your Diam on these trips, A windscreen mount or a console mount? If it's a console mount, most likely you have an air vent blowing directly at it & that's just asking for moisture build up. But, if it was a "moisture" issue as you stated, then HTC would not be fixing it for free. They would see the oxidation from the moisture & say that it's your fault for getting it wet, & charge you out the ass for that part. {That's why ALL devices have LDIs} If you use a windscreen mount, then you have your device sitting in the sun for a long time! Sunlight KILLS LCDs!!! It may be more likely that you burned your screen by having it exposed for long periods. But it's probably just the issue that many people have. If you go to HTCforums you will see a lot of people have LCD issues.
If you have warranty return it to the store.
Humblehippie said:
@ cocomic: Where is Your Diam on these trips, A windscreen mount or a console mount? If it's a console mount, most likely you have an air vent blowing directly at it & that's just asking for moisture build up. But, if it was a "moisture" issue as you stated, then HTC would not be fixing it for free. They would see the oxidation from the moisture & say that it's your fault for getting it wet, & charge you out the ass for that part. {That's why ALL devices have LDIs} If you use a windscreen mount, then you have your device sitting in the sun for a long time! Sunlight KILLS LCDs!!! It may be more likely that you burned your screen by having it exposed for long periods. But it's probably just the issue that many people have. If you go to HTCforums you will see a lot of people have LCD issues.
Click to expand...
Click to collapse
I have a windscreen mount, the air vent doesn't blow directly on the device. furthermore, the sun couldn't have burnt the LCD as the last time it died (for good), it was 11 PM.
the phone is in service and has the online status on their website: "the phone is in the lab, waiting for spare part". this means that whatever the issue is, hopefully it's gonna be fixed under warranty.
nevertheless, I find it appalling that a device built in 2008 has huge design and construction faults causing it to malfunction whenever used in a car with the AC turned on...
I'll keep you posted on the outcome
later edit: update: I've just got off the phone with a secretary at the htc service. apparently the motherboard fried and they ordered a new one. from what she said only the case will remain the same, it may be that the lcd display was caught in the chain reaction . the bad thing is that I will probably have to wait for another week, the good thing is that I will get an almost new phone...
as they didn't say anything about the LDI, it's either that the condensed vapors didn't touch it, only the circuits, or the fault did not come from the humidity... one can only guess...
It may not have been condensation that caused the problem. It could be that your Mainboard had a problem that was amplified by your trips in the car. Either way, you get a factory refurbished Diamond, & that's jus' sweet. I have to call them this week about my Diam because my front cam isn't working. I never really use it, but if it's covered, I might as well make them flip the bill while I can.
no, really, do that... i remember that a few weeks before the 'incident' my rear camera stopped working, too... i never payed too much attention as i considered it to be just a spb mobile shell software issue which would have eventually gone away after a hard reset or something...
you are probably right, my MB was slowly dying, organs failing (i have just watched a house md rerun, sorry )... if you have the possibility to have it checked while it's still in warranty and have the camera fixed while at it, why not?
I'm moving this, as it has no pertinece to the original topic. This link; http://forum.xda-developers.com/showthread.php?p=4476473#post4476473 is a post I started to see if anyone else had these issues. Read the update on the first post

Touch Screen has stopped working

Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.
Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.
Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.
When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night
Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.
Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.

HOW TO: fix Droid/Milestone touchscreen lack of responsiveness and Ghost Touch issues

NOTE: THIS SOLUTION IS POTENTIALLY DAMAGING AND MAY NOT WORK FOR EVERYONE
PROBLEM: touch screen acts erratic, notification bar keeps opening, screen appears to be touched by someone else continuously (Ghost Touch), and parts of the screen DO NOT RESPOND TO TOUCH.
MY OWN SPECIFIC CASE: I had the Ghost Touch issue for 3 days suddenly without intro, which often used to go away after a reboot or two, then phone worked normally after I removed the battery and left it in a dry area (in a closed drawer between books, no air entering, very dry atmosphere), however the RIGHT SIDE of the screen (Search button, rightmost letters [L and Delete and sometimes ENTER] do not work. If the phone is in normal landscape, you cannot open the notification bar by dragging it normally.
DIAGNOSIS: for some people, the problem is more severe. The Digitiser itself could be malfunctioning and has to be fixed, while for others it could be a true problem with the screen itself. However, for MANY OF US, it is a problem of HUMIDITY. The humidity sensors are causing the phone to act like that. Some say part of this problem happens because the way the keypad affects the phone internally as you open and close it a lot.
SOLUTIONS:
1- To be safe: send the phone to the shop. Ask them to open the phone and apply an extra layer of insulation, in case the digitiser and the screen are okay.
2- If something is faulty, replace it at the shop.
3- MY OWN SOLUTION: based on something I read many times, the solution was to apply DRY HEAT for at least 45 mins. What I did, based on averaging out many experiences I read online, was to remove the SD Card and SIM, remove battery, I heated up a toaster oven for 10 minutes, waited until the temperature was at about 60-70 degrees Celsius, SHUT DOWN THE HEAT, put the phone on its screen on a plate, screen facing down and covered by a cloth to protect it from direct contact with metal, then all inside the oven. The oven is a relatively big one, so phone was AWAY FROM A SOURCE OF DIRECT HEAT. I closed the lid, then every while 15 minutes I would heat the oven for 40 seconds to maintain the temp. This is LIKE (ALTERNATIVE SOLUTION) leaving your phone in the glove compartment of your car while its parked in a sunny spot, to find it really hot in the morning and tough to touch for a while. TO CONTINUE, after the phone was out of the oven (I can't believe I am saying this), I left the phone overnight in a dry area for 8 hours (could need less time). Then, I put everything back in, plugged it, and THE PHONE IS WORKING PERFECTLY NOW!
NOTE that solution number 3 could affect your keyboard buttons if heat is too much. It may cause the glue holding the keys to melt a bit. Be delicate with your keyboard after you restore your phone.
Again, I only did this YESTERDAY. With the exception of some keypad stickiness, the phone is working perfectly now.
I hope this was useful
B.
EDIT: Today is the First of May, phone is still working without a glitch
N.B. Press the Thank you button if you wanna congratulate me on daring to toast my milestone in the name of scientific inquiry
SECOND EDIT: Phone did it again for 2 days. Applied the same method, and it worked again. I think partially it happened because I was in a very humid location.
That didn't work for me, I had no option but to replace the touchscreen/gorila glass.
I love the idea of toasting a milestone
Thought with all my aggression against Moto, I think I just might leave it in there
Luckily I dont have these problems so I wont get tempted
AirLancer said:
I love the idea of toasting a milestone
Thought with all my aggression against Moto, I think I just might leave it in there
Luckily I dont have these problems so I wont get tempted
Click to expand...
Click to collapse
I have to admit, I cared litte whether or not this actually worked. I just wanted to toast it But it did work, so
Pretty tempted to try this out, I think I will when I have free time.
My phone had the dead zone problem for 2 months now, but in some very rare cases, like when it's a very hot day, the screen will work normally for a minute or something. Then it goes back to dead part. I assume this would fix it?
Lesiroth said:
Pretty tempted to try this out, I think I will when I have free time.
My phone had the dead zone problem for 2 months now, but in some very rare cases, like when it's a very hot day, the screen will work normally for a minute or something. Then it goes back to dead part. I assume this would fix it?
Click to expand...
Click to collapse
If it DOES indeed work on hot days, then it means the phone is not entirely dead. But I would suggest you do something less drastic first, such as the Glove Compartment method. No responsibility though
If you're trying to remove moisture, you could also try putting it in a baggie of crystaline cat litter (NOT the clay kind!) - this stuff is sold at a MUCH higher price as a way to save a phone from water damage, but it's the exact same substance. Does a great job removing moisture. It's the same sort of silica gel that's in those packets in medicine/vitamins that says "Dessicant - do not eat".
Or you could just put it in a sealed bowl with raw rice for a couple of days... this is the best and cheapest way (and then you have the silicon "grains", the ones that you find in shoe boxes or computer parts boxes).
Sent from my Milestone using Tapatalk
CybeRNerO said:
Or you could just put it in a sealed bowl with raw rice for a couple of days... this is the best and cheapest way (and then you have the silicon "grains", the ones that you find in shoe boxes or computer parts boxes).
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Pretty sure that rice doesn't do anything, I don't know how that started as a suggestion, but its not better than anything else; its not known to be absorbant, but the silicon is.
I've tried the method but the right segment of the digitizer still doesn't work.
My biggest issue with regards to "lack of responsiveness" are the 4 capacitive buttons. Pressing the Home key is always hit and miss. I know I hit it all the time because I can feel the vibration feedback but it only goes to homescreen 50% of the time.
Will also be testing this out as soon as I have the spare time. My screen started acting up after I accidentally put my milestone in a small beer spill at a party Hopefully this will work out for me too!
Abazel said:
I've tried the method but the right segment of the digitizer still doesn't work.
Click to expand...
Click to collapse
Luckily for me, I was still under warranty, heh. Cause I had insurance. This is my second Droid this has happened to. Hopefully my replacement won't do the same thing.
How many times did you reheat the oven? I tried just once and it didn't help. My phone has been having this problem since January.
decon89 said:
How many times did you reheat the oven? I tried just once and it didn't help. My phone has been having this problem since January.
Click to expand...
Click to collapse
I feel I am on a cooking show
Well, depends on your over. Mainly I was trying to maintain a temp varying between 50-60 c. Mostly 50, but sometimes 60 to up the ante a bit and make sure things stay warm. 30 minutes at least. However, I have to say that I did this twice in 6 weeks, and after that the phone just died again, and I found my warranty card and sent it there to be fixed, and they fixed it, but ruined something else.
If you have the warranty card, take your phone and send it to them Someone told me the method worked and the phone has been good for quite a while, but most of us seem to re-experience the issue after a while.
I've been having these issues for a few days now too, and I think I know why. I've been using this Milestone for 4 months now, and I never had this problem until a few days ago. What I noticed yesterday was that after some acting up, the phone started working properly again. So I ran Touch Test. And I noticed that if I pressed really hard on the top side of the phone(where the logo and the ear piece are located) it started acting up again. My first impression was that the glue holding down the gorilla glass was loose. So I left the phone as usual on my night stand and then I tried the same thing with the pressing on the same area. Guess what? It didn't happen again. Now there seems to be no problem. So I tried to remember what happened yesterday before the screen started acting up, and I remember talking to my wife for a while when I was in my car. Yesterday was a pretty hot day and I was a little sweaty when I talked to her. Now since only that specific part with the earpiece was causing this issue(I tried pressing equally hard on other areas without any problem my guess is that the insulation between the earpiece and the touchscreen has been breached. Maybe because of all the sweat that went in there in time. You know the salt and acids in the swear are known to melt things, and poor quality glue is among them.
How to fix this? I do not know yet, but I do have a good idea that I'd like to share. I want to buy a screen protector foil, and put just a little band around the ear piece. That would probably lower my in-call volume, but since the Milestone is very loud anyway I hope it the quality of the calls won't be too much affected. After that I'll use it in normal conditions again and see if the ghosting happens again.
try completely formatting your SD CARD/PARTITION.
& then reinstalling using (FAT 32/EXT 2, 3, or 4)
sometimes traces from the previous ROM might interfare with touch codecs (maybe)
just trying to help. had similar issue & this is what i did.
bandroid842 said:
NOTE: THIS SOLUTION IS POTENTIALLY DAMAGING AND MAY NOT WORK FOR EVERYONE
PROBLEM: touch screen acts erratic, notification bar keeps opening, screen appears to be touched by someone else continuously (Ghost Touch), and parts of the screen DO NOT RESPOND TO TOUCH.
MY OWN SPECIFIC CASE: I had the Ghost Touch issue for 3 days suddenly without intro, which often used to go away after a reboot or two, then phone worked normally after I removed the battery and left it in a dry area (in a closed drawer between books, no air entering, very dry atmosphere), however the RIGHT SIDE of the screen (Search button, rightmost letters [L and Delete and sometimes ENTER] do not work. If the phone is in normal landscape, you cannot open the notification bar by dragging it normally.
DIAGNOSIS: for some people, the problem is more severe. The Digitiser itself could be malfunctioning and has to be fixed, while for others it could be a true problem with the screen itself. However, for MANY OF US, it is a problem of HUMIDITY. The humidity sensors are causing the phone to act like that. Some say part of this problem happens because the way the keypad affects the phone internally as you open and close it a lot.
SOLUTIONS:
1- To be safe: send the phone to the shop. Ask them to open the phone and apply an extra layer of insulation, in case the digitiser and the screen are okay.
2- If something is faulty, replace it at the shop.
3- MY OWN SOLUTION: based on something I read many times, the solution was to apply DRY HEAT for at least 45 mins. What I did, based on averaging out many experiences I read online, was to remove the SD Card and SIM, remove battery, I heated up a toaster oven for 10 minutes, waited until the temperature was at about 60-70 degrees Celsius, SHUT DOWN THE HEAT, put the phone on its screen on a plate, screen facing down and covered by a cloth to protect it from direct contact with metal, then all inside the oven. The oven is a relatively big one, so phone was AWAY FROM A SOURCE OF DIRECT HEAT. I closed the lid, then every while 15 minutes I would heat the oven for 40 seconds to maintain the temp. This is LIKE (ALTERNATIVE SOLUTION) leaving your phone in the glove compartment of your car while its parked in a sunny spot, to find it really hot in the morning and tough to touch for a while. TO CONTINUE, after the phone was out of the oven (I can't believe I am saying this), I left the phone overnight in a dry area for 8 hours (could need less time). Then, I put everything back in, plugged it, and THE PHONE IS WORKING PERFECTLY NOW!
NOTE that solution number 3 could affect your keyboard buttons if heat is too much. It may cause the glue holding the keys to melt a bit. Be delicate with your keyboard after you restore your phone.
Again, I only did this YESTERDAY. With the exception of some keypad stickiness, the phone is working perfectly now.
I hope this was useful
B.
EDIT: Today is the First of May, phone is still working without a glitch
N.B. Press the Thank you button if you wanna congratulate me on daring to toast my milestone in the name of scientific inquiry
SECOND EDIT: Phone did it again for 2 days. Applied the same method, and it worked again. I think partially it happened because I was in a very humid location.
Click to expand...
Click to collapse
Thank you for that Solution.
It fixed the Issue of my friends MS without other problems
I'll have to try and the oven methode again. My phone has started to really act up again.
I've tried to install new roms, wipe ect. and it doesn't help with the screen.
Have anyone tried to replace the digiziter? They are pretty cheap on ebay
My milestone started freaking out just an hour ago. No more warranty here but I'm not brave enough to do the oven method. Had anybody tried the Rice alternative?

[Q] phone's touch screen having difficulties

my phone is having difficulties with the touch screen. at the top of the screen, it totally wont work when I touch it. do I need to replace the screen or is there a way to fix it? I cleaned the screen many times so, help me?
It's just the top part that isn't responsive?
DO AT YOUR OWN RISK!!!!! but it worked for me with my screen problems. I had dropped my poor hero in a glass of water. After quick action and rice it was dried pretty good but the bottom screen would go all wonky and only a reboot sort of fixed it till I stumbled on Google.
1st take out the battery and SD card!!!!!!! Can't stress this enough.
I had found if you took a hair dryer on high heat for about 2 minutes and move it around the screen during that time so as to not heat just a certain spot. After the approximately 2 minutes place something heavy like a big book but not too heavy to crack the screen and place it on top of the phone til it cools. About 15 minutes. Replace SD card and battery and boot up. Should be responsive as hell now.
Haven't had an issue since and can't tell its been in water unless you look at the stickers ... oh well I'm never selling it so
I had been dealing with the same nightmare your complaining of for weeks.
Eventually i had to reflash the clean sprint OS and take it to the store and within an hour they had replaced the touch screen and it was just like new. As of yesterday I did not have insurance but fortunately they have open enrollment for it, and at a cost of $4 for comprehensive insurance they were able to replace the touch screen.
Before biting the bullet and taking it to tech support I tried recalibrating the keyboard, flashing tons of different roms, cleaning it, but finally brought it in. I suggest you do the same since we are not the only ones complaining of this problem. Goodluck

Possible MAJOR discovery regarding battery/red lite issue.

So I'm one of the people that's been having major issues with the red light/ no boot issue.
I think the issue (for me at least) is a hardware flaw. Upon completing the steps to reboot the phone (take case apart, disconnect battery, connect power, wait for battery charge indication, reconnect battery) I can get the phone to boot and function just fine.
I have discovered that upon screwing the battery connection back into the phone, it applies a bit too much pressure on the connection which sends the phone back into the redlite "no boot" mode.
TL;DR, If the battery is connected to the phone too "tightly" with the screws, the issue is caused.
Hardware flaw? I think so.
My Fix? Took out the connecting screws, the connection seems to hold without them and there is no more pressure on the connection without the added thickness of the screws (when putting the back of the case on)
EDIT: Here's a video of what I'm talking about, for those of you who haven't had to deal with this (yet?)
Video of Issue
Hey Google/LG, if you're reading this, Send me a new phone, please!! This is unacceptable!
Good find. Maybe you could try packing the back in places so that no pressure is put on the battery
Michealtbh said:
Good find. Maybe you could try packing the back in places so that no pressure is put on the battery
Click to expand...
Click to collapse
Good Idea, will try it if I encounter this problem again. Seems to hold up, though, even when pressing on the back of the case where the connection is made (down and to the left about 0.5cm from the "n" on the back of the case).
bump--I think people should really see this.
Nice find dude!
I always thought it was a software issue but turns out it is not!
It's still strange that most people have encountered the issue when benchmarking.
Sent from my Nexus 4 using Tapatalk 2
alwaysbboy said:
It's still strange that most people have encountered the issue when benchmarking.
Click to expand...
Click to collapse
Perhaps it's just a coincidence. I'll still stay away from benchmarking, though.
alwaysbboy said:
I always thought it was a software issue but turns out it is not!
It's still strange that most people have encountered the issue when benchmarking.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If the finding is true then here my theory on why it happens mostly during benchmarks.When you run benchmarks, your phone and battery heats up a lot. This can cause the connectors to expand causing screws to get tightened.
i can confirmed this find is true, altough its kinda late for me to read this thread.
here is my version.
im a proud owner of nexus 4. got my phone from the 1st batch order, and the original bumper also :angel:
this morning while watching my kid at school, got nothing to do but overclocking my nexus 4 with morfic's latest beta kernel.
silly i put the min and max at 1.8++ghz and run an antutu test on it. and in another 5 seconds the N4 turned off and practically dead. all buttons combo were negatives. as soon as i arrived home i plugged in the official charger. it just blinking red. few moments after i plugged in the N4 to my laptop. blinking red and driver installed notification showed up. then the red light gone. like forever... no red when i put it on charger nor when connected to the laptop.
ok its a dead meat. im in JAKARTA n got my n4 from the US. none of any LG service centre in my country could help me with it. and the RMA things just too far from me.
so since i left with zero to none option, i was wondering "what if i take off the battery?"
i remember read an article from ifixit about how to teardown the nexus 4 then i found the link.
here it is:
http://www.ifixit.com/Teardown/Nexus+4+Teardown/11781/1
what i did was:
1. follow steps number 6 [pictures #1 & #2]
2. number 7 [pictures #1 & #2]
3 and number 9. [pictures #1 & #2. no need do the pictures #3]
4. see the white wire with blue sticky tape right next to the battery? i dont know what is that but i unplugged the golden head off also.
i left it that way for 10 minutes before i put it back all together again [ including the screw battery port holder. just dont screwed them too tight. give a small effort to none power ]
all done and i pressed the power button. its ON like nothing happened before.
when im about to share my fixed in the other thread, i got someone direct me to this thread. so here i am confirming this fixed is legit
Wow!! This fixed my nexus that didn't even have an LED light. You are a life saver!
It's been dead for a week and I was just waiting on warranty. But now it's up and running like a bawse!
Hi
ethugp3pp3r said:
So I'm one of the people that's been having major issues with the red light/ no boot issue.
I think the issue (for me at least) is a hardware flaw. Upon completing the steps to reboot the phone (take case apart, disconnect battery, connect power, wait for battery charge indication, reconnect battery) I can get the phone to boot and function just fine.
I have discovered that upon screwing the battery connection back into the phone, it applies a bit too much pressure on the connection which sends the phone back into the redlite "no boot" mode.
TL;DR, If the battery is connected to the phone too "tightly" with the screws, the issue is caused.
Hardware flaw? I think so.
My Fix? Took out the connecting screws, the connection seems to hold without them and there is no more pressure on the connection without the added thickness of the screws (when putting the back of the case on)
EDIT: Here's a video of what I'm talking about, for those of you who haven't had to deal with this (yet?)
Video of Issue
Hey Google/LG, if you're reading this, Send me a new phone, please!! This is unacceptable!
Click to expand...
Click to collapse
This is simply a fault with your phone. Most likely a chip or component isn't soldered correctly or you have a dry joint. When the board is flexed by some force it is breaking or making the connection.
The time will come when even this "fix" for you stops working.
The reason the phone is sometimes failing during stress tests and not coming back on is a safety device. The lithium battery is reporting it is under stress or too hot and the phone shuts down to avoid an explosion. Because there is a big chance the battery is permanently damaged and so potentially dangerous the phone remains in a safety condition wanting to be returned to the manufacturer for testing. Lithium batteries if damaged can explode, imagine if a phone explodes next to your face while you are talking on it? The manufacturers, not wanting a law suit that disfiguring someone might bring, deliberately er on the side of caution.
It's a bit like the limp home mode some cars have when they detect some parameter outside of the norm. You might be able to reset that back to normal by some hack found on the internet but it hasn't fixed the underlying cause.
Regards
Phil
This thread should be stickied as this is a common problem with the Nexus 4.
Just wrote this to bump the thread back to first page so more people can see
Sticky This!
This needs to be stickied!
I'm having a similar issue with my completely stock nexus 4. I can only turn the phone on when it is connected to charger, but this is also very rare. If I manage to turn it on, it shows I have -22% battery left and this doesnt change. I can enter bootloader when charger is connected. I have left it charging overnight, but still it doesn't boot without the charger connected.
Any idea if the fix described here can help me? Can LG service somehow see that the phone has been opened?
I live in unsupported country, so I can't send the phone back to Google. My only hope is this fix here or my local LG service, but I'm not sure if my local LG can even help me, because the phone is not sold here.
Ahhh good thoughts. I've got a replacement battery on the way for that reason... Hopefully it's a problem there.
Sent from my Nexus 4 using xda app-developers app
Nexus 4, 8Gb, in UK
It arrived Sat (2 days ago) @ 80% charge & about 5 mins after unpacking I noticed it was the 8Gb & not the 16Gb I had ordered
Phoned google for RMA - currently awaiting replacement.
Repacked it, took it to work, had a play, installed maybe 3 apps, browsed a lot though - reboxed it afterward. as I had no case & as I didn't want to risk the RMA I decided not to take it next day.
Case arrives from amazon & I'm back to work today, so I decided to risk it - nexus battery almost dead & powered off.
Connected charger - nexus indicates charging on screen when power button is pushed.
As I lift the phone to power it on 20mins later, charging display blanks & red light starts blinking - swap cable, charger & check connections - all ok - nothing but a red light on a dead phone.
*panic*
read internet: wasted half an hour on button combos streetfighter would be proud of
Found this post here:
http://forum.xda-developers.com/showpost.php?p=37461951&postcount=3
"Seems to hold up, though, even when pressing on the back of the case where the connection is made (down and to the left about 0.5cm from the "n" on the back of the case)."
After pressing down around there, the red light clears instantly, small vibration & nexus is now charging again.
Am glad I'm sending this unit back, if replacement does this within 30 days then I will give up on LG & wait for next gphone; between this and the glass cracking issues I read of, this may not be the best nexus ever quality wise.
tl;dr Almost virgin Nexus got red light & unresponsive on first charge. After all else failing, firmly pressing the back, directly above the battery connection area immediately revived it...
kwft said:
Nexus 4, 8Gb, in UK
It arrived Sat (2 days ago) @ 80% charge & about 5 mins after unpacking I noticed it was the 8Gb & not the 16Gb I had ordered
Phoned google for RMA - currently awaiting replacement.
Repacked it, took it to work, had a play, installed maybe 3 apps, browsed a lot though - reboxed it afterward. as I had no case & as I didn't want to risk the RMA I decided not to take it next day.
Case arrives from amazon & I'm back to work today, so I decided to risk it - nexus battery almost dead & powered off.
Connected charger - nexus indicates charging on screen when power button is pushed.
As I lift the phone to power it on 20mins later, charging display blanks & red light starts blinking - swap cable, charger & check connections - all ok - nothing but a red light on a dead phone.
*panic*
read internet: wasted half an hour on button combos streetfighter would be proud of
Found this post here:
http://forum.xda-developers.com/showpost.php?p=37461951&postcount=3
"Seems to hold up, though, even when pressing on the back of the case where the connection is made (down and to the left about 0.5cm from the "n" on the back of the case)."
After pressing down around there, the red light clears instantly, small vibration & nexus is now charging again.
Am glad I'm sending this unit back, if replacement does this within 30 days then I will give up on LG & wait for next gphone; between this and the glass cracking issues I read of, this may not be the best nexus ever quality wise.
tl;dr Almost virgin Nexus got red light & unresponsive on first charge. After all else failing, firmly pressing the back, directly above the battery connection area immediately revived it...
Click to expand...
Click to collapse
So you didn't even take it apart to revive it? Interesting... I haven't had this issue myself in the 2 and a half months with this phone, but nice to know what to do if it arises.
It sounds like it could be dodgy solder joints, although I'm tempted to say that I'm currently ****ting myself. Things like glass cracking doesn't worry me, people are clumsy and that usually will cause that. However, we have no control over the quality of the circuitry inside.
The thing is, the poster above says wait for the next GPhone, it's been announced for next year. So you're going to be waiting a hell of a long time. This phone I hope will suffice while you do so however.
kwft said:
After pressing down around there, the red light clears instantly, small vibration & nexus is now charging again.
Click to expand...
Click to collapse
Nice to see that helps. I need a fix that allows me to "pull" on it and then push it again

Categories

Resources