Database Info

Stock, rooted...cannot install 4.4.1. WHY???

I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.

velveteen71 said:
I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.
Click to expand...
Click to collapse
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.

If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.

Synyster06Gates said:
If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.
Click to expand...
Click to collapse
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!

desucca said:
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!
Click to expand...
Click to collapse
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701

Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.

Synyster06Gates said:
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
*update* worked! thanks very much, it's updating right now.

desucca said:
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
Click to expand...
Click to collapse
I was the same as you. I had to flash stock boot.img and system.img for it to work. I only tried Bricked but went back to stock and at one point I tried Xposed. Guess one of them left a trace.
Sent from my Nexus 5 using xda app-developers app

david23c said:
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.
Click to expand...
Click to collapse
This. What did you modify in your build.prop? Revert to your backed up original build.prop (.bak), install a new stock build.prop, or flash system.img.

Nitemare3219 said:
Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.
Click to expand...
Click to collapse
you should flash boot.img and system.img to make sure you have a stock system partition.

david23c said:
you should flash boot.img and system.img to make sure you have a stock system partition.
Click to expand...
Click to collapse
i have the same problem, does flashing these files affect any of my data or configuration?

cannot update rooted nexus?
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?

Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!

gaurishmhatre said:
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?
Click to expand...
Click to collapse
Yes you can. I flashed the OTA in CWM after undoing the changes I'd made and it flashed fine without losing data

lowlow2 said:
Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!
Click to expand...
Click to collapse
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
chucky8 said:
i have the same problem, does flashing these files affect any of my data or configuration?
Click to expand...
Click to collapse
No, your data and configuration will be fine.

Synyster06Gates said:
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
No, your data and configuration will be fine.
Click to expand...
Click to collapse
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
Click to expand...
Click to collapse
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks

lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks
Click to expand...
Click to collapse
You should be able to just edit it back to original configuration.

Synyster06Gates said:
You should be able to just edit it back to original configuration.
Click to expand...
Click to collapse
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!

lowlow2 said:
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!
Click to expand...
Click to collapse
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701

Synyster06Gates said:
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
thanks!!

[Q] 4.4.3 update

I'm rooted and have S-off and have twrp for my recovery and the OTA downloaded to my phone and set it to update in a couple hours and im wondering if this is going to mess anything up if it updates? Im completely stock btw. If it is going to mess my root/s-off is there any way to stop it other than installing a rom?

tdc0z10 said:
I'm rooted and have S-off and have twrp for my recovery and the OTA downloaded to my phone and set it to update in a couple hours and im wondering if this is going to mess anything up if it updates? Im completely stock btw. If it is going to mess my root/s-off is there any way to stop it other than installing a rom?
Click to expand...
Click to collapse
It cannot flash on twrp. Did you mess with your rom other than rooting it?

dottat said:
It cannot flash on twrp. Did you mess with your rom other than rooting it?
Click to expand...
Click to collapse
No i havent flashed a rom or and mods since iv had it rooted/s-off. I delayed to update until 9:00Pm eastern, so it wont update since i have twrp?

tdc0z10 said:
No i havent flashed a rom or and mods since iv had it rooted/s-off. I delayed to update until 9:00Pm eastern, so it wont update since i have twrp?
Click to expand...
Click to collapse
So you will want to flash stock recovery back to the phone. Let it update. Then flash the newest twrp in fastboot. Then boot to Twrp and flash su.zip

dottat said:
So you will want to flash stock recovery back to the phone. Let it update. Then flash the newest twrp in fastboot. Then boot to Twrp and flash su.zip
Click to expand...
Click to collapse
can i just flash a rom to stop the update? if i cant flash stock recovery and the update goes through what is going to happen?

tdc0z10 said:
I'm rooted and have S-off and have twrp for my recovery and the OTA downloaded to my phone and set it to update in a couple hours and im wondering if this is going to mess anything up if it updates? Im completely stock btw. If it is going to mess my root/s-off is there any way to stop it other than installing a rom?
Click to expand...
Click to collapse
I just got done flashing the new OTA. I kept S-Off and bootloader unlock. In order to do this, you will need to flash stock recovery.
Flash stock recovery
Download 4.4.3 OTA in About > Software update > Check new
Install update
Reboot
Boot into bootlader and flash TWRP 2.8
Root
Just make sure you're S-Off and bootloader unlocked before you take the new OTA.

