Database Develop

[Q] Returning to un-rooted 5.0 on XT1095?

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.

[Q] OTA 5.1 Update file location?

So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.

You need to unroot too.
Ota can be downloaded online.

d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.

rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU

Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.

OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.

Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?

Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6

Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images

Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache

Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.

Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.

liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip

Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...

Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!

Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.

/data/data/com.google.android.gms/app_download/update.zip

d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.

At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip

[Q]how can i fully exploit root features & receiving OTA updates?

Hello XDA,
Im quite sure this has already been asked on the forum but i couldn't find an answer.
I need some advise about my recently rooted Nexus 6. I want to fully enjoy from a custom recovery but i dont want to lose the option of receiving OTA updates to my phone.
What do you guys do so your nexus keeps getting the lastest of Android?
Can i use WugFresh's root toolkit to sideload OTA updates even when i have a custom recovery?
What other ways can i use to update Android?
Thanks,

No but you could use the tool kit to reload recovery and stock then take your OTA then reroot and reload TWRP.
And you can side load but it is important you understand exactly what you're doing. the kit does nothing more than you can from the command line it just tries to save you from yourself. it can be a help or hindrance. If you don't understand what's going on it will be the latter
Sent from my Benzo'd Google N6 on VZ

If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...

Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Agreed. OTA is overrated. If I was on T-Mobile or the factory image was not available. I would grab the radio and load what I wanted.
Now I am running the E radio and the i build on VZ
Sent from my Benzo'd Google N6 on VZ

Didgeridoohan said:
you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?

torecdude said:
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
Click to expand...
Click to collapse
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.

Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Evolution_Freak said:
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Click to expand...
Click to collapse
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.

Updating via OTA on a Nexus is an undesirable method IMO. As mentioned previously, if you download and flash the factory images, you avoid the potential update failures in an OTA from modified stock parameters. As for recovery, you don't need to flash a custom recovery, you can simply boot a custom recovery from the PC using fastboot and having the recovery image of choice in your platform tools.
fastboot boot name_of_recovery_image_here.img
I don't flash from the device any more. Keeps me out of trouble. Being connected to the PC helps remind me to move a copy of my backup to the PC before flashing.

torecdude said:
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Click to expand...
Click to collapse
I put the link to that thread in mine as a quick way for people who are rooted/unlocked and running a custom recovery to find. Those are not the "official" way of updating. They work because someone here put the time in to make them work for unlocked/rooted users. No, you can't use an "official" OTA process if you've altered your device but that method uses TWRP to flash just like you were flashing a custom ROM.
I'm glad my thread has helped you! Since I'm not a developer yet, it is my sole purpose here to help users with anything I can. So a comment like that is very reassuring that I'm on the right path.

Not a noob, but still confused.

I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.

Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.

mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
FWIW: I would recommend that you:
1) Unlock bootloader
2) Decide if you want uncrypted kernel, or not (since it wipes data, just like unlocking bootloader).
3) Fastboot flash TWRP recovery.
4) Download SuperSU .zip and flash it in recovery.
5) Now, when a new OTA comes out, they usually show up here > http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
6) You can download your current factory image here > https://developers.google.com/android/nexus/images
7) Unzip your current factory image. Fastboot flash the system.img and that will unroot and restore the stock recovery.
8) Fastboot flash the stock boot.img if you have a custom kernel (or an unencrypted stock kernel).
9) Relax and wait for the OTA.

RW-1 said:
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
Click to expand...
Click to collapse
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!

mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.

mad_rulzzz said:
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
Click to expand...
Click to collapse
What he just explained is what I said, unroot and take the OTA.... He listed how as well.

RW-1 said:
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
Click to expand...
Click to collapse
Yup.

@rw_1 @cam30era thanks guys

I would do what gee2012 said.
From what I have seen the OTA and the images are released pretty close together.
Instead of flashing images to get back to stock and waiting for the OTA. and then re-rooting
Just download the image files from Google. Manually flash all the files EXCEPT user data if you want to keep your data.
Re-root.
You are now updated and don't have to wait for OTA.
Either way works so it depends on which you are happier with.

mad_rulzzz said:
@rw_1 @cam30era thanks guys
Click to expand...
Click to collapse
Welcome. And BTW: there's a button for that.

gee2012 said:
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
Click to expand...
Click to collapse
Just to be sure I understood right:
If I don't care about app data or settings ( I have titanium backup),
1)I can just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
one last thing... Does Google upload factory images after each OTA happens?

cam30era said:
Welcome. And BTW: there's a button for that.
Click to expand...
Click to collapse
My BAd!!

mad_rulzzz said:
If I don't care about app data or settings ( I have titanium backup),
1)Can I just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
Does Google upload factory images after each OTA happens? i.e; If Nexus 6 receives an OTA to 5.2, will they upload the 5.2 factory image soon?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the contents of your SD card. Make sure it is backed up on your PC.
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.

