Database Develop

[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.

[Q] 5.1.1 OTA while rooted?

I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!

greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919

Evolution_Tech said:
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919
Click to expand...
Click to collapse
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?

greycobalt said:
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?
Click to expand...
Click to collapse
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.

greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi hi. Made me smile. Thanks for that.

Evolution_Tech said:
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.
Click to expand...
Click to collapse
I will definitely do this! Thanks. They haven't posted the Verizon 5.1.1 to the image site yet, so I'll have to wait a bit I guess. :-/ Thanks!
Didgeridoohan said:
Hi hi. Made me smile. Thanks for that.
Click to expand...
Click to collapse

N6 won't boot stuck in Google boot screen

I somehow managed to soft brick my N6 using NRT to flash 6.0 factory image. At the time, N6 was stock no root. It will not boot past the Google boot screen. I have tried factory/data reset, clearing cache, and manually flashing fastboot files which fail at system.img during process...I l am also getting a "target reported max download of 5326722560 bytes" message prior to every file flash but it seems to complete. I currently can boot into bootloader and customer recovery....no OS loaded at the moment. Any assistance would be greatly appreciated...
Nexus 6 XT1103 64GB

nexus 6
dray said:
i somehow managed to soft brick my n6 using nrt to flash 6.0 factory image. At the time, n6 was stock no root. It will not boot past the google boot screen. I have tried factory/data reset, clearing cache, and manually flashing fastboot files which fail at system.img during process...i l am also getting a "target reported max download of 5326722560 bytes" message prior to every file flash but it seems to complete. I currently can boot into bootloader and customer recovery....no os loaded at the moment. Any assistance would be greatly appreciated...
Nexus 6 xt1103 64gb
Click to expand...
Click to collapse
i have the same problem . I tried nrt and cannot get the bootloader to unlock, only thing is i am rooted. No os loaded at the time either on teamwin.

dray said:
I somehow managed to soft brick my N6 using NRT to flash 6.0 factory image. At the time, N6 was stock no root. It will not boot past the Google boot screen. I have tried factory/data reset, clearing cache, and manually flashing fastboot files which fail at system.img during process...I l am also getting a "target reported max download of 5326722560 bytes" message prior to every file flash but it seems to complete. I currently can boot into bootloader and customer recovery....no OS loaded at the moment. Any assistance would be greatly appreciated...
Nexus 6 XT1103 64GB
Click to expand...
Click to collapse
Whats the system.img failure? Is it that it's too big? If so, your fastboot is out of date Update it to the latest.
drizzel57 said:
i have the same problem . I tried nrt and cannot get the bootloader to unlock, only thing is i am rooted. No os loaded at the time either on teamwin.
Click to expand...
Click to collapse
Nothing you can do. Send it for repair. There is no fix.

Ok I followed this tutorial to a tee and it worked like a champ:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

drizzel57 said:
i have the same problem . I tried nrt and cannot get the bootloader to unlock, only thing is i am rooted. No os loaded at the time either on teamwin.
Click to expand...
Click to collapse
My situation was a little different...I managed to unlock bootloader and load custom recovery before things went a little wonky

dray said:
Ok I followed this tutorial to a tee and it worked like a champ:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I nay have jut foudn the culperate, i flashed the ewer 7.1.1 onto my ohne afte factory resttubg then i rebooted anyeverthing was greatso i decided to go back int recovery and fkash thaoks for the 7.1.1 ans the enwest auperau 79, or whicher its at now

Valhalla875 said:
I nay have jut foudn the culperate, i flashed the ewer 7.1.1 onto my ohne afte factory resttubg then i rebooted anyeverthing was greatso i decided to go back int recovery and fkash thaoks for the 7.1.1 ans the enwest auperau 79, or whicher its at now
Click to expand...
Click to collapse
Wow dude... Now that was one hell of a hard to read post...

5.1 said:
Wow dude... Now that was one hell of a hard to read post...
Click to expand...
Click to collapse
You instantly made me laugh. I almost forgot about looking a solution for my problem

Corrupt Message after Dirty Stock Flash - MRA58K to MRA58N

I am fully stock since MRA58K came out. I applied the security update today via the factory images but left user data alone. I am now getting the Corrupt Message during Boot. I accidentally booted TWRP 2.8.7.1 from Fastboot but did not flash it. Just selected reboot. Any Ideas on ways to get rid of it without a factory reset?

what's the exact message?

jj14 said:
what's the exact message?
Click to expand...
Click to collapse
Sorry, I thought it was inherently known with the phrase corrupt during boot. But this with the Red Status
https://support.google.com/nexus/answer/6185381?p=verified_boot

GMoGoody said:
Sorry, I thought it was inherently known with the phrase corrupt during boot. But this with the Red Status
https://support.google.com/nexus/answer/6185381?p=verified_boot
Click to expand...
Click to collapse
So your device is still booting ok . That message shows up if your device is rooted or has some other changes (recovery perhaps).
If you want to stay stock, just reflash the factory images using fastboot (all files skip userdata)

jj14 said:
what's the exact message?
Click to expand...
Click to collapse
jj14 said:
So your device is still booting ok . That message shows up if your device is rooted or has some other changes (recovery perhaps).
If you want to stay stock, just reflash the factory images using fastboot (all files skip userdata)
Click to expand...
Click to collapse
Which I have tried three times and I am still getting this message. The second and third time I tried Flashing MRA58N over itself it did not optimize or anything. I guess I will wait for the next security update, or flash back to MRA58K reboot and try flashing MRA58N again

Did you flash everything? bootloader/boot/recovery/system/radio/cache? (reboot bootloader after flashing radio and bootloader)

flash a custom kernel and it should go away

GMoGoody said:
.>....... the Corrupt Message during Boot. I accidentally booted TWRP 2.8.7.1 from Fastboot but did not flash it. Just selected reboot. Any Ideas on ways to get rid of it without a factory reset?
Click to expand...
Click to collapse
Flash a custom kernel like Franco's kernel

jj14 said:
Did you flash everything? bootloader/boot/recovery/system/radio/cache? (reboot bootloader after flashing radio and bootloader)
Click to expand...
Click to collapse
Yes I flashed everything but the userData even though some things like the radio and bootloader didn't change

Strange. Hopefully somebody else will chime in.

NLBeev said:
Flash a custom kernel like Franco's kernel
Click to expand...
Click to collapse
I want to use android Pay. So I am staying stock. I am trying to figure out why this message suddenly started appearing between MRA58K and MRA58N. If Others are seeing it and potentially how to recover from this state with staying stock but not doing a factory reset. Seems like factory reset may be in order

jj14 said:
Strange. Hopefully somebody else will chime in.
Click to expand...
Click to collapse
My thoughts exactly. When I get home from work I will go back to MRA58K , reboot, then reflash MRA58N. Hopefully this fixes the issue. I will report back tonight. In other threads I saw people were having to go all the way back to 5.1.1 when they saw this when first upgrading to MRA58K
Edit:
This worked. I flashed back to MRA58K, Let it optimize, Verified no corrupt message. then Flashed MRA58N and did the same. So far so good. Also note there is an update to platform-tools in the SDK

GMoGoody said:
I want to use android Pay. So I am staying stock. I am trying to figure out why this message suddenly started appearing between MRA58K and MRA58N. If Others are seeing it and potentially how to recover from this state with staying stock but not doing a factory reset. Seems like factory reset may be in order
Click to expand...
Click to collapse
I think it has to do with TWRP. You used it temporary with fastboot, but it is pushed to the phone's memory. You could try to fastboot flash stock recovery.

SOLVED
I'm getting the same as OP. flashed manually bl/reboot/radio/reboot/system/boot/recovery/cache then tried again with a fresh D/L through Wug's NRT. No joy. Maybe there is something different between the OTA and factory image that would require a data wipe with the latter. Is there an OTA in the wild that I could dissect? Also having bluetooth problems after dirty flashing MRA58N as stated above.
EDIT: Flashed back MRA58K, all is better.
Also noted that after flashing MRA58N the cache didn't rebuild. Hmmm.
SOLUTION: Update platform-tools in your SDK. Just updated and manually dirty flashed, no corrupt message and app cache is rebuilding. :good:

6.0.1 Update Download and Sideload Failed to Install--Why?

My SIM-less Nexus 6 (which I'd previously flashed to MRA58X from 58K using the Wugfresh NRT) got the download notification re. the 6.0.1 update last night. It got that notification 3X, and the install failed each time. My attempts to sideload the OTA link version to MMB29K from MRA58X also failed multiple times, evidently because of a "non-standard" release key. Here's the error message:
Package expects build fingerprint google/shamu/shamu:6.0/mra58x/2353551: user/release-keys or google/shamu/shamu:6.0.1/mmb29k/2419427:user/release-keys;
this device has google/shamu/shamu:6.0/mra58k/2256973:user/release-keys
Error in @/cache/recovery/block.map (Status 7)
Right now, I really just want to know a couple of things:
What's a release key?
Why would my MRA58X phone be using a 58K release key?
Is there any way to find out if my now MMB29K phone is also using a "bad" release key?
It's an unrooted and unlocked Nexus 6. The only modification-like thing that I've done to it is flash factory images to it using the Wugfresh NRT. I flashed it from LYZ28N to MRA58K , from MRA58K to MRA58X (after T-Mobile approved the X build), and finally from MRA58X to MMB29K.

well, if your system is moddified in any way, it will always fail. moddified does not only include root. you can always flash the factory image, not ota.

Can you flash a factory image over the top of a rooted 6.0? Or do you have to wipe first?
I'm kinda bummed lately, i just want to keep my root for adblock, but keeping the phone up to date is more of a chore than i remember back in the earlier nexus days.

propain4444 said:
Can you flash a factory image over the top of a rooted 6.0? Or do you have to wipe first?
I'm kinda bummed lately, i just want to keep my root for adblock, but keeping the phone up to date is more of a chore than i remember back in the earlier nexus days.
Click to expand...
Click to collapse
Just flash the factory image (no need to do any wipe).

I too am having trouble updating to 6.0.1 with root/ custom kernel. I am flashing factory image via fastboot but fails everytime flashing system image. "unknown error" I feel like a dang noob...lol

dray said:
I too am having trouble updating to 6.0.1 with root/ custom kernel. I am flashing factory image via fastboot but fails everytime flashing system image. "unknown error" I feel like a dang noob...lol
Click to expand...
Click to collapse
unzip the factory image, then flash each part separately. flash-all is broken.

simms22 said:
unzip the factory image, then flash each part separately. flash-all is broken.
Click to expand...
Click to collapse
I'm sorry I should have been more clear. Yes that is what I am doing. Unzipped and flashing manually. Everything flashes just fine except system.img ?

dray said:
I'm sorry I should have been more clear. Yes that is what I am doing. Unzipped and flashing manually. Everything flashes just fine except system.img ?
Click to expand...
Click to collapse
odd. thats tne way it always works, since flash-all is broken.

simms22 said:
odd. thats tne way it always works, since flash-all is broken.
Click to expand...
Click to collapse
Yeah IDK WTH is going on. I'm at a loss.

dray said:
I'm sorry I should have been more clear. Yes that is what I am doing. Unzipped and flashing manually. Everything flashes just fine except system.img
Click to expand...
Click to collapse
Update fastboot to the new one. The system img is too big for the old one.

istperson said:
Update fastboot to the new one. The system img is too big for the old one.
Click to expand...
Click to collapse
Yes good idea I will try this. Where do I get the updated fastboot files?

Well, I feel better knowing that I'm clearly not the only one who's clueless about release keys and their connection to OS updates.