TWRP extremely slow to load - Moto X Q&A

When I reboot to recovery it takes f-o-r-e-v-e-r for it to load up. It just sits at the splash screen for a full 2 or 3 minutes (maybe longer). Anyone else experience this? Is there a fix?
2013 Moto X
Verizon Dev edition
Stock, rooted, xposed, twrp

Well, I did a factory reset and then wiped internal storage and it's fixed. NOt sure what the problem was but at least it's fixed.

Related

[SOLVED] Unrooted VZW Moto X Will Not Boot Past Splash Screen

I cannot get my phone to boot. It started when I was installing updates from the Play Store. It suddenly rebooted in the middle and it hasn't made it past the boot animation since.
When I try to turn it on, it will go through the boot animation and then end with the Verizon logo. The screen turns off afterwards. If I leave it alone, it eventually reboots itself again.
I've had this happen a couple times in the past but it always recovered after a couple of reboots.
This is an unrooted phone. The only sideloaded app installed is SwiftKey Beta. It has that latest 4.4.2 update. The battery was ~50% when it rebooted the first time. It's set to use ART runtime. I've tried clearing the cache from the bootloader AND from fastboot. Neither helped. I really don't want to restore to factory defaults if I don't have to. Advice?
SOLVED: My solution in 3rd post.
TL;DR: Reflashed stock system partition. Turned on and plugged in overnight. Hard reboot via holding down power button for 7-10 seconds. YMMV
You mention Unrooted, does that mean you've never used SlapMyMoto/RockMyMoto/etc or MotoWpNoMo?
If so, and you don't mind re-writing your /system partition (putting it back to stock), you can try option 2 or 3 on -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html . Option 2 will definitely not touch your data/apps. Option 3, if you follow EXACTLY will also not touch your data/apps.
KidJoe said:
You mention Unrooted, does that mean you've never used SlapMyMoto/RockMyMoto/etc or MotoWpNoMo?
If so, and you don't mind re-writing your /system partition (putting it back to stock), you can try option 2 or 3 on -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html . Option 2 will definitely not touch your data/apps. Option 3, if you follow EXACTLY will also not touch your data/apps.
Click to expand...
Click to collapse
Thanks for the reply, Mark.
I actually tried flashing the stock system partition last night shortly after I posted here but it didn't work.
However, I left it plugged in and turned it on once before I went to bed. In the morning, it was still stuck after the boot animation so I held down the power button for about 10 seconds to hard reboot it. I went to brush my teeth and get ready for work and when I came back, the phone had booted up all the way! Reflashing the stock system partition may have helped but I can't be sure.
I've seen this happen before but I think it was after I switched to ART and my sister's Dalvik Moto X doesn't do it. I'll be switching back to Dalvik after this scare.
thebrianiac;52700161I've seen this happen before but I think it was after I switched to ART and my sister's Dalvik Moto X doesn't do it. I'll be switching back to Dalvik after this scare. ;)[/QUOTE said:
Art is still "experimental" and not all apps work with Art.. so.. Its best to stick with Dalvik for now.
Click to expand...
Click to collapse

X2 Black screen

Hello,
I did a reboot and now I can't use my phone anymore. I see the Boot animation but after the Boot up, the screen just turns black. I receive notifications and active display is working, also I can start my camera with the twist but I can't take picture because the touchscreen does not respond. On active display or the power off pop up, the touchscreen is working. So I did a cache partition wipe but this hasn't fixed my problem. The strange thing is that after a couple of frustrated reboots, the Boot animation changed to the old animation with the spinning world. I want to reset the phone via recovery but first I need to backup my data. I have very important Data on my phone like whatsapp log or Photos and videos.. I can't connect my phone to the computer because I have a pin... How I can Backup my data and what caused the black screen?
If your bootloader is unlocked you can flash TWRP. TWRP has the ability to decrypt userdata if you have the password. I don't know if it can decrypt the moto x or not, because TWRP only officially support ASOP type encryption, if motorola uses a different technique for encryption it will say the password is wrong. If it works you can browse and backup files from TWRP recovery.
If it says the password is wrong or you don't have the bootloader unlocked, then you are SOL and have lost everything.
In either case doing a factory reset will hopefully fix your issue.
Sent from my XT1095
So I did a factory reset now. But I stuck in Bootloop, i just see the M logo. How I can fix it? And no, my Moto X is stock like out of the Box.
rupro327 said:
So I did a factory reset now. But I stuck in Bootloop, i just see the M logo. How I can fix it? And no, my Moto X is stock like out of the Box.
Click to expand...
Click to collapse
After the factory reset bootup takes longer than normal, how long did you wait?
If that is not the case, what model moto x do you have? For example mine is xt1095. Also what version of android do you have? 5.0, 4.4.4, 5.0.2, 5.1, etc?
Sent from my XT1095
same issue today
also have the same issue, black screen after reboot. moto voice, active display/notifications are responsive, camera too when twisting the phone. moto voice says "unlock your phone to continue" but i currently don't have any screen locks or anything, just swipe. i have a pure edition running on 5.1. Skeptical about a reset since the phone is still responsive.. tried looking for other fixes, but looks like this issue is just coming up today...
This exact same thing happened to me. Updated to 5.1 about a week ago via the OTA. Wiping cache did nothing. Diagnosing it as a software issue, I attempted to sideload the official 5.1 OTA that's posted elsewhere in the forums. It came back as installation aborted, so I gave up on any hope of keeping my data and did a factory reset. Now all it does is bootloop, sometimes settling on the prone android no command screen for a little while. I can boot into recovery and the bootloader, but thats it. Really hoping someone can come up with a solution. XT1096.
AGISCI said:
After the factory reset bootup takes longer than normal, how long did you wait?
If that is not the case, what model moto x do you have? For example mine is xt1095. Also what version of android do you have? 5.0, 4.4.4, 5.0.2, 5.1, etc?
Sent from my XT1095
Click to expand...
Click to collapse
I've waited about 30 minutes, in this time my phone just bootet into the recovery by his self. I've contacted Motorola and I'll send my device to repair.
It's a xt1092 with 5.1 RETDE.
I personally think that this issue is caused by the Boot animation update.
swankylaxplayer said:
This exact same thing happened to me. Updated to 5.1 about a week ago via the OTA. Wiping cache did nothing. Diagnosing it as a software issue, I attempted to sideload the official 5.1 OTA that's posted elsewhere in the forums. It came back as installation aborted, so I gave up on any hope of keeping my data and did a factory reset. Now all it does is bootloop, sometimes settling on the prone android no command screen for a little while. I can boot into recovery and the bootloader, but thats it. Really hoping someone can come up with a solution. XT1096.
Click to expand...
Click to collapse
Flash the stock 5.1 logo, kernel, system, modem, baseband and recovery for the XT1096 - the full image files are available.
JulesJam said:
Flash the stock 5.1 logo, kernel, system, modem, baseband and recovery for the XT1096 - the full image files are available.
Click to expand...
Click to collapse
Thank you! I don't know how I missed that! Back in business now.
nrsmsn said:
also have the same issue, black screen after reboot. moto voice, active display/notifications are responsive, camera too when twisting the phone. moto voice says "unlock your phone to continue" but i currently don't have any screen locks or anything, just swipe. i have a pure edition running on 5.1. Skeptical about a reset since the phone is still responsive.. tried looking for other fixes, but looks like this issue is just coming up today...
Click to expand...
Click to collapse
I have the exact same problem. Any fix?
Edit: Can't get adb to recognize phone. Phone is rooted.
kunal_07 said:
I have the exact same problem. Any fix?
Edit: Can't get adb to recognize phone. Phone is rooted.
Click to expand...
Click to collapse
Have you tried reflashing the system image from the bootloader?
is that possible without adb? If so, can you tell me how?
kunal_07 said:
is that possible without adb? If so, can you tell me how?
Click to expand...
Click to collapse
You still do everything through terminal. You have to cd to your folder that has adb and fastboot enclosed, usually platform-tools. Instead of starting each command with "adb", you'll start with "fastboot" and you'll be flashing these while your phone is at the fastboot screen.
The full image files are in the forums, and all the commands you'll need, in order, are posted in this thread earlier
I have found that some time the fastboot from Moto wouldn't recognize the phone. I, then, use the mfastboot-v2 found somewhere around this forum works great.
Me too faced this problem few days back. Only option left to do was factory reset.
Read below just to go through of what i faced:
( I had gone through bunch of articles for restoring my data but i had a pin lock because of which while connecting to pc it couldnt detect phone.
Other things i tried includes flashing lockscreen bypass zip via stock recovery. There i faced signature verification failed error because i had done it through stock recovery where it doent let u toggle signature verification on/off as in CWM. )
And for those who wants their data back , i found many articles of data recovery after factory reset. But it needed your device to be rooted. All you have to do is after factory reset dont make use of phone and after rooting you can recover your phone by software as EASEUS android recovey, Dr fone android recovery. Thats all .
I am too facing this issue as of last night,, I have the verizon version (complete stock, no root, locked bootloader) and I am not sure how to go about fixing this without losing all my data.. I tried wiping cache but it did nothing.. Can anyone provide some kind of troubleshoot guide please? It would be much appreciated.
A friend of mine is also having the same issue.
I tried the 5.0 image and it won't flash.
I'm locked and without root. Is it even possible to flash even the factory images? (And yes, I've tried to go to the Customer Portal for the Moto X and that isn't giving me anything)
Edit: Finally got it to flash the stock image. Didn't help. Factory reset fixed things.
Note: I had this problem and was able to fix it through a factory reset, but I had to do it through minimal adb and fastboot. The bootloader factory reset option didn't work.
I am having the exact same issue. Has anybody had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a bunch people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?

[Q] Internal memory full. Can't even access recovery

I ignored the low memory warning while downloading a few things. Surely it can wait a few seconds till I'm done with what I'm doing then I'll stop downloading and delete something. Nope. Phone froze. Completely. Never seen anything like it. So I long pressed the power button and waited for it to power back on (neither of my phones ever stay off, they turn back ok as soon as they turn off). Now it's stuck at the unlocked bootloader screen. Trying to get into recovery works as far as the TWRP logo. Then it freezes for eternity.
What do? Everything on it is backed up, so I don't really care about the data. I can't find any hard reset combos for it and the battery is non-removable.
Moto G 2014 (2nd Gen) Titan running the latest AICP nightly and the latest TWRP.
You would have to restore stock probably... I faced the same issue and I had to restore stock and then flash twro again ! Hope that helps

Phone in bootloop please help...

So i wanted a new rom for the awesome features so after i had rooted and installed twrp custom recovery i downloaded cm12 then created a nandroid. I put my phone into recovery wiped everything except internal storage and installed cm12 and gapps. This is where my problems started, as much as i liked the new rom it wasnt connecting to my cellular network so i thought ok ill just recover my nandroid so i wiped everything except the internal storage and then started the recovery when it finished i rebooted and it goes to the warning bootloader unlocked screen and sits for about 15 seconds the goes black and repeats. My phone is a motorola moto x 2014 victara, any help is much appreciated.
Please give us more details:
1) can you access recovery? Try holding the "power" button for like 20 seconds and trying to reboot into recovery when the phone boots.
2) can you access fastboot mode on the phone? maybe you lost your custom recovery but can access the bootloader and that makes things easier.
3) what is your device number? (xt1097, xt1095, xt1092, etc)
You are going to want to factory reset. Most times coming from a customer rom to another or even back to stock you will need to do a factory reset in order to wipe out anything that may have been left over that could cause issues.

