Mismatching build numbers when flashing Stagefright update

Mismatching build numbers when flashing Stagefright update - Nexus 6 Q&A, Help & Troubleshooting

Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!

rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.

prdog1 said:
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.
Click to expand...
Click to collapse
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash either, right? It certainly seems like an exploit worthy of my time to patch, but I was trying to avoid the data loss :/

rvrzl said:
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash, right? It certainly seems like an exploit worth of my time to patch, but I was trying to avoid the data loss :/
Click to expand...
Click to collapse
You can fastboot flash the corresponding factory images. Skip the userdata data image and will will not wipe data. OTA's are worthless if gonna run root and recovery. Someone may make a TWRP flashable. Would have to search for it.

Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1

rvrzl said:
Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1
Click to expand...
Click to collapse
If you're running root, fastboot flash the system.img only. If you don't run a custom kernel, you probably should also fastboot flash the boot.img too.
Keep supersu on your sdcard and after flashing system DO NOT boot the rom. Boot straight into TWRP and flash supersu
If you boot rom install-recovery.sh will install stock recovery on first boot. .flashing super su amended this script so that won't happen.
You can also flash the radio.img. Your choice.

rvrzl said:
I have an unlocked & rooted Nexus 6 (T-Mo, I My build number is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP,
Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Click to expand...
Click to collapse
For OTA's the device needs to be unrooted and complete stock. Including 'recovery'. So flashing with TWRP-recovery will not work.
An alternative is to flash only the new system.img with fastboot.

FWIW, recovery flashable updates are here:
http://forum.xda-developers.com/showthread.php?t=3066052

rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.

snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.

snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
You can flash the OTA all day anyway you want but if you are not stock it won't take. Only other way is one of the flashable TWRP versions that were linked to. And right now looks like that thread is down for update.

danarama said:
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.
Click to expand...
Click to collapse
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.

rvrzl said:
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
!
Click to expand...
Click to collapse
Because of this, I did the update twice; different methods, to see of there are possible differences.
Differences between official OTA and flashing the new system.img only.
Update 1: Flashing only the new system image (1,7 Gb) with fastboot.
Update 2: Return to stock LMY47Z and install official OTA (24,2 Mb)
Both updates have the same results. Data and apps were kept but there were changes:
a. Changes in build.prop gone (DPI, Wifi interval);
b. Standard icons because the DPI value 384 was changed to 560;
c. BGN-launcher replaced. Google Now launcher became white again;
d. Root gone (SuperSu and Busybox);
(Update 2. Of course returning to stock, replaces the custom kernel).
After rerooting the N6 the following actions were needed after both update methods:
- edit the file: system/build.prop to change the dpi and wifi interval;
- reflash/reinstall: BGN-Launcher, SuperSU and Busybox;
- uninstall updates of the Google app to get BGN-launcher working;
- replacing icons from drawer to start screen.
So when you have made changes to the system, like DPI settings, an update will leave your data alone, but not the settings.

Clawz114 said:
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.
Click to expand...
Click to collapse
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk

efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".

efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
That said, the only reason not to flash the rightbversiin is if the download link.is down or you have a local copy of a different version anyway.
Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
How are you trying to flash the OTA?
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work

Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
What is the error?
danarama said:
[snip]
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
Click to expand...
Click to collapse
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).

danarama said:
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
Click to expand...
Click to collapse
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
danarama said:
How are you trying to flash the OTA?
Click to expand...
Click to collapse
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
danarama said:
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work
Click to expand...
Click to collapse
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
efrant said:
What is the error?
Click to expand...
Click to collapse
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".

efrant said:
What is the error?
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).
Click to expand...
Click to collapse
I believe it changed for lollipop OTA's. I don't think it had changed for kitKat.
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
Clawz114 said:
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
Click to expand...
Click to collapse
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?

danarama said:
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?
Click to expand...
Click to collapse
I'm going to have to do just that by the looks of it.

Related

[Firmware] Nvidia Root-Friendly Updates [No Wipe]

