Database Info

[DEVS][OTA] Original M7UL 4.4.3 OTA update zip

The original update OTA can be obtained here: WWE_4.07.1700.4-3.62.1700.1_KTU84L.H4_release_377648
This cannot be flashed unless your device meets all requirements. Wait for a ROM otherwise.

Can someone with the latest version of the stock 4.4.2 GPE help me out! Need one file to update to 4.4.3!
http://forum.xda-developers.com/showthread.php?t=2772266
Thanks!

Orginator said:
Can someone with the latest version of the stock 4.4.2 GPE help me out! Need one file to update to 4.4.3!
http://forum.xda-developers.com/showthread.php?t=2772266
Thanks!
Click to expand...
Click to collapse
Googling for this MD5 first gives me your postings (scattered across XDA ) as well as this link: http://rghost.net/53665485
EDIT: file has been deleted.

sanderg said:
Googling for this MD5 first gives me your postings (scattered across XDA ) as well as this link: http://rghost.net/53665485
EDIT: file has been deleted.
Click to expand...
Click to collapse
Trust me, the first thing I do is google.. been there, done that! Yeah sadly deleted and I'm still stuck at 4.4.2, so many must have made a CWM backup before updating to 4.4.3, yet so hard to get that file :/

Orginator said:
Trust me, the first thing I do is google.. been there, done that! Yeah sadly deleted and I'm still stuck at 4.4.2, so many must have made a CWM backup before updating to 4.4.3, yet so hard to get that file :/
Click to expand...
Click to collapse
What if you manually edit updater-script to not patch Youtube?

I could do that, but then I'll have the same issue on next OTA! I'd rather have a 100% clean update, if you know what I mean!

Could you make a ROM GPE with Sense camera ?

Orginator said:
I could do that, but then I'll have the same issue on next OTA! I'd rather have a 100% clean update, if you know what I mean!
Click to expand...
Click to collapse
Mine fails as well - on basicDreams.apk. It doesn't look like it can be applied to every device, e.g. when integrating apps into the ROM using Titanium Backup it will most likely fail. Will be taken care of by the ROM devs though.

sanderg said:
Mine fails as well - on basicDreams.apk. It doesn't look like it can be applied to every device, e.g. when integrating apps into the ROM using Titanium Backup it will most likely fail. Will be taken care of by the ROM devs though.
Click to expand...
Click to collapse
I don't use Titanium Backup or anything alike.

Can we flash this OTA.zip from stock recovery after we returned back to Google Edition ?

HAAANG ON!! hang on......
this....is a 4.xx.xxxx.x update
previous was 3.62.xxxx.x
....I may assume that is like a....major release or something...?
I expect a good improvement, even in performance (that on sense roms is always 2 times better, dunno why)

Can we flash this?
Sent from my HTC One using Tapatalk

gaja22 said:
Could you make a ROM GPE with Sense camera ?
Click to expand...
Click to collapse
No
---------- Post added at 06:13 AM ---------- Previous post was at 06:12 AM ----------
throcker said:
HAAANG ON!! hang on......
this....is a 4.xx.xxxx.x update
previous was 3.62.xxxx.x
....I may assume that is like a....major release or something...?
I expect a good improvement, even in performance (that on sense roms is always 2 times better, dunno why)
Click to expand...
Click to collapse
Stick to your sense ROM then because performance hasn't changed much between 4.4.2 and 4.4.3
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
mrgwap said:
Can we flash this?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Don't think so, it's an OTA file that needs to be installed by the stock recovery, not a custom recovery.

Nic2112 said:
No
---------- Post added at 06:13 AM ---------- Previous post was at 06:12 AM ----------
Stick to your sense ROM then because performance hasn't changed much between 4.4.2 and 4.4.3
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
Don't think so, it's an OTA file that needs to be installed by the stock recovery, not a custom recovery.
Click to expand...
Click to collapse
About to RUU back to 4.4.2 with stock recovery.
What do I do afterwards. I have the file in the OP downloaded. Do I just place it in root storage and look for a update than root afterwards.