Stuck on just a sec screen.

My LeEco S3 X522 has not been able to get past the just a sec screen. At first it was after unlocking the phone it would just stay on the loading android screen but i was able to get into the settings by using the notification bar at that time i was using pixel experience but not the latest (one before the latest) so i updated and still would not work so i just formatted everything completely then re installed the latest pixel experience. Now i am stuck on the just a sec screen when starting up the phone. The phone goes dim then the screen goes off yet i am still able to use the hardware nav buttons ( they dont do anything but light up and vibrate). Screen will come back on after a few mins but it just repeats it self.
Also, prior to this happening my phone was dropped and the screen cracked. It took a week or two until i fixed the screen.
lepenguin33 said:
My LeEco S3 X522 has not been able to get past the just a sec screen. At first it was after unlocking the phone it would just stay on the loading android screen but i was able to get into the settings by using the notification bar at that time i was using pixel experience but not the latest (one before the latest) so i updated and still would not work so i just formatted everything completely then re installed the latest pixel experience. Now i am stuck on the just a sec screen when starting up the phone. The phone goes dim then the screen goes off yet i am still able to use the hardware nav buttons ( they dont do anything but light up and vibrate). Screen will come back on after a few mins but it just repeats it self.
Also, prior to this happening my phone was dropped and the screen cracked. It took a week or two until i fixed the screen.
Click to expand...
Click to collapse
Try flashing 8 august nano gapps.
Do you have a nandroid backup of Pixel experience, if yes, then you can restore it and remove all sorts of screenlocks via twrp (Google how to) . Then flash latest gapps and os zip. Clear dalvik and cache. It should work.
It did not work. Still on just a second, even with the august 10th GAPPS. I formatted everything completely. No OS etc. Then i tried to install the stock ROM by using the chinese twrp (YDDS or something like that). It has worked before but now it did not even boot into the recovery screen unless its US twrp. I flashed RR OS (Oreo) and it would just boot loop. I can't seem to find any solution. I do not see why even after formatting all data, neither ROM will load. (Have noticed on twrp it says it could not find internal storage, yet it installs the ROMS and GAPPS. Not sure what that is about but could not find anytning online.)
lepenguin33 said:
It did not work. Still on just a second, even with the august 10th GAPPS. I formatted everything completely. No OS etc. Then i tried to install the stock ROM by using the chinese twrp (YDDS or something like that). It has worked before but now it did not even boot into the recovery screen unless its US twrp. I flashed RR OS (Oreo) and it would just boot loop. I can't seem to find any solution. I do not see why even after formatting all data, neither ROM will load. (Have noticed on twrp it says it could not find internal storage, yet it installs the ROMS and GAPPS. Not sure what that is about but could not find anytning online.)
Click to expand...
Click to collapse
Try the 6 July gapps here https://github.com/opengapps/arm64/releases/tag/20190706
I think it shouldn't give rise to your issue.
Remember to flash the nano version.
It's possible your data partition is corrupt.
First wipe system, cache , dalvik cache and data.
Then repair data, format to ext2 and them reformat to ext4. Then reboot to recovery and repair data again and finally wipe it. Reboot to recovery again. Flash stock ROM first. Then flash your preferred ROM.
RandomDelta said:
Try the 6 July gapps here https://github.com/opengapps/arm64/releases/tag/20190706
I think it shouldn't give rise to your issue.
Remember to flash the nano version.
It's possible your data partition is corrupt.
First wipe system, cache , dalvik cache and data.
Then repair data, format to ext2 and them reformat to ext4. Then reboot to recovery and repair data again and finally wipe it. Reboot to recovery again. Flash stock ROM first. Then flash your preferred ROM.
Click to expand...
Click to collapse
Sadly it still didn't work. Possible the memory chip itself is damaged? Idk

Categories

Resources