Database Users

VZW Software Update inside

Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
It does "fix" the bootloader unlock exploit though
http://www.droid-life.com/2013/07/1...the-kernel-exploit-for-unlocking-bootloaders/

scoobaspeaz said:
Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
Click to expand...
Click to collapse
So, stock recovery to install this?

I would assume you would need to be 100% stock, including the recovery, to install this.

scoobaspeaz said:
I would assume you would need to be 100% stock, including the recovery, to install this.
Click to expand...
Click to collapse
hmm put it on my internal storage and its not found, I think stock recovery wants to see it on a sdcard.

If your boot loader is unlocked before the update, it should stay unlocked. You just will not be able to unlock with methods out there now.
Sent from my Razr HD using xda app-developers app

I received the OTA today on my Max HD. It was build 9.18.79.
Sent using xda premium

A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!

LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1

Thanks for the reply! A few more questions if you don't mind (would hate to do something wrong... like I did last time... luckily I was able to revert back to an original version and fix the install... sigh...):
4) With protecting root, I need the SuperSU Pro version, yes? To be able to use the survival mode, yes? Will Voodoo OTA Rootkeeper do the same thing? Is it possible to use both "to be sure"?
5) I have everything backed up with Titanium Backup. Should I bother getting the pro version and backing everything up using the cloud backup and hypershell? Or won't this matter since if root doesn't keep I won't be able to use Titanium Backup?
6) I also have performed the VZW Wireless Hotspot hack using SQLite. Am I going to have to undo the hack in order for the OTA update to work?
Thanks again for all your help!

Update - I decided to attempt the update and hope for the best. System update 9.18.79.xx updating from 9.16.6.xx.
I purchased the SuperSU Pro from the Play Store, and used the survival mode in SuperSU. I also used the Voodoo OTA Rootkeeper and protected root. I figured if one didn't work the other might... Voodoo worked to protect and re-install root access (not sure about SuperSU as I tried Voodoo first to restore root after the install).
I am unsure if the bootloader is still unlocked, but from what people have said there doesn't seem to be a reason to believe it is re-locked. I haven't tested it out to know for sure though.
It appears that the entire update installed correctly. No errors, and the baseband version was updated to the new radio (xxx.15P).
I did not undo the VZW Wireless Hotspot hack prior to installing the update.
Hopefully this post helps others out there.
My final question... what does updating the radio/baseband do exactly?

i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options

rodmc123 said:
i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options
Click to expand...
Click to collapse
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny

KachowPow said:
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1
Click to expand...
Click to collapse
So any idea how one might fix this?

LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
I tried to take the 9.18.79 update I protected the root (I'm not unlocked) before I did so I also temporarily un-rooted (I've always been told to do this before and update) Now I an no longer rooted and it can't find any SU binary codes. Gonna have to flash back to 9.6.16 and try it again I guess or stay on 9.6.16 in order to maintain root for now. If you find a solution please share.

IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
I agree with Lenny. This same thing happened to me when I tried to take the liquid smooth ROM. Follow his instructions above. You'll lose all your pics, vids, files, etc. But at least you'll have a working phone again.

Went smoothly here
All my devices except this one are rooted and some are rom'd. I thought long and hard about whether to void this warranty but decided one day it would be out of updates from VZW and I would want to flash something. I have been denying the OTA for the last day so I figured now or never.
Here are the simple steps:
Download and install Moto device manager (for the USB drivers) here
Enable USB debugging in developer options on the phone
run motochopper here
run motoapocolypse here
install voodooOTA root keeper from Play and backup root
apply OTA
It went error free. The phone has the 15P radio update, unlocked BL and root.

larsdennert said:
It went error free. The phone has the 15P radio update, unlocked BL and root.
Click to expand...
Click to collapse
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?

bananapeapod said:
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?
Click to expand...
Click to collapse
Yes, the bootloader won't get locked again after it is unlocked. Moto would be shooting themselves having to reinstate warranties if they did that. Yes I wanted the option of flashing later becuase the ota will install sooner or later. I also want to stay on the upgrade path for now to have current radios.
I still have an Eris lying around that is long out of support but i have gb on it.

IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
that's what i want to do, but i cant because my power button is broken! so i cant enter to fastboot mode without the power button.. i will have to open my phone and try to fix the power button myself.

