• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Emergency! (Maybe...)

While talking on my [landline] phone, I waved my hand over my [smart]phone to see the time...but nothing happened. I pressed the fingerprint scanner. Nothing happened. I pressed the power button. Nothing happened.

When I finally hung up, I plugged it in, even though I knew it was 98-ish percent charged. Nothing. I LONG-pressed its power button numerous times. NUH-thing!!

I came out to use my main laptop to see if Google could find it. Nothing. I checked its last activity with Google: approximately 20 minutes before I noticed the problem. Its last backup was an hour before that.

After more long-pressing [and throwing quite a few expletives around], voila!, the Motorola symbol lit up! And it booted up like nothing had ever been wrong. :thinking: (Except that it immediately told me KDE Connect had stopped working--and that's NEVER happened before.)

I'm currently copying over some files to the laptop that are newer than the last time I did that. You all know I'm pretty [expletive] compulsive about backing things up, so I don't have much to lose even if it just DIES. But I'd like to know...WTF?!

Any ideas why this 6-1/2 month old Moto Z2 Force Edition would suddenly act dead? It was a replacement for an identical phone whose screen got burn-in; it was definitely brand-new when I got it. Any thoughts on what to make sure I back up that Google doesn't?

It's running Oreo 8.0.0 and is not rooted.
 
Something I didn't notice right away: its keyclick sounds are gone again, as I described recently in this thread.

What do you think? Related? :thinking:

Hi MoodyBlues, have you tried a 'Wipe cache partition'?

I used to do that on my HTC M9 when I had strange glitches and it worked. Both my wife and I have had HTC 10s for almost 2 years now, running 8.0 and I've done a cache wipe on both of them at least once for similar problems with success.
 
Upvote 0
Hi, MoodyBlues have you tried a 'Wipe cache partition'?
No. But this just happened, so I've been busy making sure everything's backed up--just in case it conks out on me for good!

I've actually never wiped cache partition, so I'm not familiar with it. It doesn't require root, does it? It's been years since I rooted a device! I'm guessing this is buried somewhere in System Settings...?

ETA: I found this handy-dandy guide, which explains the process.
 
Last edited:
  • Like
Reactions: tommo47
Upvote 0
No, it doesn't require root. I found the following info on Google :-

https://support.t-mobile.com/docs/DOC-37750

Hope this helps :).

I've never had the urge to root any of my devices. My HTC M7, M9 and 10 have all suited me in stock form but all have exhibited strange glitches from time to time and have always responded positively to a Cache Partition wipe. I got into the habit of doing the wipe after every update as a matter of course as well as responding to the occasional glitch/misoperation :).

The procedure does not affect the data on the device.
 
Last edited:
Upvote 0
No, it doesn't require root. I found the following info on Google :-

https://support.t-mobile.com/docs/DOC-37750

Hope this helps :).
Yes, thanks, that's specifically for my phone.
I've never had the urge to root any of my devices.
For me, being a mutli-decade UNIX person, it was fun and exciting! Getting that # prompt made me feel like I was home. :D But somewhere along the way, it lost its appeal. Probably because Android kept adding/tweaking things to make stock more appealing, and rooting less necessary.
y HTC M7, M9 and 10 have all suited me in stock form but all have exhibited strange glitches from time to time and have always responded positively to a Cache Partition wipe. I got into the habit of doing the wipe after every update as a matter of course as well as responding to the occasional glitch/misoperation :).
Well, my keyclicking is back this morning....just like the last time it went out. So right now everything's good, but I'm going to wipe its cache anyway. Yesterday's sudden "playing dead for no apparent reason" spooked me. :eek:
The procedure does not affect the data on the device.
Right. I gleaned that from my search, but it's good to say it so others will know, too.

Thanks for your help!
 
Upvote 0
Well...guess what? As I just confirmed by reading this thread, there is no 'wipe cache partition' on my phone. :eek: As in that thread, this is what my recovery menu gave me:

Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Power off

Apparently, starting with my Android version, that option was removed--and you're stuck individually wiping each app's cache. Fun, right?! Especially when you have 200 apps installed, plus all the system stuff. Oh well.

If anyone has other ideas/advice/suggestions, let 'em roll! I've never before had a phone just play dead. I mean it was DEAD last night...
 
  • Like
Reactions: ocnbrze and tommo47
Upvote 0
Well...guess what? As I just confirmed by reading this thread, there is no 'wipe cache partition' on my phone. :eek: As in that thread, this is what my recovery menu gave me:

Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Power off

Apparently, starting with my Android version, that option was removed--and you're stuck individually wiping each app's cache. Fun, right?! Especially when you have 200 apps installed, plus all the system stuff. Oh well.

If anyone has other ideas/advice/suggestions, let 'em roll! I've never before had a phone just play dead. I mean it was DEAD last night...
I was going to get to that. The new Android partitioning (with live updates) no longer has a cache partition as there is no longer a dalvik cache to clear (if my understanding is correct). Even in old Android clearing the cache partition != clearing the individual app cache's.

