Database Develop

[Q] 5.1 OTA rooted

I have a N6 rooted and I am waiting for the OTA rollout for 5.1 and I am wondering if i need to unroot before doing the 5.1 OTA?

zd913 said:
I have a N6 rooted and I am waiting for the OTA rollout for 5.1 and I am wondering if i need to unroot before doing the 5.1 OTA?
Click to expand...
Click to collapse
To take an OTA, you'll need a 100% stock system image and be on stock recovery.
To be sure the OTA updates your system, your best option would be to fastboot flash the stock system.img and recovery.img from the stock 5.0.1 factory images (assuming you are on 5.0.1 now).
You could, just as easy, stop waiting and download/flash the 5.1 factory images manually, not flashing the userdata.img to keep your data intact (must be bootloader unlocked of course), then re-root.

tcrews said:
To take an OTA, you'll need a 100% stock system image and be on stock recovery.
To be sure the OTA updates your system, your best option would be to fastboot flash the stock system.img and recovery.img from the stock 5.0.1 factory images (assuming you are on 5.0.1 now).
You could, just as easy, stop waiting and download/flash the 5.1 factory images manually, not flashing the userdata.img to keep your data intact (must be bootloader unlocked of course), then re-root.
Click to expand...
Click to collapse
Yes i am on 5.0.1. Do i need to unroot before i flash the 5.1 factory image?

zd913 said:
Yes i am on 5.0.1. Do i need to unroot before i flash the 5.1 factory image?
Click to expand...
Click to collapse
No, Flashing will overwrite the rooted system you have now. You will have to root after flashing 5.1.

I will ask question in this thread as I don't want start new one.
I'm in uk. I have n6, I didn't do anything on it, no root, no unlocked bootloader.
Can I take OTA 5.1 , without worrying that it will stay in boot loop or I'm pretty safe to do so?
Also how long I have to wait for OTA 5.1 , I can see plenty of you on this forum had it already, but I even if I check for system updates it keep telling me system is up to date.

It can take a few weeks. And everything should be fine if you wait and accept it normally

rootSU said:
It can take a few weeks. And everything should be fine if you wait and accept it normally
Click to expand...
Click to collapse
I hope you don't mind me asking a question here also? I hate to start another thread.
I'm on custom rom and kernel both still at 5.0.x. I've updated my bootloader and radio to 5.1. If I just wipe, flash the 5.1 rom, gapps and the 5.1 kernel, I don't have to flash the factory image's, they are baked into the rom and kernel already? Thanks in advance.

jackpollard said:
I hope you don't mind me asking a question here also? I hate to start another thread.
I'm on custom rom and kernel both still at 5.0.x. I've updated my bootloader and radio to 5.1. If I just wipe, flash the 5.1 rom, gapps and the 5.1 kernel, I don't have to flash the factory image's, they are baked into the rom and kernel already? Thanks in advance.
Click to expand...
Click to collapse
I'm sorry, I do not quite understand your question.

rootSU said:
I'm sorry, I do not quite understand your question.
Click to expand...
Click to collapse
Thanks for responding and sorry I was not clear. I'm currently on a custom Rom and kernel that are 5.0 based. I flashed the 5.1 radio and bootloader when they came out. I want to upgrade to the 5.1 versions of the custom Rom and kernel. Do I have to flash stock 5.1 then flash the custom stuff or can I just flash the 5.1 custom Rom and kernel and be at 5.1.

jackpollard said:
Thanks for responding and sorry I was not clear. I'm currently on a custom Rom and kernel that are 5.0 based. I flashed the 5.1 radio and bootloader when they came out. I want to upgrade to the 5.1 versions of the custom Rom and kernel. Do I have to flash stock 5.1 then flash the custom stuff or can I just flash the 5.1 custom Rom and kernel and be at 5.1.
Click to expand...
Click to collapse
You just flashing your custom 5.1 ROM. It wouldn't make much sense to flash one ROM (i.e., a stock 5.1 ROM) and kernel to then immediately overwrite it with another ROM (i.e., your custom 5.1 ROM) and kernel, now would it?

[Q] How would I downgrade from official CM12 to 4.4.4? XT1052

