Okay, so today I bought a Pixel Xl for 30 bucks off a guy on craigslist. He stated in the post that the phone was continuously rebooting and he couldn't fix the issue. He ended up buying a Pixel 4 XL instead of paying to have a repair done. I fix electronics and all that good stuff so I figured it would be a component on the logic board, most likely some failed solder joints or something along those lines. Well before I went and opened it up a I stated realizing that there were times when the phone would boot into android but only if I was holding the device. I thought it was weird and so I kept reading online and someone mentioned heating the back of the phone up would get it to boot and sure enough they were right but inevitably it would reboot again. Well I eventually realized that if I continuously pressed to power button as follows..... 1 press 1 press, wait 1 press 1 press wait the phone would remain on. Thats when I started seeing the lock screen was not activating at all as I pressed each time which it should've done. So I continued to press the button at that same rate of speed for about 2 minutes and eventually the lock screen began responding as it should've.
Long story short, if your Pixel is stuck in a constant reboot then it looks like a possible cause is the pin on the ribbon cable becoming pushed in and held in place by something. Could be dirt and gunk or something that possibly seeped into the button area and is causing the button to remain in a pressed state regardless of any actual pressure being applied to the button that's meant to activate the pressure point on the power cable. So if you're in the same situation try continuously pushing the button in order to free what's ever loved itself in place being the button and eventually the device will stop rebooting. You should also use a tiny bit of rubbing alcohol on a tip and light apply it around the power button to help free up any dirt that's undoubtedly managed to make its way in there.
HOPE THIS HELPS SOMEONE ELSE!!
Loved your solution. It worked like a charm on my pixel 3XL.
Initially while reading the other articles which clearly stated it's a hardware issue and that you need to go to store, or do some factory reset and stuff, it freaked me out. But with more research I was lucky to have come across your article. I'll be honest here, I didn't think it will work. Sounded like a troubleshoot kind of solution which generally aren't so effective, but, conitinuously pushing the button, worked like a charm and my device switched on.
Thanks for saving my device, my repair cost money, my mental peace.
Greetings from India.
This is a light case scenario, because people who are in this kind of situation don't have a issue with the buttons. You would probably be able to define this behavior if the screen immediately blacks out, or you see a blue line across the display (sign of hard reboot). More common cases are the device sticking through the Google > G animation then crashing, which is often the case of failing UFS, more potential in 128gb models, however I've seen and even owned a 32gb model that had this same exact issue.
Ohhhhhhhh thank you so much!! Thought it was a software failure but it kept rebooting when rebooting into fastboot by holding power down. After hitting it hard on the table multiple times it finally stopped rebooting. Very bad hardware by Google.
djared704 said:
This is a light case scenario, because people who are in this kind of situation don't have a issue with the buttons. You would probably be able to define this behavior if the screen immediately blacks out, or you see a blue line across the display (sign of hard reboot). More common cases are the device sticking through the Google > G animation then crashing, which is often the case of failing UFS, more potential in 128gb models, however I've seen and even owned a 32gb model that had this same exact issue.
Click to expand...
Click to collapse
if that were the case, would it not random or bootloop whether in recovery or fastboot?mine does an infinite bootloop but it wont bootloop in stock recovery or fastboot. sometimes it would crash and reboot then spin to a bootloop from twrp. google pixel
I finally figured out a solution for this as well! I sideload the latest Google OTA for an XL and it fixed the stuck bootloop! It was simply a software issue!
Related
Hey guys,
So today my phone started acting up, the power button has become touch sensitive. As soon as I touch it or come close to it on either side of it, it acts as if I'm holding it down. I tore it apart to see if it was sick and it isn't so I can't figure out why it's doing that? Anyone ever had this same problem or have an idea of how to fix it?? Any help would be greatly appreciated.
This has become a common problem with our phones; do a search for "power button" and you'll find several threads reporting the same/similar problems. Some people seem to have managed to fix their issues by wiping the area with alcohol or re-flashing their recovery and/or ROM (I personally don't see how that could help a hardware issue, but whatever). In my case, as well as several others, the power button became permanently damaged, the phone was stuck in a vibrating bootloop and the only way to stop it was to take out the battery. I chose to have the power button replaced using the MobileTechVideos repair service. I wasn't 100% satisfied with their customer service, but the power button was replaced and my phone works fine now.
I suggest the same, I got my phone back a week ago after my power button got stuck.
KaneHusky said:
I chose to have the power button replaced using the MobileTechVideos repair service. I wasn't 100% satisfied with their customer service, but the power button was replaced and my phone works fine now.
Click to expand...
Click to collapse
I bought a replacement power button for my Sprint S2, and it looks like they now offer mail-in power button repair service too. Their feedback looks better than the experience you had.
root_galaxy said:
Hey guys,
So today my phone started acting up, the power button has become touch sensitive. As soon as I touch it or come close to it on either side of it, it acts as if I'm holding it down. I tore it apart to see if it was sick and it isn't so I can't figure out why it's doing that? Anyone ever had this same problem or have an idea of how to fix it?? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Don't bother buying a new power button yet! I had the exact same problem, and it was throwing my T989 into a boot loop. Your most likely problem is that your power button internals are getting jammed up with dirt from your finger and lint.
Here is a thread with a person experiencing a similar problem. Here is another thread where I go into detail on how to attempt to fix your problem. You already have the know-how on how to disassemble your phone, so this should be easy for you.
HERE is the original thread that I found which addresses the problem you seem to be having.
CRC QD Electronic Cleaner saved me from having to replace the hardware and I haven't had power/boot loop problems since!
If you feel as if you don't want to over-do it with the electronic cleaner, you can give your entire logic board a nice rub-down with some Isopropyl alcohol (I got mine from a general pharmacy). You should be able to get the electronic cleaner from any auto shop, but I've had specific success with CRC QD Electronic cleaner. I don't know enough about electronics or chemistry to recommend any other brand/type, so if you can't get that specific brand, then I can't help ya!
Hey all! I've had my T989 for about half a year now, and since I've gotten it, it's had this strange issue that has persisted across multiple complete hardware and software swaps. I'm pretty convinced I won't be free of it until I can afford to upgrade, but I figured I'd post here since NOTHING seems to work, and see if anyone can come up with something.
To start off, I got the device from Koodo, as they had a great deal on it that allowed me to get it cheap. Ever since the first device, it's occasionally rebooted for seemingly no reason, and hung after the initial boot screen. In order to reset it, I have to hold the power button for a good 10 seconds, causing it to fully reboot again after two short vibrates, following which it will boot up normally.
I initially had a broken speaker, so I took it back and had it replaced, only for the second device to have the same issue. I took that back, and temporarily tried a few other carriers with different phones, but came back to Koodo because I love the T989 too much for the price.
This third phone still had the issue, so I took it back and called Koodo's support line. They fedexed me a new model, which STILL had the same issue.
That would make me think it's a software issue, and a friend suggested that perhaps I had a bad root, but after the phone finally slowed down to near-unusability on Jedi Knight 6, I flashed a few stock ROMs back onto it, until finding one that returned it to normal speed.
I've re-rooted and tried multiple ROMS, with no success. The issue seems to persist across hardware and software. The only thing that seems to be common among them all is that I had a ghost armor screen protector applied to them all. I've since heard that ghost armor was using what was basically soapy water to clean the phone before applying the protector, and that this could have entered the phone and caused some kind of problem.
It seems to happen far more frequently when the phone is in my pocket, which leads me to think that it may have something to do with the power button, and perhaps the moisture or something else causing partial pressure on the button to trigger an incorrect reboot. This seems like a long shot to me, but it's the only commonality I can find.
I should note that I have seen the phone do this randomly while sitting on the desk in front of me after I set it down, so it may be that turning the screen off manually causes the same incorrect reboot issue, or it could be that I simply have some kind of magnetic aura that is insistent on trolling me.
Either way, thanks in advance to anyone who replies!
I just got this tablet (to replace the garbage SGH-I467) a few days ago (Thu., May 15th). For the first couple of days it worked like a dream. However, the last 4 nights/3 days, I have been encountering some strange issues. What I will do here is describe the issues I've been having, what I have done in attempts to fix them, list some of the things I think may have caused it, and include any additional info/questions.
Before all that though, I would like to mention that I am not a developer, but I am a bit 'tech savvy' and am more familiar with/knowledgeable of technology than the average user. Also, I have spoken with Samsung tech support and even had the support guy access my Tab Pro 12.2 remotely (I will explain what I learned from that below). So, without further ado (I apologize in advance for the long winded nature of this post, but I want detailed):
The Issues:
1) Screen "flickering"—By flickering I mean that it is shutting off and turning on rather rapidly and sporadically, though inconsistently.
I first encountered the problem 3 days ago (the 18th).
Four nights ago (the 17th), before going to bed, I plugged the device into the same outlet I have used for all my mobile devices, when I woke up (on the 18th) the screen was doing exactly what I described. I hit the home button a few times and it stopped.
That night (the 18th) I plugged it back in to the usual spot before going to bed. The next morning (yesterday, the 19th), the screen was "flickering" again. I tried to press the home key a few times, as well as both the soft keys, nothing. In between "flickers" you can see the lock screen, where I have to enter a pin, but even while visible I can't type anything. So this time, to try to solve the problem, I held the power button + volume up to get to recovery and wiped the cache partition, rebooted the device, and viola, it worked again. Thinking that I may have to factory reset the device if the problem persists, I used Kies to backup all my data. I used the tablet the rest of the day, even plugged it in (in a different outlet than the one next to my bed) for a while and had no issues.
Last night (the 19th) I did pretty much the same thing, but this time, thinking that it might be an issue with the device getting too much power (the Quick Start Guide says: "Note: Connecting the travel adapter improperly may cause serious damage to the device."), I used a travel adapter from one of my other, USB 2.0 devices (the only difference between the adapters is the output: 2.0 = 5.0V—2.0A vs. 3.0 = 5.3V—2.0A, and output was specifically what I was concerned with). This morning (the 20th) the problem has returned, but now includes my second issue: the hard home button and both soft keys, back and recent apps, no longer function. So I immediately tried to wipe the cache partition and reboot, but this time it didn't work. Thankfully I had anticipated this yesterday and had that Kies backup, so I wiped the entire device back to factory settings. But alas, it was unsuccessful and the problem persists, including the loss of button functionality, with the exception of the power and volume buttons.
It is important to note that when I first got the Tab Pro 12.2 and set up the lock screen, I used the option that delays the actual locking of the device 10 minutes after screen timeout, but set it so that if I lock the screen with the power button it ISN'T delayed and immediately locks. That being said, a couple of times when the "flickering" stopped long enough to momentarily use the device, I was able to enter my pin and unlock. But when the screen starts flickering again, it locks the device, so the power button must be affected as well. Though since the first factory reset of the device, I haven't set up a pin. I have done several factory resets and none of them have worked. The best result has simply been limited (no back, recent apps or home key) and momentary functionality. I tried using Kies to do emergency firmware recovery, but every time I click the option it disconnects the device.
When Samsung tech support remotely accessed by device (I used one of the momentary functionality windows to download the required application) the agent was able to utilized soft and home key functionality, even though I couldn't. This tells me that it was hardware related, not related to UI/software.
So there are a couple of things I think may have caused/contributed to the problem:
The first, which I vaguely touched on above, is the power issue. Perhaps I have shorted the device out somehow. The outlet I use to charge things while I'm sleeping is on the wall behind my bed, so I have to use a common extension cord, one that has 3 outlets at the end. I have a light plugged into that and in the past have charged both my SGH-I467 (AT&T Note 8.0) and my SGH-I747 (AT&T S4 Active) with that cord and outlet. That is the only place I have charged the SM-T900 overnight, but none of the other power sources I have used have caused these issues.
The second possibility is a virus some sort. I have never used the Samsung app store on any of my other devices, but in order to update the Hancom Office suite I had to. Since I had an enjoyable time using it to that end, I decided to see what else I could find on Samsung's store. I downloaded a couple of things (the "Official Captain America game" and a couple wallpaper/theme apps) and was looking around the store to see if there was anything else I wanted to download. I found several apps that had reviews claiming they were trojans, so I immediately checked the reviews for the apps I had downloaded, but none of them had similar reviews. However, that does not mean they didn't have viruses.
So, what do the resident Android gurus of XDA think about these issues?
I tried searching all over the forums and elsewhere online for people having the same issues, but couldn't find anything. Have any of you ever encountered something similar to this?
Until recently, I hadn't ever heard of anyone getting a virus on an Android device. Are they common? What is the nature of Android viruses?
If these issues do have something to do with overcharging/shorting the device, how can I mitigate that problem? Tonight when I charge the tablet, instead of using the USB 3.0 charging cable, I am going to try just using the 2.0 cable. As I understand it, that can be done by simply plugging it into the right side of the port. Hopefully that will stop exacerbating the problem.
Again, I apologize for such a long winded post. I would like to thank you all in advance. If ever I have problems with an Android, you guys are the ones to ask!
*UPDATE* Before I started typing this I was attempting to run the Kies 'Firmware Upgrade and Initialization', as opposed to 'Emergency Firmware Recovery', to see if that too would disconnect the device. Unfortunately it said that my device needed to be charged first. So I shut it down and plugged it into a surge protected strip and began typing this post. Occasionally I would go over an check the charge. While it was shut down and charging I was able to use the home key to bring up the green battery. Once the charge looked like it was about 75% complete I turned it back on and lo and behold, the "flickering" issue looks resolved and so does the button issue. I can go back, enter the recent apps and task manager, and use the home key functions. For how long this will last, however, is unknown. I guess we'll see in the morning. I'll post what happens tomorrow.
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
RE: Case?
dodo99x said:
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I am not using a case or cover at all...
same issues here
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
VeinkWiles said:
So, what do the resident Android gurus of XDA think about these issues?
Click to expand...
Click to collapse
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Mike Austin said:
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Click to expand...
Click to collapse
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
VeinkWiles said:
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
Click to expand...
Click to collapse
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Re: developer settings; display touches
dottat said:
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Damn! That's an outstanding idea! The only downside is that last night I sent the tablet to Samsung's repair department, so I can't test that out. But once I get it back, if the problem persists I will definitely be doing that first. Thanks for the advice dottat.
Fw:Re: developer settings; display touches
mikegbg said:
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
Click to expand...
Click to collapse
Hey dude, check out dottat's reply. He's got a really good idea that may shed some light on the source of the problem. Unfortunately, I can't try it out. If you do it, let me know how it goes. Maybe you can take some screenshots? Either way, hopefully you can get something out of it.
Hey all, so I just replaced the screen (followed the great guide on this site) and now I'm getting some odd behavior when trying to boot.
The power button is completely unresponsive. When I plug the phone into power, the LG screen comes up for ~3 seconds, as normal. The LED is flashing thru all the colors per the usual as well. Then the screen goes black for another 3 seconds, all the while the LED flashing. Then LG pops up again just for a moment, then to the normal phone-is-off-but-charging screen, with the LED flashing red.
Really don't know what to make of this. I had it rooted with a one-click root from here. The only changes were deleting stock apps and enabling the front touch keys (but never had an issue with it booting after this, I did that at least a week ago). Also my PC recognizes that something is plugged in, so I guess that's good.
Thoughts?
Update: tried booting into recovery mode, I held the buttons for much longer than normal to no response. As soon as I let go, I get the LG screen. Then black. Then LG. Then an unusually long AT&T screen, then it booted. Now the power button works as it should, and it boots in that same odd fashion. And it seems that I can not go into recovery. Yikes.
I'd be fine with that except I have a dead zone across the lower portion of the screen, it's about a half inch tall and about covers the asdfgh... row of the keyboard. Weirdly if I start pressing on any other key and then swipe to any area in the "dead" zone it WILL register, as in, I can select the S key, normally in the dead zone, but swiping to it from a working area. Will try soaking the mobo in alcohol and swabbing the digitzer connector with a q-tip. Any other thoughts?
Update 2: I tried cleaning the contacts of the digitzer connection- both the end of the cable and the motherboard connection- with rubbing alcohol. Reassembled, and we're back to square one. Power button unresponsive, when plugged in I'll get the LG screen, then black, then the LG screen will flash and I'll get the chargining screen. But now, trying to boot into recovery mode does nothing. So then I soaked the mobo in alcohol, and cleaned ALL the contacts and ribbon cables on the frame. Reassembled, no change. I really hope someone sees this, as I'm at he end of my tech know-how. Tonight I'll try to reconnect my old touchscreen and see what happens. Maybe the new one is just defective? But you'd think the phone would still turn on...
God I hope somebody sees this. I feel like a complete nut talking to myself.
mityman50 said:
Hey all, so I just replaced the screen (followed the great guide on this site) and now I'm getting some odd behavior when trying to boot.
Click to expand...
Click to collapse
Okay sounds like a hardware issue with the power button being unresponsive. I would take the device apart look around all connections of the power button and look for any hair line cracks or dirty, sticky, grimmy connections. Try cleaning upall that stuff, while there I would look at the digitizer and clean that up. When done flash a new rom with the LG flash tool, allow boot and reboot normally several times before testing. I hope this helps I am new to the phone and have yet to get my repair kit for it so I will not know much more about it till I get into it myself. Hair line cracks can be easily fixed as long as its on the sadder areas. Just re sadder it
---------- Post added at 09:01 PM ---------- Previous post was at 08:34 PM ----------
Now for the weird flashing on and off booting mine does this as well but all functions regardless are working flawlessly. My phone will need serious structural repairs but nothing I can't do just had a horrible owner. Definitely worth the trouble this thing runs so smooth better than any other I have used and it will continue to hold for a couple years cause of the power behind it. I wouldn't worry about the booting flashing like that I'm just thinking it does this to show it has been tampered with.
Sent from my LG-E980 using XDA Free mobile app.
Hey man thanks for your reply. Reminded me to update this for anyone else who finds it.
So the new screen was definitely defective. The one time I managed to get it on there was a dead spot. I sent it back, a replacement is on its way.
Now the good news- I realized why my phone wouldn't boot. Turns out that when removing the motherboard, the top part of it got a little... bent. Nothing bad, nothing permanent, but when I mounted back onto the housing, the top part of it had a tendency to stick up a little bit. Well if you follow the small ribbon cable off the power button, it leads to two gold contacts. Sure enough on on the bottom side of the motherboard there are two nodes that would press against the contacts.
Basically, the power button wasn't even connected to the board.
So I actually put the whole thing together, screws and all, and with that, the motherboard sits snugly as it should and the button works fine.
Right now my phone is some sort of hacked up zombie, with a cracked up screen, an upper-left corner that's completely decimated/missing, and no adhesive to hold it together. Hopefully the screen makes it here soon!
Oh and I agree totally, this is the smoothest and most reliable Android I've owned, better than the Evo 3D (which I quite liked) and a GS3 (meh, it got very unreliable after a year). I'm happy the screen replacement is cheap and easy so I can keep this thing for at least another year.
Cool glad it worked out for you or hopefully will. Can you do me a solid once your screen comes in and if it replaced well all working that is could you post the site you got it on or pm me with it. I am here tons of issues with defective screens. Would like to have a reliable market to shop from.
Sent from my LG-E980 using XDA Free mobile app
Fant0m3 said:
Cool glad it worked out for you or hopefully will. Can you do me a solid once your screen comes in and if it replaced well all working that is could you post the site you got it on or pm me with it. I am here tons of issues with defective screens. Would like to have a reliable market to shop from.
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
I have never had a bad part for any kind of phone from Wholesale Gadget Parts in Bixby, OK (Tulsa area). I found them on Amazon and originally ordered because they were close and I was in a hurry. I kept ordering because they get it right. I have about a 50/50 success rate with phone parts off other sellers on Amazon. If you buy cheap, expect a high failure rate.
Glass and digitizer for G Pro is about $18 before shipping and any applicable tax.
Hey there. I'm a bit new to this side of XDA. Honestly with how long I've been AWOL from this site nothing is familiar anymore. How time flies. Well my first post back in years couldnt be more unfortunate phone wise, I've had my Z2 for a couple of months now and as a mechanic it's been treated like all my others phones prior, rough. I've been locally recognized as the guy who has a new phone every couple of months because he can't not shatter a phone. An expensive hobby of breaking phones. Well luckily I didn't shatter my Z2. I just water logged it. Gotta change things up right? So here's where the interesting problem comes in, I let the phone sit in rice for 30 hours, switching the rice out half way through. It acted up like you would expect in the first couple of hours but then stopped. When I pulled the phone out I scraped the rice out of all the books and crannies and tried to power it on, to no avail. Dead battery I assume, so I plug it in. Charge icon pops up, a sign of life! How glorious. So I let it sit for a minute as I assume the battery probably dropped below minimum voltage when the LEDs were freaking out. Went back to the phone, held the power button and no screen, but "Hello, Moto!" So at this point I'm convinced the screen is dead, so I force it off with the volume down method and pry off the screen. To find what? More water. Good Lord. This phone is incredibly water resistant just in reverse. So I do the only thing that makes sense at this point, I remove the ribbion connector from the board for the display and put the phone back in new rice as 2 separate pieces. I then leave it in there for another 30 hours switching the rice halfway. Bringing us to now. I took the phone out, cleaned all the rice out of the 2 pieces and off the remaining adhesive and connected the ribbion back to the board. Plug the charger in, and again, charging logo. But then I hold the power button and the TMobile splash screen pops up! Then the screen goes dead and once again, "Hello, Moto!". But whats different is now when the boot sequence is finished I can interact with the phone and it works, shake for flashlight, enter my passcode (just by feel cause I'm good like that, ladies hmu), and the button responds with vibration. The phone is working but no screen. So at this point I'm sure, the display driver is done. I murdered it in cold daylight. So I shut it off and start looking around for new screens, in the midst of this I knock the phone and accidentally hit the power button, and it starts to boot up. T-Mobile spash screen, screen death, "Hello, Moto!", and nothing. Now that seems weird. Why would it work twice on the TMobile splash? So I decide I'll try putting it in fastboot for S&G's. Restart, put it in fastboot and the screen stays on. Beautiful and clear as day, all buttons work, everything reads fine, but, if I go to boot it or do anyother action than "retart bootloader", the cycle continues. T-Mobile, death, hello Moto, nothingness. Now at this point I'm okay with the phone being dead, it's fine, but I'm intrigued now. What would cause the screen to work just fine when in the bootloader and the TMobile splash screen, but die when it boots? The phone is very clearly working in the background. I logged in, used Google assistant, used the flashlight, pressed buttons on the dialer, all without the screen but with haptic feedback and audio. Could the graphical side of the main partition just be corrupt, or maybe the display driver is dead but the main board interacts with it differently during fastboot? I'm far from being knowledgeable on the hardware side of these things but I'm really genuinely interested in getting feedback here from anyone with an idea of what is going on. I'll post a video here in a half an hour or so when I finish up with dinner.
AFAinHD said:
...snip...
Click to expand...
Click to collapse
Well... It sounds like there is a short between the screen and the main board. It could have happened when you plugged it into power while parts were still wet causing a short to ground and frying a chip that controls display but not touch on the screen.
Best way I can describe it for you is if an ECU on a car got wet and shorted out. Everything works but you get an engine code for TPS sensor failure due to said short. (The ECU can't read TPS due to a short). That is what seems like what happened.
Uzephi said:
Well... It sounds like there is a short between the screen and the main board. It could have happened when you plugged it into power while parts were still wet causing a short to ground and frying a chip that controls display but not touch on the screen.
Best way I can describe it for you is if an ECU on a car got wet and shorted out. Everything works but you get an engine code for TPS sensor failure due to said short. (The ECU can't read TPS due to a short). That is what seems like what happened.
Click to expand...
Click to collapse
Well see I would think that as well but the screen does work. Just only in fastboot, and the boot logo.
I got the video here.
Fastboot is a pretty low level and most likely uses basic hardware. I mean really what is there to see but a simple background with some text. Once you load the OS then all the hardware and it's drivers into play. Have you tried booting into safemode? Ultimately you'll probably have to repair or replace, but there could be a slim chance that there's still a little moisture in there and it still has a short somewhere.