If coming from the original JellyBean and have not updated your custom recovery since, you will need to install the recovery provided below. This step only needs to be performed once to support the newer updates.
Recovery Update
Boot into bootloader mode, connect the USB cable, and from a terminal window or command prompt type:
Code:
fastboot flash recovery recovery.img
To root an OTA, the procedure is pretty simple.
Code:
Copy the OTA from the cache folder to the sdcard.
Move the OTA zip somewhere it can be opened and unzip it
Go to system/etc/ to find the file named recovery and delete it
(extension may vary, but it is always named recovery)
Open the META-INF/com/google/android/updater-script
Delete all of step 1 and step 3 so that all that is left is the large middle portion without any steps
That's it. You have made the same files you find here.
Download the desired package below and copy it to your sdcard, along with the SuperSU recovery package.
Boot into recovery, select install from sdcard, and choose the update. Go back and repeat the install for SuperSU.
KitKat Update 98
KitKat Update 99
Lollipop Update 110
XDA:DevDB Information
Nvidia Root-Friendly Updates [No Wipe], ROM for the Nvidia Shield
Contributors
twistedumbrella
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-11-08
Last Updated 2018-07-05

twistedumbrella said:
The new update has a few things that require updating the recovery, but since a recovery is not officially developed, updating the kernel of the existing recovery will do the trick. Flash this first.
Recovery Update
The install requires removing the assert checks since there is an error that the device is a Thor but looking for a Roth (same thing, right?). Install this from the new recovery.
KitKat Update
Immediately after installing the update, install the SuperSU recovery package to restore root and you're all set.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?

NapalmDawn said:
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
Click to expand...
Click to collapse
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands

twistedumbrella said:
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
Click to expand...
Click to collapse
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?

NapalmDawn said:
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
Click to expand...
Click to collapse
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.

KitKat Update Without Complete Re-root
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.

twistedumbrella said:
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
Click to expand...
Click to collapse
Ahh I gotcha. Well that's good to know. I haven't had a chance to really look at many of the files yet. Do you know if nvidia released the factory recovery packages yet?
EDIT:
Nevermind looks like 72 is out now.

Yeah, they are pretty good about that. It may be nearing the last update for this version, though

hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?

NapalmDawn said:
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
Click to expand...
Click to collapse
Exactly

twistedumbrella said:
Exactly
Click to expand...
Click to collapse
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?

NapalmDawn said:
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
Click to expand...
Click to collapse
The OTA will restore the stock recovery. This way updates it to one compatible with KitKat.

KitKat Update Without Complete Re-root
OTA 98 has been added. No recovery update is needed coming from 72. Flash the build and SuperSU and off you go. No data wipe necessary, either.

Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.

Neoistheone2000 said:
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Click to expand...
Click to collapse
Updated

twistedumbrella said:
Updated
Click to expand...
Click to collapse
Thanks, that worked a treat

Yeah, to clarify, in recovery, you must press and hold Shield and Home buttons for a second, then release to bring up the menu. Then use X and Y to navigate, A to select. Don't understand why the bootloader or recovery don't use the D-pad at all. They're weird. Anyway, downloading this now, and will report back in a few minutes. This is just sideloaded via the stock recovery, right? I hope so, that's how I'm doing it right now.
EDIT: Nope. Failed again.
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I think I'll try that new recovery (funny, because I had flashed the one included in the original update archive, still had issues). I shouldn't have to use that one, I was on update 92 already.
EDIT 2: Oh, I'm dumb. Here I thought this was still being done with the STOCK recovery. Didn't realize this would flash in CWM. Awesome. Flashed SuperSU 2.16 while I was at it. Rebooted, and it's at .98, with root access. You ROCK, @twistedumbrella!

Did you do this with update 99 yet? Just came out today.

GuyInDogSuit said:
Did you do this with update 99 yet? Just came out today.
Click to expand...
Click to collapse
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.

twistedumbrella said:
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
Click to expand...
Click to collapse
Hmmm. It started downloading as soon as I turned mine on. I'm just gonna do the usual process.

[Q] OTA Updates on Rooted XT1095 (Stock Recovery)

I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?

Dan Again said:
I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?
Click to expand...
Click to collapse
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.

grneyez said:
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.
Click to expand...
Click to collapse
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?

If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.

Dan Again said:
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?
Click to expand...
Click to collapse
As long as you don't make any changes to /system, you *should* be good to go for updates. If you didn't intentionally flash a custom recovery then you still have the stock one.