cam30era said:
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
Click to expand...
Click to collapse
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.

mad_rulzzz said:
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
Click to expand...
Click to collapse
Correct. M is intended for T-Mobile. My point, though, is that Google doesn't always, 100% of the time publish a factory image for every OTA.

[Q] Got 5.1.1 system update message but I'm on att?

Got 5.1.1 system update message but I'm on att? And when I check the list of stock android images, there is no 5.1.1 for att. Is it possible they are pushing ota's before they make the new image available to developers? Sounds odd to me.
I'm also rooted (but with stock recovery), so it sounds like I can't do the ota? I also have a Fi request out there. Or can I? I'm rooted but I haven't changed any system files. Can I do the ota rooted but with stock recovery and unmodified system files?
Should I unroot and try to get the ota?
-peter

If I'm not mistaken they normally do otas before images. You might be the first one to get this one. Get the url.

pcrussell50 said:
Got 5.1.1 system update message but I'm on att? And when I check the list of stock android images, there is no 5.1.1 for att. Is it possible they are pushing ota's before they make the new image available to developers? Sounds odd to me.
I'm also rooted (but with stock recovery), so it sounds like I can't do the ota? I also have a Fi request out there. Or can I? I'm rooted but I haven't changed any system files. Can I do the ota rooted but with stock recovery and unmodified system files?
Should I unroot and try to get the ota?
-peter
Click to expand...
Click to collapse
Buff McBigstuff said:
If I'm not mistaken they normally do otas before images. You might be the first one to get this one. Get the url.
Click to expand...
Click to collapse
AT&T is pushing LMY47Z via OTA. Factory image file has been available for some time on the Google website.

Buff McBigstuff said:
If I'm not mistaken they normally do otas before images. You might be the first one to get this one. Get the url.
Click to expand...
Click to collapse
hmmm, not sure how to get the url. the message was a system message, not an email with a link. the message says "Android 5.1.1 System Update Downloaded and Verfied..." i'm rooted with root permissions on ES file explorer, i can look for the ota but i'm not sure where they are kept after they are downloaded.
-peter

cam30era said:
AT&T is pushing LMY47Z via OTA. Factory image file has been available for some time on the Google website.
Click to expand...
Click to collapse
This was cut and pasted from the google website list of images about a minute and a half ago. can you tell me which one is 5.1.1 for att:
5.0 (LRX21O) Link af4520213c1a3e2b3dd811aef030b87b e028f5eab0952d0df60c63d6095b56c1c6f8e474
5.0.1 (LRX22C) Link a95f291164b5b438b5fc9e77c222d703 ff173fc66eca5a27b34ae28a9b69f9ad7f4d3b80
5.1.0 (LMY47D) Link 4d99d16bae3c5a638268731a5d27062e 6c44d4021142ffaa2197fb1308996a8846a79e26
5.1.0 (LMY47E) Link 7c50606b7d68ddd1b8a81d544ec59aff cf3131641c2bda2eba54bcc0108ce0325327f58e
5.1.0 (LMY47I) Link d6e750e58938de3b8516a4718c491d9c c8afc588e44ec087e8b98c1d6ed3ed565a9b9644
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
Click to expand...
Click to collapse
cuz if LMY47Z is for AT&T too, the "(For Sprint, USC ONLY)" bit was making me think otherwise.
-Peter

pcrussell50 said:
This was cut and pasted from the google website list of images about a minute and a half ago. can you tell me which one is 5.1.1 for att:
Code:
5.0 (LRX21O)Linkaf4520213c1a3e2b3dd811aef030b87be028f5eab0952d0df60c63d6095b56c1c6f8e474
5.0.1 (LRX22C)Linka95f291164b5b438b5fc9e77c222d703ff173fc66eca5a27b34ae28a9b69f9ad7f4d3b80
5.1.0 (LMY47D)Link4d99d16bae3c5a638268731a5d27062e6c44d4021142ffaa2197fb1308996a8846a79e26
5.1.0 (LMY47E)Link7c50606b7d68ddd1b8a81d544ec59affcf3131641c2bda2eba54bcc0108ce0325327f58e
5.1.0 (LMY47I)Linkd6e750e58938de3b8516a4718c491d9cc8afc588e44ec087e8b98c1d6ed3ed565a9b9644
5.1.0 (For T-Mobile ONLY) (LMY47M)Link0469ca2018c923498cc603baae4fd6485228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z)Linkc8fe950ad9e861120a1074825b92cfba33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E)Link9ea32a7ff1751afa2a16214ac23ef000b542b88a0ad478110f9f111dd32b62a1cb65b9d5
-Peter
Click to expand...
Click to collapse
There is only one LMY47Z. It says "For Sprint and USC only". Same build AT&T is pushing via OTA.

