I got a message saying that an update is availible and i tried to download and install it but it failed two different times so i gave up. Now after several power cycles due to normal use my razr i is stuck in a boot loop (static red moto symbol then boot animation with intel inside repeating).I got the phone into fastboot mode and then I downloaded and installed rsd-lite and all motorola drivers. 2 different computers that ive tried rsd lite does not detect the phone however fastboot does. Factory option just resumes the boot loop. I dont know how to procede from here?
Edit: Phone is locked bootloader unrooted
Okay i guess this thread can be left incase anyone else gets in my position. I was able to fix my phone as fastboot was able to detect. i simply typed
Code:
fastboot -w reboot
and it wiped my userdata and cache and allowed the phone to boot.
megamit said:
Okay i guess this thread can be left incase anyone else gets in my position. I was able to fix my phone as fastboot was able to detect. i simply typed
Code:
fastboot -w reboot
and it wiped my userdata and cache and allowed the phone to boot.
Click to expand...
Click to collapse
It really works!
Thank you!
Related
So I'm restoring my old Nexus 6 that is being sent back for RMA and I encountered an issue. I have flashed things so many times I should remember how to fix this, but I haven't encountered it since my Nexus 7. I flashed all of the images and wiped the userdata as per the usual order. Everything boots fine until I lock the BL. When I re-locked the BL and restart the phone it goes to wipe its self and encrypt. The issue is that the stock recovery which it boots into during this process just has a android with a hexagonal floating blue orb in his chest and sits there for what seems like indefinitely. Its been sitting like that for a hour or so now and when I check what its doing using the "hold power press and release vol up" it says formatting data. I also tried booting into the stock recovery via the BL menu and its doing the same thing. I tried both 5.0 and 5.01 images with the same result. The last time I did this I didn't encounter this issue. I just want to make sure it boots normally so I can send it back in. If I unlock the BL it boots just fine after I format userdata and cache, but it won't go past the above mentioned state when I lock it.
This is what I did as far as fastboot flashing goes (LRX21O) the 5.0 stock rom:
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot oem lock
fastboot reboot
I'll try to re-download both images to see if maybe something changed but its odd because I have done this so many times its second nature. I think the issue lies with the encryption because I was unencrypted before and maybe it just takes forever.
Edit: after 2+ hours of it sitting there the phone finally booted. I thought it would never go past that screen but I guess encryption just takes forever.
Pilz said:
So I'm restoring my old Nexus 6 that is being sent back for RMA and I encountered an issue. I have flashed things so many times I should remember how to fix this, but I haven't encountered it since my Nexus 7. I flashed all of the images and wiped the userdata as per the usual order. Everything boots fine until I lock the BL. When I re-locked the BL and restart the phone it goes to wipe its self and encrypt. The issue is that the stock recovery which it boots into during this process just has a android with a hexagonal floating blue orb in his chest and sits there for what seems like indefinitely. Its been sitting like that for a hour or so now and when I check what its doing using the "hold power press and release vol up" it says formatting data. I also tried booting into the stock recovery via the BL menu and its doing the same thing. I tried both 5.0 and 5.01 images with the same result. The last time I did this I didn't encounter this issue. I just want to make sure it boots normally so I can send it back in. If I unlock the BL it boots just fine after I format userdata and cache, but it won't go past the above mentioned state when I lock it.
This is what I did as far as fastboot flashing goes (LRX21O) the 5.0 stock rom:
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot oem lock
fastboot reboot
I'll try to re-download both images to see if maybe something changed but its odd because I have done this so many times its second nature. I think the issue lies with the encryption because I was unencrypted before and maybe it just takes forever.
Edit: after 2+ hours of it sitting there the phone finally booted. I thought it would never go past that screen but I guess encryption just takes forever.
Click to expand...
Click to collapse
After all of this, did you test the recovery? I've been having the same issue today, but my recovery still isn't coming up. Every time I try, I still get the dead android with the triangle in the belly, but I am booted up and running.
I have a stock Verizon Moto X (XT1060) that was running 4.4.4. I was on a flight Friday using the phone in airplane mode to run Spotify and Podkicker - noticed the phone was running a little hot so I shut the apps down for a while. Anyway, upon landing I take the phone off airplane mode and the usual minor flood of emails/texts/updates comes in. About 30 seconds after this the phone begins alternately flashing "Process android.process.acore has stopped" and "Process android.process.media has stopped." These cycled for about 5 displays of each, then would disappear for about 45 seconds, then start again. Tried resetting the phone, letting the battery die, no success.
Saturday I tried to navigate into settings to do a factory reset, but the screen froze whenever I tapped on the "backup and reset" menu. Could access all the other menus from settings (until the error cascade started again....). I was able to boot the phone into recovery mode and wiped the cache - nothing. Went back into recovery mode to do a factory reset and now I appear to be stuck in a boot loop - the Moto logo pops up, buzzes, and then does nothing for about a minute or two before trying again. I can get it into recovery mode and tried to wipe the cache and factory reset again, but still nothing.
Any thoughts? Tried looking at other threads but didn't seem to find anything like this. Thanks!
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
hbenz2008 said:
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
Click to expand...
Click to collapse
No luck, unfortunately. Still stuck on the Moto screen. I can force the phone to reset by holding down the power button and then get it into fastboot, my computer recognizes the fastboot device, and the code seems to have run fine. Thanks for the idea - any other thoughts?
If you can still get into fastboot mode you can try flashing only the stock 4.4.4 system.img via mfastboot. That will not wipe your data. If that does not work I would do a full return to stock via mfastboot or you can use rsd.
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
cmcgowan said:
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
Click to expand...
Click to collapse
No, don't need to unlock boot loader to flash the system.img just enable USB debugging in developer options. Tap build number 5 times to enable developer options. If you have never flashed anything before via fastboot rsd might be easier for you.
Thanks - I've used fastboot before on an older phone but never enabled USB debugging on this phone and now can't get to enable it since I'm stuck with this boot loop. Downloading the files from Moto now so will give it a shot tonight anyway. Can't really break it more than it's already broken since all I've got now is a shiny light up paperweight.
You will still need to download the stock images for 4.4.4 for Verizon and extract them. You can flash via rsd or simply flash just the system by running the command "mfastboot flash system system.img"
You will have to have the image file in the same folder as your mfastboot.exe I usually keep all mine in platform tools.
Sigh. Got everything downloaded but when I tried to flash either the boot image, recovery image, or system image, I ran into errors
Here's what displayed (sub boot/recovery for system - same basic error):
c:\{Path}\mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [16.793s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.756s
I was following option 5 from mark @ cdma forum's guide to return motox to stock (can't link b/c I don't have enough posts...) . No issues until I got to the flash boot boot.img step.
I'm assuming this is due to not having USB debugging enabled prior to my phone eating itself, though I'm not sure. Willing to try other things since I love my Moto X but my cheap replacement phone arrives tomorrow (hopefully) so at least its not the end of the world...
You are sure you got the 4.4.4 images? You did not try to downgrade right?
Yup. Definitely got the 4.4.4 images (went back to the Moto site and it will let me download the 4.4.4 immediately but made me request authorization for 4.4.2) and I know I was running the most recent version since I checked for an upgrade on my phone last week in the hope that Moto had released 5.0.
You are following this guide? http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
If USB debugging is not on you can manually boot you device to boot loader mode. Then fastboot or rsd should work fine.
---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------
Moto X Restore and unbrick for any major US carrier: https://youtu.be/jhhktIkwi7Q
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
cmcgowan said:
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
Click to expand...
Click to collapse
You are opening the cmd screen from the same folder as your images and fastboot and mfastboot.exe correct? From your error it looks like your cmd screen is directed to your "C" drive.
Sorry, just didn't type out the whole thing - the cmd path is to the platform-tools folder where all of the files are also located...
Damn was hoping it was something simply like that. Have you tried rsd?
I haven't - didn't enable USB debugging and for whatever reason the package I downloaded from Moto doesn't include the XML file of instructions. Most of the links from the youtube video and some of the links from the XDA guide earlier are also dead so seems like I'm pretty much out of options. Thanks for all of your help - guess I'm going with the $80 replacement till I'm up for an upgrade!
Hey guys, last night I tried to root my device (XT1058) following the guide [here](http://forum.xda-developers.com/moto-x/general/howto-root-moto-x-ver-4-4-4-xt1060-t3118342). Stupid me decided I wouldn't need to go back to stock ROM like it says in the first step. I continue with the guide, follow every step, until I reboot. After rebooting my Moto X gets stuck at the white screen with the blue circle M. I panicked, read a lot of things online, followed them, and nothing worked. I reset the cache partition in recovery mode when rebooting into fastboot, still nothing. I also noticed that my device is no longer detected in ADB at all, even in fastboot. So after just giving up, I read online in multiple places going to recovery mode, and wiping the whole phone/factory resetting would fix it. It still is not recognized by ADB or finishing booting. I realize I should've been more careful. Please help!
First thing... when the phone is in Fastboot AP menu, you can't use ADB. ADB wont work and wont see your phone unless the phone is fully booted. (i.e. adb.exe and fastboot.exe use two different modes on the phone).
Next, I've seen that symptom before, but I don't recall how to fix.
I would really consider asking in the thread for the process you were following.
If no one gives you any suggestion, you could always try re-flashing the stock image for your phone that matches the highest version you've had installed on your phone. (On fastboot screen you can see bootloader version, so match you stock version to that. see the list of known bootloader versions at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 ) And use mfastboot to flash it (follow option 5 in the 2nd post at -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
I'm pretty sure I saw this on reddit. You had a mac right?
You need fastboot installed on your mac:
http://forum.xda-developers.com/showthread.php?t=1917237
Assuming you have fastboot working on your mac and your phone this thread method two:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Use fastboot instead of mfastboot for the sytem.img file.
If you receive an error with flashing system you could try:
Code:
fastboot -S 0 flash system system.img
If u can still enter recovery mode, factory data reset from it , if u can't boot still after resetting , u have to flash the full stock ROM.....
Sent from my HM NOTE 1LTE using XDA Free mobile app
Hello, I've a stock rooted moto g 2014 edition.
Today my phone started rebooting randomly. Half an hour ago it would restart after unlocking my device. Now it can't even get past the bootloader unlocked screen.
I've gone into fastboot and tried getting into recovery but it just reboots again after showing the TWRP splash.
I can't execute any commands through fastboot itself either, Minimal ADB and fastboot doesn't recognize the device.
Flash mode says battery low and asks me to connect the usb cable, but it already is and windows is prompting me "unknown usb device" even after the automatic fastboot driver install.
I haven't messed with any system files in a looong time.
Please help me, thanks.
EDIT: I had to get the drivers from the website, then all I had to do was erase userdata from fastboot.
Case solved =]
I am new to the forums and I need your help. The display on my LGWR went black after update even on cradle. It cannot even connect to my mobile via BT. The only thing it does is vibrate when the button is pushed and the heart sensor blinks a single time (when it turns on I guess.) as the vibration is a small one. When connected to PC running Windows 7, it is detected as Android Bootloader Interface, but ADB does not show any attached devices. Fastboot does show some alphanumerical device when (fastboot devices command is run). I have disassembled to remove the battery and tried to run it without the battery on cradle to no avail. Your help is needed as to what to do.
So it seems to hang in fastboot mode?
Try some fastboot commands then:
Code:
fastboot getvar all
fastboot reboot
Dear Ranf.
Many thanks for your reply. I ran fastboot getvar all and this is what I got. Screenshot is attached. Please guide me further.
Thanks.
Looks like you already downloaded the firmware? Right?
If so start with wiping cache and userdata:
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
I have downloaded the M1D63X boot, recovery and system (Disc Image Files) saved in my PC. They are not present in the SD card of LGWR. Shall I execute the commands or can I use fastboot and install this M1D63X on the LGWR. Thanks for your support.
The 2 format commands are basically the same as a factory reset. Please try them and then reboot.
Where did you download the file (URL please)?
Boot and recovery usually aren't trouble makers. system.img will if it's not a sparse image file.
The download like is as under Ranf:
http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
Dear Ranf,
I tried to run Fastboot flash cache, and this is what the result was. Please guide.
Oh I see: you first need to unlock the bootloader with:
Code:
fastboot oem unlock
How can I dod that, as the screen is blank on the watch. I have tried it, fastboot says OKAY on my PC screen, but the watch does not reboot on its own and I have to manually restart it to get recognized in PC at Android ABD Interface. What can I do.
After running "fastboot oem unlock" you somehow need to acknowledge your decision (I'm a Sony SW3 user)
Either swipe the screen from tp left to bottom right or
press the power button.
Do you see anything on the watch screen when in fastboot mode?
Dear Ranf,
I finally able to unlock bootloader and formatted cache and userdata and then rebooted it, but the problem still exists i.e. black screen and only vibration.
Is there any way I can install stock Rom via fastboot and if so please guide me how and from which url should I download the files.
Thanks.
Screenshot of the fastboot format cache and userdata is attached for your perusal.
At 1st look the download you have is fine.
You need to flash 3 partitions:
Code:
fastboot flash boot M1D63X_boot.img
fastboot flash recovery M1D63X_recovery.img
fastboot flash system M1D63X_system.img
When you see errors at any of these steps post them here.
Thankfully all things well without any errors, but the watch is still the same, no display whatsoever. I am really devastated now. If there is anything else that can be done, please guide.
Screenshot of the processes is attached.
Sorry I must admit I'm a bit lost now. Best you ask @vt0r in the thread where you got the firmware from.
Thanks a lot Ranf. God Bless You.
You have done all steps that you can do, probably your display is broken...
I'm sorry...
When your watch starts, you see the lg logo?
Is there a way to check if the display is broken as when I disassembled the watch everything looked fine with no signs of wear or moisture. The battery also is not holding charge as when you put the watch on cradle it vibrates but off of it, vibration stops. How can I charge the battery manually.
Hey,
my watch had exactly the same problem.
I had to repair it. They had to replace the mainboard.
Luckily the warranty paid for this.
Lucas
Lucky for you that you had warranty left. For me there are two problems. First no warranty left and secondly replacement parts are not available here in Pakistan, so if there is any online store from I can manage the parts, do let me know Lucas.