Just to make a point and to clear up any confusion, this Update will not lock the Bootloader. If you have an Unlocked Bootloader then you will have an Unlocked Bootloader after the update, regardless if it fully works or not, and even if you lose Root, the Bootloader will still be Unlocked. If Root is lost with an Unlocked Bootloader, I suggest downgrading through an FXZ of either 9.16.6 or 9.16.9 and restore Root.

Monthly OTA updates from Google

This is new: http://www.androidpolice.com/2015/08/05/google-announces-new-update-policy-for-nexus-devices-including-monthly-security-patches-for-3-years-and-major-otas-for-2-years-from-release/
That would be a real pain for us rooted users....but I guess the security patches are a good thing

A real pain...
Sent from another Nexus..
6...

No pain, it literally takes minutes to flash stock, update, root using the toolkit. [emoji1]

I wonder if there are again going to be separate builds for each carrier.

meldroc said:
I wonder if there are again going to be separate builds for each carrier.
Click to expand...
Click to collapse
That's a good point...maybe?

I wish there was an app for rooted users to get notifications about these updates (and maybe offer a way to download a flashable zip as well?)
I got a Nexus 6 because I wanted to be able to always have access to a stable, current version of Android. I didn't realize that OTA updates wouldn't work out of the box with rooted devices though.
Would be nice to have some method to get back that functionality!

ArmoredCavalry said:
I wish there was an app for rooted users to get notifications about these updates (and maybe offer a way to download a flashable zip as well?)
I got a Nexus 6 because I wanted to be able to always have access to a stable, current version of Android. I didn't realize that OTA updates wouldn't work out of the box with rooted devices though.
Would be nice to have some method to get back that functionality!
Click to expand...
Click to collapse
There is, stay stock or learn how to manually update to new versions. It's quick to do.

Xplicit84 said:
There is, stay stock or learn how to manually update to new versions. It's quick to do.
Click to expand...
Click to collapse
Both those things ignore the whole point of what I brought up.
I'm saying it would be nice if there was an equivalent automatic notification/update process for rooted users.

ArmoredCavalry said:
Both those things ignore the whole point of what I brought up.
I'm saying it would be nice if there was an equivalent automatic notification/update process for rooted users.
Click to expand...
Click to collapse
That is the equivalent. Stay stock or manually update. Rooted users don't worry about such a thing, since changing ROMs and adding various features are a common occurrence.

Xplicit84 said:
That is the equivalent. Stay stock or manually update. Rooted users don't worry about such a thing, since changing ROMs and adding various features are a common occurrence.
Click to expand...
Click to collapse
Rooted users don't care about convenience? I dunno about you, but I'm rooted, and I still would prefer to do repetitive/manual processes as little as possible...
You can be a rooted user just to use rooted apps, and not care about trying a different ROM every week. In which case, it would be nice to have the same benefits of automatic updates as stock users. Not sure why you seem to be against the idea?
I get that you think it is unnecessary, but I'm saying I would prefer it as an option. So, maybe we can just leave it at that?

ArmoredCavalry said:
Rooted users don't care about convenience? I dunno about you, but I'm rooted, and I still would prefer to do repetitive/manual processes as little as possible...
You can be a rooted user just to use rooted apps, and not care about trying a different ROM every week. In which case, it would be nice to have the same benefits of automatic updates as stock users. Not sure why you seem to be against the idea?
I get that you think it is unnecessary, but I'm saying I would prefer it as an option. So, maybe we can just leave it at that?
Click to expand...
Click to collapse
I would also like that if it was possible...

It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's

hdtechk said:
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
Click to expand...
Click to collapse
and that's exactly what I am going to do...

hdtechk said:
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
Click to expand...
Click to collapse
I don't think this will work. If your N6 is rooted, you can't sideload the OTA file. Your phone will need to be stock (unrooted) to apply the OTA.
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.

jj14 said:
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
Isn't there a chance of losing the ability to reroot with this method though? I've been waiting for users to publish flashable zips for this reason, but maybe that is not necessary?

ArmoredCavalry said:
Isn't there a chance of losing the ability to reroot with this method though? I've been waiting for users to publish flashable zips for this reason, but maybe that is not necessary?
Click to expand...
Click to collapse
Is there a chance that google will publish a new Nexus factory image that can't be rooted? Sure - in theory, that is possible. But unlikely.
Till date, all nexus devices have been rooted (thanks @Chainfire)

