Not sure if this is the right forum to post to, so maybe you can point me in the right direction if not.
So I may have gotten some water damage to my phone, it was never submerged, only damp. I did the bag o' rice trick but and having some funny issues with it now. It powered on when charging but continued to turn on and off, flashing the Motorola start-up, and sometimes bringing up the reboot menu as if the power button was being held down.
I disconnected the flex ribbon cable for the power/volume control buttons, and it seemed to actually work. But now it's doing the same thing occasionally after it's been on for a while. Is this savable? Is it possible that if I clear the data cache that it might solve the problem?
cariboukid said:
Not sure if this is the right forum to post to, so maybe you can point me in the right direction if not.
So I may have gotten some water damage to my phone, it was never submerged, only damp. I did the bag o' rice trick but and having some funny issues with it now. It powered on when charging but continued to turn on and off, flashing the Motorola start-up, and sometimes bringing up the reboot menu as if the power button was being held down.
I disconnected the flex ribbon cable for the power/volume control buttons, and it seemed to actually work. But now it's doing the same thing occasionally after it's been on for a while. Is this savable? Is it possible that if I clear the data cache that it might solve the problem?
Click to expand...
Click to collapse
You are in the right place.
Unfortunately, your symptoms are NOT good... (you already know this, obviously). The Moto X is "nano-coated", so you MAY have some hope, yet.
Try a factory reset. If that doesn't work, we can HOPE the issue is data corruption on one or more partitions. At this point, you can TRY flashing the entire stock SBF for your carrier as per the "Return to Stock" thread in the General sub-forum....IF you even can (this is done from bootloader screen - it is NOT required to be unlocked, as the Stock SBF is signed with release-keys). This re-writes ALL the partitions, and often fixes corruption issues.
If you try, and THAT doesn't work, I suspect an un-recoverable hardware failure.
Good Luck :good:
samwathegreat said:
You are in the right place.
Unfortunately, your symptoms are NOT good... (you already know this, obviously). The Moto X is "nano-coated", so you MAY have some hope, yet.
Try a factory reset. If that doesn't work, we can HOPE the issue is data corruption on one or more partitions. At this point, you can TRY flashing the entire stock SBF for your carrier as per the "Return to Stock" thread in the General sub-forum....IF you even can (this is done from bootloader screen - it is NOT required to be unlocked, as the Stock SBF is signed with release-keys). This re-writes ALL the partitions, and often fixes corruption issues.
If you try, and THAT doesn't work, I suspect an un-recoverable hardware failure.
Good Luck :good:
Click to expand...
Click to collapse
Thanks so much!! I created a backup once I was in bootloader. Then I cleared the cache, which didn't seem to help. But then I wiped it clean with fastboot and that seems to have done the trick.
Related
My toddler got a hold of my HTC Hero phone and no telling if she dropped it or what but ever since I have been having a touchscreen issue. Everything I am seeing is pointing to a touchscreen failure
symptoms:
No visible damage
Can't pull down notification bar (sometimes comes down when swiping from bottom to top or side to side or sometimes randomly dropping down when I press to select something)
Typing on the keyboard is almost impossible, adjacent keys are selected when typing
Unresponsive touch randomly
Can't answer calls sometimes
troubleshooting:
Tried wipe boot, system, data, cache and reinstall multiple ROMS, multiple times resulting in same behavior
Restore backup from 5/30 - no dice, issue still exists
Currently I am on aospCMod-HEROC-20110523-signed - NO custom kernel, laucher, etc..., just straight up aospCMod 5/23 release
Has anyone had a similar experience or know of a fix or have some additional troubleshooting suggestions?
Thanks in advance.
I had the same problem but i found out my problem was that the charger i was using it kept messing it up. I found out when i took off the charger that it would work fine then while charging i couldn't use it. Now i switched charger and it works fine using it while charging.
If your s-off. Try a fastboot erase. If your not s-off then you should look into it. Hope this helps. Warning fast boot will erase everything. Proceed with caution.
#Root/Hack-Mod_Always*
laie1472 said:
If your s-off. Try a fastboot erase. If your not s-off then you should look into it. Hope this helps. Warning fast boot will erase everything. Proceed with caution.
#Root/Hack-Mod_Always*
Click to expand...
Click to collapse
I am S-Off so I went ahead and tried the fastboot erase. Seems like the random dropdown issue isn't occurring and the keyboard seems to work fine now but the top of my screen is still unresponsive. I guess it's time for new phone! Will have to live with it until my contract is up.
Thanks
Verizon Moto X
Every time an incoming or outgoing call is made, audio output is only on the speaker. If I hit the button to turn off speaker, it goes back to speaker seconds later. Can anyone help?
EDIT: No ROM, pure stock from Verizon. I reset the device and cleared cache already.
G00gle26 said:
Verizon Moto X
Every time an incoming or outgoing call is made, audio output is only on the speaker. If I hit the button to turn off speaker, it goes back to speaker seconds later. Can anyone help?
Click to expand...
Click to collapse
Are you using a ROM? Xposed? Stock? First off you could try clearing cache and data of the phone app. If you are using a ROM, search the ROM thread. If you are using Xposed, uninstall it and see if the problem goes away. If the problem persists try a factory reset after backing up your data.
PiousInquisitor said:
Are you using a ROM? Xposed? Stock? First off you could try clearing cache and data of the phone app. If you are using a ROM, search the ROM thread. If you are using Xposed, uninstall it and see if the problem goes away. If the problem persists try a factory reset after backing up your data.
Click to expand...
Click to collapse
Sorry I should I specified that info.
No ROM, pure stock from Verizon. I reset the device and cleared cache already.
G00gle26 said:
Sorry I should I specified that info.
No ROM, pure stock from Verizon. I reset the device and cleared cache already.
Click to expand...
Click to collapse
Boot in safe mode: hold volume down at the first splash screen. From a power on. But if you did a data reset then I suspect a hardware failure.
---------- Post added at 06:37 AM ---------- Previous post was at 06:35 AM ----------
Do a RSD restore of the XML/FXZ.
two issues i have dealt with on the same problems across multiple devices. Main two options causing this are:
1. you downloaded some weird app that did some weird stuff with the speaker phone, even uninstalling the app could still be causing the problem. For this issue (if you can think of any apps you downloaded and possibly used for a day or a minute then uninstalled) go download the app again, look for any setting that could have delt with car mode, or plugged in mode, or docking mode, or speakerphone mode, or something similar and disable it, clear data and cache on app, then uninstall and see if it works.
2. you have dust or some debris in the charging port that is causing the phone to think that it is in dock mode where speaker phone automatically turns on. use air blaster or a toothbrush if the dirt is bigger in there.
those are the two main ones i have seen. see if they work it out. one phone that downloaded an app that caused this was an app about speed velocity while travelling, it had some weird settings for some docking thing i think and i had to check an uncheck it before unsinstalling to get the problem fixed
jayboyyyy said:
two issues i have dealt with on the same problems across multiple devices. Main two options causing this are:
1. you downloaded some weird app that did some weird stuff with the speaker phone, even uninstalling the app could still be causing the problem. For this issue (if you can think of any apps you downloaded and possibly used for a day or a minute then uninstalled) go download the app again, look for any setting that could have delt with car mode, or plugged in mode, or docking mode, or speakerphone mode, or something similar and disable it, clear data and cache on app, then uninstall and see if it works.
2. you have dust or some debris in the charging port that is causing the phone to think that it is in dock mode where speaker phone automatically turns on. use air blaster or a toothbrush if the dirt is bigger in there.
those are the two main ones i have seen. see if they work it out. one phone that downloaded an app that caused this was an app about speed velocity while travelling, it had some weird settings for some docking thing i think and i had to check an uncheck it before unsinstalling to get the problem fixed
Click to expand...
Click to collapse
Didn't download any new apps. I won't through them all and the only ones that are related to the speaker or phone calls is:
eCID
AutomateIt
I did what you said on both apps and cleaned the charging port with an air duster, didn't fix it.
G00gle26 said:
Didn't download any new apps. I won't through them all and the only ones that are related to the speaker or phone calls is:
eCID
AutomateIt
I did what you said on both apps and cleaned the charging port with an air duster, didn't fix it.
Click to expand...
Click to collapse
it might not be an app that you would think is related to phone calls. any app that may change its settings if it is in dock mode could cause. such as moto assist. it could also just be a faulty charger port. I haven't seen anyone else say anything about this issue on an x so i would assume it is either HW related and you need to return it or it is app related. even dusting out the port though might not have gotten some gummy stuff out that could be causing it fyi. but these are the first reports that i have seen so thats all that i got.
jayboyyyy said:
it might not be an app that you would think is related to phone calls. any app that may change its settings if it is in dock mode could cause. such as moto assist. it could also just be a faulty charger port. I haven't seen anyone else say anything about this issue on an x so i would assume it is either HW related and you need to return it or it is app related. even dusting out the port though might not have gotten some gummy stuff out that could be causing it fyi. but these are the first reports that i have seen so thats all that i got.
Click to expand...
Click to collapse
First thing I did was I cleared out Moto Assist and turned off it's features. Thank you for trying though.
G00gle26 said:
First thing I did was I cleared out Moto Assist and turned off it's features. Thank you for trying though.
Click to expand...
Click to collapse
If you are willing to try, attempt to flash the FULL SBF for your carrier (the same version you are currently on) using RSD Lite or manual method (instructions in the General sub-forum, "Return to 100% Stock" thread).
You see, using an SBF to return to stock can actually repair a corrupted or damaged filesystem because it *replaces* the partitions. A "factory restore" cannot. It only erases userdata and cache.
It will erase everything, so copy anything important (pictures etc.) to your PC before doing this. It is your best hope of recovering. If this does not fix it, it is almost certainly a hardware issue.
Good Luck :good:
If after a full reflash this still occurs, I'd think it's a hardware related issue that you'll have to RMA your phone for or have swapped by Verizon. Personally, I hate Verizon refurbs as they use a cheaper 3rd party to "fix" phones (they usually make them worse). The 4.4.4 image doesn't wipe data, and when manually flashing, you can exclude the erase userdata command. For manual flashing, use mfastboot and follow the flashing order and commands in the XML. RSD will do it automatically.
Some people have also had no front or rear camera access too, and that's hardware related (usually a ribbon cable connection or defective sensor).
Jason.DROID said:
If after a full reflash this still occurs, I'd think it's a hardware related issue that you'll have to RMA your phone for or have swapped by Verizon. Personally, I hate Verizon refurbs as they use a cheaper 3rd party to "fix" phones (they usually make them worse). The 4.4.4 image doesn't wipe data, and when manually flashing, you can exclude the erase userdata command. For manual flashing, use mfastboot and follow the flashing order and commands in the XML. RSD will do it automatically.
Some people have also had no front or rear camera access too, and that's hardware related (usually a ribbon cable connection or defective sensor).
Click to expand...
Click to collapse
The new 4.4.4 "image" -does- erase data. The original leaked FXZ posted by @SamuriHL didn't include the erase userdata command, but the new leaked FXZ does include it. SamuriHL only hosted the first leak temporarily until the new was posted to the droid-developers website.
The actual "images" inside both leaks are 100% identical though. The only difference is the new one contains the erase userdata command, and (I think) the "<step operation="getvar" var="max-download-size" />" command as well. Before anyone asks, NO you don't need to use the new one if you already used the original one. Other than the stated commands, they are completely identical.
I'm only putting this out there so someone doesn't flash the new one thinking their data will be saved -- it will not. That is, of course, unless you use SamuriHL's excellent tools made for this purpose....they allow you to preserve your userdata.
:good:
Jason.DROID said:
If after a full reflash this still occurs, I'd think it's a hardware related issue that you'll have to RMA your phone for or have swapped by Verizon. Personally, I hate Verizon refurbs as they use a cheaper 3rd party to "fix" phones they usually make them worse!
Click to expand...
Click to collapse
I always thought so. I got my first Official Moto refurbished phone when Moto sent me a Maxx for my X. Totally different packaging.
---------- Post added at 08:31 AM ---------- Previous post was at 08:14 AM ----------
Oh, & the Maxx is flawless!
I solved it! I isolated the problem to the app AutomateIt. There was a rule that was enabled by default when the app installed that turned the speaker on when away from the ear but the second rule to turn it off when it goes back next to your ear never triggered. So it's not a hardware issue thank GD. Case closed folks, thanks for all your help and the tip for safe mode. :good:
So I was on my phone this morning and the screen kinda froze, so I force rebooted [hold power for 10 sec] and when it turned back on this is what I saw instead of the motorola logo. After this, the screen goes black and I can't do anything on my phone. I know the phone is working because I have a Pebble and I still get notifications on it and I can control my music, but that's about it.
Any ideas?
Attached is a picture of the screen when the moto logo should be showing. Also there is an IR light to the left of the speaker (or below the speaker grill?) that is flashing that I noticed when I tried to take this picture, but the camera I used couldn't catch it in a picture.
You could try taking all your personal data off the phone and then reflash if you can get into the bootloader.
You may want to contact Motorola or your carrier, though
dier325 said:
You could try taking all your personal data off the phone and then reflash if you can get into the bootloader.
You may want to contact Motorola or your carrier, though
Click to expand...
Click to collapse
Not sure how I could take my data off. I can't connect via USB unless I unlock my phone at least once, and I can't reboot into the bootloader/recovery to backup anything. I'll probably contact Motorola just to be safe.
iSecks said:
Not sure how I could take my data off. I can't connect via USB unless I unlock my phone at least once, and I can't reboot into the bootloader/recovery to backup anything. I'll probably contact Motorola just to be safe.
Click to expand...
Click to collapse
Hm, my X automatically mounts on my computer so I can browse my ondevice files.
As for rebooting into recovery, you can do so in ADB/Fastboot. But you probably need to enable developer options.
Well, I guess you're outta luck.
Have you tried holding the power button and volume down to get into fastboot.
sent from "my kungfu is stronger then yours" XT1080
iSecks said:
Not sure how I could take my data off. I can't connect via USB unless I unlock my phone at least once, and I can't reboot into the bootloader/recovery to backup anything. I'll probably contact Motorola just to be safe.
Click to expand...
Click to collapse
You should be able to restore to stock w/o USB debugging via fastboot/mfastboot, even though you loose data.
http://forum.xda-developers.com/moto-x/development/script-adb-fastboot-mfastboot-directly-t2817544
&
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
---------- Post added at 08:37 AM ---------- Previous post was at 08:35 AM ----------
Try not erasing user data.
Well someone on Reddit solved my issue, posting it here in case someone else runs into the same problem:
I've had the exact same problem occur every few weeks on my 9-month old Verizon model--from the frozen screen to the confetti garbled display on reboot--and I've come up with a reliable, if inelegant, solution.
It usually happens after dropping or jarring my phone or excessively flexing the charging cable, which led me to suspect that there's a problem with the physical connections in the device, maybe a loose display cable.
To fix it--and this has always worked--I hold the phone in one hand and whack the back repeatedly against the heel of my other hand. It's taken several minutes and a few dozen whacks in the worst cases, but it hasn't failed me yet. Sometimes I'll see the display flicker back on only to garble again, so I continue. Shouldn't require a reboot, either; the display should instantly come back to life once it works.
EDIT: I should add that even when I'm experiencing the problem, I can still boot into recovery mode and see that screen without any issues. Not sure how that reconciles with the physical connector theory, but the whacking clearly works.
Click to expand...
Click to collapse
It's so weird that this would work. It's probably some connector issue because otherwise it makes *no* sense.
iSecks said:
Well someone on Reddit solved my issue, posting it here in case someone else runs into the same problem:
It's so weird that this would work. It's probably some connector issue because otherwise it makes *no* sense.
Click to expand...
Click to collapse
You still might want to get a replacement so this won't happen again.
So, I was clean flashing Titan Prime back into my XT1064 after testing CM12.
Everything went well, same apps, same configurations as always, no major changes.
I was about to reboot the phone when it did it by itself.
The boot screen (you know, the white one that burns your eyes) showed up, then it went away, and then oh surprise!, it came back again.
So the phone was in this bootloop within the boot screen.
I tried to enter to the Bootloader and the key presses (Power + Volume Down) did not work.
Every time I would try that, the phone screen would stay off for as long those keys were pressed down, and then, Bootloop.
After many tries I was about to let the phone stay in the bootloop until I find a solution here on XDA.
But I tried one more time, and lo and behold, it went into the Bootloader.
From there everything went as normal.
Now, the question is, could I have bad sectors?, could the Bootloader be corrupted?, could I have a ghost trapped?.
Thank you for answers and/or ideas.
And if any of you happens to be in my same situation, do not give up, let it be, try many times, and it finally will work (hopefully)
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Tel864 said:
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Click to expand...
Click to collapse
You do everything right, the phone gets screwed, it gets fixed, and the problem is something no one else has had so you have no freaking idea of why or what it was.
It is not my power button, the only times I use it is when I turn the screen on, and it would not be the reason because it made a difference when it was pressed.
I will try some fastboot commands to scan sectors, but I need to remember how they worked. The last time I used them it was when I had a Galaxy Note 1.
Lars124 said:
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Click to expand...
Click to collapse
As noted on the first post, I did not do anything out of the ordinary. Same apps, same configuration as always.
The good thing is that I now can say I have every app that I need, with the configurations that I need, so I almost never need to change.
Let's hope it will not happen again.
Hi all !
I'm a retired recording engineer from eastern Québec, Canada, enjoying retirement and keeping busy buildingand fixing audio equipment and restoring vintage British motorcycles.
I'm having a very strange problem with my Moto G5 (not Plus) that started out of the bue earlier this week. When the phone is locked, be it after locking it manually or after exceeding the preset time, and I receive a call, I do not get the phone logo on the screen anymore. If I want to take the call, the screen remains dark and I can't simply swipe it. I need to press the "start-stop" button, then a white box appears telling me who is calling and the padlock appears at the bottom of the screen. Then I have to trace the security pattern and the phone app appears, but on the in-out call screen instead of showing the button that would allow me to take the call. Instead I have to swipe down in order to get the box that allows me to take the call or reject it. I did countless Google searches and went through all the settings but I couldn't find any mention of that problem. The weird thing is that the phone was working perfectly one night, and then the following morning I had that problem. Can anyone help ?
Welcome to XDA
Was the phone updated overnight?
Clear the system cache if possible on this model.
Try in safe mode to help rule out 3rd party app interference.
It could possibly be a virus, rootkit or the hidden users settings have been corrupted.
The rom itself may have been corrupted, not necessarily anything nefarious... maybe just a high energy particle that flipped a flash memory cell read state. Atomic particles playing god, I hate that
Worse case solutions, factory reset, if that doesn't work reflash last known good firmware.
If all that fails it's likely a hardware failure but this is probably the least likely cause.
Hi !
Thanks for your reply. As far as I can tell there is no recent update. I tried everything you suggested except the factory reset because I dread reinstalling all the apps, but I guess I'll have to bite the bullet. Hoping it's not one of those pretentious atomic particles... ;-)
lanhet said:
Hi !
Thanks for your reply. As far as I can tell there is no recent update. I tried everything you suggested except the factory reset because I dread reinstalling all the apps, but I guess I'll have to bite the bullet. Hoping it's not one of those pretentious atomic particles... ;-)
Click to expand...
Click to collapse
Try disabling the lock screen etc. Go back to where it needed no password to use.
That's the first thing I tried, no luck... :-(
lanhet said:
That's the first thing I tried, no luck... :-(
Click to expand...
Click to collapse
I'm not familiar with that phone.
In general, try clearing the system cache.
I don't like messing with the phone app data but... first backup your contacts then start clearing data in the associated phone apps.
If a hidden user setting has been toggled it may be very hard to find/correct unless you know how. A factory reset would do so.
If that fails the firmware has become corrupted and needs to be reflashed.
If all that fails it's likely a hardware failure, either the mobo or possibly the C port PCB.
A C port pcb failure can do strange things on a Samsung like loss of internet/phone connection. I bring up the C port pcb because they get a lot of wear and tear... and they're a lot cheaper than a mobo.