[Solved] Return to stock... With Linux? - Moto X Q&A

I'm running a Moto X on VZW and am attempting to take the 4.4 update. As I run a Linux PC, the tools that are available (rsd lite and the toolkit) will not work for me.
When I attempt to flash back to stock via fastboot using system images, I get an error... "Data size exceeds download buffer." And the system.img flash fails. I've been able to flash the recovery and the boot.img, but just doing that causes the OTA install to fail.
If anyone has any ideas on this, they would be greatly appreciated.
Edit: m-fastboot binary fixed the issue.

Related

[Q] What is the best way to completely reflash the stock firmware?

I have an XT1053 with an unlocked bootloader. I've tried factory-data-resetting to solve my issue, but it is absolutely not working. I think there is something messed up with my system partition that isn't allowing my device to recognize the "audio" folder where ringtones and notification sounds are contained. I have tried reverting to stock with this toolkit: http://forum.xda-developers.com/moto-x/development/tool-moto-x-toolkit-v1-2-1-t2477132
I keep getting errors when trying to do so, and I'm thinking it may have to do with some OTAblockers I may have installed as system apps. Is there a command line method that I can use to manually flash the proper system .img over what I have now so that I can flash over that with the 4.4.2 OTA?
This thread should have all of the info you need to re-flash the stock system img
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515

Couple questions after unlocking bootloader (XT1096)

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!

[Q] 1092 Return to unrooted 5.0

It's been a while since I meddled with my phone and I fear some of the adb basics are failing me. I had rooted my XT1092 a while ago and changed the DPI via a build.prop edit. Now since my device was rooted, I could not update to the subsequent 5.0.2 and later 5.1 via an OTA. As the damned "Update device" message keeps popping up and annoying the bejeezus outta me, I decided to take the 5.0.2 update via a zip (which again failed, since it needed stock unrooted 5.0 (Status 7 error, if I remember correctly).
I managed to unroot my phone, but the edited build.prop still stops me from an OTA/zipped stock update. I'd rather not do a full wipe of my device to get back to stock 5.0 (LXE22.46-19). So my question is this: can I get back to complete stock unrooted 5.0 by merely flashing the system.img files via mfastboot? Or would that cause an issue? Or flash all the files from logo.bin to fsg.mbn and stop there without wiping data? Or any other suggestion to get to 5.1 on a once-rooted phone with an edited build.prop? TIA!
You can always flash the same version of Android without a data wipe. Just download a stock firmware for same or higher Android version, follow all steps for flashing in the flashfile.xml, just don't use the command fastboot erase userdata at last. And you must flash from system image, the OTA won't work.

I am unable to restore stock ROM, please help!

long story short ive completely messed up my phone in trying to restore stock
its basically stuck on the Botloader unlocked warning screen and i can boot into fastboot/bootloader, but not recovery
it was rooted and was on lollipop 5.1
its an xt1052 retail asia version moto x 2013
ive tried everything,
RSD Lite does not show my device
i have all the latest drivers and it shows up under device manager as "Mot single ADB interface"
i have ADB, fastboot and the lastest lollipop xml file zip
i have tried flashing the recovery, system img files individually, but i get an error when trying to flash system.img :it says cannot load it and cannot allocate memory or something
please help me, i have no idea what to do
vidhart said:
long story short ive completely messed up my phone in trying to restore stock
its basically stuck on the Botloader unlocked warning screen and i can boot into fastboot/bootloader, but not recovery
it was rooted and was on lollipop 5.1
its an xt1052 retail asia version moto x 2013
ive tried everything,
RSD Lite does not show my device
i have all the latest drivers and it shows up under device manager as "Mot single ADB interface"
i have ADB, fastboot and the lastest lollipop xml file zip
i have tried flashing the recovery, system img files individually, but i get an error when trying to flash system.img :it says cannot load it and cannot allocate memory or something
please help me, i have no idea what to do
Click to expand...
Click to collapse
are you able to get into recovery? if so, try wiping everything (cache/dalvik, data, internal storage), then flash the stock images. which instructions are you following?

Cannot update 7.1.1 OTA (help needed)

So I've received an OTA notification that will NOT go away for the last 3 days.
I'm currently on N6F27E build (June 5th build)
I download the update & it reboots to TWRP & then does nothing...
I've tried using twrp's sideload mode, but that too does nothing...
So I need to know where to get the latest stock recovery.img & how to flash it, so I can update everything.
Additional info:
- unlocked bootloader
- stock / no-root
To take an OTA you must be on stock, as you probably have guessed by now. Download a system image from Google, extract it, and inside will be a recovery image you can flash. An easier way to go here would be to simply download the latest system image and flash everything but the recovery image using fastboot commands.
Strephon Alkhalikoi said:
To take an OTA you must be on stock, as you probably have guessed by now. Download a system image from Google, extract it, and inside will be a recovery image you can flash. An easier way to go here would be to simply download the latest system image and flash everything but the recovery image using fastboot commands.
Click to expand...
Click to collapse
Thank you for the help.
I have had no issues flashing OTA's until last month...
Then something messed up. Idk...
Now they're forcing the OTA...
You're likely having issues because Google is offering Android 7.1.1 again via OTA and you're likely still on 7.0. Thus flashing a stock image via fastboot is likely a better bet than the OTA, even though doing so will wipe data.

Categories

Resources