Database Develop

[Q] Bricked my Moto X - can I resurrect it?

My Moto X now refuses to boot. With stock recovery it'll get past the bootloader, then blink an image of a dead android with the message "Error" briefly, and keep doing so every ~10 seconds. If I flash TWRP, any attempt to boot takes me to TWRP, with log messages reading "unable to mount..." for a bunch of partitions (/data, /cache, storage, etc.)
Can I recover my device?
The short sequence of events: I rooted my phone (T-Mobile phone, unlocked it via Motorola's website) and installed TWRP. Later I tried to accept the 4.4.2 OTA update, but the phone wouldn't take the update, because TWRP. Flashed stock recovery tried again, got stuck in bootloop. Tried flashing back the 4.4 / 140.44.3 images from here, now I'm stuck with a blinking error message.
I see there are a bunch of image files bundled into the 4.4.2 / 161.44.25 update - would flashing those do any good?

What version is your bootloader?

Steve-x said:
What version is your bootloader?
Click to expand...
Click to collapse
Version 30.B2.

OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!

Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Fast boot erase cache should work . its trying to flash the it's ,so you need to delete the cache where the ota file downloaded to
Sent on my Gummy running Lenoto X

so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
that is the file you need to flash with RSD Lite or Fastboot and it should get you 100% back up and running.
But then if you want to go to 4.4.2 after you flash the firmware before you add anything or install TWRP just update the phone to 4.4.2 then install the custom recovery and SuperSU.

Steve-x said:
OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!
Click to expand...
Click to collapse
I have tried both RSD Lite, and applying all of the commands from the XML file manually, following the directions from here. Both ways, I still get the blinking error message

The "can't mount..." log messages I get if I flash back to TWRP suggest it could be some sort of partitioning problem, but I'm not sure how to diagnose that.

And the flashing of all files completes successfully?

Steve-x said:
And the flashing of all files completes successfully?
Click to expand...
Click to collapse
I could have sworn that I wasn't getting any errors previously. Now, however, after trying to flash system.img (making sure to use mfastboot, of course), I get an error on the phone, "sp space is not enough". Not sure what it means, and Googling around doesn't turn up any answers.

dray_jr said:
so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
Click to expand...
Click to collapse
Yep, that's exactly what I flashed. Made sure the md5sum matched my download and everything.
flashallthetime said:
Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Click to expand...
Click to collapse
Yep, cleared the cache, no luck

Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.

So I guess more warnings into my noobs guide to accept an ota thread
Maybe I should put a notice not to accept the ota and only flash your carriers sbf firmware when available?
Sent on my Gummy running Lenoto X

Steve-x said:
Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.
Click to expand...
Click to collapse
Code:
C:\Users\spiffytech\Documents\sdk\platform-tools>fastboot erase system
(bootloader) Variable not supported!
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.101s

Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.

spiffytech said:
Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.
Click to expand...
Click to collapse
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X

flashallthetime said:
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'll go with that plan What is it that makes flashing from sbf safer?

So if you perform a full factory reset the phone will boot up normally now? If that is the case then I don't see any problem with accepting the OTA to 4.4.2.

Help PLZ
I had the exact same problem as OP, took the same course of action, and got a successful boot. I do some minimal stuff, check if everything is working, turn on dev mode, etc. I put in my wifi password.
I wanted to check if my bootloader was back to stock, so I turned off my device, and then tried to power on. Pressing the power button does nothing.
So I get into fastboot, and select factory (reset) again. It boots up, but it doesn't seem like it actually did a factory reset, because it automatically connected to my wifi..
Have you any idea what's going on, and how perhaps to solve this weird dilemna?
EDIT: I'm not sure if I actually did anything, but after a couple reboots it just started working normally. I installed the update to 4.4.2 and everything is smooth thus far.

Eventually the phone prompted me to apply the 4.4.2 update so often the phone was actually unusable - it'd go back to the "do you want to update?" screen as soon as I backed out of it. I was thus forced to apply it OTA. Fortunately, the update went through fine this time, and my phone continues to work fine
Thanks for your help, folks!

[Q] [STOCK] Flashed the Update (5.1) - Phone Won't Boot

I am 100% stock.
I did the update using Minimal ABD and Fastboot. Once that was finished, the phone booted up (after optimizing all my apps) and gave me a System UI error and would never get past that (even if I hit OK or Report). I turned it off and then went it came back on, it went straight to the Google Logo. It didn't even vibrate like it usually does when it boots up.
If I hold down all 3 buttons, it will boot to the bootloader screen, but anything I do from there, just goes back to the Google logo and that's it. I had to go to Recovery and get another error, then hit power + volume up, and I did a factory wipe. However, after that, it still does the same thing. Goes to the Google Logo and nothing else. I've wiped it a few times now and no luck.
Any suggestions on what to do?

Which ROM did you flash? There is no 5.1 factory image at the moment. If you are flashing through ADB, try manually erasing then flashing each file first instead of using flash-all. Don't forget to flash userdata.
edit: Didn't realize update file was sent out through OTA. Try flashing factory 5.0.1 then flash the update which is in the cache folder. Extract and save that 5.1 OTA file somewhere else before flashing 5.0.1, if not its gone. Best suggestion is to wait go back to 5.0.1 and wait for 5.1 factory image.

DevilMR said:
Which ROM did you flash? There is no 5.1 factory image at the moment. If you are flashing through ADB, try manually erasing then flashing each file first instead of using flash-all. Don't forget to flash userdata.
Click to expand...
Click to collapse
Sorry, no ROM, just the OTA.zip I tried. I used it from here: (can't link) but AndroidPolice FLASH ALL THINGS post

mikebio said:
Sorry, no ROM, just the OTA.zip I tried. I used it from here: (can't link) but AndroidPolice FLASH ALL THINGS post
Click to expand...
Click to collapse
Most likely going to have to download the 5.0.1 factory image and reflash that if you didn't make a backup before doing the OTA.
I'm assuming you don't have a 3rd party recovery since your title says "STOCK" correct?

meest said:
Most likely going to have to download the 5.0.1 factory image and reflash that if you didn't make a backup before doing the OTA.
I'm assuming you don't have a 3rd party recovery since your title says "STOCK" correct?
Click to expand...
Click to collapse
This is correct. I also can't get my computer to recognize my Nexus anymore. Any tips on that?

OK, i see what you did. Try flashing factory 5.0.1, then flash that 5.1 update. I rather wait for factory 5.1.

DevilMR said:
OK, i see what you did. Try flashing factory 5.0.1, then flash that 5.1 update. I rather wait for factory 5.1.
Click to expand...
Click to collapse
Will do. Do you know the exact USB driver I need for nexus 6? When I plug it into my computer now, it comes up Shamu and I can't get the phone to be recognized by Nexus Root Toolkit or Minimal ADB & Fastboot
Nevermind, got it... I am going to reflash factory image... I tried 5.0.1 and it failed.

mikebio said:
Will do. Do you know the exact USB driver I need for nexus 6? When I plug it into my computer now, it comes up Shamu and I can't get the phone to be recognized by Nexus Root Toolkit or Minimal ADB & Fastboot
Click to expand...
Click to collapse
If I remember right I just downloaded the google driver pack and pointed windows to that directory and it found one.
http://developer.android.com/sdk/win-usb.html

meest said:
If I remember right I just downloaded the google driver pack and pointed windows to that directory and it found one.
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
The issue is, it comes up Fastboot Shamu and it isn't recognized. Only when I put in into Apply update from ADB does it show up Nexus 6 on Windows... Not sure what to do. I can't flash right now because of this.

Mismatching build numbers when flashing Stagefright update

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.

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.