If you're rooted OTAs won't work. In KitKat and lower they just performed checksums on each file before updating, so the altered root files were left untouched and the update installed. In Lollipop and up (at least for Nexus devices), it does a total checksum and if /system has been altered in any way (including for root) OTA's won't install.

grneyez said:
If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.
Click to expand...
Click to collapse
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?

Dan Again said:
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?
Click to expand...
Click to collapse
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery

juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?

Dan Again said:
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?
Click to expand...
Click to collapse
You can always flash a ROM or custom ROM via fast boot, but you will loss all your settings, apps etc because you are flashing an entire new system... The OTA only patches

The only way back is to flash your stock ROM if you can get a hold of it.

floepie said:
The only way back is to flash your stock ROM if you can get a hold of it.
Click to expand...
Click to collapse
So, funny story - this weekend I accidentally wiped my OS and had to flash stock ROM to get back up and running. See: here. Good resource for others who might be looking for Moto X 2014 stock Lollipop firmware...definitely saved that on my computer

juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?

yurkennis said:
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?
Click to expand...
Click to collapse
yes
just flash via fastboot
1. recovery (stock)
2. system
if your phone is 5.0 xt1095 and you didn't flash modems you should be able to receive OTA.

Repeat of Question
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!

jhworth8 said:
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!
Click to expand...
Click to collapse
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk

AGISCI said:
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?

summit15 said:
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?
Click to expand...
Click to collapse
Correct, it won't erase those things.
Sent from my XT1095 using Tapatalk

so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?

yamahakid said:
so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?
Click to expand...
Click to collapse
It's more difficult with Lollipop: updates now "look for" a completely stock unmodified unrooted system. So you'll have to flash a stock image of the current build and then take the OTA.

[Q] Need stock recovery !

i need to do OTA update , already with twrp and root , so in order to do ota update i need to fastboot stock recovery !
upload a stock recovery.img if anybody having it.

download shamu image , extract to get the recovery.IMG

It's a Nexus load what you wish. Images here :
https://developers.google.com/android/nexus/images#shamu
Sent from my Google N6 on VZ

yes i know that , i thought rather downloading whole image if somebody could provide me the recovery image only well thanks. ill do it.

ashupulse said:
yes i know that , i thought rather downloading whole image if somebody could provide me the recovery image only well thanks. ill do it.
Click to expand...
Click to collapse
It needs to be more than just "stock recovery". It needs to be the exact version the ota will expect. So you'll have to download the matching image to your version you're on now...
Which if you're doing that, hadn't you just as well download the latest 5.1 image and just flash all that?

I would just flash the factory image..... less chance of a mess....

Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data

mymusicathome said:
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
Click to expand...
Click to collapse
I hear you. if anything, back in the days, we used to avoid the OTA. I'm not sure why everybody has such a hard on for it.
Sent from my Google N6 on VZ

Only ota I took was when my n5 forced one on me out of the box. Never intentionally took one since android 1.5

recovery from 5.0.1
rootSU said:
It needs to be more than just "stock recovery". It needs to be the exact version the ota will expect. So you'll have to download the matching image to your version you're on now...
Which if you're doing that, hadn't you just as well download the latest 5.1 image and just flash all that?
Click to expand...
Click to collapse
yes you are right actually i downloaded 5.1 exctracted recovery , flashed via fastboot.... and i hit error.
so lesson is recovery from 5.0.1 is needed.

ashupulse said:
yes you are right actually i downloaded 5.1 exctracted recovery , flashed via fastboot.... and i hit error.
so lesson is recovery from 5.0.1 is needed.
Click to expand...
Click to collapse
How are you flashing?

mymusicathome said:
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
Click to expand...
Click to collapse
When updated to 5.1 from 5.0.1 -- I had to do Factory Data Reset, since after update N6 was showing 32GB instead of 64GB.
Was there a way to avoid Factory Data Reset ? Thank you!

[Q] 5.1.1. OTA Update Error

My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.

I downloaded the factory image and fastboot flashed the files.
Sent from my Nexus 6 using Tapatalk

Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
What error? Also, have you unencrypted?

Evolution_Tech said:
What error? Also, have you unencrypted?
Click to expand...
Click to collapse
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.

Shift2win said:
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.
Click to expand...
Click to collapse
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.

Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
Mine is doing the exact same, I'm also stock and on T-Mobile.