Andrew C said:
I just got done flashing the new OTA. I kept S-Off and bootloader unlock. In order to do this, you will need to flash stock recovery.
Flash stock recovery
Download 4.4.3 OTA in About > Software update > Check new
Install update
Reboot
Boot into bootlader and flash TWRP 2.8
Root
Click to expand...
Click to collapse
do you have a link for the stock recovery?

tdc0z10 said:
do you have a link for the stock recovery?
Click to expand...
Click to collapse
So just flashing a ROM wont do any good? im not at my computer to flash stock,but i do have a custom rom on my phone i can flash if that would stop the update from going through. if not then i guess im stuck with letting it go through? is my phone going to go into boot loop?

tdc0z10 said:
do you have a link for the stock recovery?
Click to expand...
Click to collapse
Stock recovery
---------- Post added at 05:13 PM ---------- Previous post was at 05:07 PM ----------
tdc0z10 said:
So just flashing a ROM wont do any good? im not at my computer to flash stock,but i do have a custom rom on my phone i can flash if that would stop the update from going through. if not then i guess im stuck with letting it go through? is my phone going to go into boot loop?
Click to expand...
Click to collapse
You won't be able to flash the OTA with a custom recovery. You have to have un-modified stock ROM and stock recovery.

Andrew C said:
Stock recovery
---------- Post added at 05:13 PM ---------- Previous post was at 05:07 PM ----------
You won't be able to flash the OTA with a custom recovery. You have to have un-modified stock ROM and stock recovery.[/QUOTE
I really dont want the OTA i just dont want it to do anything to my phone if it does update.
Click to expand...
Click to collapse

tdc0z10 said:
Andrew C said:
Stock recovery
---------- Post added at 05:13 PM ---------- Previous post was at 05:07 PM ----------
You won't be able to flash the OTA with a custom recovery. You have to have un-modified stock ROM and stock recovery.[/QUOTE
I really dont want the OTA i just dont want it to do anything to my phone if it does update.
Click to expand...
Click to collapse
Download m8vzw_OTA-Killer.zip | m8vzw_OTA-Killer.zip in this thread then. be sure to thank the OP of that thread.
Click to expand...
Click to collapse

I'm having trouble getting root back. I was attempting to flash supersu using TWRP, and it says it's successful but when I go to my apps list it's not there. Any suggestions on what I'm doing wrong? I'm S-Off still after I took the 4.4.3 OTA.
Andrew C said:
I just got done flashing the new OTA. I kept S-Off and bootloader unlock. In order to do this, you will need to flash stock recovery.
Flash stock recovery
Download 4.4.3 OTA in About > Software update > Check new
Install update
Reboot
Boot into bootlader and flash TWRP 2.8
Root
Just make sure you're S-Off and bootloader unlocked before you take the new OTA.
Click to expand...
Click to collapse

dmdobson88 said:
I'm having trouble getting root back. I was attempting to flash supersu using TWRP, and it says it's successful but when I go to my apps list it's not there. Any suggestions on what I'm doing wrong? I'm S-Off still after I took the 4.4.3 OTA.
Click to expand...
Click to collapse
Try downloading SuperSU from the market and installing from there.

Andrew C said:
Try downloading SuperSU from the market and installing from there.
Click to expand...
Click to collapse
Is it safe to update the binary the "normal" way, it recommends using TWRP.
Edit: excellent, that worked great. Got my root back, xposed framework updated, now I'm back to where I was but with the new 4.4.3 update.

dmdobson88 said:
Is it safe to update the binary the "normal" way, it recommends using TWRP.
Edit: excellent, that worked great. Got my root back, xposed framework updated, now I'm back to where I was but with the new 4.4.3 update.
Click to expand...
Click to collapse
I'm glad you got it working!

OTA hanging with stock recovery
I have reverted back to stock recovery (file downloaded from the link in this threat) but the OTA is still not working. After downloading, the update begins and I see the small icon of the phone with a green update symbol (two circular arrows). The green progress bar starts up, but then in a minute, it stops and the screen immediately jumps back to the stock recovery screen (phone icon with red triangle and exclamation point).
The process has run three times with the same result.
Can someone verify the md5sum of the stock_recovery.img file is d296a9a7289e10b2f04983e07409ee6c
Any ideas?

