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
Related
Last night, I downloaded InnovationsOS v3 from the Nexus One Android Development forum. Prior to this I was using FRF50, and I have a rooted Tmobile Nexus One. I wiped the phone back to factory settings and also wiped the Dalvik cache (as I've been told in the past). Flashing went just fine and within a few minutes I had InnovationsOS after a reboot. (Let me just say, with this one minor exception, InnovationsOS looks incredible and I loved every minute of it).
After install, I set up AdFree which removes ads. I decided to do a quick reboot. The reboot wasn't so quick, and it stuck on the startup screen (the Nexus One/Google logo with the unlocked symbol below) for about 3 minutes. I didn't think this was good, so I tried a battery pull hoping for a normal reboot. Instead, what I got was the android falling out of the box. I tried a battery pull again and attempted to enter recovery, which worked. I wiped, and reloaded FRF50, and rebooted. I got the android and the box image, which wouldn't let me even boot into recovery anymore after several battery pulls. After a couple minutes of being completely stumped (and scared lifeless) I let the phone sit, and somehow it booted into recovery, where I wiped (again) and flashed InnovationsOS (again). After it loaded, it rebooted, and it's been working great since then, with the exception of one minor screen/keyboard bug...I press S, and get Z, or I press delete, and I get enter, etc. Plus hitting OK or Cancel on dialog boxes is impossible and need to use the trackball.
So, I would like to reboot to fix this problem and want to know what will happen, and I want to know what I did wrong above. I know all this sounds completely noob for this forum but I'm willing to learn, which is why I've been experimenting with rooting and flashing roms.
Thanks a lot, any help is appreciated.
Just rooted my droid with this:
forum.xda-developers.com/showthread.php?t=764470
All of that went fine and I went to install my first ROM. The phone went to restart as I assumed it should and it has been on the red eye/droid screen for the past half hour+ now. Assume I know nothing, how can I fix this?
Assuming you have a custom recovery flashed (I hope you do) reboot into it and wipe data and cache. It should then reboot just fine into your new ROM. Worked twice before for me.
SandmanGTP said:
Just rooted my droid with this:
forum.xda-developers.com/showthread.php?t=764470
All of that went fine and I went to install my first ROM. The phone went to restart as I assumed it should and it has been on the red eye/droid screen for the past half hour+ now. Assume I know nothing, how can I fix this?
Click to expand...
Click to collapse
I'll be adding "whipe data/clear cache" to the instruction set of that post.
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.
Firstly, this device has never been rooted or had anything flashed to it. It is completely stock.
My step-daughter has been having issues with her Droid 4. About a month back or so, she started noticing that it wouldn't boot. It would flash the Motorola logo, and then the screen would just hang on the bootanimation. Eventually if we rebooted (power+vol down) enough times it would boot up.
Last night however, this happened again and it would not boot at all. I tried rebooting many times and it would never get past the bootanimation. After about 20 or so reboots I figured it was time for a Factory Reset. After the reset however, it wouldn't even display the bootanimation. It would still display the Motorola splash screen, but after that the screen would just go black with the display is still on. I Factory Reset several more times and nothing. Eventually after a number of times rebooting, it finally booted up. Well that was yesterday. Today she had to reboot it and it wouldn't boot again. Would just hang on a black screen.
I'm about ready to send it back since it's still under warranty, but figured I would check here to see if any of the amazing XDA guru's had experienced this and found a solution. I searched Google and this forum and didn't really see anything. Any help would be greatly appreciated!
jdiamond7 said:
Firstly, this device has never been rooted or had anything flashed to it. It is completely stock.
My step-daughter has been having issues with her Droid 4. About a month back or so, she started noticing that it wouldn't boot. It would flash the Motorola logo, and then the screen would just hang on the bootanimation. Eventually if we rebooted (power+vol down) enough times it would boot up.
Last night however, this happened again and it would not boot at all. I tried rebooting many times and it would never get past the bootanimation. After about 20 or so reboots I figured it was time for a Factory Reset. After the reset however, it wouldn't even display the bootanimation. It would still display the Motorola splash screen, but after that the screen would just go black with the display is still on. I Factory Reset several more times and nothing. Eventually after a number of times rebooting, it finally booted up. Well that was yesterday. Today she had to reboot it and it wouldn't boot again. Would just hang on a black screen.
I'm about ready to send it back since it's still under warranty, but figured I would check here to see if any of the amazing XDA guru's had experienced this and found a solution. I searched Google and this forum and didn't really see anything. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Only other I can think to do would be to flash the fastboot files. A factory reset basically just wipes data while fastbooting it should reset the system itself to complete bone stock. You can do this using rsdlite or download a utility like jsnweitzel's ICS Only Utility in the Dev section.
Really sounds like a hardware issue to me since it's not rooted or anything but still might be worth a shot.
Sent from my Droid 4 - LiquidSmooth
kwyrt said:
Only other I can think to do would be to flash the fastboot files. A factory reset basically just wipes data while fastbooting it should reset the system itself to complete bone stock. You can do this using rsdlite or download a utility like jsnweitzel's ICS Only Utility in the Dev section.
Really sounds like a hardware issue to me since it's not rooted or anything but still might be worth a shot.
Click to expand...
Click to collapse
Thank you very much for the quick reply. I've downloaded jsnweitzel's ICS Only Utility and am charging up the phones battery so I can use it.
Just a quick question before I do this. I'm assuming that running the restore through ICS Only Utility is flashing a stock system image. That image is not rooted is it? Not that I would typically care, but if I do have to bring it back to Verizon I don't want them hassling me for rooting the device.
jdiamond7 said:
Thank you very much for the quick reply. I've downloaded jsnweitzel's ICS Only Utility and am charging up the phones battery so I can use it.
Just a quick question before I do this. I'm assuming that running the restore through ICS Only Utility is flashing a stock system image. That image is not rooted is it? Not that I would typically care, but if I do have to bring it back to Verizon I don't want them hassling me for rooting the device.
Click to expand...
Click to collapse
The image flashed in the fastboot process is completly stock, unrooted.
Sent from my Droid 4 - LiquidSmooth
Thanks for the help but that didn't do it. Guess I'll be taking it back to Verizon!
Sent from my SCH-I535 using xda app-developers app
Ok so I'm pretty sure my phone is done for, but I thought I'd see if anyone knew a solution before I go buy a new phone
Yesterday I dropped my phone (which was running Slimbean), but I popped the battery back in and it worked fine. Then about three hours later, it randomly shut off while I was using it, then started going into a bootloop. Occasionally it will start up all the way, but I'm lucky if its on for 10 minutes before turns back off and starts bootlooping again. I got it to boot into CWM, (the first time it shut off while I was in CWM) and wiped everything and reflashed Slimbeam, but it didn't change anything. Any ideas?
Go back in and do wipes on everything but external drive reflash wipe cache + dalvik cache + fix permissions then boot. Let sit 10 minutes before doing g any setup with Google or phone. This allows all drivers to load and configure prior to having more data to configure.
Sent from my CM10 Linero Odexed Powered by Evil