So I didn't read any guides and was following an old YouTube video on how to go back to stock and OTA. Unfortunately the link was for an older version of the Moto X Toolkit and it took me back to 4.2.2 and I accepted the OTA. gg.
I have tried flashing 4.4.4, 4.4.2, 4.2.2 again from fastboot and in the end the result is the same: a flashing dead android popping up every few seconds that says error. After reading the Q/A I think this is a hard brick but has there been any updates on ways to fix this?
I can't USB mount to put in a custom rom either and it won't let me sideload since the USB mounting isn't working. I can flash custom recoveries but that's about it.
Thanks.
Not researching first on any device is a mistake for sure... Especially the X. You've done the procedure that guarantees bricking a Moto X unfortunately.
This thread may be your only hope now...
http://forum.xda-developers.com/showthread.php?t=2629057
Good luck!
I looked into this method but couldn't get it to work since it wasn't recognizing the phone when I plugged it in. I did manage to unbrick it somehow by flashing a 4.2.2 version again using the toolkit (post camera I believe). I managed to boot up again in 4.2.2 but not really sure how to upgrade to 4.4.4 at this point without bricking again.
Is it safe to RSDlite to 4.4.4 using the right carrier?
edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .
The lollipop upgrade caused my 2013 Moto X frequent crashes and the BT stack is broken. So I decided to downgrade. I found this walkthrough: https://www.youtube.com/watch?v=SRV2qoQX-P4
and followed it. It wasn't until I was done that I found it was for Moto G not X. The phone starts, but is obviously in a corrupted state - wifi doesn't work, etc...
What is my best/easiest course of action to downgrading to Moto X's image of Kit Kat?
Thanks!
Use this guide:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Thank you. I was able to unlock bootloader, root and install CM11. However, something major is screwed up in my phone as a result of the incorrect as the Wifi and BT don't work (don't turn on).
Also, as soon as I try to open security in setting, it crashes. Is there a way to do a deeper recovery/reinstall?
Thanks!
Andy T11 said:
Thank you. I was able to unlock bootloader, root and install CM11. However, something major is screwed up in my phone as a result of the incorrect as the Wifi and BT don't work (don't turn on).
Also, as soon as I try to open security in setting, it crashes. Is there a way to do a deeper recovery/reinstall?
Thanks!
Click to expand...
Click to collapse
Try installing CM12.1 and wipe the '/system' partition in the process before flashing CM12.1.
If that doesn't fix WiFi and Bluetooth then try this:
http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
Andy T11 said:
Thank you. I was able to unlock bootloader, root and install CM11. However, something major is screwed up in my phone as a result of the incorrect as the Wifi and BT don't work (don't turn on).
Also, as soon as I try to open security in setting, it crashes. Is there a way to do a deeper recovery/reinstall?
Thanks!
Click to expand...
Click to collapse
If you followed the guide you were linked to, it used fastboot to reflash all the partition on your phone... This means your rewriting basically all the phones software. If it is not working after that
a.) The software is bad
b.) The user is bad
OR
c.) The hardware is bad.
Read all the output of the commands you enter, make sure there are no errors, and verify you have the correct software.
scryan said:
If you followed the guide you were linked to, it used fastboot to reflash all the partition on your phone... This means your rewriting basically all the phones software. If it is not working after that
a.) The software is bad
b.) The user is bad
OR
c.) The hardware is bad.
Read all the output of the commands you enter, make sure there are no errors, and verify you have the correct software.
Click to expand...
Click to collapse
The '/persist' partition never gets written upon.
And it stopped working after he flashed the Moto G firmware.
So it's obvious that the software that is bad.
What XT is this phone and is it locked into a carrier?
Did you re flash back the stock radios for the X? Flashing CM on your device does not include the radios. Having the wrong radios will cause you to have problems. If you flashed the radios for the moto g you will need to flash the ones back for the moto x.
Travisdroidx2 said:
Did you re flash back the stock radios for the X? Flashing CM on your device does not include the radios. Having the wrong radios will cause you to have problems. If you flashed the radios for the moto g you will need to flash the ones back for the moto x.
Click to expand...
Click to collapse
THIS
I'm a bit slow to realize this, but after updating to T mobile's latest 20b firmware (lollipop 5.0x), it lost root. I then tried to root it, using the three methods mentioned here: http://forum.xda-developers.com/showthread.php?t=2732311.
Towelroot clearly doesn't work anymore. The zip file in the above thread couldn't be flashed since there's no recovery operation possible (just showing an android with ! in a triangle sign). I also tried the purpledrake, but the script doesn't run when the phone is connected with all drives installed and adb devices showing the phone. I then tried to get fastboot mode back (to install twrp/cwm recovery to flash the zip file) by following http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825 which I have done successfully before, but then couldn't do it because it requires root (doh!).
So it seems that I just lost my ability to root, unless I downgrade to a stock kitkat (10e?) from tmobile, and then towelroot/etc. assume those work.
Anyone with experience on the stock 20b firmware? Can you root it and how? I'd love to use the beautiful 12.1 Cyanogen that's available here, but the camera doesn't work right on mine. Thus stock 5.0 seems to be the best option. Many thanks.
I got a bit further on the purpledrake method, in that I had to do a clean restart on the phone and connect to usb before the script will recognize. However, it ends up giving a really quick error message after trying a temp root: "your phone is not running a compatible software version. No vulnerable mode detected. Rebooting phone."
Anyway, many thanks to @brossovitch I followed http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/ and it works like a charm. I can't seem to delete this very short thread so I thought I'd wrap it up with a solution. If it seems a bit useless please remove the thread (or tell me how to do it since I can't find the "easy button"). Thanks.
I attempted to root the moto G, but the instructions were unclear and I think I flashed the stock firmware incorrectly. So now the WI-FI won't turn on and my device still isn't rooted. Can somebody walk me through the process of fixing this please? Thanks in advance.
I'm in a bind and have tried almost everything that your boards have to offer.
I've been trying to extend the life of my Moto X (2013) XT1056 via rooting to do some tasker things.
The recent OTA update came out and I tried to use FlashFire to run it and it has softbricked my phone. Through TWRP, I have tried flashing the stock firmware via sideload and via loading the zip onto the deceive without success. Ultimately, I tried loading a custom ROM (EpsilonProject v3.1) which is working well, except that I have no network connectivity. I've tried almost everything but keep running into the same problem when I try to manually flash the stock firmware:
bootloader variable not supported
I've tried using the help offered in the forums to locate the file that I supposedly need to rename in the /system folder, but that file does not exist.
Any other ideas? I'm not tied to fixing this, as I've extended the life of my phone by about a year as it is. But my Moto X (2013) was working great until the forced OTA effed it. I mean, how many people actually get three years out of their smartphone nowadays? :/
Thanks for the help!