charlieb620 said:
About to RUU back to 4.4.2 with stock recovery.
What do I do afterwards. I have the file in the OP downloaded. Do I just place it in root storage and look for a update than root afterwards.
Click to expand...
Click to collapse
All I had to do was RUU to 4.4.0 because that's the one I had handy, let the phone OTA to 4.4.2, and when it booted all I had to do was hit the "check for update" button 2-3 times and then it prompted me to download the OTA and voila, 4.4.3

Nic2112 said:
All I had to do was RUU to 4.4.0 because that's the one I had handy, let the phone OTA to 4.4.2, and when it booted all I had to do was hit the "check for update" button 2-3 times and then it prompted me to download the OTA and voila, 4.4.3
Click to expand...
Click to collapse
Alright I will do the RUU and just check for Update.

charlieb620 said:
Alright I will do the RUU and just check for Update.
Click to expand...
Click to collapse
You would have to put the OTA at the right location and name it exactly what the recovery expects and I don't know how to do that.
Thing is with stock recovery, there are no options, it either updates or resets to factory default.

can someone make a flashable zip of the rom? Wouldn't really want to go thru all the trouble of converting back to stock recovery and rom to update since im on a custom rom now? A flashable zip would mean a lot!

ace-user said:
can someone make a flashable zip of the rom? Wouldn't really want to go thru all the trouble of converting back to stock recovery and rom to update since im on a custom rom now? A flashable zip would mean a lot!
Click to expand...
Click to collapse
Just wait a day or two.

I haven't really noticed a performance increase or decrease tbh after flashing the new firmware. It says "5.11.401.10" because I edited the android-info.txt file. But the date is 5/16/2014, to confirm that it is the newer v1.54 hboot. How would I go about making a deodex system dump into a flashable rom.zip? I have the system dump if someone can help me with the procedure.