I'm slightly confused on how I would downgrade to the official GB retail 4.4.4 ROM, is it as simple as flashing it on the recovery? or will I have to do it via ADB fastboot? If so, how would I go about doing that?
My bootloader is 30.B7, which I have read to be the correct one for 4.4.4, I'm just confused on the method to use.
I want to go back to 4.4.4 so I can prepare for the official update which, with the recent soak tests, seems pretty imminent.
Thanks in advance!

https://docs.google.com/file/d/0B5XNxZ2OcfKtdDROTk5kb21ObU0/edit?usp=docslist_api
Download this file.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Then follw the steps mentioned in the above post.

pinhead97 said:
I'm slightly confused on how I would downgrade to the official GB retail 4.4.4 ROM, is it as simple as flashing it on the recovery? or will I have to do it via ADB fastboot? If so, how would I go about doing that?
My bootloader is 30.B7, which I have read to be the correct one for 4.4.4, I'm just confused on the method to use.
I want to go back to 4.4.4 so I can prepare for the official update which, with the recent soak tests, seems pretty imminent.
Thanks in advance!
Click to expand...
Click to collapse
Good job checking your bootloader, I think your not as confused as your think
CM12 doesn't upgrade your phone like an official update does, it only messes with the system and as such going back to 4.4.4 does not require downgrading GPT.bin or MOTOBOOT.img
If you have a backup of your stock system, or a 4.4.4 rom you can just flash it from recovery. If you didn't make a backup, you will have to find one that works with your phone or you can just reflash the sbf with fastboot ( http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 )

scryan said:
Good job checking your bootloader, I think your not as confused as your think
CM12 doesn't upgrade your phone like an official update does, it only messes with the system and as such going back to 4.4.4 does not require downgrading GPT.bin or MOTOBOOT.img
If you have a backup of your stock system, or a 4.4.4 rom you can just flash it from recovery. If you didn't make a backup, you will have to find one that works with your phone or you can just reflash the sbf with fastboot ( http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 )
Click to expand...
Click to collapse
Cheers man, this has helped a lot

How can I back up recovery.img from Lollipop 5.1?

I recently unrooted my Moto X 1053 DevEd (GSM) in order to accept the Lollipop 5.1 OTA. I got the update and it's working great.
Now I want to re-root my phone, but first I want to be sure that I have a copy of stock recovery.img for Lollipop 5.1.
How can I back up recovery.img from my phone without my phone being rooted?
Thanks!

is temp booting custom recovery still possible... I haven't messed around with stuff in a while, but I think if you can temp boot twrp recovery (fastboot boot twrp) you might be able to use it to back up the stock recovery... you should google for more info on that, make sure it doesn't flash instead of boot.
otherwise you can't backup stock recovery without root. it's kind of a catch 22: you want to back up stock recovery before you root, but you can't do that on the device without root.
normally you can get the recovery from the stock firmware zip file. but I don't think Motorola is handing them out for 5.1 yet - if they are then it will be in that file. if not I suppose the next best thing is to rummage through the OTA file. I haven't unzipped it myself but it has to be in there right? some info that might help: the recovery size is 10mb. I can see it with the DiskInfo app, along with its block partition name mmcblk0p34, although it probably won't be named that in the zip file idk... anyway you can find the OTA here: https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1

That is a really, really helpful post, dtg7. I had hoped Moto would have posted the firmware, but I guess I'm too impatient. As I didn't have a separate copy of the OTA, I'm doing as you suggested and grabbing the OTA from the site you linked to. I'll try to extract the recovery.img file from there. I'll post my results.
Yes, this is a classic catch 22, as you say.

