Related
I'm having issues flashing factory images for 5.1.0 LMY47D & LMY47E (tried both) from my ubuntu box. Every time I try these images, I see this:
Code:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
and then end up with:
Code:
sending 'system' (1736396 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Boot loader on "Device is UNLOCKED Status Code: 3" and I've updated fastboot to the best of my knowledge, using Android Studio SDK Manager, as well as ran apt-get update. Bootloader version is moto-apq8084-71.08. I did an md5sum on the .tgz files and confirmed I'm not getting a bad download on either. After extracting I removed the -w from
Code:
fastboot -w update image-shamu-LMY47D.zip
in the flash-all.sh file, really would rather not wipe, but if someone tells me there's a valid reason I need to, I'll do it. I do not have encryption turned off.
This leaves my phone in an unusable state due to the partial flash, so I'm about to FDR it, but was hoping someone could help first.
Have you tried flashing each image manually?
jfcooley said:
Have you tried flashing each image manually?
Click to expand...
Click to collapse
That was a good idea, just tried it. no dice:
Code:
****@Ubuntu-Media:~/Downloads/shamu-lmy47e$ fastboot flash system system.img
sending 'system' (1736380 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
I just read something about how I might need to use mFastboot made by motorola... trying that now
You have to unzip. Fastboot flashes IMG.
When you download the factory image you unzip, should leave you with 2 image files and another .zip. You have to unzip that as well. It contains the rest of the img you need to manually flash.
jfcooley said:
You have to unzip. Fastboot flashes IMG.
When you download the factory image you unzip, should leave you with 2 image files and another .zip. You have to unzip that as well. It contains the rest of the img you need to manually flash.
Click to expand...
Click to collapse
yeah, sorry realized that seconds after I posted... edited my original post, sorry for thread confusion.
So after a few other mistakes I'd rather not own up to, I figured out that yes, mFastBoot was the solution to my issue. I'm not sure why I can't find any other folks posting about needing it for 5.1 builds on the the N6, but I did. I never needed it before 5.1, but I'm assuming the system.img file has grown larger than the standard SDK fastboot supports. I'm wondering if this is only an issue when flashing from linux. Theoretically, it should not be though; this issue is based on the memory available on the device (tmo N6, btw).
For those that don't know, "mFastboot" aka Motorola Fastboot is a tweaked version of fastboot provided by Motorola. It will actually split up the image and flash it in pieces.
Here are Instruction for installing and using mFastBoot to flash a Moto G on linux, but the process is the same, except for the images obviously. You'll have to either modify the flash-all.sh file or do each of the images manually.
Hope this helps someone else... it would be really weird if I'm the only one that runs into this.
GoldPaintedLemons said:
So after a few other mistakes I'd rather not own up to, I figured out that yes, mFastBoot was the solution to my issue. I'm not sure why I can't find any other folks posting about needing it for 5.1 builds on the the N6, but I did. I never needed it before 5.1, but I'm assuming the system.img file has grown larger than the standard SDK fastboot supports. I'm wondering if this is only an issue when flashing from linux. Theoretically, it should not be though; this issue is based on the memory available on the device (tmo N6, btw).
For those that don't know, "mFastboot" aka Motorola Fastboot is a tweaked version of fastboot provided by Motorola. It will actually split up the image and flash it in pieces.
Here are Instruction for installing and using mFastBoot to flash a Moto G on linux, but the process is the same, except for the images obviously. You'll have to either modify the flash-all.sh file or do each of the images manually.
Hope this helps someone else... it would be really weird if I'm the only one that runs into this.
Click to expand...
Click to collapse
just fyi, fastboot works fine with all the factory images google puts online but you have to use the latest version. it's available as part of the Android sdk and is included with Android studio.
PhilDX said:
just fyi, fastboot works fine with all the factory images google puts online but you have to use the latest version. it's available as part of the Android sdk and is included with Android studio.
Click to expand...
Click to collapse
Thanks, but if you read my original post you'll see I did that and more. Not saying you're wrong, but unless someone can tell me specifically a step in that process I apparently missed, I think there might be exceptions to that rule.
GoldPaintedLemons said:
Thanks, but if you read my original post you'll see I did that and more. Not saying you're wrong, but unless someone can tell me specifically a step in that process I apparently missed, I think there might be exceptions to that rule.
Click to expand...
Click to collapse
guilty as charged
I see now that you're on Linux, I use a Windows box so that's probably the difference. glad to see you found a solution.
GoldPaintedLemons said:
Thanks, but if you read my original post you'll see I did that and more. Not saying you're wrong, but unless someone can tell me specifically a step in that process I apparently missed, I think there might be exceptions to that rule.
Click to expand...
Click to collapse
On Windows with virtually the exact same issue. I went back to 5.0.1 but the bootloader is stuck on the newer version and can not be modified. I do not use ADB manually anymore. I use toolkits these days and then try manually. Now I'm stuck on 5.0.1 and can not update the OS at all. I get some message when attempting to ADB-Sideload the 5.1m T-Mo OTA saying that "a file located at dev/block/msm.... Has been changed to R/W. Reflash and reboot to regain OTA privilege."
Only issue is I am on a LRX22C Factory Image with Stock recovery. Any help or questions will be welcomed.
PhilDX said:
guilty as charged
I see now that you're on Linux, I use a Windows box so that's probably the difference. glad to see you found a solution.
Click to expand...
Click to collapse
Google images flash perfectly fine in Linux with fastboot.
Sent from my Nexus 6 using XDA Free mobile app
Freshly_Snipes said:
On Windows with virtually the exact same issue. I went back to 5.0.1 but the bootloader is stuck on the newer version and can not be modified. I do not use ADB manually anymore. I use toolkits these days and then try manually. Now I'm stuck on 5.0.1 and can not update the OS at all. I get some message when attempting to ADB-Sideload the 5.1m T-Mo OTA saying that "a file located at dev/block/msm.... Has been changed to R/W. Reflash and reboot to regain OTA privilege."
Only issue is I am on a LRX22C Factory Image with Stock recovery. Any help or questions will be welcomed.
Click to expand...
Click to collapse
I'm not a T-Mobile guy but based on the posts I've come across, the radio in the M update is 95R. since you can't take the OTA now with the boot loader issue, one option may be to flash the D or E factory image to get back onto 5.1. either way I think you want the 95R radio included with D, not the 98R included with E. I have to believe the M update will be released as a factory image at some point or something newer will be released.
GoldPaintedLemons said:
So after a few other mistakes I'd rather not own up to, I figured out that yes, mFastBoot was the solution to my issue. I'm not sure why I can't find any other folks posting about needing it for 5.1 builds on the the N6, but I did. I never needed it before 5.1, but I'm assuming the system.img file has grown larger than the standard SDK fastboot supports. I'm wondering if this is only an issue when flashing from linux. Theoretically, it should not be though; this issue is based on the memory available on the device (tmo N6, btw).
For those that don't know, "mFastboot" aka Motorola Fastboot is a tweaked version of fastboot provided by Motorola. It will actually split up the image and flash it in pieces.
Here are Instruction for installing and using mFastBoot to flash a Moto G on linux, but the process is the same, except for the images obviously. You'll have to either modify the flash-all.sh file or do each of the images manually.
Hope this helps someone else... it would be really weird if I'm the only one that runs into this.
Click to expand...
Click to collapse
You're not alone. I spent over 11hrs trying to get one or the other to flash too using a Mac with OS v10.10.2 and had the exact same issues. Found an mfastboot and was able to flash the images separately (flash-all.sh still failed).
Glad we're both all set... Now to delete the Android SDK and Java files!
X
Nexus 6 via Tapatalk
Freshly_Snipes said:
On Windows with virtually the exact same issue. I went back to 5.0.1 but the bootloader is stuck on the newer version and can not be modified. I do not use ADB manually anymore. I use toolkits these days and then try manually. Now I'm stuck on 5.0.1 and can not update the OS at all. I get some message when attempting to ADB-Sideload the 5.1m T-Mo OTA saying that "a file located at dev/block/msm.... Has been changed to R/W. Reflash and reboot to regain OTA privilege."
Only issue is I am on a LRX22C Factory Image with Stock recovery. Any help or questions will be welcomed.
Click to expand...
Click to collapse
Have you tried using mFastboot (just google it the windows exe is easily found)? You'll need to use that and flash each .img separately.
THANK YOU
I've been working with this off and on for some time, and your post was immensely helpful.
Latest fastboot drivers, latest ADB (truly the latest, not just apt-get-whatever). Same issue - system.img would not flash. Not with a script, not standalone, not in the zip file, nothing. What I see (almost constantly) is a buffer issue where the actual size of system.img is throwing a significant error with fastboot drivers. mFastboot (as you provided) on the other hand, utilizes a component called "sparse-flash", which appears to break large files into smaller (256mb) chunks that for whatever reason my N6 preferred. No issues with flashing after that, but again it must be done individually (system, boot, radio, etc.) - never as a zip with "-w update".
I find it curious that so few people have this issue (others can use the "normal" fastboot with large system files and no issue occurs). Those who do run into this problem seem to know their way around a terminal, so it makes me wonder what the underlying difference between us is.
For the record, I was on a machine running Mint 17.2, which is essentially Ubuntu 14.04.
Just really wanted to say thank you and hopefully promote the thread a bit to help others. Especially as many of us are flashing to bone stock momentarily to properly activate Project Fi.
@caain,
A couple of points/questions:
1) You mention having the latest fastboot "drivers". I'm not sure what you are referring to, but I've never heard of such a thing on Linux.
2) Where did you get ADB and fastboot from? Did you download the latest Android SDK?
2a) The point here, is that Google updated fastboot in November of last year to enable flashing the very large system.img from Lollipop. You can only get this necessary version of (if your are running Linux) fastboot via the Android SDK.... And without it, you can not successfully flash a Lollipop system.img.
cam30era said:
@caain,
A couple of points/questions:
1) You mention having the latest fastboot "drivers". I'm not sure what you are referring to, but I've never heard of such a thing on Linux.
2) Where did you get ADB and fastboot from? Did you download the latest Android SDK?
2a) The point here, is that Google updated fastboot in November of last year to enable flashing the very large system.img from Lollipop. You can only get this necessary version of fastboot via the Android SDK.... And without it, you can not successfully flash a Lollipop system.img.
Click to expand...
Click to collapse
You can flash the system image manually with fastboot. Can't fastboot flash the flash-all.bat without SDK 23+ platform tools. System image will fail. The 15 second adb/fastboot is not updated to achieve this. Not sure about Linux but if have latest SDK updated it will do the flash-all.bat.
none
I flashed M just to check it out, but prior to doing that I grabbed the SDK that had very recently updated to include the 6.0 M files, so I updated the 6.0 SDK prior to trying M, and when I went back I had zero issues with the flash.bat The only issue I had which was more of a pain than a problem is that flashing the factory image it unrooted the phone so I had to completely set up the phone all over again.
No more M for me until it's released because in the preview 3 not every component is functional, why they would do that I have no idea, so after learning that M wasn't complete I abandoned it. Hope this helps if you want to go back
cam30era said:
@caain,
A couple of points/questions:
1) You mention having the latest fastboot "drivers". I'm not sure what you are referring to, but I've never heard of such a thing on Linux.
2) Where did you get ADB and fastboot from? Did you download the latest Android SDK?
2a) The point here, is that Google updated fastboot in November of last year to enable flashing the very large system.img from Lollipop. You can only get this necessary version of (if your are running Linux) fastboot via the Android SDK.... And without it, you can not successfully flash a Lollipop system.img.
Click to expand...
Click to collapse
I suppose I use the word "drivers" a bit too flippantly, as you are correct and there is most certainly not a fastboot "driver" for linux. Perhaps the issue I was running into is that I was merely installing ABD and fastboot standalone, without including the entire Android SDK. In which case I ought to feel quite foolish!
Thank you for the clarification regarding the patch from November. I've no need for fastboot in the immediate future, but will certainly make sure install the SDK as a whole rather than pulling tools from other repositories in the future.
caain said:
I've no need for fastboot in the immediate future, but will certainly make sure install the SDK as a whole rather than pulling tools from other repositories in the future.
Click to expand...
Click to collapse
That's a very good idea. I would suggest doing this soon, so it's set up and ready to go when you need it.
I'm assuming that since I've rooted my Pure Edition that once the official 5.1 OTA comes it will fail to install just like 5.0-5.02 on my N7 did. I'm wondering how I can get back to unrooted without wiping the phone out (if that's possible). I can't seem to find the factory 5.0 image at the Motorola site so right now I'm assuming I'll have to install the 4.4..4 image and then let the OTA's roll in?
When I ran into this on my N7 other than rooting the only system installed app I had added in was better battery stats and removing root and getting rid of (at least I think I got rid of it) BBS the OTA failed still and I had to just flash the system.img from the factory image. On my XT1095 I only have SuperSU installed. I never installed BBS or any other new apps as system apps so maybe telling SuperSU to unroot and clean up will work?
Maybe I'm wrong, but I was under the impression you could still receive the OTA with root as long as you were on stock recovery, you would just lose root access in the process. I could be way off, though. I have always had TWRP on my rooted phones. I am pretty confident that you cannot switch back to stock recovery from TWRP without wiping. You can always use Helium Pro to back everything up. Unlike TiBu, it does not require root. Or you could just wait on someone to release a .zip of the OTA and flash it manually.
Paddington said:
Maybe I'm wrong, but I was under the impression you could still receive the OTA with root as long as you were on stock recovery, you would just lose root access in the process. I could be way off, though. I have always had TWRP on my rooted phones. I am pretty confident that you cannot switch back to stock recovery from TWRP without wiping. You can always use Helium Pro to back everything up. Unlike TiBu, it does not require root. Or you could just wait on someone to release a .zip of the OTA and flash it manually.
Click to expand...
Click to collapse
It used to be that way before 5.0. Something changed in 5.0+ and now if certain parts of the file system are off at all from stock, OTA will fail. That's why I mentioned the example of my Nexus 7 failing the update from 5.0 to 5.02. I don't know if Motorola is keeping the same kinds of checks as Nexus OTA's though. I do still have the stock recovery. If I need TWRP for something I just temporarily boot it with fastboot instead.
Any luck with this? I too would like to unroot. Still stock recovery.
flyinion said:
I can't seem to find the factory 5.0 image at the Motorola site
Click to expand...
Click to collapse
Here you go:
http://www.graffixnyc.com/motox.php
flyinion said:
so right now I'm assuming I'll have to install the 4.4..4 image and then let the OTA's roll in?:cyclops:
Click to expand...
Click to collapse
No, 4.4.4 won't boot with the 5.0 boot.img. And NEVER attempt to downgrade the bootloader (motoboot.img) or partition table (gpt.bin) of a Motorola Moto X. These are NOT Nexus devices.
Thanks very much! So...in an abundance of caution, I should be able to flash boot.img and that will get rid of root? Or system.img too? And neither of those affect my data? Edit: I am rooted on 22.21.11 XT1095 with stock recovery
Hmm. Not available on that site anymore but found it at http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
Mnemoch said:
Thanks very much! So...in an abundance of caution, I should be able to flash boot.img and that will get rid of root? Or system.img too? And neither of those affect my data? Edit: I am rooted on 22.21.11 XT1095 with stock recovery
Click to expand...
Click to collapse
Just flash 5.0 system.img that is all you need unless you flashed a custom kernel
Personally I would not take the OTA - I would use Motorola Device Manager to update. If you are rooted you can uninstall MotorolaOTA and then when people report the OTA is being pushed, flash system back to stock and then let MDM update you - you will have a copy of the 5.1 fxz on your computer then.
Thanks for the advice, I will check out MDM and yes, waiting for the OTA to be published officially.
That other link I posted for the full image file was corrupt, but I found http://graffixnyc.com/development/motox2014/lollipop/22.21.11/ which has system.img available. But this is huge! Does it seem correct to you by any chance? Should be able to flash without losing my data?
JulesJam said:
Just flash 5.0 system.img that is all you need unless you flashed a custom kernel
Personally I would not take the OTA - I would use Motorola Device Manager to update. If you are rooted you can uninstall MotorolaOTA and then when people report the OTA is being pushed, flash system back to stock and then let MDM update you - you will have a copy of the 5.1 fxz on your computer then.
Click to expand...
Click to collapse
Thanks guys, I did find the image and had downloaded it from that link a while back. I also picked up the mfastboot tool, but I'm not sure how to use it to flash a system.img. That download has a bunch of system.img_sparsechunk.n files where .n is a number from 0-7 but there's no "base" system.img file. Do I just tell it to flash file 0 and it will pick up the rest of them automatically?
flyinion said:
Thanks guys, I did find the image and had downloaded it from that link a while back. I also picked up the mfastboot tool, but I'm not sure how to use it to flash a system.img. That download has a bunch of system.img_sparsechunk.n files where .n is a number from 0-7 but there's no "base" system.img file. Do I just tell it to flash file 0 and it will pick up the rest of them automatically?
Click to expand...
Click to collapse
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
JulesJam said:
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
Click to expand...
Click to collapse
Ah ok, I thought I needed mfastboot from what I was able to read around here. So the standard fastboot that comes with the android sdk can be used on the chunks?
Actually I think maybe I understand now. I read something a little bit ago about the difference between fastboot and mfastboot (Motorola Fastboot) and that the latter was created due to a file size limitation with the original fastboot. It didn't go into more detail than that. My assumption instantly was motorola was splitting the system image up into chunks and created that new fastboot to handle that. Seems it's the other way around? Google's fastboot can handle chunks and Moto's can handle a single image that is larger than what the standard fastboot can so they don't have to split it up in the first place?
Which download has chunks, the zip that we can't download any more or the system.img that I found? Should I try to extract it?
flyinion said:
Actually I think maybe I understand now. I read something a little bit ago about the difference between fastboot and mfastboot (Motorola Fastboot) and that the latter was created due to a file size limitation with the original fastboot. It didn't go into more detail than that. My assumption instantly was motorola was splitting the system image up into chunks and created that new fastboot to handle that. Seems it's the other way around? Google's fastboot can handle chunks and Moto's can handle a single image that is larger than what the standard fastboot can so they don't have to split it up in the first place?
Click to expand...
Click to collapse
Mnemoch said:
Which download has chunks, the zip that we can't download any more or the system.img that I found? Should I try to extract it?
Click to expand...
Click to collapse
Oh, the one that doesn't work anymore. I downloaded it a few weeks ago. Not sure when it got taken offline since the link is there, but yeah I see the download doesn't work any longer. If you have just a single system.img and not a bunch of system.img_sparsechunk.n files then you have a different image.
Anyone unrooted since the OTA came out?
JulesJam said:
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
Click to expand...
Click to collapse
Anyone use this process to unroot stock 22.21.11?
And if so, did you get and take the 5.1 OTA or did you sideload it?
Thanks
eKeith said:
Anyone use this process to unroot stock 22.21.11?
And if so, did you get and take the 5.1 OTA or did you sideload it?
Thanks
Click to expand...
Click to collapse
Unrooting using this method does work!
Maybe unrelated, but in my confusion as to what's going on, is it at all possible to flash the 5.1 ota update over a custom rom? I'm currently on resurrection remix that's running on 5.1.1, but I really want to go back to stock. Thanks in advance.
dcdrew713 said:
Maybe unrelated, but in my confusion as to what's going on, is it at all possible to flash the 5.1 ota update over a custom rom? I'm currently on resurrection remix that's running on 5.1.1, but I really want to go back to stock. Thanks in advance.
Click to expand...
Click to collapse
Not possible. You have to flash the stock rom first, then take the ota.
Sent from my XT1095 using Tapatalk
Any idea what stock rom to use? 5.0? Sorry, I'm not the best with this stuff anymore, haha.
Hello,
This is a short (hopefully) guide on how to downgrade your Moto X 2013 from Android 5.1 to 4.4.4 (and lower).
The procedure is fairly simple and takes about 10-15 minutes, once you get the files you need.It does however needs some technical understanding of how to use fastboot, command prompt and eventually unlocking your bootloader.Fairly strong reading skills recommended.
WIth that said, make sure you read thorough and even few times before you take any actions.
This method has now been proven to be working by multiple people, on many different versions of Moto X 2013, including GPE
Disclaimer
Although this procedure has been tested by me and some friends numerous times, it still has some risk involved.You MUST be aware of the potential risks of modifying your phone software and performing actions that may lead to complete defunct of your device.
As you may expect I will not take any responsibility or be accountable for any damage or loss you may incur by following this guide.
Performing a system downgrade WILL void your warranty and it is NOT supported by Motorola/Lenovo or their service network.
I also recommend you read This post by KidJoe about the potential risks that downgrade might involve.
This guide has came up being needed as many people were afraid to downgrade after reading the post of KidJoe and I don't blame them, it is possible something to go wrong and you end up with non-working device.
HOWEVER, this has been tested on more than 10 separate Moto X 2013 and more than 12 times on my own device, which makes me to believe that it's generally safe.
Prerequisites
You need your bootloader unlocked.Motorola and their bootloader does NOT support downgrading and it will spit errors in fastboot.
WHEN YOU UNLOCK YOUR BOOTLOADER ALL YOUR PERSONAL DATA ON YOUR DEVICE WILL BE LOST.MAKE SURE YOU BACKUP YOUR FILES AND THEN PROCEED.
You can find how to unlock your bootloader HERE or just use the search here in the forums, plenty of info on that matter.
If you cannot or don't want to unlock your bootloader, then you CANNOT downgrade.
Files Needed
For this tutorial we`ll do downgrade from 5.1 to 4.4.4.This is the safest downgrade and it will be successful if you follow all the steps w/o any skipping.
The Android image used is for XT1052, but if you got different model, you can find the image for your own model and use that instead.
1.First you need a signed image of Android 4.4.4 for Moto X 2013.You can find one Filefactory or RetailEU here <=> RetailGB here <=> RetailDE here
If you want to download the image faster, use the Yandex-hosted images, FileFactory is slow.
2.Motorola Device Drivers: You can find them Here
3.Motorola Fastboot and generic adb/fastboot tools package: You can find it attached to this post or click Here
Flashing your device
0.Charge your device's battery to at least 35%.
1.Extract the archive with the signed images somewhere (in this case I`ll use C:\temp , but you can use any drive or directory if you so desire).
2.Extract the android-tools archive in the same directory.You should have boot.img, recovery.img, system.img and mfastboot in same directory.
3.Reboot your device in bootloader (Power your device off -> Hold Volume Down and Press Power button -> then release).
!!THIS WILL DELETE YOUR USER FILES EVEN IF YOU HAVE YOUR BOOTLOADER ALREADY UNLOCKED!!!
4.Open a command prompt and navigate to C:\temp and execute the following commands:
Code:
mfastboot erase cache
mfastboot erase userdata
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot erase userdata
mfastboot reboot
DO NOT skip erasing the userdata, doing so , you'll most likely end up with soft brick.Just don't do it.
Result
Congratz, now you have successfully downgraded your device to Android 4.4.4
The device will take some time the first boot to create dalvik cache and some other stuff, but it should not take more than 5 minutes.
When your device boots, it will ask you at some point to downgrade the motorola services bla bla, agree to that, your device will reboot and it will tell you that the downgrade was successful.I did this more than 10 times, seems to be totally safe.
Any feedback will be appreciated, you may ask questions, but don't expect me to answer to every single one.
If I missed something, I'll add up/fix as soon as I can.
FAQ
What if I want to downgrade to Android 4.4.2 / 4.3 / 4.2.2 ?
This is possible, the procedure is the same as listed above.You just have to know that if you do such downgrade, you should never update via OTA update, at any cost.This will corrupt the bootloader of your device and you won't be able to restore it.If you downgrade to anything below 4.4.4 and you want at some point to upgrade, you should do it ONLY by official signed image and NOT OTA.
You've been warned.
I can't find the exact same firmware that my device runs, eg. AsiaRetail.Is it possible to use firmware image from a different region/operator?
While it's recommended to use your exact firmware image, it is not necessary. You can use an image from other region, but you should follow some simple rule. Try to stick to the same phone model, eg XT1052 firmware.
I updated via OTA but I've recently rooted and installed a custom rom. Is it necessary to go back to stock 5.1 to downgrade?
No need, as long as your custom rom/kernel didn't mess with the fs of the partitions.
Why is this flashing procedure cut down, omg there are other commands that I've read in other guides and they say that I must flash modem, fsg, delete some magical modem states, why you didn't include these?!?
While it is true that other guides suggest you flash modem, fsg and some other things, these are mainly driven from the Motorola's own procedure xml file, flashing these is not necessary at all, this is used to repair eventual errors in these parts, but usually there is no problem there at all.
Another thing is that these parts are cross-compatible and leaving them as they are is perfectly fine.
How do I go back to 5.1 stock?
1.Do NOT update by OTA, just to be on the safe side.
2. Use the same procedure as described, but with image of 5.1 instead.
How do I disable the OTA notifications?
1. If you're rooted, then just delete or revoke permissions of /system/priv-app/3c_ota.apk
2. If you're not rooted, then don't install the Motorola Update Services from the Play Store. If you already updated them, then just uninstall the update and that's all.
I'm getting "Not enough space" errors, when I try to flash the system.img.I'm using mfastboot, but still the same problem?!?
Use this and it will work:
mfastboot flash system system.img -P
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
legend.in.boxers said:
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
Click to expand...
Click to collapse
Having custom recovery doesn't affect anything. This process will flash the stock recovery.
You don't need to enter any mode in the list, just leave the phone in the bootloader menu.
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
SanD-82 said:
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
Click to expand...
Click to collapse
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
I also have a problem with the optimising apps bug every time I reboot. Going to downgrade today. Hopefully everything will go well
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
SanD-82 said:
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
Click to expand...
Click to collapse
That's not the case either, it was set to never keep it on during sleep and scaning always available was not allowed.The wifi just wont go off durring sleep and that's it.Tried all possible settings to no avail.Actually wifi was the 2nd highest battery consumer in the stats after the screen.This problem does not exist in 4.4.4.
I see...
It's actually hard to see how in 2015, Android keeps having these deal breaker issues...
I somehow feel that the best version of my xt1058 was when it was at 4.2.2... After the subsequent updates, bugs started to appear, and on 5.1 i got the first big issue...
Sent from my XT1058
Works!
Successfully downgraded. Thank you so much!
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
SanD-82 said:
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
Click to expand...
Click to collapse
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
IS Android 4.4.2 or 4.2.2 files avalable for indian moto x (xt1052 asian retail)
liveroy said:
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
Click to expand...
Click to collapse
WHere can i find those files??
visheshjotshi said:
WHere can i find those files??
Click to expand...
Click to collapse
Check the first post, the File Factory link, you can find tons of images there, the moto x 2013 is codenamed Ghost, if there is no model listed.
Good Luck.
Cant find files
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
visheshjotshi said:
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
Click to expand...
Click to collapse
Try searching 4pda.
Also, you don't need exactly your original firmware to begin with, it's recommended, but not necessary.
Thank you for this information. I dont have the wifi bug. But i have the mobile data bug. (Even turning it off it still continues to sap battery)
Sent from my XT1052 using XDA Free mobile app
I was looking for a post like this becouse my WiFi doesn't work on XT1058 5.1... i thought was a Lollipop related issue so wanted to downgrade to 4.4.4 and see if the problem really was related to android version, but it isn't. I downgraded successfully from 5.1 to 4.4.4 with your tutorial, but the WiFi problem persist. Now i know i'm really screwed up becouse i tried i believe everything possible... airplane mode, factory reset, cache wipe, full wipe, custom rom, custom kernel, android 5.1, android 4.4.4, different AP's and routers, delete supplicant conf... So i don't know what to do. Te specific problem is that WiFi can see available networks, but randomly some of them disappear and others show up, and when i try to connect por ex to my home network, it says "connecting" and then "saved", with all networks happens the same. Does anyone has a clue? BTW, thanks for your post!
Download the archive from this link https://app.box.com/s/idnxxhunecvtxf1mbqve0bpooyogvxng
unzip it on your device and copy the files to /persist.You need root to do that. Set the permissions to rw-r-r--- and rw-rw---- for the .bt_nv.bin
Reboot and see if something changes.
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Motorola Z2 Force users! Your issues will be resolved!
Reasons for using this method:
If you haphazardly flashed a ROM, and now can't boot.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock.
You then can update.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:
Motorola Firmware Team for the zips
Great, So you've read why you might have borked your phone!
Now, let's get it fixed! Below is the link to the only flashall bat file I currently have. This is a simple process to do. There are some requirements though.
Requirements:
Correct drivers (ADB and fastboot is included in the utilities zip if you don't have minimal adb and fastboot installed, or don't have the SDK.)
Over 4GB of RAM.
How to fix your phone:
Download the Utilities zip
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
This process can take up to 10-15 minutes depending on USB connection and your PC
Disclaimer: I did not personally test the zips below besides the Sprint and T-Mobile ones. These are the official Firmware links from the Motorola Firmware Team. My only contribution is this thread and the utilities zip.
Disclaimer 2: it is never suggested to flash a zip not intended for your device/major patch version. If you're on Oreo, DO NOT FLASH NOUGAT. (I flashed T-Mobile to my Sprint phone for testing purposes and so I can tell you what it does. I lost all sim functionality and had to do some wonky stuff to get my phone back to working shape... Word of advise: don't do it.)
Disclaimer 3: if you have minimal adb and fastboot or the Android SDK, please be sure you update to the latest fastboot. The exe files included in the zip are for those who don't have a development environment set up.
Downloads:
Flash All Utilities
AT&T Oreo Flash All
Sprint Oreo Flash All
T-Mobile Flash All (Not official download link, but official files, See here)
USC (check version) Flash All
Verizon Flash All
NOTE: yes, it's in the Z2 play folder. Motorola Firmware Team did not make another folder for our device. Check the file name. It has "Nash" specifying the Z2 force. If you ask why it's in the Play folder, I will not respond.
If you have any other official links, I will add to second post and give proper credits to who found the zip. Only perm links like the AFH ones I posted.
Uzephi said:
First: The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA. This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
This zip will fix that and put you back to stock on the "August" security patch (September update). You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits: Motorola Firmware Team for the zips
Me for modifying the zip to fix oem.img issue on B partitions and turning the xml into a simple flash all.bat
Note: I am mobile and I will clean up the OP and second post when I get time @ home
Click to expand...
Click to collapse
I was going to add yours in but kinda got busy
Thanks for this! I flashed a modified boot.img for root to get my phone unlocked, and flashed the stock kernel back, but I couldn't update to the September patch. After flashing this, updates are working fine. A bit of a lifesaver!
full circle...
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
esuormai said:
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
Click to expand...
Click to collapse
I don't take donations, just pay it forward! Thanks for the offer though.
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
WeUseLord- said:
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
Click to expand...
Click to collapse
Added in requirements, thank you for verifying that.
Uzephi said:
Added in requirements, thank you for verifying that.
Click to expand...
Click to collapse
Okay thanks OP
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
cooleoboom5 said:
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
Click to expand...
Click to collapse
That is a "permanent" flag that triggers when you flash something unsigned and not from Motorola. I.E. custom boot image for root. Reason it's in quotes is because we don't know how to return it back or if we even can.
moto z2 force
WeUseLord- said:
Okay thanks OP
Click to expand...
Click to collapse
where do you download the bat file from
irule1977 said:
where do you download the bat file from
Click to expand...
Click to collapse
It's in the zip
So Sprint Z2 can't get GSM unlocked by flashing ROMs from other carriers? Any idea how it can be unlocked?
How to get back to software status official in bootloader menu? I did managed to do it with T-Mobile version but cant get that from this one.
Uzephi said:
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Sprint Motorola Z2 force users! Your issues will be resolved!
First: Our phone differences
The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA.
This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
Reasons for using this method:
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock on the "August" security patch (September update).
You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:Motorola Firmware Team for the zips
Versions currently available:
NCXS26.122-59-8-6
NCX26.122-59-8
NCX26.122-51
Versions on OTA but no firmware files available:
NCXS26.122-59-8-9
Click to expand...
Click to collapse
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
robdevil said:
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
Click to expand...
Click to collapse
I would only release something I can test. I don't have TMobile service, so I won't be releasing TMobile only firmware. There is a thread by joemossjr for TMobile flashall.
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
hackenggr said:
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
Click to expand...
Click to collapse
My Sprint model has the -03 identifier. You should be safe if the bootloader is unlocked. Needs that to flash this
I wanted the oreo update, but it wasn't coming OTA for some reason. I rooted my phone a year ago when I first got it and had some issues and flashed it back to stock fairly quickly.
So I figured that I could flash the oreo update no big deal. The commands all looked familiar for the first time.
Well I flashed the wrong version. I have tried custom roms such as the pixle but non of them can mouth /oem/ or /vendor.
So do I just need to give up on it?
I have been trying for 5-6 days many hours of frustration.
I'm not developer, but it seems Like there should be a way to get the stock rom back in the box.
I just need to know if its garbage now or not.
Thanks
Did you try to fastboot the device back to stock? There are several guides out there. Unless you cant get into the basic ADB mode, this should be able to be done.
This is the guide I used. Just make you get the Sanders version from stockrom.net
jordanhaughee said:
Did you try to fastboot the device back to stock? There are several guides out there. Unless you cant get into the basic ADB mode, this should be able to be done.
This is the guide I used. Just make you get the Sanders version from stockrom.net
Click to expand...
Click to collapse
Yes, I have tried that. the oem.img always fails and the sparce chunk.0 always fails.
So it doesn't take.
So I am going to answer myself. After much searching and reading.
Due to the phone not allowing downgraded stock firmware ....
It seems that I am stuck.
If Motorola comes out with a new firmware than I can flash that but until than its a brick.
That seem about right?
So With the help of a developer on here, I was able to force oem using a shell command. I than was able to load oreo on and it is running just fine.
Hyde1234 said:
So With the help of a developer on here, I was able to force oem using a shell command. I than was able to load oreo on and it is running just fine.
Click to expand...
Click to collapse
Can you help me? I think I did the same as you..
I tried to install the stock ROM and appears "(bootloader) Validating 'gpt.default.xml' (bootloader) Security version downgrade".
Then I tried to update the OTA through ADB and received this message "This package expects the value "sander" for "ro.product.name"..."