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!
Related
Hi,
I own a Moto X DE for few days. It runs Kit Kat, and is unlocked and rooted with TWRP. Today, I've got a notification about an OS update. But when I try to update my system, the phone reboots on the TWRP menu, and no way to update.
Any idea about this?
Thanks.
I have a the T Mobile (Same as Dev). Had it rooted and bootloader unlocked. I didn't really care for saving data tbh. So what I did was return to stock.
Already had the 4.4 in my fastboot folder. So I booted into recovery and wiped everything.
Then went back to download mode and fastbooted the T-Mobile 4.4 version. Ran phone setup, check for update and installed. Took about 10 minutes max.
Though of course this is one way out of a few. The stickies in this section have the various ways. Find one which better suits you.
Do note you should not take OTA with root and a custom recovery
Sent from my XT1053 using Tapatalk
Thanks, should have read a bit before asking. Sorry, and thanks again for the help.
Ok so heres the situation. I was running a Stock custom rom but was on 4.4 and was getting constant update notifications. so i decided to installed the updated 4.4.2 version of my custom rom. BTW my phone is a verizon locked bootloader phone. anyways i tried the workaround for retail phones and i ended up totally screwing my phone up. everything is wiped and i cant get anywhere but the fastboot screen. I have tried the Moto X toolbox but that fails and so does every other script i have tried. I thought that this would be my saving grace http://forum.xda-developers.com/mot...ty-windows-t2597625/post49119224#post49119224. but it looks like there server host is down so i cant download it. I have tried everything on both a Windows 8 with USB 3.0 and a Windows 7 with USB 2.0. both failed. My device only shows up at Fastboot ghost S in devices, i downloaded the PDAnet drivers but that didnt help. I can see the Fastboot in RSDlite though but the flash fails everytime. I keep getting "Partition (Boot) security version downgraded" and yes im using stock Verizon Roms.
baile508 said:
Ok so heres the situation. I was running a Stock custom rom but was on 4.4 and was getting constant update notifications. so i decided to installed the updated 4.4.2 version of my custom rom. BTW my phone is a verizon locked bootloader phone. anyways i tried the workaround for retail phones and i ended up totally screwing my phone up. everything is wiped and i cant get anywhere but the fastboot screen. I have tried the Moto X toolbox but that fails and so does every other script i have tried. I thought that this would be my saving grace http://forum.xda-developers.com/mot...ty-windows-t2597625/post49119224#post49119224. but it looks like there server host is down so i cant download it. I have tried everything on both a Windows 8 with USB 3.0 and a Windows 7 with USB 2.0. both failed. My device only shows up at Fastboot ghost S in devices, i downloaded the PDAnet drivers but that didnt help. I can see the Fastboot in RSDlite though but the flash fails everytime. I keep getting "Partition (Boot) security version downgraded" and yes im using stock Verizon Roms.
Click to expand...
Click to collapse
If you can get into Fastboot and RSDlite you should be able to install the 4.4.2 Verizon files from http://sbf.droid-developers.org/phone.php?device=0
I figured it out, my problem was that i was trying to flash 4.4 and not 4.4.2. got it unbricked but now it looks like i lost my root and my safestrap... :/
baile508 said:
I figured it out, my problem was that i was trying to flash 4.4 and not 4.4.2. got it unbricked but now it looks like i lost my root and my safestrap... :/
Click to expand...
Click to collapse
Yes, if you used RSDLite to flash you will loose root, etc.
But taking the OTA 4.4.2, you could have kept root, BUT would have lost write protect disable making root pretty useless (since any changes to /system or other protected folders would not survive power off/on)
Hi,
I just got a new Moto G, but it's the XT1064 version. I'd like to root, but it seems there's no XT1064 option for CF-Auto-Root from Chainfire. Should I use the XT1063 one?
http://autoroot.chainfire.eu/
motorola XT1063 titan_retuglb titan_umts MSM8226 msm8226 KXB21.85-17 4.4.4 11 720 230 Download a71b95caf989138032a5c4f0dad83519 2 387
Thanks
Sakura90 said:
Hi,
I just got a new Moto G, but it's the XT1064 version. I'd like to root, but it seems there's no XT1064 option for CF-Auto-Root from Chainfire. Should I use the XT1063 one?
http://autoroot.chainfire.eu/
motorola XT1063 titan_retuglb titan_umts MSM8226 msm8226 KXB21.85-17 4.4.4 11 720 230 Download a71b95caf989138032a5c4f0dad83519 2 387
Thanks
Click to expand...
Click to collapse
I have had a huge amount of frustration attempting to root the XT1064 over the past couple of days. If you're not afraid of reflashing your phone then you can try it but I highly doubt you'll be able to get it to work.
You can easily upgrade it to Lollipop with "official" firmware, but rooting has given me bootloop after bootloop.
After purchasing the Moto G XT1064 and spending 8+ hours trying to update and root the phone and remove all of the Motorola crapware, I eventually gave up. Right now I have version 22.11.6 installed, which is named "Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip", it makes sense to include the old version number, but they should at least call it "Blur_Version_from.21.11.17.titan...".
I really wish Google would REQUIRE manufacturers to release a stock android rom and an easy way to flash it with every consumer Android phone sold. Then developers could focus on improving the phone instead of millions of programmer-hours wasted on trying to remove the crapware and get it updated.
If you're a developer who wants a clean phone and don't want to waste dozens of hours screwing with flashing roms, just get a GPE or Nexus device, it's not worth saving $200. It's a great phone, but if you were looking for a phone that is easy to develop with, this doesn't seem like the right one. After my Droid X I swore off non-nexus devices, but the Amazon sale got me.
A couple of people claim to be able to get UPDATE-SuperSU-v2.16.zip working, (yes, SuperSU v2.39 exists now, it probably won't work though), but many more people (including myself) were not able to get it working.
Good luck! Please report back if you find a good solution, I'm guessing that many people are tired of the hoops we have to jump through to get a non-crapware stock Andorid device.
The seller kindly told me he can exchange my XT1064 for an XT1063, as rooting is my first concern (need to get Japanese fonts on it). So I hope to easily root with CF-Auto-Root now. I'll get my new phone in two days. I'm already crossing my fingers . Rooting should be a readily available option by the manufacturer, just like Motorola offers you to unlock the bootloader. Otherwise you're extremely limited. For example, to change a font. Samsungs let you do it in the original firmware, something as basic as this should already be in stock Android. And at least ext2 support, it's a Linux FS from 1993. We are stuck with crappy FAT32.
Btw, I just found this tweet by Chainfire: https://twitter.com/chainfirexda/status/533298320647925760
@ChainfireXDA are you going to be doing a CF-Auto-Root for the moto g xt1064? or will the one for the 1063 work? @Bobboman_2000 1063 version should work
Can you try it on the XT1064? I don't know the risk, but if you say you can reflash the firmware, maybe you can go back?
Sakura90 said:
The seller kindly told me he can exchange my XT1064 for an XT1063, as rooting is my first concern (need to get Japanese fonts on it). So I hope to easily root with CF-Auto-Root now. I'll get my new phone in two days. I'm already crossing my fingers . Rooting should be a readily available option by the manufacturer, just like Motorola offers you to unlock the bootloader. Otherwise you're extremely limited. For example, to change a font. Samsungs let you do it in the original firmware, something as basic as this should already be in stock Android. And at least ext2 support, it's a Linux FS from 1993. We are stuck with crappy FAT32.
Btw, I just found this tweet by Chainfire: https://twitter.com/chainfirexda/status/533298320647925760
@ChainfireXDA are you going to be doing a CF-Auto-Root for the moto g xt1064? or will the one for the 1063 work? @Bobboman_2000 1063 version should work
Can you try it on the XT1064? I don't know the risk, but if you say you can reflash the firmware, maybe you can go back?
Click to expand...
Click to collapse
I'll probably try it tonight. Will let you know the result.
You can change the file systems using: TWRP2.7.1.1-titan-motog-2014.img as your recovery.
I agree about the manufacturers. I thought it was growing pains in the early days of Android but we millions of us have to waste several hours trying to get decent security, privacy, and performance out of our phones. All anybody wants is stock Android.
Great if you try, I've seen no feedback of someone using it on XT1064. Won't changing the recovery affect future OTA updates? I was thinking of trying Stickmount with NTFS-3G. It only needs rooted device.
Sakura90 said:
Great if you try, I've seen no feedback of someone using it on XT1064. Won't changing the recovery affect future OTA updates? I was thinking of trying Stickmount with NTFS-3G. It only needs rooted device.
Click to expand...
Click to collapse
I was able to get 5.0 rooted. Not with CF Auto Root though.
I used TWRP2.7.1.1-titan-motog-2014.img and BETA-SuperSU-v2.38.zip but SuperSU had to be put on my internal storage.
Can you go back to stock recovery after installing SuperSU? As to have future OTA updates. I'm mean, only use TWRP for rooting.
derekm_ said:
I was able to get 5.0 rooted. Not with CF Auto Root though.
I used TWRP2.7.1.1-titan-motog-2014.img and BETA-SuperSU-v2.38.zip but SuperSU had to be put on my internal storage.
Click to expand...
Click to collapse
You put SuperSU on internal storage because that's the only way TWRP can flash it or because that's the only way you could get root (I.e., flashing from external storage didn't work)?
I have tried both CFAutoRoot and flashing SuperSU from external storage. SuperSU resulted in bootloop. AutuRoot worked but I couldn't power off my phone without the next power up throwing things into a bootloop. I chose not to leave my phone on all the time, so flashed a non-root backup.
I haven't tried flashing SuperSU from internal storage. So maybe that's something to try.
So just to summarize what I've done so far, I have a Moto G (2014) which has been updated to Lollipop through normal means. I started off following this guide: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818/page12
The guide then lead me to this one, as my model is XT1064, a Moto G from Windmobile. I had no issues unlocking my bootloader. http://forum.xda-developers.com/moto-g-2014/development/xt1064-lollipop-root-t2938051
With the guide above, after I flashed that file, my wifi would not turn on. Every time I pressed the toggle, it would immediately switch back to off. I then flashed the TWRP Recovery, and used that to finally root my device with SuperSU.
I checked my root, and my device is confirmed to be rooted, but the wifi is still not working. I looked around a little, and found this: http://forum.xda-developers.com/moto-g-2014/general/guide-lollipop-xt1064-north-edition-t2955076
The problem with the guide above is that its for a phone that was kitkat, while my phone is already lollipop. The guide does mention the wireless issue though, so I was thinking of trying out the steps outlined in that guide, also using that file (though that file is for 4.4).
Would this work? Or is the safer bet finding an 5.0.1 stock rom, and flashing back to that?
Edit: I found a link to a 5.0.2 stock rom (which is the version my phone currently is) I think downloading that and using that to fix the modem files is the better thing to do. (link: http://www.filefactory.com/file/53c1pepzp9cp/RETCA_XT1064_5.0.2_LXB22.99-24.2_cid14_CFC.xml.zip)
Thanks for all and any help.
I recommend flashing the stock images, that will almost certainly fix your issue with Wifi.
Hi, First off, I'm super rusty in the custom rom and kernell scene so explain things as easily as you can please.
Now, I have a moto x XT1053, the unlocked variant that they sold on the moto website that came with a net10 chip.
The thing is that I obviously unlocked the bootloader and installed the TWRP recovery. I have (almost) stock android and by that I mean stock with Xposed. I want to know if any of you guys could point me in the right direction, I mean, do I install the OTA update or do I return my phone to stock, and if it's the later, How do I return my phone to stock to do a proper OTA update?
Thanks in advance!
I have the same phone and was in pretty much your situation, including being rusty in flashing roms, kernels and such. I went with the OTA and am very glad I did. My subjective impression is that it's faster and at least as stable.
I thought my phone was close-to-stock, as I had removed some stuff (Xposed, notably) a while back to receive the 4.4.2 OTA. But the new Lollipop OTA wouldn't install, so I took the bull by the horns and flashed stock system.img that I got from Motorola's official firmware repository. I had to request access, and it took about 12 hours for that to come through.
After I downloaded the firmware zip file, I unpacked it and located the system.img file. Search on Google or this forum for the way to flash an img file to your phone, if you've forgotten (as I had). When I have time later today, I'll try to post a link to some clear instructions. I don't want to try to tell you from memory, as this is something I do about once or twice year since I got a Moto X (I tinkered a *whole* lot more when I had an HTC Sensation, but I've decided that if I want to keep my wife, I'd better stop playing with my mobile phone.)
I did this at the advice of a Motorola technician, who said the "most definitive way to return to unroot" was to flash stock system.img for 4.4.4. (I was part of last week's U.S. soak test, so Moto techs were handling questions from people like me who were wrestling with the OTA.)
I had worried that I might lose apps and data by flashing system.img, but I didn't lose a thing. I *did*, though, lose root, and I haven't re-rooted yet. Before I root, I'm waiting for the stock Lollipop 5.1 firmware to be made available on the Motorola repository so that I can have a backup of stock recovery.img.
Meanwhile, I'm enjoying Lollipop, which is like having a new phone.
varxx said:
I have the same phone and was in pretty much your situation, including being rusty in flashing roms, kernels and such. I went with the OTA and am very glad I did. My subjective impression is that it's faster and at least as stable.
I thought my phone was close-to-stock, as I had removed some stuff (Xposed, notably) a while back to receive the 4.4.2 OTA. But the new Lollipop OTA wouldn't install, so I took the bull by the horns and flashed stock system.img that I got from Motorola's official firmware repository. I had to request access, and it took about 12 hours for that to come through.
After I downloaded the firmware zip file, I unpacked it and located the system.img file. Search on Google or this forum for the way to flash an img file to your phone, if you've forgotten (as I had). When I have time later today, I'll try to post a link to some clear instructions. I don't want to try to tell you from memory, as this is something I do about once or twice year since I got a Moto X (I tinkered a *whole* lot more when I had an HTC Sensation, but I've decided that if I want to keep my wife, I'd better stop playing with my mobile phone.)
I did this at the advice of a Motorola technician, who said the "most definitive way to return to unroot" was to flash stock system.img for 4.4.4. (I was part of last week's U.S. soak test, so Moto techs were handling questions from people like me who were wrestling with the OTA.)
I had worried that I might lose apps and data by flashing system.img, but I didn't lose a thing. I *did*, though, lose root, and I haven't re-rooted yet. Before I root, I'm waiting for the stock Lollipop 5.1 firmware to be made available on the Motorola repository so that I can have a backup of stock recovery.img.
Meanwhile, I'm enjoying Lollipop, which is like having a new phone.
Click to expand...
Click to collapse
So, should I:
Delete GravityBox and Xposed
Install the .img file found within the zip for the Moto X dev Edition
Then I'll be able to install the OTA withouth losing data?
mundofeliz said:
So, should I:
Delete GravityBox and Xposed
Install the .img file found within the zip for the Moto X dev Edition
Then I'll be able to install the OTA withouth losing data?
Click to expand...
Click to collapse
The sequence you describe worked for me, assuming "deleting" GravityBox and Xposed is the preferred way of removing them. I can't remember.
The .img file to flash is system.img. You need to know how to get to fast boot/bootloader mode and perform the flash, of course.
If your experience is like mine, after receiving and installing the OTA, you'll have Lollipop without having lost any apps or data.
But you may want to wait for someone whose more up on this procedure to weigh in. When I updated, I proceeded as if I might lose all my apps and data, so I was pleasantly surprised.
BTW, I've since re-rooted, and I haven't had any problems. It's reassuring that the 5.1 ROM image is now available officially from Moto and elsewhere (info courtesy of dtg7: http://forum.xda-developers.com/showpost.php?p=61800775&postcount=11).
I'll do a Nandroid just in case. I'll do the steps above too, since all I've done is unlock bootloader, root and xposed I think this'll work for me. Kinda did only that originally for that reason but that was sooooo long ago. And also because the Moto X is such an amazing phone to begin with, I never saw the need to install other roms. Did you flash just the system.img, the recovery.img or both? I requested the firmware from moto and they approved but in the meantime I also downloaded the original too from filefactory, the exact same firmware I'm running (without modifications I mean.
mundofeliz said:
I'll do a Nandroid just in case. I'll do the steps above too, since all I've done is unlock bootloader, root and xposed I think this'll work for me. Kinda did only that originally for that reason but that was sooooo long ago. And also because the Moto X is such an amazing phone to begin with, I never saw the need to install other roms. Did you flash just the system.img, the recovery.img or both? I requested the firmware from moto and they approved but in the meantime I also downloaded the original too from filefactory, the exact same firmware I'm running (without modifications I mean.
Click to expand...
Click to collapse
IIRC, you'll need to do the Nandroid backup before you unroot, right?
I just flashed system.img. Won't that effectively restore the stock recovery? EDIT: According to the readme.txt file bundled in the stock ROM's zip file, recovery.img is flashed separately from system.img, so system.img will *not* restore the stock recovery.
I always feel safer running official firmware from Moto. For one thing, the labeling on the Moto dl site is very explicit, so you know exactly what you're getting.
I agree that the Moto X is a cool enough phone with a stock ROM that there's little need for custom ROMs. I was a flash-aholic when I had an HTC Sensation. But the Moto X pretty much has everything I need. Under KitKat, I did use XPosed to kill the Google search box, but otherwise I've been happy with the stock ROMs.
Oh, and I usually eventually run a custom recovery (TWRP) so I'll have more boot options. But I don't see that as essential now. I find I'm actually using my phone more than tweaking it, which is a change from previous phones.