dtg7 said:
I haven't messed around with stuff in a while,...
Click to expand...
Click to collapse
This is precisely my problem. I get semi-proficient with phone stuff every now and then when I'm changing things around, but then I forget almost everything I need to know to do the most basic geek maneuvers. When I had an HTC Sensation, which was a favorite for ROM-makers and modders, I was swapping out the ROM nearly every day between meals. With the Moto X I haven't done this much, maybe because I've gotten older, but mainly because there don't seem to be as many custom ROMs for the Moto X (nor is as much need for them, with Xposed and with a decent stock ROM.

dtg7 said:
anyway you can find the OTA here: https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
Click to expand...
Click to collapse
Isn't that a link to KitKat 4.4.4 (i.e., 213.44.1)?
I've got Lollipop 5.1 on my phone, and "About Phone" lists it as 222.21.15.
It's actually system.img from 222.21.15 that I'm trying to get ahold of.

varxx said:
Isn't that a link to KitKat 4.4.4 (i.e., 213.44.1)?
I've got Lollipop 5.1 on my phone, and "About Phone" lists it as 222.21.15.
It's actually system.img from 222.21.15 that I'm trying to get ahold of.
Click to expand...
Click to collapse
Or is this still the case (quoted from elsewhere on this site)?
file name ... references the build your phone must be on to accept the update, not the version of the update itself. That is how Moto has done it for some time now.
Click to expand...
Click to collapse

varxx said:
Or is this still the case (quoted from elsewhere on this site)?
Click to expand...
Click to collapse
yes that is still the case, moto otas refer to the android version you're updating From
that file is what I used to update from 4.4.4 to lollipop

dtg7 said:
yes that is still the case, moto otas refer to the android version you're updating From
that file is what I used to update from 4.4.4 to lollipop
Click to expand...
Click to collapse
Thanks for clarifying this.

varxx said:
Thanks for clarifying this.
Click to expand...
Click to collapse
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.

AaronCompNetSys said:
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
Click to expand...
Click to collapse
I can't find recovery.img in the uncompressed file dtg7 kindly linked above:
https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
Maybe I didn't look hard enough.
I *did* find the 4.4.4 recovery.img in the uncompressed file I requested and received from Moto. It seems like Moto sometimes uses the same recovery.img from release to release, but I'd be skittish about using this with stock 5.1 until someone can give it the all-clear. As of right now (27 june 15, 9:00 GMT), Moto hasn't posted stock 5.1.

AaronCompNetSys said:
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
Click to expand...
Click to collapse
varxx said:
As of right now (27 june 15, 9:00 GMT), Moto hasn't posted stock 5.1.
Click to expand...
Click to collapse
Looks like the stock XT1053 5.1 firmware is available now. See the links here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628

dtg7 said:
Looks like the stock XT1053 5.1 firmware is available now. See the links here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Click to expand...
Click to collapse
Thanks! I'm not sure if I want to try flashing just the recovery or not, I've been having lots lof radio active time so I migh full wipe/flash to try to clear that up.
Here is just the recovery from the "tmo_retail_xt1053_5.1_lpa23.12-15.222.21.15.ghost_row.retail.en.us.tgz" file:
https://mega.co.nz/#!WU5WjaqL!109FXTQovfywRxJM67YBH5KHrErNZYILPVyzk4HGK-c
varxx said:
I recently unrooted my Moto X 1053 DevEd (GSM) in order to accept the Lollipop 5.1 OTA. I got the update and it's working great.
Now I want to re-root my phone, but first I want to be sure that I have a copy of stock recovery.img for Lollipop 5.1.
How can I back up recovery.img from my phone without my phone being rooted?
Thanks!
Click to expand...
Click to collapse

Just got an OTA alert, is it LMY48I?

I'm on Verizon, rooted and unlocked, currently running LMY47Z. I just got an OTA alert for an android system update - is it LMY48I?
I'm looking for confirmation since it seems to have the same version number as LMY47Z (5.1.1). Thanks!
EDIT: I flashed LMY48I through fastboot and it works fine. Apparently the only fix is for that MMS exploit, nothing major.

Probably not but if you are rooted don't matter. Can't flash the update.

You can flash the radio and bootloader(firmware only), if you want I, and then you'll be on LMY47I. If your on a custom ROM then your system is whatever build they want to label it. Data,recovery and boot are not necessary. I updated from E to Z by simply flashing radio and bootloader in twrp.
Sent from my Nexus 6 using Tapatalk

Hi... I'm in the same boat, sort of. I have LMY47D.
I just discovered the link on Google to the OTA for the Nexus 6 to get to LMY48I. But the link text said "shamu LMY48I from LMY47Z." I guess what I really need is "shamu LMY48I from LMY47D" but something tells me that will never exist. So my question is, can I just apply the LMY47Z to LMY48I OTA via sideload? I know how to do it with the Nexus Root Toolkit.
Any advice would be appreciated!

713brianp27 said:
You can flash the radio and bootloader(firmware only), if you want I, and then you'll be on LMY47I. If your on a custom ROM then your system is whatever build they want to label it. Data,recovery and boot are not necessary. I updated from E to Z by simply flashing radio and bootloader in twrp.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
radio and bootloader do not get you an update, system is what gets you the actual update. and you didnt mention it anywhere.

simms22 said:
radio and bootloader do not get you an update, system is what gets you the actual update. and you didnt mention it anywhere.
Click to expand...
Click to collapse
I was referring to being on a custom ROM, I'm on blisspop for ex., I update w just firmware. My system is updated w ROM. Data,cache are null. And I did tell him since he's on stock he Does need system.
Sent from my Nexus 6 using Tapatalk

713brianp27 said:
I was referring to being on a custom ROM, I'm on blisspop for ex., I update w just firmware. My system is updated w ROM. Data,cache are null. And I did tell him since he's on stock he Does need system.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
ah, i see what youre doing there. my bad..

Flashed to LMY48I, no issues so far for those who are wondering.

mordrukk said:
Flashed to LMY48I, no issues so far for those who are wondering.
Click to expand...
Click to collapse
Good to know. I'm wanting to flash to it as well...but regarding my previous post, do you or anyone else know if I'm on LMY47D if it's safe to use the "shamu LMY48I from LMY47Z" OTA file? I'm not LMY47Z, I'm on LMY47D.
Thanks

JPMontana said:
Good to know. I'm wanting to flash to it as well...but regarding my previous post, do you or anyone else know if I'm on LMY47D if it's safe to use the "shamu LMY48I from LMY47Z" OTA file? I'm not LMY47Z, I'm on LMY47D.
Thanks
Click to expand...
Click to collapse
It's most likely fine to go from LMY47D to LMY48I, since flashing the system.img file overwrites the entirety of the OS (note: I only ever flash boot.img, system.img and the radios). Though if you're cautious, take a look at the list on the nexus image site, and try flashing from LMY47D to LMY47Z, then to LMY48I.

Thank you for the response... the Nexus images are full images, so I could (should?) probably just flash the entire LMY48I image.

JPMontana said:
Good to know. I'm wanting to flash to it as well...but regarding my previous post, do you or anyone else know if I'm on LMY47D if it's safe to use the "shamu LMY48I from LMY47Z" OTA file? I'm not LMY47Z, I'm on LMY47D.
Click to expand...
Click to collapse
No. The OTA file will not work if your phone is on LMY47D, and your OTA file expects LMY47Z
Edit: See http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 - there is an OTA link in the first post that will get you from LMY47D to LMY47Z, and there is another OTA link there that will then take you from LMY47Z to LMY48I
mordrukk said:
It's most likely fine to go from LMY47D to LMY48I, since flashing the system.img file overwrites the entirety of the OS (note: I only ever flash boot.img, system.img and the radios). Though if you're cautious, take a look at the list on the nexus image site, and try flashing from LMY47D to LMY47Z, then to LMY48I.
Click to expand...
Click to collapse
If using the factory images, no need to jump thru' multiple images. Just pick the right image that you want and flash it.

Unable to upgrade to 6.0-marshmallow

Hi,
I'm trying to upgrade my Moto X 2014 to Marshmallow. The OTA upgrade appeared last week, but fails without any error message.
When the devices was new, I unlocked the boot and rooted it. The first upgrade (5.0) installed without any problem, but I chose not to root it anymore.
Upgrade to 5.1 failed. It worked after I reflashed the recovery.img(following idea from Q18 in http://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769). The same happened with the Stagefright update some time later. Now, the Marshmallow upgrade is available, but reflashing recovery.img is no longer working. It simply fails without any meaningful message. Could someone help me?
Tks,
Roberto
Device:
Moto X 2014, Brazilian retail version, version 23.16.2.victara_retbr.retbr.en.BR.retbr, version number LPE23.32-14.2

rgreiner said:
Hi,
I'm trying to upgrade my Moto X 2014 to Marshmallow. The OTA upgrade appeared last week, but fails without any error message.
When the devices was new, I unlocked the boot and rooted it. The first upgrade (5.0) installed without any problem, but I chose not to root it anymore.
Upgrade to 5.1 failed. It worked after I reflashed the recovery.img(following idea from Q18 in http://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769). The same happened with the Stagefright update some time later. Now, the Marshmallow upgrade is available, but reflashing recovery.img is no longer working. It simply fails without any meaningful message. Could someone help me?
Tks,
Roberto
Device:
Moto X 2014, Brazilian retail version, version 23.16.2.victara_retbr.retbr.en.BR.retbr, version number LPE23.32-14.2
Click to expand...
Click to collapse
Flash the stock 5.1 firmware to get completely back to stock, then try again.
Sent from my XT1095 using Tapatalk

AGISCI said:
Flash the stock 5.1 firmware to get completely back to stock, then try again.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Isn't there a way to avoid it? I would like to avoid fully resetting the phone.
Tks,
Roberto

rgreiner said:
Isn't there a way to avoid it? I would like to avoid fully resetting the phone.
Tks,
Roberto
Click to expand...
Click to collapse
No there is no other way. An OTA fails if you are not 100% stock. So that means no root, no xposed, no custom kernels, no modifications to anything that is in system. If even one thing is modified it WILL fail. So the solution is to go back to 100% stock by flashing the full firmware.
Sent from my XT1095 using Tapatalk

AGISCI said:
No there is no other way. An OTA fails if you are not 100% stock. So that means no root, no xposed, no custom kernels, no modifications to anything that is in system. If even one thing is modified it WILL fail. So the solution is to go back to 100% stock by flashing the full firmware.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
That's strange. When I upgraded to 5.1 and 5.1/stagefright, I had exactly the same setup: Boot unlocked, no root. It upgraded fine after just reflashing 'recovery.img'. Actually, when I upgraded from 4.4 to 5.0, the phone was rooted, and yet it upgraded perfectly.
Roberto

rgreiner said:
That's strange. When I upgraded to 5.1 and 5.1/stagefright, I had exactly the same setup: Boot unlocked, no root. It upgraded fine after just reflashing 'recovery.img'. Actually, when I upgraded from 4.4 to 5.0, the phone was rooted, and yet it upgraded perfectly.
Roberto
Click to expand...
Click to collapse
Again as I stated, something is modified. In the OTA it checks for modifications, if it finds something modified it fails and exits without upgrading it. So if you want to take the upgrade you need to flash back to stock.
This forum is filled with posts and topics of people having to unroot to get the OTAs to work. So why it worked for you, no idea, since you are the only person I have ever seen who has stated that it worked while rooted. According to every other post on this forum, OTA fails when rooted...
Sent from my XT1095 using Tapatalk

AGISCI said:
Again as I stated, something is modified. In the OTA it checks for modifications, if it finds something modified it fails and exits without upgrading it. So if you want to take the upgrade you need to flash back to stock.
This forum is filled with posts and topics of people having to unroot to get the OTAs to work. So why it worked for you, no idea, since you are the only person I have ever seen who has stated that it worked while rooted. According to every other post on this forum, OTA fails when rooted...
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok. But still, why fully-reflashing? As I said, my phone is NOT rooted since 4.4. It's only boot unlocked, and both 5.0 and 5.1 where installed and no modifications made after that.

rgreiner said:
Ok. But still, why fully-reflashing? As I said, my phone is NOT rooted since 4.4. It's only boot unlocked, and both 5.0 and 5.1 where installed and no modifications made after that.
Click to expand...
Click to collapse
Look, somewhere in your phone there IS something that is NOT stock. What it is, we don't know. The ONLY way for you to take an OTA is to be 100% stock, if not it will fail. So the only solution is to get your phone to 100% stock to take the OTA, which means flash the full firmware. If you don't want to flash the full firmware then you will stay on 5.1.
Sent from my XT1095 using Tapatalk

AGISCI said:
Look, somewhere in your phone there IS something that is NOT stock. What it is, we don't know. The ONLY way for you to take an OTA is to be 100% stock, if not it will fail. So the only solution is to get your phone to 100% stock to take the OTA, which means flash the full firmware. If you don't want to flash the full firmware then you will stay on 5.1.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok,
if that's the only route left, I will try it.
Tks,
Roberto

rgreiner said:
Ok,
if that's the only route left, I will try it.
Tks,
Roberto
Click to expand...
Click to collapse
Ok. After backing-up everything I needed, I flashed the stock 5.1 image. Reinstalled all apps (actually, everything reinstalled automatically), restored backups, and then tried the upgrade. Both stagefright and marshmallow upgrades worked fine, and 6.0 is running fine.
Tks.