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.

Wife possibly soft bricked??

Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?

Zugshad said:
Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?
Click to expand...
Click to collapse
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work

XxZombiePikachu said:
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work
Click to expand...
Click to collapse
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:

Zugshad said:
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:
Click to expand...
Click to collapse
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code

XxZombiePikachu said:
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code
Click to expand...
Click to collapse
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )

Zugshad said:
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )
Click to expand...
Click to collapse
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)

XxZombiePikachu said:
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)
Click to expand...
Click to collapse
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
edit... ok that is the ota file.... thanks again )

Zugshad said:
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
Click to expand...
Click to collapse
yep that should be it; just delete and goodbye updates should stop working as a whole (if you want to get tibu to freeze you can always log in with your play account on her device and download the pro version)
edit: just noticed you solved it

5.1 Update - Use Motorola Device Manager to Get the FXZ

I have pointed this out in several places, but I wanted to make a thread about it so that it gets more widespread attention.
When the 5.1 update is released, if instead of taking the OTA you use Motorola Device Manager to update, you will have a copy of the 5.1 fxz for your device on your computer. It will be in the folder c:\programdata\motorola\SUE\firmwares if you have a PC.
If the OTA has already begun to download on your device, then MDM won't update you b/c it will say there is an update in progress. So if you are rooted, you must delete or freeze the MotorolaOTA app. If you are not rooted, I think there may be some way to avoid the OTA but idk, you would have to read up on it. I think you may be able to wipe your data partition and/or cache if the download has begun in order to erase it, idk.

You know, I have been meaning to freeze the update app, thats always kinda been SOP with modded phones, though I know how much everyone loves their OTAs
I know I searched once before and couldn't find the name, as most don't seem to do it; which app do I need to freeze?
I think I am planning to wait for the official to drop, then try it for a bit hopefully from a TWRP backup before updating my bootloader and what not via fastboot (assuming Moto gives the dev editions an SBF again...)

I googled for FXZ... Which means Full XML Zip, but didnt seem to find what it does and, how it is important..??
Any xplanation wud really be helpfull...
Thank you..!

rohitdna said:
I googled for FXZ... Which means Full XML Zip, but didnt seem to find what it does and, how it is important..??
Any xplanation wud really be helpfull...
Thank you..!
Click to expand...
Click to collapse
It is the full ROM, so if you wanted to go back to stock, you would flash it, wipe user data, and be ready to go.

So, whn 5.1 is released, if i update it using Motorola device manager, the previous operating system which is 4.4.4 will be backed up, using FXZ...??

rohitdna said:
So, whn 5.1 is released, if i update it using Motorola device manager, the previous operating system which is 4.4.4 will be backed up, using FXZ...??
Click to expand...
Click to collapse
No, it's the full 5.1 so that when/if you screw up your phone you can fastboot flash the stock 5.1. Once you update fully, you can't ever go back. This just gives you the safety net of being able to restore a stock 5.1 system.

scryan said:
I know I searched once before and couldn't find the name, as most don't seem to do it; which app do I need to freeze?
Click to expand...
Click to collapse
MotorolaOTA.

tcrews said:
No, it's the full 5.1 so that when/if you screw up your phone you can fastboot flash the stock 5.1. Once you update fully, you can't ever go back. This just gives you the safety net of being able to restore a stock 5.1 system.
Click to expand...
Click to collapse
Stock 5.1 system and recovery!
You can NEVER* safely downgrade the bootloader and partition table of a Moto X!!!!!!!
* there was 1 exception to this that jcase and found and was able to use it to root 4.4.4 - if you are not jcase though, you should not try to downgrade motoboot.img or gpt.bin!!!!!!

JulesJam said:
MotorolaOTA.
Click to expand...
Click to collapse
Doh. Yeah stupid me, used to other phones with more cryptic updater apps... Guess thats what I get for not just trying to find it on my own. Thanks.

bump

JulesJam said:
I have pointed this out in several places, but I wanted to make a thread about it so that it gets more widespread attention.
When the 5.1 update is released, if instead of taking the OTA you use Motorola Device Manager to update, you will have a copy of the 5.1 fxz for your device on your computer. It will be in the folder c:\programdata\motorola\SUE\firmwares if you have a PC.
If the OTA has already begun to download on your device, then MDM won't update you b/c it will say there is an update in progress. So if you are rooted, you must delete or freeze the MotorolaOTA app. If you are not rooted, I think there may be some way to avoid the OTA but idk, you would have to read up on it. I think you may be able to wipe your data partition and/or cache if the download has begun in order to erase it, idk.
Click to expand...
Click to collapse
What's the difference between an FXZ versus an SBF? Now that the official 5.1 OTA is out for the XT1053, I need it to update my phone from the 5.0.2 soak
Sent from my XT1058 using Tapatalk