All that said, did you possibly get / apply an OTA? You mentioned a backup prior to the unexpected behavior. The phone can get quite sluggish leading up to and following the reboot for an update, and if you understand the new way of updating with stock Android (and on my Moto X4, so I'll make the leap that Moto is doing it the Android way for all their new devices).
  • Your phone has two partitions where Android is installed (A & B). When you get an OTA it is downloaded and installed in the partition you aren't currently operating out of (i.e. if you are running on partition A it will download and install it on partition B). This may explain why the phone gets sluggish prior to a reboot.
  • Once the installation is complete, the phone will reboot into the partition with the newly installed OTA (partition B) and complete the installation. Upon a successful reboot (i.e. successful OTA update) Partition B is copied over to partition A. This may explain why the phone gets sluggish following the reboot.
The process is the same whether the OTA is small like a security update which may be only a few MBs or a massive version OTA like Android 10 with was GBs, the entire partition is copied following a reboot.
 
Upvote 0
Thanks, @Unforgiven. The backup I mentioned was just Google doing its thing; there was no update involved. In fact, other than app updates--which I do not let happen automatically--there have been no system updates for quite awhile.

It was just so weird, so out of the blue, so ALARMING! Just like that, I had a dead phone.

At this point I really don't know what to do, other than make sure I keep everything backed up.

I wonder about its warranty--I bought it directly from Motorola, originally about a year ago, then 6 months ago they sent me a new replacement. So when did the warranty clock start ticking on THIS phone? :thinking:
 
Upvote 0
Nothing else has happened, but in light of both the mysterious 'dead phone' incident, and the on-again, off-again keyclick issue, I'm getting an itch to factory reset. What do you think--should I scratch it?

That would be my last option but it may be necessary. The good new is you have backups the bad new is its inconvenient and time consuming. If the problem persists, that may be you only option. Personally, I would wait to see if the issue continues before I factory reset.
 
Last edited:
Upvote 0
Nothing else has happened, but in light of both the mysterious 'dead phone' incident, and the on-again, off-again keyclick issue, I'm getting an itch to factory reset. What do you think--should I scratch it?

Hello MoodyBlues, I was just wondering, did you factory reset you're Motorola?
 
Last edited:
  • Like
Reactions: ocnbrze
Upvote 0
Hello MoodyBlues, I was just wondering, did you factory reset you're Motorola?
No! Not yet, anyway. I think complacency has taken over, since everything's just as normal as can be.

I am being [even more] diligent [than usual] about backups...just in case. :eek:
 
  • Like
Reactions: ocnbrze and MrJavi
Upvote 0
Yeah, probably--but a scary one! No warning signs, no problems, and then...DEAD. :eek:

Yes it is, especially be a non rooted device. What most concerning is your key combinations had no effect. If it was a Note 4 I'd suspect the infamous emmc/mmc motherboard failure. You wise to continue back up your data more frequently than usual given the circumstances.
At one point I was going to recommend wiping da wipe dalvik/ART Cache and/or Cache but someone else beat me to it. Then, after reading your response, I realized, how out of touch I am with stock recovery, how embarrassing. I thank you for inadvertently bringing that to my attention. Anyway, Im interested in knowing the out come.
 
  • Like
Reactions: MoodyBlues
Upvote 0
Oh, silly MrJavi, there's no need for embarrassment! :)

We all learn new things all the time. I know I do. It's impossible to keep up with anything 100%--and when you're dealing with Android, it's even harder. Just think of all the distinct, manufacturer- and model-specific versions of Android--and then throw in root, custom ROMs, a decade of devices...it's overwhelming.

I'm very, very, very out of the loop these days. :eek: I'm glad we have AF to talk and learn about our OS. It's not only a great resource for that, but for meeting nice people like you! :D
 
  • Like
Reactions: MrJavi
Upvote 0
Oh, silly MrJavi, there's no need It's impossible to keep up with anything 100%--and when you're dealing with Android, it's even harder. Just think of all the distinct, manufacturer- and model-specific versions of Android--and then throw in root, custom ROMs, a decade of devices...it's overwhelming.

I'm very, very, very out of the loop these days. :eek: I'm glad we have AF to talk and learn about our OS. It's not only a great resource for that, but for meeting nice people like you! :D


I dont have formal education or the experience with computers. My friend tell me "you know alot about Android". I just laugh and say "not really". Its just a hobby of mine. Im also glad to be a member of AF. I also think you a nice person , kind hearted and very intelligent. So many people trying to scam but AF is filled with honest members who generally want to help someone else. How very refreshing it is to know theres still good people and even though none of use will ever meet or from what country we live in, that does mean were no friends. Im great full to be here and I thank you for welcoming MoodyBlues and I truly mean that.
 
Last edited:
  • Like
Reactions: MoodyBlues
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones