My elderly neighbor held onto her Motorola Moto E (2nd Gen) for years till it recently stopped responding all of a sudden to her touches. It still charges fine and the display exhibits no issues, but the touchscreen is totally unresponsive despite repeated reboots. I'm guessing the touch digitizer is dead? Anyway, I've convinced her it's pointless to waste money repairing it and to simply get a new device. Since there weren't too many apps in use (most apparently stopped working over time on what must've been either Lollipop or Marshmallow), those aren't the issue here. What is required is to extract the bare minimum but very important data from the phone like **pictures, videos, contacts and messages (SMSes)**, and finally import everything into a new Android phone. So my question is, is any of this even possible with a completely unresponsive touchscreen? And if so, how?

I've Moto E with Lollipop 5.1 updated. This Version of OS gives me troubles like Disables Networks, Doesnot go in Wifi Settings etc., since a week ago. Before that, its working good only. Warranty for this mobile also expired. So that, i have tried to install my Older 4.4.4 kitkat Version to my Moto E using this Tutorial. Downgrade from Lollipop to KitKat for Moto E I've done all those steps mentioned in the downgrade process. I've used the some resource files mentioned in that youtube page. But problem arised in the final process of Downgrade. After formatting process, it gives me error that "Invalid Signed Image" & "Preflash Validation Failed". I Could not find out any solution for this issue. Now my phone has no OS. SO Can anyone suggest me to Boot OS to my Phone? Any suggestions will be greatly helpful to me..

I'm new to the Android world when it comes to these matters, so I ask for your patience if I say something wrong. I have a Motorola Moto E5 Plus cell phone and I used my Linux Ubuntu to help with the commands. With all the tutorials I've seen, basically what I did was: 1. I downloaded the [TWRPAPP](https://dl.twrp.me/twrpapp/) APK, transferred it to my cell phone and installed it; 1. I ran the application and downloaded the latest version of TWRP (3.7.0_9-0-hannah): 1. NOTE: After downloading the image, I also transferred it to my computer. 1. I activated USB debugging and OEM unlocked; 1. I restarted the phone into the bootloader with: adb reboot bootloader 1. I unlocked the bootloader: 1. I got information from the OEM: fastboot oem get_unlock_data 1. I registered on the Motorola website and got the unlock key and executed: fastboot oem unlock 1. _Everything went well and the bootloader was unlocked..._ 1. Back at the bootloader screen, I started TWRP with the command fastboot boot twrp.img (as it was the only way I could get it to start); 1. _And now the problem begins..._ 1. When TWRP finishes loading, the first screen asks for a password to decrypt: 1. I didn't really know what that password was. When I researched, I understood that this password was the same password to unlock the cell phone when it is on, however, the cell phone did not have a password. 1. So I clicked "Cancel" on the start screen and it continues to enter TWRP but on the logs screen it shows mounting errors and that was bad because I couldn't see anything inside the phone's folders and consequently I couldn't see the zipped image to flash. 1. From the tutorials I verified that I needed to: Wipe > Advanced Wipe > Check "Data" > Swipe to Wipe 1. Then return to the main menu: Wipe > Format Data > Type "yes" > Press Enter Button in Keyboard After that I restart in TWRP and in fact I no longer have any password to enter and it even goes directly to the main menu, however, I also no longer have the GSI image that I downloaded. PS: After all these things I tried to use OTG but I also couldn't get it to be recognized in TWRP.

In the process of installing a new ROM on my Moto E5 Plus (not after it has been installed, even before, on the main TWRP screen for example) and after the new ROM has already been installed, the following happens: If my cell phone locks the screen, When I click on the power button and the screen turns on, the touch does not work, however, if I connect the USB cable that is connected to my Linux computer to the cell phone, the touch works again. After doing this, when I lock the cell phone again, if the cable is still connected the effect is reversed and the touch does not work until I unplug the cable, however, if I remove the cable before blocking, when I unlock the effect It will be the same as the first time, the touch will only work if you plug the cable in again. Does anyone have any idea what it could be? Hardware problem perhaps? EDIT 1: I noticed that this actually doesn't happen exclusively when the cable is connected to my computer, but the behavior also happens if I connect the cell phone to the charger, that is, this happens when the cell phone is receiving power or not.

I'm using Motorola Moto E (first gen) running Android 5.1. I'm fairly new to Android, I know I could forward message if I tap and press on the message for a while, wait for the dropdown menu to pop up and then tap on "Message". The problem is, if there is a link in the message body, no matter where I tap on the message - it gets me to that website instead of showing this context menu. How do I forward this type of text?

Before christmas I bought a motorola moto e20 for my grandparents. I set it up but for some reasons I didn't write down any credentials and account information and I forgot everything. So I though I'll factory reset it only to discover the thing that's frp. Is there any way to bypass it? I already contacted motorola support and waiting for a reply. I still have the original receipt and package with the IMEI on it so I can really prove that I legally purchased the phone.

I have a Moto E which is only a few days old. It keeps switching off and on all day, automatically and usually around 20 times each day. It supports up to 32GB memory card, and I'm using a 32 GB card (if this might causing problem).

I have a bricked Motorola Moto E (2nd gen) XT1527 which throws a preflash validation failed error whenever I try to flash any of the files included in the stock firmware. Some guy told me to enter EDL mode, and I would prefer not to disassemble the device. Searching through the internet, I found a way to enter EDL mode with a modified fastboot.exe, but it seems to work only for Xiaomi devices. Is there some way to do this in Motorola devices? USB debugging and OEM unlock are disabled, and the bootloader is locked.

Today I flashed *AOKP Marshmallow ROM* in my Moto E. After that I flashed *Nano GAPPS* from *OpenGapps*. Since then this message keeps popping up for about 2-3 minutes after I launch any Google Play related app. I have tried every conventional solution. I wiped cache and data of Google Play Store, Google Play Services and Google Play Framework, but to no avail. Just now I flashed another GAPP (pico). But still the problem is there. So what can I do to make it stop?

**tl;dr** _I cannot use saved destinations when using Google Maps through Android Auto, because I always see a message that I must login to Google Maps first. I am logged into my Google account in both system and every other Google-like apps. Only with Google Maps there seems to be a problem. Is there any fix for that?_ ---- I was more than sure that when I have an Android phone, not rooted etc., where I am logged in (system wide) to an active Google account then I am also logged in to that account in any Google-related app, including Gmail, Calendar, Contacts etc. Yet, when I plugged my Motorola Moto E4 to my Toyota Aygo and started using Android Auto with Google Maps, this turned out to be not true. When selecting new destination address, I can: * Type it manually * Pick it from Google Calendar (I am logged in there and see my account's events) * Select one of the latest or * Browse by a category. But I cannot use one of the saved ones (i.e. starred), because I am always hitting the wall with message saying that I must login to Google Maps first. Here is a screenshot (in Polish, but it does the job): How should I proceed in this situation?

I try to install a custom ROM on my Motorola Moto E5+. To do that, I'm following this tutorial (and check what is said online on the tools used): https://www.getdroidtips.com/lineage-os-17-motorola-moto-e5-plus/ . So I'm at the step where I need to flash the TWRP image, but it seems to don't work.

$ ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
ZL5225HPHW	device
   $ ./adb reboot bootloader
   $ sudo ./fastboot flash recovery ../twrp-3.6.0_9-0-hannah.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20972 KB)                      OKAY [  0.851s]
Writin 'recovery'                                  (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
   $ sudo ./fastboot boot ../twrp-3.6.0_9-0-hannah.img
Sending 'boot.img' (20972 KB)                      OKAY [  0.685s]
Booting                                            (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed

So I try to use the command: ./fastboot flash recovery ../../Downloads/twrp-3.6.0_9-0-hannah.img (I'm sudo because it doesn't recognize my phone without) and I try to boot with the image as proposed here: https://android.stackexchange.com/questions/211996/cant-flash-custom-twrp-recovery-image-on-motorola-moto-g7-power-phone But it doesn't work either. On my phone, it says "Mismatched partition size (recovery)" when I try to flash. And when I try to boot, it just say download and boot and that it. Btw, I download the file from here: https://twrp.me/motorola/motorolamotoe5plus.html . So do you know what I'm missing and what I need to do? Or even if I'm doing it right? PS: when I'm trying with the official guide of LineageOS, it's doing the same:

$ sudo ./fastboot flash recovery ../lineage-18.1-20220104-recovery-hannah.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15432 KB)                      OKAY [  0.666s]
Writing 'recovery'                                 (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed

And it's say the same on the phone:

cmd: download: number
cmd: boot
cmd: getvar:has-slot:recovery
cmd: getvar:max-download-size
cmd: getvar:is-logical:recovery
cmd: download: another number
cmd: flash:recovery
Mismatched partition size (recovery)

PS²: I'm not sure if it's recognize in the good way, since, when I try the command sudo ./fastboot devices, it's listed as ZL5225HPHW Motorola Fastboot Interface, but I'm not sure that the Motorola Fastboot Interface is good or not? PS³: Here are some more commands and the output (I made them under the guidance of @alecxs): So here is the output:

$ sudo fastboot getvar unlocked
(bootloader) unlocked: not found
getvar:unlocked FAILED (remote failure)
finished. total time: 0.003s
$ sudo fastboot getvar securestate
securestate: oem_locked
finished. total time: 0.009s

So, what I'm understanding is that my phone is not unlocked? How I can do that?

I have a motoE 2 LTE (XT1514 Surnia) that originally had Android 5.0.2, but it went to motorola for repair and came back with 6.0. Despite the upgrade, the bootloader screen still showed "software status: official". Then I have unlocked the bootloader, installed TRWP and used it to flash supersu. The log says the process was successful but I checked with the app root checker that it was not. Then I wanted to go back with the stock ROM. I downloaded the XT1514_SURNIA_RETBR_DS_6.0_MPI24.65-39_cid12_subsidy-DEFAULT_CFC.xml ROM from this link I found on xda-developers and flashed it using RSD Lite. The system works but the bootloader screen now says "software status: modified"; before this process I made a backup using TWRP but after restoring the bakcup image the message still didn't change back to "software status: official". I thought maybe I need to install the original Android (5.02) and then upgrade it to 6.0, so I downloaded the XT1514_SURNIA_RETBR_DS_5.0.2_LXI22.50-53.8_cid12_subsidy-DEFAULT_CFC.xml ROM from the same link. The problem is I get a failure message when I try to flash the 5.0.2 image # mfastboot flash partition gpt.bin target max-sparse-size: 256MB sending 'partition' (32 KB)... OKAY [ 0.125s] writing 'partition'... (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 0.570s I did try with RSD Lite too, but I get the same message. I've read somewhere you can't dowgrade stock firmware, is this the problem here ? Is there any workaround ? My final objective is to have stock firmware with android 6.0 installed and the bootloader message saying it is official. I appreciate any help =) this is the log of RSD Lite flashing the stock image with android 6.0 28/16 05:39:10 The FlashLog key is turned off. 09/28/16 05:39:10 Multi upgrade started for 1 phones 09/28/16 05:39:10 [Device ID: 0] 1/20 getvar max-sparse-size 09/28/16 05:39:10 [Device ID: 0] 2/20 oem fb_mode_set 09/28/16 05:39:10 [Device ID: 0] 3/20 flash partition "gpt.bin" 09/28/16 05:39:11 [Device ID: 0] 4/20 flash bootloader "bootloader.img" 09/28/16 05:39:12 [Device ID: 0] 5/20 flash logo "logo.bin" 09/28/16 05:39:12 [Device ID: 0] 6/20 flash boot "boot.img" 09/28/16 05:39:15 [Device ID: 0] 7/20 flash recovery "recovery.img" 09/28/16 05:39:18 [Device ID: 0] 8/20 flash system "system.img_sparsechunk.0" 09/28/16 05:39:42 [Device ID: 0] 9/20 flash system "system.img_sparsechunk.1" 09/28/16 05:40:03 [Device ID: 0] 10/20 flash system "system.img_sparsechunk.2" 09/28/16 05:40:22 [Device ID: 0] 11/20 flash system "system.img_sparsechunk.3" 09/28/16 05:40:42 [Device ID: 0] 12/20 flash system "system.img_sparsechunk.4" 09/28/16 05:40:49 [Device ID: 0] 13/20 flash modem "NON-HLOS.bin" 09/28/16 05:40:54 [Device ID: 0] 14/20 erase modemst1 09/28/16 05:40:54 [Device ID: 0] 15/20 erase modemst2 09/28/16 05:40:54 [Device ID: 0] 16/20 flash fsg "fsg.mbn" 09/28/16 05:40:54 [Device ID: 0] 17/20 erase carrier 09/28/16 05:40:55 [Device ID: 0] 18/20 erase cache 09/28/16 05:40:55 [Device ID: 0] 19/20 erase userdata 09/28/16 05:40:57 [Device ID: 0] 20/20 oem fb_mode_clear 09/28/16 05:40:57 [Device ID: 0] reboot 09/28/16 05:40:57 CMultiFlashFlex::RebootPhone, waiting for phone to disconnect, status=2, state=0. 09/28/16 05:40:58 Removal, interface=28(0x0), device id=1636460. 09/28/16 05:40:58 CMultiFlashFlex::RebootPhone, waiting for phone to connect, status=3, state=4. 09/28/16 05:48:08 00002de8 Phone.cpp 1571 0 ERROR Waiting for phone's handle is setted successfully after restart [430000 ms] completion. failed 09/28/16 05:48:08 CMultiFlashFlex::RebootPhone, unable to wait for phone, status=3, state=4. 09/28/16 05:48:08 [Device ID: 0] Please manually power up this phone. 09/28/16 05:55:18 00002de8 Phone.cpp 3974 -1 ERROR CPhone::WaitForPhone timed out. Iteration-1 09/28/16 05:55:18 [Device ID: 0] Please manually power up this phone. 09/28/16 06:02:28 00002de8 Phone.cpp 3974 -1 ERROR CPhone::WaitForPhone timed out. Iteration-2 09/28/16 06:02:28 [Device ID: 0] Please manually power up this phone. 09/28/16 06:08:36 Arrival, interface=36(0x0), device id=1636460. 09/28/16 06:08:36 [Device ID: 0] Waiting for others to finish current operation. 09/28/16 06:08:36 Arrival, interface=20(0x0), device id=1636460. 09/28/16 06:08:36 Arrival, interface=19(0x0), device id=1636460. 09/28/16 06:08:36 The FlashLog key is turned off. 09/28/16 06:08:36 FlashLog file is turned off. 09/28/16 06:08:36 Multi upgrade finished.

It's been a while I tried few options, but I was not able to find how to add users in Moto E3 Power running Android Marshmallow. It is not present in the settings.  Any way to debug this or to activate this, as Android Marshmallow supports multi-users?

My phone is running out of internal memory. So I searched online and found a solution, which was to dial *#9900# and then delete dumpstate/logcat. But when I dial the same on my MOTO E, I dont see anything happening. It Just says USSD Code running and closes. My phone is running on Lollipop 5.1. Can you please help me delete dumpstate/logcat?

I have a Moto E 2015 LTE (surnia) running Lineage OS, Android 7.1.1. Every time I bump the phone the screen turns on to tell me the time. I can't find a setting to turn this off. I couldn't find such a setting in the stock Android either. Does anyone know if there is a hidden setting somewhere to control this? I'd be willing to build my own Lineage ROMS if that is what it took. It looks like modifying com.android.systemui will be necessary. Does anyone know how to download that code, and build that APK (perferably without building an entire ROM?) **EDIT**: A friend clued me in to the fact that this is sort of standard behavior for android phones these days (it's been a while since I had one). But the question still stands. I would even be ok with some way to disable the accelerometer completely, if that's what it took. **EDIT 2**: I found out that I can disable this behavior by disabling com.android.systemui. I am afraid that is a bit too drastic, so perhaps I will browse some source code to see if I can modify just that app, instead of the whole Lineage ROM. The question remains though, in case anybody knows how I would go about finding and building source code for com.android.systemui.

I have this moto e 2nd gen (not the 4g one)
It worked fine for 3-4 months..
Today morning i see strange "Unfortunately google play services has stopped"
error..
Slowly I figured out that all google related apps stopped working..
the playstore, gmail all show a blank screen when opened .... whatsapp was
working fine but every time a popup with that "Unfortunately...."
message comes.

Things that I've tried so far:
1. Reset all app preferences
2. Uninstalling updates of both playstore as well as play services and
cleared caches
3. Tried removing google account but it is not able to do it.. Its showing
this error like "Google sync is currently not availabe..." (I think this
is due to the fact that sync itself is a google app)
4. Tried factory reset option but it does nothing even when i click on that
reset button (Strange :( )
5. Tried factory reset using the recovery menu.. but its not loading only..
Like i enter the bootloader and when i click the recovery option, It
shows just an android in distressed icon... I even tried holding the
volUP + click power button thing on that screen but its not going into
the recovery screen

Its quite strange nothing is working for me

isRooted: **false**
isInWarranty: **true**

I have a surnia xt1527 which was bricked because of some mistakes I made when trying to make a factory reset (I don't remember what I did because it was a while ago). The device has usb debugging disabled and hence I can't use adb tools. I also can't flash the stock firmware or a custom recovery from an sd card because the recovery won't let me access the sd card. Is there anything I can do to save the phone even though usb debugging is disabled? thanks

I am having a Moto E XT-1022 (1st generation) 2014 model. In order to update its OS from 4.4.4 to 5.1, I had to make 500MB space available so I deleted all WhatsApp database backup files without copying them elsewhere as I knew from my own experience that WhatsApp had nothing to do with Android OS upgradation process since I had already upgraded the same android from OS 4.4 to 4.4.4 and my old Samsung even before that without losing any of my WhatsApp messages but unfortunately, this time all my chats are gone after OS update. As I thought, WhatsApp tried to take the backup automatically on 3 AM like any other day, but it's not working either. Now I'm left with a possibly corrupt file msgstore.db.cypt8 (size: 103.62 MB). I read somewhere in here that there is a possibility of mending the corrupt backup and regenerating it afresh if the key can be extracted somehow. So is there any ray of hope for me? PS: Mine is a non-rooted device.

How would I flash this ROM: XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml.zip From https://firmware.center/firmware/Motorola/Moto%20E%20%282nd%20gen-2015%29/Stock/XT1524/XT1524_RETEUALL_MOTOE2%284G-LTE%29_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml.zip On A Moto E2 XT1524

I have a Motorola Moto E, and according to USB Host Diagnostics, the stock OS and kernel claim OTG USB support, and the proper classes are present, but it won't detect a thumb drive connected via OTG cable. I can't find a stock rom image for download, so, until I can, rooting is out of the question...Any suggestions?