jj14 said:
. . . Your phone will need to be stock (unrooted) to apply the OTA.
. . . use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
Recently I used both methods just to see if there were differences.
Both had the same results. That means among others that my settings were gone.
- LCD_density defaults (384)
- WiFi interval defaults (was 200)
- Needed to flash Black Google Now Launcher and uninstall Google.app updates to get my black background back.
When this happens every month . . . [email protected]#$%&

jj14 said:
I don't think this will work. If your N6 is rooted, you can't sideload the OTA file. Your phone will need to be stock (unrooted) to apply the OTA.
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?
Does google always post a whole new image for each ota? What about the carrier variants like tmobile? Is there a new image for each ota?
Thanks. I'm not a N6 owner yet but I plan to be stock rooted and am trying to determine the ota update process in advance.

@NCguy
"When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?" Correct
Does google always post a whole new image for each ota?" Yes
"What about the carrier variants like tmobile? Is there a new image for each ota?" There has been a T-Mobile specific factory image for each OTA.
Here are the factory images > https://developers.google.com/android/nexus/images

cam30era said:
@NCguy
"When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?" Correct
Does google always post a whole new image for each ota?" Yes
"What about the carrier variants like tmobile? Is there a new image for each ota?" There has been a T-Mobile specific factory image for each OTA.
Here are the factory images > https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks cam30era. I was a bit concerned that being a stock rooted device might be too much trouble, especially with the security updates. But this looks manageable to me.

[Q] Another Rooting Question

The majority of my phones have been HTC so not really sure if unlocking the bootloader is normal procedure for a Motorola phone to obtain root. So i have a couple of questions on rooting this device, I'm happy to stay on a rooted stock so don't really see the point/need of unlocking the bootloader at this time.
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Thanks in advance.

rnscotch said:
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
Click to expand...
Click to collapse
Yes, at this time there's no way to obtain root without unlocking the bootloader.
rnscotch said:
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Click to expand...
Click to collapse
It can be relocked but then it'll be just "re-locked" not "locked", that means it'll have a different status.

Also note that you void the warranty just by obtaining the unlock code from Motorola; it doesn't matter if you've actually applied it to your device

If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?

LuizHenrique91 said:
If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?
Click to expand...
Click to collapse
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.

If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.

eskamhl said:
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.
Click to expand...
Click to collapse
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------
ooklathemok said:
If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.
Click to expand...
Click to collapse
Yes.. I'm considering to root mine X Play for be able to change the kernel and get the LED working (and maybe some optimizations). It's not prioritary, but I want. I won't install a custom ROM, because I like Moto Voice to much and I know we lost it.

LuizHenrique91 said:
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
Click to expand...
Click to collapse
Of course in that case you'll need to install the recovery and root, but as ooklathemok said you'll be able to update through a stock rooted rom simply from recovery

How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong

deaksfrost said:
How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong
Click to expand...
Click to collapse
Do not reboot to OS after flashing recovery, just reboot to recovery. If you reboot to OS after flashing twrp the stock Rom will over write recovery

Do Custom OS support Active/Moto Display and Moto voice?

yekollu said:
Do Custom OS support Active/Moto Display and Moto voice?
Click to expand...
Click to collapse
No, custom Roms do not support moto voice nor will they ever. Active display is all custom Roms provide.
This is my second moto x, I had the original moto x from 2013 and hated moto display.

Android 6.0 Marshmallow

Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.

joe1blue said:
Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.
Click to expand...
Click to collapse
You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool and take the ota them reroot
2) Wait for a flash able zip to become available.

TrenchKato said:
2) Wait for a flash able zip to become available.
Click to expand...
Click to collapse
Which will most likely be faster available than waiting for the OTA.

I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.

Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.
Click to expand...
Click to collapse
Chances are, if you unlocked your bootloader, you flashed a custom recovery. You can't take an OTA through a custom recovery -- not because it's "blocked," but because the OTA tool is not written to work with that recovery.

Could be. Easy enough to fix if so. Just tell TWRP to allow the OS to overwrite it, the reflash TWRP after the update.

Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!

jonathanbailie said:
Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!
Click to expand...
Click to collapse
A modified system will prevent the install. You would need to flash the system image as well.
Sent from my XT1575 using Tapatalk

