5.0.1 Build LRX22C OTA to 5.1 Build LMY47M "T-Mobile"
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
Your bootloader MUST be unlocked already, if not, these instructions do not apply to you so don't do them, it won't work.
These are the steps I did that worked for me. No guarantees that it will work for you, or if it wipes or bricks your phone.
Basically, you're downgrading your phone to 5.0.1 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None. Set OEM Unlock in Developer Options on just in case.
2. Reboot phone to bootloader (adb reboot-bootloader), or Power+Vol Down while the phone is off.
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
Green Android with Red Exclamation mark is stock recovery. Press Power + Vol Up to activate the menus. I sometimes have to press them a lot to get it to show.
If your PC does not recognize ADB Sideload mode, unplug your phone and plug it back in, it should work. If not check Device Manager and reload ADB drivers.
nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
Click to expand...
Click to collapse
Thank You! THANK YOU! THANK YOU! lol thanks for sharing
How do i install this again what are the requirements
Looks like I'm reverting back to 5.01 to get this one.
Just installed it. Thank you!
iGoogleNexus said:
Just installed it. Thank you!
Click to expand...
Click to collapse
Good job, mine is still optimizing apps, super slow, 160 of 202.
someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???
simms22 said:
someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???
Click to expand...
Click to collapse
Radio is 95R, it's the same in the D system image.
nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
You must be bootloader unlocked already, if not, these instructions do not apply to you so don't do them.
Basically, you're downgrading your phone to 5.01 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None.
2. Reboot phone to bootloader (adb reboot-bootloader)
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
FYI, Radio is 95R, the E (Verizon build) is 98R
Click to expand...
Click to collapse
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?
the.emilio said:
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?
Click to expand...
Click to collapse
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.
nxt said:
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.
Click to expand...
Click to collapse
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol
Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!
I just finish side loading it......
mr pnut said:
I just finish side loading it......
Click to expand...
Click to collapse
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
the.emilio said:
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol
Click to expand...
Click to collapse
Same not sure. Ended flashimg all the img, 47E
jay661972 said:
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
Same not sure. Ended flashimg all the img, 47E
Click to expand...
Click to collapse
Yes sir.......
Sorry too far OT delete
kaos2569 said:
Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!
Click to expand...
Click to collapse
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?
LGSilva said:
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?
Click to expand...
Click to collapse
What if u already stuch with 5.1 47E bootloader, flash the one from op but when about tonto recovery, got the same woth the other guy, android with the spinning thing and not exclamation.
Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)
lainemac said:
Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)
Click to expand...
Click to collapse
98R and E build is for Verizon phones. The D builds are for all other non Verizon nexus 6 phones. I went back to 95R because 98R was giving me calling issues.
Related
Edit: The attached zip in post #2 in a minor update the original 4.4.4 release for XT1060 FXZ. Below are the instructions. This is NOT the Full 4.4.4 OTA update.
Instructions to flash
1.) Move zip file from /cache folder to /sdcard folder if you received OTA (Zip file in 2nd post if you do not have it.)
2.) To be safe, disable xposed framework (if you have it running).
3.) Reboot into bootloader
4.) Use mfastboot to flash stock recovery (if not running it)
mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
5.) Boot into recovery from bootloader
6.) Hold Power + Up Button to get recovery menu.
7.) Flash zip file from sdcard.
8.) When complete reboot, then boot into bootloader.
9.) Use mfastboot to flash custom recovery (aka twrp)
mfastboot flash recovery <twrp file name>.img
Click to expand...
Click to collapse
10.) Reboot and enable xposed framework.
11.) Done.
Another suggestion by @KidJoe
After mfastboot flash recovery <recoveryyouwant>.img its long been suggested to do a mfastboot reboot-bootloader then go into recovery, before doing anything else.
We've seen many instances where skipping the reboot-bootloader and enter recovery giving symptoms like the flash of recovery didn't work... (i.e. "old" recovery was still on the phone)
Click to expand...
Click to collapse
just received the update as well but haven't installed
Zip attached.
Maintenance update.
Maintenance update. Does not break root.
911 bug fix, as mentioned in three other threads
WhammyDroid said:
Zip attached.
Click to expand...
Click to collapse
You flash this through RSD lite? I couldn't flash it through my TWRP recovery on my Moto X Developer Edition.
Cindy
cindylike24 said:
You flash this through RSD lite? I couldn't flash it through my TWRP recovery on my Moto X Developer Edition.
Cindy
Click to expand...
Click to collapse
I believe you have to have stock recovery to flash.
dannyxiii said:
I believe you have to have stock recovery to flash.
Click to expand...
Click to collapse
Well then, I'll have to put this on my to do list for when I get home tonight. No biggie.
Cindy
It's far, far more than a 911 bug fix ... there's 2500 lines in the updater script, touching dozens (if not hundreds) of app and files.
Does this require removal of root/xposed or just needs stock recovery?
TheDave1022 said:
Does this require removal of root/xposed or just needs stock recovery?
Click to expand...
Click to collapse
I generally disable xposed and flash stock recovery but root should be fine. Anyone have a copy of the stock recovery? I'm on the dev edition. OTA's are so infrequent on this device that I forget where I stash the stock recovery all the time.
I got the notification last night, and hid it this morning (turned off notifications for the Moto Updater app). I am on an XT1060 Moto Maker, with an unlocked bootloader. In the past I've flashed /system and /recovery to update (from 4.4.2 to 4.4.4) with the OTA, then reflashed TWRP and flashed SuperSU from there. Do I need to do all that, or just stock recovery?
I do have Xposed, Cerberus and App Ops installed as System Apps, I believe.
I found the recovery for myself at the following link:
http://motofirmware.center/files/file/47-vzw_xt1060_444-kxa2112-l126_cfc_1ffxmlzip/
Might help someone else...You can verify your build by going to About phone. I had Build number KXA21.12-L1.26
Maverick0984 said:
I found the recovery for myself at the following link:
http://motofirmware.center/files/file/47-vzw_xt1060_444-kxa2112-l126_cfc_1ffxmlzip/
Might help someone else...You can verify your build by going to About phone. I had Build number KXA21.12-L1.26
Click to expand...
Click to collapse
That's the exact model number on my phone! Thank you for putting this link up there!!
Cindy
For some reason, I cannot use either mfastboot or fastboot to flash the stock recovery. When flashing it, I get the android icon with the red triangle.
Its been a while since I have had to flash back to stock recovery. What am I missing? I have the stock recoverystored for the last official FXZ.
when android with red triangle appears, press vol up for 3 seconds and you will be given option to flash from sd card.
Well, this has locked me out of re-flashing custom recovery, which - of course - means there's nothing that can be done beyond that.
Any version of TWRP up to, and including, the latest flashes without error ... but when you boot, it's still got stock recovery on it.
So no way to root, apply supersu, or do anything.
---------- Post added 3rd June 2015 at 12:04 AM ---------- Previous post was 2nd June 2015 at 11:37 PM ----------
Anyone got the fxz for this yet?
Ok, figured this out ...
(was able to back down to the original 4.4.4 w/rsd-lite and regain TWRP and develop these steps)
So the following can be done to upgrade to this new version, and retain TWRP (plus you have the new recovery later on for 5.1 when it comes along ...)
First, the presumption here is you are unlocked. If you are not, none of this will work.
Also, you will need RSD-Lite installed and operational.
Download :
https://dl.dropboxusercontent.com/u...RIZON_4.4.4_KXA21.12-L1.26-3_cid2_1FF.xml.zip
https://dl.dropboxusercontent.com/u...4.4.4_KXA21.12-L1.26-3/twrp-2.8.6.0-ghost.img
https://dl.dropboxusercontent.com/u/22067374/GHOST_VERIZON_4.4.4_KXA21.12-L1.26-3/servicefile.xml
Unpack the GHOST zip file, and overwrite the "servicefile.xml" in the unpacked folder w/the one you downloaded, then copy the twrp .img in there.
Fire up RSD-Lite, put your phone in fastboot, and apply this update by loading the servicefile.xml as the update.
It will update everything, installing the TWRP instead of the new stock recovery.
Note: you can delete the twrp line in servicefile.xml if you wish to retain your existing custom recovery.
When done, you should reboot, update, and be up and running with the new 4.4.4 and TWRP ... so easy path back to root via TWRP.
FYI... its already confirmed that you do NOT have to disable Xposed... All you need is stock recovery.
See -> http://forum.xda-developers.com/moto-x/moto-x-qa/ota-custom-recovery-t3124492
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Why dont you try to revert back stock using a factory image?
chichu_9 said:
Why dont you try to revert back stock using a factory image?
Click to expand...
Click to collapse
I used MDB08M factory instead of MDB08L which originally from the phone, I am not sure this the course of the problem.
The red exclamation usually means either no recovery or incompatible recovery. Did you flash mmb29m recovery for mdb08m rom? If you get stuck too bad you can always enter fastboot and just reflash everything its not that hard to do.
dontbeweakvato said:
The red exclamation usually means either no recovery or incompatible recovery. Did you flash mmb29m recovery for mdb08m rom? If you get stuck too bad you can always enter fastboot and just reflash everything its not that hard to do.
Click to expand...
Click to collapse
Yes, I flashed whole mmb29m factory image over mdb08m. Still can't boot to recovery manu . I'm worried about OTA will fail.
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Once you're on that screen, you've held down the power button then pressed and released volume up right?
Sent from my SM-N920T using Tapatalk
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Get into fastboot, then "fastboot flash recovery xxxxxxxx.img" obviously replacing the x's with the file name. Just reflash the recovery for the same factory image you flashed. Very possible that you just need to reflash the recovery image.
spc_hicks09 said:
Get into fastboot, then "fastboot flash recovery xxxxxxxx.img" obviously replacing the x's with the file name. Just reflash the recovery for the same factory image you flashed. Very possible that you just need to reflash the recovery image.
Click to expand...
Click to collapse
Tried but doesn't work.
Sent from my Nexus 6P using Tapatalk
Flash the recovery via fastboot :
fastboot flash recovery xxx.img
fastboot reboot-bootloader
Now, when your phone reboots to bootloader, using the volume keys, find "recovery" and use the power button to confirm.
profit.
he has to press the power button and vol up on that screen to get into recovery just like guy in post 7 said...
factory recovery doesnt boot all the way into it by default, requires a user button input once it gets to that android exclamation screen
kauemelhado said:
Flash the recovery via fastboot :
fastboot flash recovery xxx.img
fastboot reboot-bootloader
Now, when your phone reboots to bootloader, using the volume keys, find "recovery" and use the power button to confirm.
profit.
Click to expand...
Click to collapse
I did this, the red little thing didn't go away
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
I did this, the red little thing didn't go away
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Did you try downloading another recovery file?
That's really strange.
I was having this error when I tried to flash twrp and boot direclty to system (skipping the recovery boot).
Did you try to install twrp?
---------- Post added at 01:53 PM ---------- Previous post was at 01:48 PM ----------
Another thing..
The system boots up normaly?
To solve this, I did the procedure that I just told you + before booting into twrp, I flashed vendor.img..
Dunno if that could cause this issue
kauemelhado said:
Did you try downloading another recovery file?
That's really strange.
I was having this error when I tried to flash twrp and boot direclty to system (skipping the recovery boot).
Did you try to install twrp?
Click to expand...
Click to collapse
When I root I installed TWRP, revert back all to stock after unroot. I have to stay unroot because of the company app. Just want to be easy to update on OTA,
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
When I root I installed TWRP, revert back all to stock after unroot. I have to stay unroot because of the company app. Just want to be easy to update on OTA,
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I know that feel bro, my company also use an app that verifies for root..
I'm rooted, but on 6.0 I had only twrp w/ no root. no problems..
kauemelhado said:
I know that feel bro, my company also use an app that verifies for root..
I'm rooted, but on 6.0 I had only twrp w/ no root. no problems..
Click to expand...
Click to collapse
So you can install twrp without root as I understand. Then do you need to lock your phone after install twrp (unlock before install twrp, right?), and also how do you do the update OTA or upgrade to 6.0.1, etc..? Thx
VanGolfer said:
So you can install twrp without root as I understand. Then do you need to lock your phone after install twrp (unlock before install twrp, right?), and also how do you do the update OTA or upgrade to 6.0.1, etc..? Thx
Click to expand...
Click to collapse
I guess you can't lock your bootloader with Twrp.
Then, to take ota's just simply flash the img files.
;s
Hi all,
I have a bit of an issue with the latest OTA update currently being pushed out and looking for help how best to proceed.
I have unlocked and rooted the phone previously and recovery is TWRP. My phone is encrypted.
When I accepted the updated the phone rebooted and showed the TWRP splash screen which flashes on and off endlessly. If I turn the phone off and on again it restarts fine but after a few seconds the update process starts again. I am currently stuck in this loop.
Any advice as to how I can get out of this without wiping my phone?
I am wondering if I could flash the standard recovery to remove TWRP if this would work. Could it and if so, where can i get the standard recovery image.
Thanks and sorry of this is already covered, I searched but couldn't find it.
For XT1575.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If you want to update be on stock rom i.e. unrooted and no xposed,nothing added or removed from system and also flash stock recovery.
After successful update flash twrp.
So, if I want to install the lastest update it's enough to unroot, remove xposed and flash stock recovery? Or it's better to flash full stock through fastboot?
So I managed to find a link to the full image for my device (XT1572 so the above link wouldn't work to the best of my knowledge - but thanks anyway @Hitti2)
I flashed the standard recovery and rebooted which stopped the endless loop. The update still fails to install but I can live with that for now.
I'll investigate further what I need to do to get the update to take properly but for now I have a functioning phone which is a good start to the day.
Thanks all.
Sent from my XT1572 using Tapatalk
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
There is a whole thread dedicated to this update in general.
lafester said:
There is a whole thread dedicated to this update in general.
Click to expand...
Click to collapse
Maybe there is but as I stated in the OP, I couldn't find the right information at the time of posting. Maybe helpful would be to also link the thread as it may help others.
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Boot image?
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
user7743 said:
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
Click to expand...
Click to collapse
nathlynn22 said:
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
This one possibly?
http://forum.xda-developers.com/moto-x-style/general/xt1575-february-2016-security-update-t3323126
---------- Post added at 10:42 PM ---------- Previous post was at 09:50 PM ----------
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
evandena said:
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
Click to expand...
Click to collapse
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Thanks so much for trying to help. I went ahead and flashed the boot and recovery files for my model. I did the Boot image first, no luck. then i did the recovery, and this time andy thought a bit longer before giving me the Error! message. And then instead of my phone doing an autoreboot, it was stuck on the dead Andy and I needed to do hold down the power button to get it to shut down.
Anyone have any additional thoughts?
user7743 said:
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Click to expand...
Click to collapse
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
This phone has never been able to take OTAs for some reason. I wish I understood why. I tried to leave the thing stock to keep things simple, but it wasn't to be... anyway...
Thanks for the advice. Any idea where to get a download of the .zip files (is it really more than one zip file, or was that a typo)? I tried searching, but can't seem to find the right things to search for.
Also, once i have the zip file(s):
1) Do I just install it via TWRP like any other zip file?
2) to get rid of the OTA prompt, do i wipe the cache and reboot before or after i install the update via the zip?
Many thanks!
InFamousD147 said:
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
Click to expand...
Click to collapse
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
chuck-fu said:
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Click to expand...
Click to collapse
I have the 1572 RETEU, but you can find the stock firmware here: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If it's like the stock firmware that I have for the 1572 it should have all the img files and the system chunks. You just need to flash all the chunks like this:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
This has to be done because Marshmallow doesn't allow any modification in the system or the boot image, and will not proceed with the OTA if the ROM is not full stock.
EDIT: You will not loose any data, but any modification to the system partition will be undone.
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
chuck-fu said:
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
Click to expand...
Click to collapse
I just let the normal OTA install after flashing system, boot and recovery, without wiping any partition. Maybe you can try a flash all the zip to make sure it's full stock and see if the OTA install. Just make a backup before in case nothing change.
Google just released May 2016 factory images for Nexus devices.
Factory Images for Nexus Devices
Android Security Bulletin—May 2016
Anyone flashed it?
OTA zip file link?
Sent from my Nexus 5X using XDA-Developers mobile app
We probably need to wait a little bit for OTA zip.
following for ota link
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
miksontije said:
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
Click to expand...
Click to collapse
Hopefully it's a good update. Sometimes they're hit-or-miss.
mxrider97 said:
Anyone flashed it?
Click to expand...
Click to collapse
Flashed it yesterday, haven't noticed anything new. However, I also haven't noticed anything bad or broken; which is just as important.
Sent from my Nexus 5X using Tapatalk
Flashed using the factory images and nothing is broken. It did trigger a Google Camera update and it has been improved a bit more. Faster startup and snappier response when changing between portrait and landscape mode. Battery life stayed the same.
waiting for ota zip :good:
I updated using fastboot. Rooted and everything is working fine. Even Android Pay with the latest SuperSU.
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Just installed! You have any advice about a compatible kernel?
Andr006 said:
Just installed! You have any advice about a compatible kernel?
Click to expand...
Click to collapse
I like EX Kernel. It has not been update with the new patches but will still work well.
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
I update all the images with fastboot then just use WugFresh to root and add TWRP.
65coupei6 said:
I update all the images with fastboot then just use WugFresh to root and add TWRP.
Click to expand...
Click to collapse
This worked in the end, thanks for your help tip!
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
if you boot using stock kernel (boot.img) android will replace whatever recovery you have flashed with stock recovery.
to prevent this from happening, PRIOR to first boot after flashing update, flash twrp in fastboot, scroll down in fastboot menu and boot into recovery/twrp, and apply supersu update.zip
after that you'll be rooted again and boot.img will no longer try and replace your recovery with stock recovery.
OTA posted:
http://forum.xda-developers.com/showpost.php?p=66781159&postcount=124
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
EDIT: Link to the zip
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
I don't believe so.
In the past you either had to go back to stock or wait on someone to create a compatible update for rooted devices.
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Can you add what variant and build you are using before the update? Also the build afterwards?
KapilFaujdar said:
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Click to expand...
Click to collapse
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
gghose said:
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
Click to expand...
Click to collapse
Yeah I can't find anything in that folder either.
I received the update and applied it. I am not rooted.
I have the XT1687 model.
My current build number is NPN25.137-35
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
bvsbutthd101 said:
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
Click to expand...
Click to collapse
If you have systemless supersu, you should just be able to apply the update after reverting to stock recovery.
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
glight0 said:
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
Click to expand...
Click to collapse
OK, so I tried flashing recovery.img from stock firmware build 33. But the OTA update will not install, instead I get an error after downloading and rebooting (red triangle at recovery mode).
So I tried fully reverting to stock firmware but I decided to skip over erasing userdata. Afterward the OTA downloaded and installed successfully. Keeping userdata does not seem to have caused an issue.
My problem now though is how to get root back without having to wipe userdata after re-flashing TWRP.
Or is this not possible and if I want to root I must first wipe userdata so that TWRP can read internal memory?
bvsbutthd101 said:
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
If your using a custom recovery flash the stock recovery, then go to the stock recovery and using your computer flash using adb sideboard command. I assume you already know how to do this. Hope that helps.
gghose said:
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
Click to expand...
Click to collapse
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone
There's a workaround to disable the "advanced LTE" or whatever it was called, so I did that. But in the meantime until a more "user friendly" means of updating is available, is there a way I can get rid of this nag screen? Way back on an earlier device (Samsung Charge?) I remember manually editing a "build.prop" file or something to match the latest version so I wouldn't keep getting the software update nag. Is there something that will do the same here, or is there a system app I can freeze in TiB?
My best guess is freezing "Moto Actions 03.022.1.4-N" because it's showing "(updated)" on the side.
rellim113 said:
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone .
Click to expand...
Click to collapse
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
glight0 said:
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
Click to expand...
Click to collapse
Strange, reflashed the stock recovery and adb can't see it (adb devices returns nothing). And when trying to install it via the normal OTA way, the stock recovery tries to install but ends with an error.
That's what happened to me when I tried reverting to stock recovery and then trying to install update from phone Settings app.
I ended up having to revert to stock rom to get ota to apply with settings app. But now I am trying to root again but after installing TWRP data is encrypted again. So looks like I will have to wipe data before re-rooting.