So I took the 5.1 OTA from 4.4.4 on Retail GB.
Had issues so then decided to flash the FXZ retail gb 5.1 rom.
Used mfastboot for everything on mac but on the device I got "sp space is not enough" red line in the boot loader, however mfastboot on the mac in the terminal gave no errors. just the lines for downloading writing.
I continued with the flash process flashing everything and erasing everything.
Rebooted and it booted to the setup screen after an expected longer first boot. I then redid the process even rebooting the bootloader after flashing it and then flashing it again. Got same s"p..." red line on the device. But continued and it booted to the setup screen.
So what do i do?
stealtheye said:
So I took the 5.1 OTA from 4.4.4 on Retail GB.
Had issues so then decided to flash the FXZ retail gb 5.1 rom.
Used mfastboot for everything on mac but on the device I got "sp space is not enough" red line in the boot loader, however mfastboot on the mac in the terminal gave no errors. just the lines for downloading writing.
I continued with the flash process flashing everything and erasing everything.
Rebooted and it booted to the setup screen after an expected longer first boot. I then redid the process even rebooting the bootloader after flashing it and then flashing it again. Got same s"p..." red line on the device. But continued and it booted to the setup screen.
So what do i do?
Click to expand...
Click to collapse
In the forum or another of moto x have a post about the fix
.....i remember
Same here...
When I flashed 5.1 over 4.4.4 through fastboot I don't recall if this message was there. I'm almost sure it wasn't.
Then I flashed CM12.1, and now when I tried to flash stock 5.1 again, I get this "sp space is not enough" after flashing system.img. However it booted fine.
I don't know what's happening. I've tried erasing data and sd card, wiping system, and nothing...I keep getting this message.
Kustaa said:
When I flashed 5.1 over 4.4.4 through fastboot I don't recall if this message was there. I'm almost sure it wasn't.
Then I flashed CM12.1, and now when I tried to flash stock 5.1 again, I get this "sp space is not enough" after flashing system.img. However it booted fine.
I don't know what's happening. I've tried erasing data and sd card, wiping system, and nothing...I keep getting this message.
Click to expand...
Click to collapse
Yip very odd. But it continued to vaguely work. I just couldn't deal with the ROM overall. WiFi bugs, YouTube bugs, worse battery life... So I chucked the shocking attempt of an update lenovo have us and went back to good old trusty cm12.1. I mean CM12.1 is technically beta software but runs rings around the official stock 5.1. I say lenovo because it's not moto anymore. Lenovo have ruined moto. They want to limit moto software testing budget and restrain them and control them, I'm gonna say cheers. Can't believe the shocking quality from a former brilliant company. They were on their way up with Google. Now I'm never buying a moto or lenovo again. Nexus or iPhone.
Ok, here's the rundown - I have a VZW Moto X (XT1096). I previously ran mofo on it had flashed the 5.1 img files to it and so had 5.1 rooted, but with a locked bootloader. After learning that JCase had gotten sunshine to work on it I unlocked my boot loader. I then decided that because I was worried about having the a kind of mish-mash of systems on it, i.e., 5.0 bootloader (unlocked) with hacked and modded 5.1 system files flashed from mofo, that I wanted to start fresh. I then used the XT1096 flash to stock script and flashed back to 5.0 (there were a bunch of problems and bootloops and force closes, but I am happy to report I am now on a fully stock 5.0 with unlocked BL). Following being stock I have tried to take the OTA but have been unable to do so. When I try it OTA on my device it just sits at 0%. When I tried using MDM it gave me an error message that it failed to install the update - on the device it said getjar: unlocked.
So, now that I am on 5.0 with an unlocked bootloader I am not sure how to proceed with my priorities, Root, WiFi tethering and upgrading to 5.1. My questions are this:
(1) How can I upgrade to 5.1 or does my bootloader unlock preclude that?
(2) How best can I achieve root?
(3) Once I am rooted what do I need to do in order to enable wifi tethering?
Thank you so much!
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot and flash the stock system.img and recovery.img before doing the update.
3. I don't have experience with Verizon network. I use T-Mobile on this Verizon device and I just enable WiFi Hotspot. In the APN settings, in the "APN type" field, I add the value "dun". And set everything to IPv4.
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
Thank you for the reply - got the update to take and have gotten the device rooted properly.
Now I just need to enable wifi tether - anyone know what is done in the Mofo images that allows it - can i do the same here?
I am interested in this question as well. I am in the exact same boat as the OP, except I am still on a Mofo 5.1 img that is giving me issues. I'd like to flash back to stock and take the OTA. But wifi tether will be a must.
Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151
eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
I tried this but after I flash TWRP I can't boot to recovery. If I choose recovery from the bootloader it just turns off the phone (charging icon). If I send it adb reboot recovery I get error android "No Command."
Flashed it multiple times, tried mfastboot, no luck. Any ideas?
Edit: I feel dumb. I was using power button to try to select, it's volume up. Good to go.
GatorsUF said:
Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151
Click to expand...
Click to collapse
The other method (the one I used) was to install the Xtether xposed module for the 2013 Moto X - worked perfectly for me.
I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?
SargeStryker said:
I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?
Click to expand...
Click to collapse
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478
juliospinoza said:
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478
Click to expand...
Click to collapse
Thanks!
Hello!
I was trying to apply the Stagefright OTA on my XT1058, but I soft bricked it. Whenever a new update comes out, I prefer to flash stock image to avoid any unecessary issues that may arise from dirty flashing and not having the system requirements to apply the update without having problems. So that's what I did:
- I flashed the 5.1 stock image for my carrier (Vivo) using RSD and it worked fine, phone booted normally and etc.;
- I skipped the Google account setup and got the Stagefright OTA notification. Since I had already downloaded it before, I wanted to test it by sideloading it from Recovery. So I did it, I entered recovery mode and sideloaded the OTA. All went fine, no errors in the log. Rebooted phone. New bootanimation. Apps optimized;
- But I was getting 'gapps process has stopped' error and couldn't log into my Google Account, so I decided to reflash the stock image (I guess this was my error) using RSD;
- gpt partition flash fails;
- Phone stops booting, it just gets to the recovery menu or to the 'No command' screen;
- I tried flashing everything manually, doesn't work;
- I tried flashing gpt.bin from a Brazilian Retail firmware. It flashes without errors, but phone doesn't boot either;
Is there a way to recover from that? I have a TWRP backup from before I started all this process, but it looks like I can't restore it because my PC doesn't seem to recognize the sdcard when mounted.
Thanks in advance!
EDIT: managed to restore it using the steps from option 5 in Mark Venture's guide here. It was the only one that worked. BUT I had to flash gpt.bin and fsg.mbn from the OTA zip. Only then the phone booted. Then I took OTA normally and it installed without any hassle. So it looks like hash mismatches do not happen in this version of the firmware.
Okay, I haven't been able to update since LMY48I. Back then I was on stock recovery. Re-locking bootloader and all but still was not able to take OTA (always came up with dead android guy with "Error"). I'll skip the (probably) irrelevant stuff since then and give you the current situation:
Currently unlocked, rooted, with custom recovery. Still on LMY48I. I can't take OTAs obviously, and have tried flashing OTA updates manually with no luck and have tried flashing the entire Marshmallow image and that will not work either (sideload or flashing from internal storage in recovery). Sideload comes up with Closed error (device DOES show up in device list and I can do other things). Flashing from within recovery just says "Failed".
Please help me get to Marshamallow!
Edit: On Project Fi by the way.
Edit 2: Also, I've tried the flash-all script.
Now it says the device is corrupted when I boot up. I can still access recovery. Any help walking me through getting all of the correct firmware and latest build on would be much appreciated.
Thank you.
Edit: Looks like i'm good. I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
altvisionx said:
......./I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
Click to expand...
Click to collapse
Flashall.bat stops; only m-bootloader and m-radio are flash. Google's fault. You did the right thing by extracting the images and fasbiot flash them.
You cannot sideload the full factory image or flash from storage. Only fastboot
And just to clarify, you can't take an OTA (sideloading or otherwise) if your phone is rooted, have a custom recovery or a custom kernel (or any other modification to the system). The state of the bootloader (locked or unlocked) does not affect the ability to take an OTA update.
Hi,
I was on 6.0 on XT1095. Tried to root it. Screwed up by flashing something that didn't work. Now i am stuck on 'warning bootloader unlocked' screen. Previously when I was on 5.1 I restored my phone from bootloop by using official images from Moto and using their instructions. Now there are no 6.0 images. I guess trying to reflash the whole 5.1 ijmages would brick my phone. I tried flashing just the system image of 5.1. It didn't work.
I found this 6.0 stock ROM here on XDA http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3277874 . How do I flash this?
Please help. I'm on stock recovery. Previously I ran commands like 'fastboot flash system x.img' and so on when phone was in fastboot mode. How to flash this zip now.
Thanks in advance.
A bootloop is simple to get out of. Just press and hold the power and volume down keys to boot into recovery and go from there. If your phone isn't booting past the unlocked bootloader warning splash then you need to elaborate on WTF you flashed. Just saying "something that didn't work" isn't sufficient to make an accurate diagnosis.
To flash that stock ROM you posted a link to above would require you to fastboot flash a custom recovery first.
As for restoring a 5.1 image I don't understand why you'd think that would brick your device. You're formatting the entire device by going back to ANY stock image. Just because you are on 6.0 doesn't mean you have to restore a 6.0 stock image (that probably won't be available for some time).
sent from my moto x™