[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

After Custom Recovery OTA and Recovery-flashable Incrementals Don't work

I've had the OPO for over a year, and just now had the need to root it. An OTA happened to come in the next day, and the update process didn't work as I expected. So I'd like to know if I did something wrong, a random problem occurred, or this is the way it's supposed to work.
Until a couple days ago, the OPO was stock + all OTAs that had been released. I unlocked the bootloader, installed TWRP recovery, and installed SuperSU. All that went as expected. When the OTA notification arrived the next day, I tried to install it with "Update Cyanogen recovery" still unchecked (because original reports with CM 11S said you could keep your custom recovery with an OTA).
When I tried to install the update, the phone just rebooted to TWRP and the update was not stored anywhere on /sdcard. I then checked "Update Cyanogen recovery" and tried to install the OTA again. It did not install, and TWRP was still my recovery. Several repeats of this had no different result.
Then I flashed the stock CM recovery with fastboot. After verifying I had the CM recovery, I installed the OTA again, and it failed again, reboting to recovery and doing nothing else. Then I downloaded the incremental update and tried to flash that via CM recovery, and that failed too. I checked the file /System/build.opt, and line "ro.build.version.incremental" said 49d90510ef, which meant I should have been able to install the cm-bacon-49d90510ef-to-d91bf047f5-signed.zip file. But it failed and said the current build number was not as expected. The number it gave me was not anything that made sense looking at the list of recent incremental updates.
So at that point I bailed out and installed via recovery the full flashable zip file, and that worked.
If this is what I have to do each time, it's certainly doable, but I don't think this is how it's supposed to go. I'm surprised the OTA didn't work with the custom recovery installed, and I'm even more surprised that the incremental installation failed. Maybe trying to install the OTA without updating the CM recovery messed things up, but that doesn't seem likely either. When the next OTA comes out, I'll see if any of these troubles are repeated. But I'd like to know how the OTA was supposed to work after installing a custom recovery.

I am still yet to figure this one out also, my friend I'm sure with time someone will respond who had better experience with this; just be patient
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava

Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs

Check the CyanogenMod website, @distante

vince.lupe said:
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava
Click to expand...
Click to collapse
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.

distante said:
Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs
Click to expand...
Click to collapse
This thread with Cyanogen mirrors and info has exactly what you need.

MidnightJava said:
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.
Click to expand...
Click to collapse
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/

vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.

Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
---------- Post added at 03:31 PM ---------- Previous post was at 03:25 PM ----------
vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?

Cholerabob said:
Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
Click to expand...
Click to collapse
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.

MidnightJava said:
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.
Click to expand...
Click to collapse
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
Cholerabob said:
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?
Click to expand...
Click to collapse
I did do both :/

MidnightJava said:
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.
Click to expand...
Click to collapse
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
vince.lupe said:
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
I did do both :/
Click to expand...
Click to collapse
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.

Cholerabob said:
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.
Click to expand...
Click to collapse
Yes, bootloader is unlocked and SuperSu was reinstalled :/

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

Essential June Update Available!

Updating now! ????

Me too! Can't wait for P!

Essential updated both radio and kernel this time.
P is just around the corner... Can't wait!!!

Does this include the multi touch bug fix?

I've never had issues with multi touch.

Nickvanexel said:
Does this include the multi touch bug fix?
Click to expand...
Click to collapse
They do not provide info about this point, but in my experience with this build, multi touch bug is fixed. At least pinch zooming in Instagram is now stable.

Is it ok to sideload over custom kernel?

I couldn't complete the update. After download is completed I am getting error "installation problem couldn't update".
I tried 3 to 4 times I even tried restarting the phone even tried downloading from a different network but none of them helped.
I checked it in a Reddit thread that many others also facing the same error like mine.
Is anyone else facing the same issue like this

prasathvishnu said:
I couldn't complete the update. After download is completed I am getting error "installation problem couldn't update".
I tried 3 to 4 times I even tried restarting the phone even tried downloading from a different network but none of them helped.
I checked it in a Reddit thread that many others also facing the same error like mine.
Is anyone else facing the same issue like this
Click to expand...
Click to collapse
No issue here, but I'm not unlocked or rooted.

No issues installing on my bone stock unrooted device.

millicent said:
Is it ok to sideload over custom kernel?
Click to expand...
Click to collapse
Yes..
You can just flash full OTA zip via twrp.
No wipes needed.

If I have the bootloader unlocked and with root, can I install this update? Without losing my data or having to re-root the phone?
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
indian84 said:
Yes..
You can just flash full OTA zip via twrp.
No wipes needed.
Click to expand...
Click to collapse
do you know where I can download the OTA zip?

prasathvishnu said:
I couldn't complete the update. After download is completed I am getting error "installation problem couldn't update".
I tried 3 to 4 times I even tried restarting the phone even tried downloading from a different network but none of them helped.
I checked it in a Reddit thread that many others also facing the same error like mine.
Is anyone else facing the same issue like this
Click to expand...
Click to collapse
Same here, no root

rockhevy1000 said:
If I have the bootloader unlocked and with root, can I install this update? Without losing my data or having to re-root the phone?
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
do you know where I can download the OTA zip?
Click to expand...
Click to collapse
Download the full OTA zip from below.
https://storage.googleapis.com/essential-static/PH1-OTA-OPM1.180104.234.zip
Reboot in TWRP, flash the zip without wiping anything.
Once the zip flashing is complete, reboot to system.
Then you can root again.
PS - Do not forget to remove your secured lock screen (PIN, Password, Pattern etc.) before flashing TWRP.

indian84 said:
Download the full OTA zip from below.
https://storage.googleapis.com/essential-static/PH1-OTA-OPM1.180104.234.zip
Reboot in TWRP, flash the zip without wiping anything.
Once the zip flashing is complete, reboot to system.
Then you can root again.
PS - Do not forget to remove your secured lock screen (PIN, Password, Pattern etc.) before flashing TWRP.
Click to expand...
Click to collapse
Do I have to flash the boot image to?
Thanks for the reply!

rockhevy1000 said:
Do I have to flash the boot image to?
Thanks for the reply!
Click to expand...
Click to collapse
Yes.
Rooting will be similar to how you did before.

Is the battery getting better? My battery life got a lot worse since I installed the May update, literally could only last a few hours.

where did you get the image from?...I meant he modded image to get the root back.

ranjaheer said:
where did you get the image from?...I meant he modded image to get the root back.
Click to expand...
Click to collapse
Google.

i have been flashing stock OTAs as sideloaded in TWRP. BL unlocked and rooted.