I know some owners rooted their device for different reasons other than roms, but imo better to wait for 6.0 for OTA first. This phone comes with pure Android rom. Not like you need to remove bloat apps. Just need custom roms and kernels which is slow developing. Maybe the devs don't want to waste time with lp and their also waiting for marshmallow. I'm surprised how slow this device is moving under development. Oneplus one didn't have mass sale but their development was quick. Being so similar with nexus 6, hopefully we can get some love with MXP.
Sent from my XT1575 using XDA Free mobile app

I have been holding out on unlocking for this reason. I'm lazy and don't want to set everything up again so I will use Marsh to back everything up first then I will go to town

Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work.
Click to expand...
Click to collapse
OTA will not work for rooted MXPE's.
1) Rooting the MXPE requires you to load an alternative recovery (TWRP), which doesn't work with the OTA installation scripts.
2) Rooting the MXPE modified /system files. And OTA updates check /system integrity before it runs the update. Rooted phones will fail that integrity check, and will fail to OTA for that reason.
You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA. I'm sure that most people will do that, and then re-install TWRP and re-root after that is done. However, I'd recommend you wait a bit for other people to try this first, just in case there are any issues and to verify that root is still available in Android Marshmallow 6.0

Makes sense. Somebody has to be first. I will do a nandroid backup before attempting to update by any means.

Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.

hijax2001 said:
Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.
Click to expand...
Click to collapse
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?

PiousInquisitor said:
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?
Click to expand...
Click to collapse
Yup, you're correct ... I just used the tool earlier today and I do indeed have stock recovery.
Sent from my XT1575 using Tapatalk

Sharing my experience... good it's supposed to. Didn't for me, for some reason, until 2nd power cycle. It is stock recovery now though. Sorry for the confusion.

Android Nougat is coming to the M9 sometime in the "far" Future

Lets see if it comes faster to our Device then Marshmellow...after Google released it to the Manufactures.
And it comes as it seems just to three Devices. (A9,M9, HTC 10)

I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out

rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.

Got that system security OTA notification as well today. I'm using the stock ROM with root (SuperSU flashed via TWRP). Can I stay rooted to apply the OTA with the stock recovery or do I have to flash the RUU first?
Solved:
Make a backup with Titanium or however you like. Save all your data from internal SD. Afterwards apply latest RUU.exe from HTC (depending on your carrier). If you wanna reroot, I would suggest SuperSU 2.65, because newer versions end up in bootloops.

Don't expect Nougat this year...

It's the August security update
Sent from my HTC One M9 using Tapatalk

hope this year released

matmaneyre said:
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Click to expand...
Click to collapse
Do you have 3.39.531.12 stock recovery??

missicolin said:
Do you have 3.39.531.12 stock recovery??
Click to expand...
Click to collapse
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.

Amishrabbit said:
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Click to expand...
Click to collapse
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?

any news on Android N at least not official

drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
you should
" fastboot oem lock "
to relock your bootloader - remeber - to save alll yor apps / settings (via TitaniumBackup for exaple) before
(re) unlocking bootlader will wipe all data
...

rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:

rtoledo2002 said:
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
Click to expand...
Click to collapse
here is a screen shot

rtoledo2002 said:
then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ??
Click to expand...
Click to collapse
That's not a bug but a security feature introduced by google. It's meant to prevent malicious apps from making you accept things/permissions you don't want (keyword: tapjacking). Go to settings > app > open the three dot menu > configure apps > draw over other apps. There you can revoke that permission from any suspicious app.
There is an article about tapjacking on the xda portal if anyone wants more information. It's called "How tapjacking made a return with android marshmallow - and nobody noticed". Btw, the article explains why the security feature isn't perfect, too. (Using xda labs at the moment I can't add a direct link to the article. However google should be able to find it.)

I just hope for the classic Non-GP Sense UI. The one with the Grid View Recent Apps.
HTC One M9 is the last chance for the full Sense experience on Nougat, because is the last Non-GP HTC that is being updated.

Rollout started
rhisendark said:
any news on Android N at least not official
Click to expand...
Click to collapse
Read that Rollout started in America for Brand free devices

HTC root mobiles cannot install OTA, RUU are only way when rooted

drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
Yeah you only need to flasb the RUU it would solve your problem