nachoport said:
I have reverted back to stock recovery (file downloaded from the link in this threat) but the OTA is still not working. After downloading, the update begins and I see the small icon of the phone with a green update symbol (two circular arrows). The green progress bar starts up, but then in a minute, it stops and the screen immediately jumps back to the stock recovery screen (phone icon with red triangle and exclamation point).
The process has run three times with the same result.
Can someone verify the md5sum of the stock_recovery.img file is d296a9a7289e10b2f04983e07409ee6c
Any ideas?
Click to expand...
Click to collapse
Not being on a completely unmodified stock HTC ROM is usually the case. Other than that this worked for me with no issues.

nachoport said:
I have reverted back to stock recovery (file downloaded from the link in this threat) but the OTA is still not working. After downloading, the update begins and I see the small icon of the phone with a green update symbol (two circular arrows). The green progress bar starts up, but then in a minute, it stops and the screen immediately jumps back to the stock recovery screen (phone icon with red triangle and exclamation point).
The process has run three times with the same result.
Can someone verify the md5sum of the stock_recovery.img file is d296a9a7289e10b2f04983e07409ee6c
Any ideas?
Click to expand...
Click to collapse
Have you modified any system files or froze any stock apps?

dottat said:
Have you modified any system files or froze any stock apps?
Click to expand...
Click to collapse
Crap, I can't even remember if I have messed with any of the stock apps. I've been into this device in so many ways in a short period of time. I'll have to dig deep into my memory... Thanks for the suggestion!

nachoport said:
Crap, I can't even remember if I have messed with any of the stock apps. I've been into this device in so many ways in a short period of time. I'll have to dig deep into my memory... Thanks for the suggestion!
Click to expand...
Click to collapse
Same I was trying to tell you, you're welcome

Nexus 5 with "TeamWin" failed update - and won't start again

Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!

Fablus said:
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Click to expand...
Click to collapse
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.

Mysticodex said:
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Click to expand...
Click to collapse
Maybe we need http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865?
Gosh, this used to be so easy all the time.

if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.

simms22 said:
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
Click to expand...
Click to collapse
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
-Do a factory reset (maybe you can keep data coming from STOCK 4.4.4 - maybe)
Click to expand...
Click to collapse
And I didn't want to count on a maybe.

I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.

Fablus said:
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
Click to expand...
Click to collapse
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
Mysticodex said:
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Click to expand...
Click to collapse
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.

simms22 said:
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
Click to expand...
Click to collapse
Trying to remove the root right now via SuperSU. I am hopeful it will work better afterwards.
Edit: SuperSU unrooted it, rebooted, did OTA again, error again. Is there no way to find out what this error is?

OTA Update

I just received notification for OTA update. (134MB)
BLU_p0010UU_V11_GENERIC_5.1_20151123-0956
1. Stagefright patch
2. google security patches
3. Mcafee security 2015
4.Other bug fixes
Anyone tried it ?

i want to know if it is going to try and stick me with mcafee. . . happy to see an update, though!

you can remove mcafee after the update.

Can anyone upload ota?

Yes please. I'm rooted and it won't let me download the update. If someone could even offer a system dump that would be helpful.
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
If only for the stage fright patch
---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------
Also if someone could offer a system dump of the newest upgrade I'd be more than willing to cook up a rooted stock rom. I know I haven't been on the forums much lately at all but I remember working on stuff back in the t-mobile g1 days

Rooting after the update
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?

blacksmithjk said:
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
Click to expand...
Click to collapse
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.

Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days

so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
ArconHadron said:
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
Click to expand...
Click to collapse

tbirdguy said:
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Click to expand...
Click to collapse
tbirdguy said:
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
Click to expand...
Click to collapse
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0

ArconHadron said:
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
Click to expand...
Click to collapse
Fastflash?
Manually search?
Under the Development heading there are 5 topics, 2 of which are for TWRP recoveries (3.0.2 is buggy but works, just takes long time to wipe and restore; and theres SOOOOO many posts about how to flash them and how to use SP Flash Tool... so once again; glad you stuck with it, but Im still going with user error due to fail to RTFM

[OTA] Official Marshmallow build MCG24.251-5

WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8

TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.

zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.

This is the stock recovery version, correct?

koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.

TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.

Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones

koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.

Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.

Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.

Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )

kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.

TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.

kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.

Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"

s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!

It works in LOCKED BOOTLOADER??? .-.

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.

TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.