I tried to use mdm on the small 4.4.4 update. When I plugged my phone in it said my device was already in the middle of upgrading even though I did not install it yet. So once you are prompted by OTA how to get mdm to work? Mfastboot seems much easier. But yes, I want the file.
---------- Post added at 02:48 AM ---------- Previous post was at 02:38 AM ----------
I am pretty sure it won't be long for someone to release the image files once they are officially released. It usually doesn't take long.

Travisdroidx2 said:
I tried to use mdm on the small 4.4.4 update. When I plugged my phone in it said my device was already in the middle of upgrading even though I did not install it yet. So once you are prompted by OTA how to get mdm to work?
Click to expand...
Click to collapse
Back up the device then do a factory reset. Then put it in bootloader mode and start MDM.
If that doesn't work, take out the SIM card and after the factory reset, activate the phone but don't put in a google account or let it connect to Wifi and then go to settings and enable developer options and USB debugging and then connect it to your computer and start MDM.

demifalcon said:
What's the difference between an FXZ versus an SBF?
Click to expand...
Click to collapse
i use those terms synonmously although there may be a difference idk.

JulesJam said:
Back up the device then do a factory reset. Then put it in bootloader mode and start MDM.
If that doesn't work, take out the SIM card and after the factory reset, activate the phone but don't put in a google account or let it connect to Wifi and then go to settings and enable developer options and USB debugging and then connect it to your computer and start MDM.
Click to expand...
Click to collapse
demifalcon said:
What's the difference between an FXZ versus an SBF? Now that the official 5.1 OTA is out for the XT1053, I need it to update my phone from the 5.0.2 soak
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
JulesJam said:
i use those terms synonmously although there may be a difference idk.
Click to expand...
Click to collapse
Doing a quick google search told me this -
FXZ = Full XML Zip
SBF = System Binary File
I guess SBF cant be extracted by winrar etc but FXZ can be

Now that 5.1 is being officially released and rolled out, can we start this back up?

do i actually have to do the update to gt the fxz?

hey i tried to flash back to stock and run the MDM, but it said that i already have the newest version (KK)
and then i tried to install the new motorola update service, and run the MDM again.. but still it said that i already have the newest version (KK)
and now i run the OTA update because i dont know how to make it using MDM, i really want the FXZ file because i want back it up for me
sorry for my super bad english

I'm on mac.
Got the 5.1 Retail.en.GB update notice OTA. But i want to use MDM to capture the FXZ.
I connect and say check and it says no updates.
Any ideas??