At&t rolled out the ota for at&t the zip is already available on xda for a few days now I sideloaded it two days ago. The factory image has not yet been posted on Google's site.
Edit: I wouldn't use the image that is posted on Google because even though it has the same build number the boot.img and radio are most likely different.

manup456 said:
At&t rolled out the ota for at&t the zip is already available on xda for a few days now I sideloaded it two days ago. The factory image has not yet been posted on Google's site.
Edit: I wouldn't use the image that is posted on Google because even though it has the same build number the boot.img and radio are most likely different.
Click to expand...
Click to collapse
I installed the OTA. Fastboot flashed back to 47D. Then after a few days flashed the 47Z factory image. They are identical. Same boot.img and same radio.

cam30era said:
I installed the OTA. Fastboot flashed back to 47D. Then after a few days flashed the 47Z factory image. They are identical. Same boot.img and same radio.
Click to expand...
Click to collapse
So you have this radio?
Edit: I ask because why would they put for sprint only on google's image download site. Kinda makes no sense to me at all, but you could be 100% correct I never flashed the image files off google's site.

manup456 said:
So you have this radio?
Edit: I ask because why would they put for sprint only on google's image download site. Kinda makes no sense to me at all, but you could be 100% correct I never flashed the image files off google's site.
Click to expand...
Click to collapse
Yes, same 101R radio. No idea why Google identifies things like they do.

i am rooted, but with stock recovery and have not edited any system files. can i go ahead and install this OTA, since it's already downloaded and verified according to the system updater?
-peter

pcrussell50 said:
i am rooted, but with stock recovery and have not edited any system files. can i go ahead and install this OTA, since it's already downloaded and verified according to the system updater?
-peter
Click to expand...
Click to collapse
you are rooted. just that in itself changes system files silly :silly:

cam30era said:
AT&T is pushing LMY47Z via OTA. Factory image file has been available for some time on the Google website.
Click to expand...
Click to collapse
simms22 said:
you are rooted. just that in itself changes system files silly :silly:
Click to expand...
Click to collapse
i had a feeling... thanks for confirming. i thought maybe just a root without any other changes might be like renaming the att splash so it doesn't happen on bootup.
-peter

AT&T 5.1.1 system update OTA, whats preventing the install?
manup456 said:
So you have this radio?
Edit: I ask because why would they put for sprint only on google's image download site. Kinda makes no sense to me at all, but you could be 100% correct I never flashed the image files off google's site.
Click to expand...
Click to collapse
pcrussell50 said:
Got 5.1.1 system update message but I'm on att? And when I check the list of stock android images, there is no 5.1.1 for att. Is it possible they are pushing ota's before they make the new image available to developers? Sounds odd to me.
I'm also rooted (but with stock recovery), so it sounds like I can't do the ota? I also have a Fi request out there. Or can I? I'm rooted but I haven't changed any system files. Can I do the ota rooted but with stock recovery and unmodified system files?
Should I unroot and try to get the ota?
-peter
Click to expand...
Click to collapse
I've had the 5.1.1 system update notice for a few days and finally clicked "install" - it counts down to reboot, then instead of rebooting it says "system up to date" with the current time stamp.
I am rooted, unencrypted, Franco kernel, stock 5.1 ROM.
I assume the root and/or un-encryption is somehow preventing the system updates? Is there any way to stop the system update notification?
Thanks.

I took a dive and did the update. My phone is now in a wonky state. Its still at 5.1. Every time I power on my phone, it does the applications countdown like its indexing all the apps.
(Unencrypted, ElementalX, 5.1)

garyHal said:
I took a dive and did the update. My phone is now in a wonky state. Its still at 5.1. Every time I power on my phone, it does the applications countdown like its indexing all the apps.
(Unencrypted, ElementalX, 5.1)
Click to expand...
Click to collapse
Do you mean you tried to install the OTA? If so, it won't install for you. You have to have be stock (encrypted kernel, no root, stock recovery). Your best option is to fastboot flash the factory image.

cam30era said:
Do you mean you tried to install the OTA? If so, it won't install for you. You have to have be stock (encrypted kernel, no root, stock recovery). Your best option is to fastboot flash the factory image.
Click to expand...
Click to collapse
Yeah, I tried to install the OTA. I heard it wasn't going to work. I just expected the "verification" step to fail before it tried to install. Apparently something fubar'd.

How do we get rid of the dang system update message?
Sent from my Nexus 6 using Tapatalk

ryan141 said:
How do we get rid of the dang system update message?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I did it by long pressing on the notification and selecting 'i' which took me to the Google Play services App notifications. Then I selected Block and the notification went away.

thrasher9 said:
I did it by long pressing on the notification and selecting 'i' which took me to the Google Play services App notifications. Then I selected Block and the notification went away.
Click to expand...
Click to collapse
Doesn't that kill all of the google play services notifications?