So here's the deal. I had a Moto X Dev Edition with TWRP recovery and the latest CyanogenMod ROM, working properly.
I returned to stock using a Motorola ROM and their instructions, did get a gpt_main error in the process, but since it worked for a certain Reddit user (goo.gl/2sEmjz -- can't post links yet!) I decided to continue. It booted fine into stock, but when I did system updates, it would reboot into TWRP. So I flashed the recovery.img file. After that, the phone booted, then rebooted, and went into a recovery "installing updates."
I walked away for a second, came back, and the screen was black. I can't "force it off," it doesn't appear to be running, and I can't get into fastboot. Is the phone bricked (which I'm leaning to), or is it still running and I just need the battery to run out, or is there some other way to revive this phone via USB?
Hoping there's some expert I can get advice from, and thanks in advance!
Related
Hello,
I'm new to unlocking / rooting / image flashing etc etc. However, I was excited to see Moto X 2nd Gen is finally unlockable so I went ahead and completed that process. I have an XT1096 on VZW.
I followed Mikeoswego's directions to run 5.1 on XT1096 detailed here: http://forum.xda-developers.com/mot...1096-victara-mofo-image-root-t3100145/page103
However, after flashing the images and rebooting my phone, it plays the motorola world animation then the screen goes black. I've let it sit for a few minutes to no avail. This happens every time i reboot it. I've tried reflashing the images as well, no difference.
Any tips on what i should do next? At least just to get it working as normal again?
Thanks,
Ryan
i had issues with that version of the stock rom after reboot, Its from the same mike user. Boot into twrp Recovery and then copy this firmware to the downloads folder. https://www.androidfilehost.com/?fid=24052804347797814. Then get the stagefright update and cm launcher from here http://forum.xda-developers.com/moto-x-2014/development/img-xt1096-victara-mofo-image-root-t3100145. Flash both those files and then if you want can run the debloat on same page as above. Then make sure ya flash a 5.1 version a gapps file too, (http://opengapps.org/) then reboot phone. Being i had accidentally wiped my phones partition during a reboot I had to start from scratch in the recovery but got it all working again. I was worried mine was bricked too but Im back on CM13 now but have been going back to the stock as well since it has better reception on verizon than CM12 or CM13 currently. You should get moto boot image animation, and will cycle through all the stages and after a few more mins of that moto screen it will begin the setup page on the phone.
Thanks very much. I replied to your PM but I also wanted to mention the issue is resolved here. I was able to flash CM 13 after i figured out how to properly use TWRP.
I've got a lot of learnin to do in this realm.
Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.
You don't downgrade Motorola phones!
Sent from my iPad using Tapatalk
Is your device fixed now?
mlspot said:
Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.
Click to expand...
Click to collapse
I purchased a 2013 moto x, used, unlocked, updated it using the official ota update, now when I boot the phone I see Andi on his back with "No Command", I can boot into fastboot, so I tried flashing the most recent update both manually and via RSD lite. No matter what I get " security version downgraded PIV block validation for (got/system) failed.
I've been through just about every thread there is about restoring to stock, and everything seems to say I'll be fine if I flash the same version, but I continue to get errors, not sure where to go from here, any help would be appreciated,! Im not a complete noob, but I'm definitely not a pro..I had intentions of rooting the phone after updating, but now .I'm just afraid I permanently bricked the new phone....
You need to flash the same ROM that you had before the update with fastboot. Also you need to turn off your phone and boot on it with Power button + volume down or you won't be able to flash the ROM.
Thanks for the reply
After an entire day of not sleeping and flashing the EXACT same firmware on my device a dozen different ways it finally worked!
RDS lite, and manually flashing didn't work, but I tried moto recovery fixer tool I found on a different forum. And flashed the same firmware, but this time it was successful and the phone is up and running like new. I think I'll be returning the phone, but I appreciate the reply and the help I found in XDA! Y'all rock!
I have had my Droid turbo since launch and as such followed the path the getting root on it for some time. I used Mofo to get root back on android 4.4.4, used it again to upgrade to 5.1 while keeping root, used sunshine to unlock the bootloader when that came out, and finally installed TWRP recovery on it. I had not done much to it since, but had Intended to install cyanogenmod for a while.
Well I thought I would finally get to it this weekend. I made a nandroid back-up with TWRP, copied it to my computer, backed up some files I didn't want to lose, and went ahead and installed the latest version of cyanogenmod 13 for quark (Moto MAXX and Droid Turbo) and the necessary gapps. It all went very well. I booted into cyanogenmod just fine, and signed in to google.
I was in the process of setting things up, like preferences/wallpapers/wigets etc, while google downloaded my apps. Not long after I started doing this, nova launcher would repeatedly crash, as well as cyanogenmod's built in launcher. I got fed up with it and rebooted. But the phone shut down and started acting odd. It would show what looked like the bootloader, but the open android guy was not there, and I had no options at the top. Sometimes it would just say AP Fastboot Flash Mode (Secure) with no other text.
I got it to go to the bootloader after holding down the power and volume down button, and got it to boot to TWRP. But TWRP said there is no OS installed, and it refused to install anything, wipe anything, and TWRP itself crashed after a bit when I left it there to try and use ADB to push my nandroid back up to it.
Now TWRP will not load from the bootloader, and I cannot flash anything. I wanted to just re-flash the stock firmware. So I downloaded fresh copies of it from the root thread here on XDA, but no matter what, i get the error "(bootloader) Failed to erase partition" It does this for anything. I tried flashing TWRP and the fresh system image. I tried following the steps on the root thread that flash things that you need to prepare the phone for the system image, but all attempts to flash fail with the same message.
I also tried using mofo to flash a clean system image. But it just stops and quits at 7%. I have had this problem before, and got around it by using mofo 0.0.2. But I no longer have that version.
I am at a loss here. I need my phone back ASAP. Any help would be much appreciated.
Have you tried doing everything from Terminal on your computer instead? That's what saved my butt once when I was in a similar situation.
Sent from my DROID Turbo using Tapatalk
arizonaomnia said:
Have you tried doing everything from Terminal on your computer instead? That's what saved my butt once when I was in a similar situation.
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
That's all I've been doing
EDIT: Everything booted up after while, just took a really long time for it to completely boot.
I had my xt1060 Verizon Dev Edition rooted and unlocked running Android 5.1. I wanted to flash it back to factory, so I downloaded "XT1060_GHOST_VERIZON_5.1_LPAS23.12-39.7-1_cid2_CFC.xml.zip" from firmware.center. Then I used the commands from Motorola's Restore to Factory guide, to flash the files.
That caused a bootloop to occur and have the screen to stay at the warning bootloader unlocked screen. So then I downloaded "XT1060_GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip" and tried that, and still the same thing.
I had an old copy of "MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml" which I've used before to flash back to factory and I tried that. And now whenever I try to boot it up, it'll go into motorola's recovery and the image of the Android opened up keeps flashing on the screen, assuming that it's in a bootloop.
Up until this point I've been using osx-fastboot to flash the files, so I pulled out my old Windows laptop which had a copy of RSD Lite in it, and attempted to flash "XT1060_GHOST_VERIZON_5.1_LPAS23.12-39.7-1_cid2_CFC.xml.zip", which I tried the first time. I was able to get through that successfully, however it still did the same thing as before where the recovery was stuck in a bootloop.
I found this thread on here, and I followed the instructions for RSD Lite and the manual flash, neither worked did the same thing as when after I tried RSD Lite the first time. However the manual flash got farther, but is just sitting at the Verizon boot screen, and that's where it is right now for the last 15 minutes.