Put your phone into airplane mode, reboot to recovery, erase cache, reboot normally (make sure you're still in airplane mode), connect to MDM, and it should see the update.

New AT&T OTA

I just received notification on my phone that there is a new software update. I didn't, nor can i install it because I've removed all of the bloat ware and rooted the phone, and installed TWRP. I'm already on 21q so this must be something newer that AT&T is pushing out. Anyone else get the OTA?

Ahh, it is more security updates. It brings the software version to 21r. It came out on September 10th. They probably patched the ability to root it. Lol

ATT 850
I think you're right, I went back to stock "D" and then took all updates. I didnt like what I saw so went back to stock "D" and now I cant root with any method. My Recent apps is now in a thumbnail format instead of tabs.... not sure there is anything I can do to root.
The Root.bat seems to work but then just hangs at the LG screen and never boots.

louvass said:
I think you're right, I went back to stock "D" and then took all updates. I didnt like what I saw so went back to stock "D" and now I cant root with any method. My Recent apps is now in a thumbnail format instead of tabs.... not sure there is anything I can do to root.
The Root.bat seems to work but then just hangs at the LG screen and never boots.
Click to expand...
Click to collapse
Were you able to get your phone to boot at all? Now I know not to flash it!

Egrier said:
Were you able to get your phone to boot at all? Now I know not to flash it!
Click to expand...
Click to collapse
No it never booted I had to reflash back to stock "D" I am trying it again this time I am taking the "F" update then trying the root

louvass said:
No it never booted I had to reflash back to stock "D" I am trying it again this time I am taking the "F" update then trying the root
Click to expand...
Click to collapse
I was able to root 21q. I'm not going beyond that if you had issues after updating it.

Egrier said:
I was able to root 21q. I'm not going beyond that if you had issues after updating it.
Click to expand...
Click to collapse
I'll keep you posted I'm still playing
UPDATE: after a few tries I was able to stump root "D" once again. I'll install TWRP and a ROM and leave it at that

I think the stupid update tried to install itself without any interaction from me. I had my phone laying next to me on the desk and heard the AT&T jingle playing. I turned to look at it and was rebooting. After it rebooted, a box was up on the screen saying that there was suspicion of my phone being rooted and that it wouldn't install. Fine by me.

Pretty sure this is the patch for the stagefright vulnerability.

Download Unsuccessful MSG - KK to N910VVRU1BOAF

I'm trying to root, then unlock my Retail phone. I heard it can be done on BOAF 5.0.1. I downgraded my phone to KK ANJ5 (details on what steps I took, here)
I actually did a Factory Data Wipe twice before beginning, although the instructions said I only needed to do it once (doing it twice shouldn't hurt).
When I tap the System Updates button, it appears to start downloading, then after a few minutes, I'll get an error message saying "Download Unsuccessful". I've done this several times. Why is this happening now? I've cleared everything. Could Verizon have pulled the update? Can I install the two files manually? If so, please point me to the right direction. Thanks.

Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I took the latest safe upgrade, I think it's BP1 or something like that., to 5.1.1. THAT worked.

So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app

rrjskj said:
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.

JOSHSKORN said:
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
Click to expand...
Click to collapse
I might give it a whirl if fix doesn't come soon. In the meantime could u point me in the right direction for the safe upgrade files and what Odin version ?? Thanks in advance.
Sent from my SM-N910V using XDA Premium HD app

http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
Already did it I appreciated.
Sent from my SM-N910V using XDA Premium HD app

I've had it work on boaf, bpa, bog5. kk wouldn't work for me. using king root 4.0,.all unlocks (n4.n4.bin. n4.fix) worked for me. bpa (5.1.1)required the emotion kernel to boot. also returned my original Cid to use kies to restore all apps & data, then odined back again, unlocked, rooted ect. be patient

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.

Sizzlechest said:
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Click to expand...
Click to collapse
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
went ahead and did the safe upgrade via Odin
Swapped out my MicroSD card for a different one I had laying around
Unlocked my phone
Powered Down (If I could, or remove the battery)
Removed the MicroSD card (otherwise it would boot loop)
Connected to My Computer
Boot to Download Mode (DOWN ARROW+HOME+POWER BUTTON)
Flashed TWRP using Odin
Reinserted the original MicroSD Card (Different SD card than what was used during the unlock process, the same one I was using prior to unlocking)
Booted into TWRP (UP ARROW+HOME+POWER BUTTON)
It prompted me to install SuperUser, so I did, it caused a bootloop, so I pulled my battery.
Removed MicroSD Card, plugged it into my computer and put SuperSU.zip and a kernel (See this post) zip file on it, re-inserted the MicroSD into my phone
Booted to TWRP (UP ARROW+HOME+POWER BUTTON)
Flashed the two files I'd just put on my MicroSD (Not sure if a reboot is required or if they could be done at the same time, I rebooted each time)
I did not clear cache/dalvik. Not sure if that was necessary.
This is all what got me to where I'm at, now.

JOSHSKORN said:
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
...
This is all what got me to where I'm at, now.
Click to expand...
Click to collapse
For 5.0.1, you don't need to flash a new kernel, so that's why it works. If you want to upgrade to N910VVRU2BPA1:
Download N910VVRU2BPA1_StockRestore.tar.md5.7z and uncompress with 7-zip.
Flash with Odin.
Reboot phone back into Download Mode and flash TWRP with Odin.
Copy MultiSystem-Kernel_LP-5.1.1.zip and BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip to the phone's internal memory. (Include xposed-v75-sdk21-arm-arter97-snapdragon.zip if you want XPosed.)
Reboot to recovery and flash all three in the above order.
Wipe cache and Davlik cache. Reboot to system.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)

Sizzlechest said:
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Click to expand...
Click to collapse
Thanks I just upgraded through Verizon to 5.0.1 and I'll give that a try and see if it works if not I'll safe upgrade to 5.1.1 thanks

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.

JOSHSKORN said:
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
Click to expand...
Click to collapse
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far

Jimmy8 said:
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Click to expand...
Click to collapse
Believe me, I'm with you right there, as well, been out of the game for so long. Thanks Verizon Retail locking. Anyway....
Where are you right now? Your Android version/Build Number.

joshskorn said:
believe me, i'm with you right there, as well, been out of the game for so long. Thanks verizon retail locking. Anyway....
Where are you right now? Your android version/build number.
Click to expand...
Click to collapse
5.0.1 / n910vvru1boaf