^same here...rooted and T-Mobile.

skipm said:
Mine is doing the exact same, I'm also stock and on T-Mobile.
Click to expand...
Click to collapse
n7plus1 said:
^same here...rooted and T-Mobile.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61119896

Evolution_Tech said:
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.
Click to expand...
Click to collapse
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?

neudof said:
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?
Click to expand...
Click to collapse
Fastboot. You need an unlocked bootloader.

I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.

robert_shipley said:
I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.
Click to expand...
Click to collapse
That's exactly my problem, I'm completely stock and have to remain that way since I use my phone at work and they require the AirWatch MDM agent to be installed. I even tried deactivating AirWatch and uninstalling it and I still couldn't get the update to install. I hope there is some way they can either erase and download the update again or just overwrite the current one because this one definitely has problems.

Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.

bchildress said:
Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.
Click to expand...
Click to collapse
Just flash the system image. No need to flash everything. If you've unencrypted, then flash boot image too.

I have the same problem totaly stock, not rooted, untouched! I have the same error. I have 64 gb nexus 6 build number LMY47D.

Ok Guys,
Here is the solution,
1. Download stock image from google developer page, https://developers.google.com/android/nexus/images
2. Flash with long way;' DONT USE FLASH-ALL SCRIPT' (I tried, update fails again)
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
fastboot flash cache C:/image-shamu-XXXXXX/cache.img
(FOR FURTHER INFO PLS SEE THE PAGE; http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008)
3. Just turn on your N6 and it will find update and will be succesfull this time

Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.

Evolution_Tech said:
Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.
Click to expand...
Click to collapse
Hey,
I am Rooted with TWRP Recovery and Elemental X custom kernel, still encrypted with unlocked bootloader. I got the OTA (LMY47Z) notification and I have got the Factory Image as well as the OTA Zip. Can you guide me as to how can I update my Nexus (currently LMY47I) to 5.1.1 without losing any data?
Thanks.

The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
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
So better to do it with the OTA.

peerpower said:
The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
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
So better to do it with the OTA.
Click to expand...
Click to collapse
Download the OTA Zip, Extract it and check the "\META-INF\com\android\otacert" file to find the version number for your phone.

Keep booting into TWRP after Android 7.0

I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?

Boot into bootloader from recovery and select start.

prestige777 said:
Boot into bootloader from recovery and select start.
Click to expand...
Click to collapse
Yeah but it still can't install the update,any way fix it?

Boot to bootloader and flash the stock recovery from factory image. Then boot into stock recovery and the update should start.

The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu

dahawthorne said:
The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu
Click to expand...
Click to collapse
May I ask which version of TWRP did you use?

twrp-3.0.2-0-shamu.img

you cant flash an official factory image in twrp..this is a known fact...

Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.

dahawthorne said:
Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.
Click to expand...
Click to collapse
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.

It seems that people don't read posts before writing. The OP clearly said that he had applied the OTA. I clearly said that this was exactly what I did with the same result. I also clearly explained what I did to fix it. The next comment should be from the OP saying what he's doing to recover. If he does what I did he'll be fine.

drmuruga said:
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.
Click to expand...
Click to collapse
He can reinstall stock recovery and side load from there
Either flash the stock recovery.img through twrp or
Flash stock recovery through fastboot or
Install factory image through fastboot
Edit: oops didn't read the entire thread

itsagood said:
I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?
Click to expand...
Click to collapse
To avoid issues, I'd say make sure you're 100% stock, recovery and all before installing an official update. Like I said, just to be sure it won't fail.

I got the the OTA notification before work yesterday. All day at work I was itching to install it but with no PC I couldn't risk it. I was on the DP5 with TWRP, no root, and unlocked. I couldn't wait. I flashed the OTA with TWRP after I restored a backup of when I first installed DP5. TWRP throw a couple of errors but after about 10 minutes of hanging on the boot animation it finally booted. My phone was encrypted but other then that it was fine. I was gonna root it afterwards but I was on stock recovery after flashing the OTA so I couldn't do anything until I got home. Made a noforc-nonverify boot IMG throw on TWRP reformatted. Running great now.
Edit: My DP5 boot.img was also noforc-nonverify.
Sent from my Nexus 6

Database Develop

welcome