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.
Related
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.
So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device
You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta
A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade
Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app
u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378
Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.
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.
I was sitting in my car and looked at the screen and I noticed that the phone was downloading MotorolaOTA 4.0 Does anyone know what it is? I am currently running KitKat 4.4.4 and never did the Lollipop update.
I also stopped the download in process but it appears that the phone would love to continue the download.
Thanks
gman
The phone has an app called MotorolaOTA, which is responsible for downloading system updates. If it was a software update it'd say it's 23.11.39.
Sent from my Droid Turbo using Tapatalk
Just caught my Turbo
I am running KitKat 4.4.4. version 21.44.12 the file it's trying to download is 770 megabytes. Could it be trying to sneak in Lollipop?
gman781 said:
I am running KitKat 4.4.4. version 21.44.12 the file it's trying to download is 770 megabytes. Could it be trying to sneak in Lollipop?
Click to expand...
Click to collapse
Yes, it will download the update but, afaik you MUST confirm installation of it... It's not going to install on it's own...
smokie75 said:
Yes, it will download the update but, afaik you MUST confirm installation of it... It's not going to install on it's own...
Click to expand...
Click to collapse
For over a month I have been getting the update screen and I would just put it off. Now it seems like it is pushing it's way into my phone.
Motorola confirmed recently that they would be patching the Stagefright exploit for the Turbo via OTA. I wonder if they can somehow force the update since it's such an important security issue this time around. I seem to remember Samsung doing something similar with the S6 shortly after release. I would recommend disabling Motorola OTA until more is known.
Not rooted, cannot disable.
Caught my phone doing the same thing. Is Lollipop larger than 770MB? I thought so, but haven't checked into it.
That's what I have been trying to figure out.
TheHolyCobra said:
Caught my phone doing the same thing. Is Lollipop larger than 770MB? I thought so, but haven't checked into it.
Click to expand...
Click to collapse
CM 12.1 ROM (Lollipop 5.1.1) for our Quarks is only 390 MB.
So, yeah, Lollipop 5.1 with Verizon bloatware is probably 770MB.
But the 5.1 OTA for Droid Turbo XT1254 posted here is 1.1GB:
http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Still 770MB is huge.
Just freeze it
Sent from my XT1254 using XDA Free mobile app
Not rooted and will not allow disable.
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
drtweak said:
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
Click to expand...
Click to collapse
Before my turbo was rooted, I was able to block the OTA's by installing the motorola drivers on my windows pc and installing Minimal ADB / Fastboot. Go here for instructions http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
However, I never did download any of the OTA's to my phone but I hope this helps. I believe this is by Rootjunky as far as credits are concerned.
Also by Misterxtc
gman781 said:
Not rooted and will not allow disable.
Click to expand...
Click to collapse
RL_Wells said:
Before my turbo was rooted, I was able to block the OTA's by installing the motorola drivers on my windows pc and installing Minimal ADB / Fastboot. Go here for instructions http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
However, I never did download any of the OTA's to my phone but I hope this helps. I believe this is by Rootjunky as far as credits are concerned.
Also by Misterxtc
Click to expand...
Click to collapse
The debloat tool is a much easier way to disable any app on your phone. On kitkat it disables and on lollipop it hides the apps. The hide command on lollipop has the same effect as the disable command on kitkat.
---------- Post added at 02:12 PM ---------- Previous post was at 02:10 PM ----------
drtweak said:
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
Click to expand...
Click to collapse
Enter recovery mode, clear cache and use the debloat tool to disable the OTA.
[/COLOR]
Enter recovery mode, clear cache and use the debloat tool to disable the OTA.[/QUOTE]
Yea no go on Recovery. It just goes straight to "Installing System update" Got my PC on, downloaded my mofo to my work PC, and not installing drivers and also downloading a stock but rooted version of 4.4.4. not quite ready to move on to 5.1 yet.
Thanks for the help though and tryin to help out! Now to finally jump into my Turbo after 8 months of having it. I miss the days of TWRP on my Razr HD. Funny because i had to reload an old backed up image so i could get some old wifi passwords.
UGH this damn phone. Won't power off when in Fastboot, so i just have to let it sit in fastboot and watch it and just restart everytime it starts up. got 20 minutes left of downloading an image. About ready to say F'it and just factory reset it for now and see if that fixes it or not.
Well flashing a stock rooted rom didn't work. Uses the rooted Quark 21.44.12 image that I download and I know i was on 21.44.12 when i checked last time. So don't know if it was because of the starting up the update or what.
Soft bricked my turbo, time to use RSD Lite again. Haven't had to use this in a LOOOOOONG time (Like Droid X Days)
drtweak said:
Well flashing a stock rooted rom didn't work. Uses the rooted Quark 21.44.12 image that I download and I know i was on 21.44.12 when i checked last time. So don't know if it was because of the starting up the update or what.
Soft bricked my turbo, time to use RSD Lite again. Haven't had to use this in a LOOOOOONG time (Like Droid X Days)
Click to expand...
Click to collapse
I'm probably too late but have you tried this to get back to KitKat? I used it earlier today and it worked great.
Misterxtc said:
I'm probably too late but have you tried this to get back to KitKat? I used it earlier today and it worked great.
Click to expand...
Click to collapse
No I had to get my phone backup asap. using the RSD Lite method actually didn't work. the program would keep freezing right after it read the zip file and then crash. Had to use Root Junky's method. I was able to restore back to stock 21.44.12 and everything was there as if nothing happened so I'm all good.
http://www.androidcentral.com/moto-x-2014-updated-fix-stagefright-exploit
"If you happen to be using a Moto X 2014 Pure Edition, you may have an update waiting for you. It appears that Motorola has begun pushing out a patch for the Stagefright exploit, along with some minor bug fixes. Here's the official word on what this update contains:
Closes a potential security vulnerability (Stagefright)
Bug fixes and other stability improvements
It's unclear if this one is landing for everyone at the same time, or if it's a gradual rollout. For what it's worth, however, we had to manually check for the 4.3MB update to pull it down, so that would be your best bet. To do so, head to your Settings menu then go to "About Phone" and tap "System Updates.""
I manually checked, and the update was available for me. Didn't accept it, as I'm not sure if my root and Xposed would be affected.
I received the notification and installed the update without thinking and now my phone is stuck on the bootloader warning screen. I was rooted. Anyone know how I can fix this?
slicck said:
I received the notification and installed the update without thinking and now my phone is stuck on the bootloader warning screen. I was rooted. Anyone know how I can fix this?
Click to expand...
Click to collapse
My suspicion is that just as a full OTA, you need to be stock unrooted.
slicck said:
I received the notification and installed the update without thinking and now my phone is stuck on the bootloader warning screen. I was rooted. Anyone know how I can fix this?
Click to expand...
Click to collapse
I did the same thing and now I have the same problem. This is going to suck majorly if I have to wipe my entire phone now. I haven't backed up in a few weeks. :-/
Any help would be appreciated.
EDIT - To be clear, I'd love to figure out a way to recover this without having to factory wipe the phone. I can get to the recovery window but I don't have TWRP or anything installed, I just had it rooted.
dbrowdy said:
I did the same thing and now I have the same problem. This is going to suck majorly if I have to wipe my entire phone now. I haven't backed up in a few weeks. :-/
Any help would be appreciated.
EDIT - To be clear, I'd love to figure out a way to recover this without having to factory wipe the phone. I can get to the recovery window but I don't have TWRP or anything installed, I just had it rooted.
Click to expand...
Click to collapse
Flash twrp in the bootloader. Backup your data in twrp. Download factory image for your version 5.0, 5.1, etc. from Motorola servers. Flash the system.img and boot.img in the bootloader. Clear the cache and dalvik. Reboot.
Sent from my XT1095 using Tapatalk
kcustom11 said:
Flash twrp in the bootloader. Backup your data in twrp. Download factory image for your version 5.0, 5.1, etc. from Motorola servers. Flash the system.img and boot.img in the bootloader. Clear the cache and dalvik. Reboot.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Awesome, thanks! I had already gotten TWRP reflashed and I was at a loss of where to go from there.
Now I have to wait for someone to approve my download or something. Wonderful. My phone is bricked and I have to wait for someone at Motorola to manually approve me.
Anyone know of a mirror for these files?
dbrowdy said:
Awesome, thanks! I had already gotten TWRP reflashed and I was at a loss of where to go from there.
Now I have to wait for someone to approve my download or something. Wonderful. My phone is bricked and I have to wait for someone at Motorola to manually approve me.
Anyone know of a mirror for these files?
Click to expand...
Click to collapse
Found this post that has the image files. http://forum.xda-developers.com/moto-x-2014/general/5-1-firmwares-t3148211/page9
bostonirishguy13 said:
http://www.androidcentral.com/moto-x-2014-updated-fix-stagefright-exploit
"If you happen to be using a Moto X 2014 Pure Edition, you may have an update waiting for you. It appears that Motorola has begun pushing out a patch for the Stagefright exploit, along with some minor bug fixes. Here's the official word on what this update contains:
Closes a potential security vulnerability (Stagefright)
Bug fixes and other stability improvements
It's unclear if this one is landing for everyone at the same time, or if it's a gradual rollout. For what it's worth, however, we had to manually check for the 4.3MB update to pull it down, so that would be your best bet. To do so, head to your Settings menu then go to "About Phone" and tap "System Updates.""
Click to expand...
Click to collapse
Is there any way to install this as a zip file from TWR?
EDIT: Found it! http://forum.xda-developers.com/showpost.php?p=62902065&postcount=3