Database Users

Help new update wont install

I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Fixed!!!!! I used Brks Asus transformer rootkit script to root which installs an insecure bootimage to work and this is what caused the problem, I just plugged my trandormer in and restored my original files then the update went on fine first try!!!! Thanks for the help!!!!

Did you install Clemsyn/Blades OC kernel? More than likely this is causing your problem.......

I'm getting the same error. Running 3.2 stock but rooted, no modified kernel. Only thing I modified was the Netflix patch which doesn't seem like it's needed now. Is there a flash able zip for this new update?

You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App

magicdave26 said:
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.

I rooted using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1125714

oilerseberle14 said:
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
---
Sent from my Asus Transformer using Tapatalk

Taomyn said:
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
Click to expand...
Click to collapse
You only get it offered the once. Your device is then marked as updated at Asus end. If it didn't work because you were rooted, then tough...

cavsoldier19d said:
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
Click to expand...
Click to collapse
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.

magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated

I always look at the updater script in the package before I update. This script contains a bunch of asserts that check the integrity of certain files before it will apply the update. If you can get the update package just open " \META-INF\com\google\android\updater-script" with notepad and that will show everything that's happening when the update occurs including the file asserts it makes. If you've modified these files then it will not update. 8.6.5.6 initially didn't work for me but by checking the script I found the problem was my srs_processing.cfg file because I tried to fix my speaker balance and this was a file that the script asserted. After restoring the original file I was able to update with stock recovery even though I had modified other system files. As long as the specific files the update checks are ok the update will proceed.

aSIMULAtor said:
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
Click to expand...
Click to collapse
You need to UnRoot it, I don't think factory reset makes any difference to rooting
http://forum.xda-developers.com/showthread.php?t=1198303

magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
The above post about altering certain files appears it might have something to do with it. I rooted using this method... http://forum.xda-developers.com/showthread.php?t=1198303
But it was V2 when i used it. It is now currently V4.

You can re-download the update if you clear your DMClient cache.
Follow the instructions in this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
I had the error with the Android + exclamation mark so I unrooted (reflashed both the stock ROM AND the stock recovery - to get rid of clockworkmod) then cleared the DMClient cache and was I able to update OTA.

As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.

DT39 said:
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
Click to expand...
Click to collapse
Good point. I did not have clockwork mod recovery installed. Had stock recovery, stock ROM rooted.
Sent from my Inspire 4G using XDA App

I used brk's rootkit script and just restored the original bootimage and it installed perfect let me know if it worked for you guys as well
Sent from my Transformer TF101 using XDA Premium App

I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?

Hizpanick said:
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Click to expand...
Click to collapse
Same thing happened to me. Tried all the above, and can't get the update to come back.

Have any of you changed original system files whilst rooted? That's why it was failing for me. I managed to get the update again but it failed. I got it once more after it rebooted but took a copy first, unrooting made no difference. Unlike the downloadable firmwares from the ftp site which I checked out, the update script checks the integrity of a ton of files mainly the system apps that cannot be changed without root. If any have changed the script aborts.
Unfortunately even though I had backed up all of them with Titanium Backup, it wouldn't restore them and TB just hung. I tried all its options but nothing helped - a little worrying.
In the end I copied off the TB backup directory to a USB stick and used the NVflash recovery to restore back to factory. I then performed the upgrade again to both the tablet and dock without issues. Four hours later I have it almost back to where I want it.
Hope this helps some of you, even though it's not the best process, but the update imho is worth it
---
Sent from my Asus Transformer using Tapatalk

[Q] 4.5.621 uprgrade failed

I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack

Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision

rom question
Thepooch said:
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision
Click to expand...
Click to collapse
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack

Rkshack said:
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack
Click to expand...
Click to collapse
RootzWiki is the best place to find roms.
You can make complete backups in ClockworkMod Recovery of your entire rom. I would use MyBackup Root to backup things like individual apps, data, SMS, etc.
Sent from my DROIDX using Tapatalk

update failed
Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
I also had the same failure, it was due to my having removed some of the bloatware. I loaded the 605 SBF file and rooted this installed al the root programs i would need along with voodoo ota and made a root backup, ran all my programs and did the update, all went ell and I was able to renew root with voodoo ota keeper. so far i have had no problems and am on the 621 update and fully rooted. Titanium backup works fine and I have been able to remove the bloatware.
Hope this helps and i am not too late.

From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.

4.5.621 install failure
Greetings. This looks like the right thread for this issue, but if not, please redirect me.
Some background:
DroidX
Android version 2.3.3
System version 4.5.605.MB810.en.US
currently rooted
Being a laggard, I did not accept the 621 update when first offered through OTA. My 4.5.605 DroidX was rooted and I'd read that I'd have to either unroot or "hide" root in some manner. It seemed like a bit of trouble and I had other life issues at the time.
After things cleared, I contacted VZ and they pushed the upgrade again. After "unrooting", I accepted the OTA upgrade, but each installation attempt failed after a successful download. No other diagnostics, just "the update failed". I tried this multiple times after reboots, battery removal, cache clearing and such. I then did a factory reset and tried again - still the same sequence, successful download, install now, update failed.
So I called VZ and Moto. They suggested accepting the update while attached to a solid WiFi. All the same tricks were turned as with the OTA (another factory reset, clear cache, remove/replace battery) only these attempts used the WiFi (excellent signal). Same failure.
Moto then suggested I ship in the unit and for $110 they would handle it. Right.
So I found Blur_Version.4.5.621.MB810.Verizon.en.US.zip, downloaded it to the SD card and attempted to install using the recovery mode menu. This also fails but at least offers up the message: assert failed apply_patch ("system/app/AccountAndSyncSettings, apk", "-" then some odd number letter sequences followed by "error in /tmp/sideload/package.zip status 7.
I've since rerooted just out of curiosity to see if that would still work.
All this to fix the irritating bug of the phone powering back on by itself.
Any hints or advice?
Thanks.
-Joe

Sending your device in is not necessary at all.
It seems that you have removed one of the systems stock apps. Replace any apps that you may have removed and attempt to take the update again.
Or, you can SBF back to 602 and take the OTA update to .621. Just be sure to back up everything that you need (not including app data).
Sent from my Galaxy Nexus using Tapatalk 2

missteps
Bloatware was renamed but I've been pretty careful not to delete anything... even kept a list of what was renamed and to what. All that has been rolled back but clearly something was missed. The only thing that threw me a curve was the symlink on the Madden Football app, but even that now looks pre-modified.
I take it that changes to ACLs would also glitch the update, but what about file timestamps? How pristine do these stock apps have to be?
I'll check them again since there's little to lose in doing so. If I can't find a discrepancy, the sbf to 602 will be the next step.
Ironically, the reason for embarking on the bloat removal at the outset was to cure the auto-power on bug, which is now supposedly fixed in 621.
But it's all about the learning.
Thanks again.

Help me please 2.3.3 to 2.3.4
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error

Legit-Reflex said:
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error
Click to expand...
Click to collapse
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app

palmbeach05 said:
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I don't know how to flash, and yes i've tried multiple times downloading the update....help

Legit-Reflex said:
I don't know how to flash, and yes i've tried multiple times downloading the update....help
Click to expand...
Click to collapse
Download RSD Lite, i think the latest revision is 5.7. then download the 621 sbf, any necessary drivers, and it also helps to have the fastboot/adb package as well (even though fastboot is useless for us, still something good to have).
backup anything you need backed up or do a nandroid. reboot to bootloader. connect device to computer. start up RSD Lite. click show device. click the button that lets you browse for files. select 621 sbf. click start. sit back and let it do its thing and you'll be back up and running in no time

Links files and instruction on how to flash a sbf, are in my list
sd_shadow's [Collection] of Links for: Droid X (MB810)
Sent from my XT862 using Tapatalk

deboyz1014 said:
From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.
Click to expand...
Click to collapse
621 isn't all bad. It's easy enough to root it now with an apk called Framaroot and you will then have all the latest security updates from Motorola. If you do go with 621 you are then"stuck" there as it is not possible to go back to any earlier versions. Most of the most recently updated Roms work fine with it.
Sent from my SCH-I535 using Tapatalk

[Q] Can you install the 4.1.2 OTA on an unlocked phone with CWM installed?

I got the ota the other day and debated installing it because my M is rooted and the bootloader is unlocked and I have flashed ClockworkMod recovery. I searched for a while to see what others were saying and didn't really find anything of note so I decided to go ahead and run the install. When the phone rebooted into recovery and tried to install the update, it gave me the following Error: E: Failed to verify whole-file signature. Then there was an option to apply unsigned update (or zip, I can't remember the wording exactly). I chose not to do this and went back in the recovery menu and rebooted back into system. The phone booted normally and then immediately rebooted on its own back into recovery to try to install the update again, ending in the same results. This happened 2-3 more times before I finally formatted the Cache Partition through cwm which ended the bootloop (not sure that you can really describe that as a bootloop since it was actually doing what it thought it should be). My question is this, is it safe to go ahead and install the unsigned update via CWM? I have also since seen threads stating that if you had removed some of the bloatware apps, that the update would fail. I have removed many of these unneeded apps, should I reinstall them? I have seen a link or two to the bloat apks...

Having a unlocked bootloader doesn't matter. You just need to be stock 4.1.1 bloatware and all.

what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.

Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app

bobcheeks said:
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No. You don't have to unroot. You must have modified something else.
Sent from my Nexus 7 using Tapatalk 2

antp121 said:
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Click to expand...
Click to collapse
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!

bwat1009 said:
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
Click to expand...
Click to collapse
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2

antp121 said:
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...

bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
I RSDed back to 4.1.1 because mine hung on the clock app. I had installed the 4.2 clock.

bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...

sloosecannon said:
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
Click to expand...
Click to collapse
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...

After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.

bwat1009 said:
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
Click to expand...
Click to collapse
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.

tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium

Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Alright, thanks for the tip and the link, I will give it a try and let you know...

tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
I'm pretty sure you need an unlocked boot loader to downgrade.

netizenmt said:
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did. It fixed an issue where my phone wasn't booting, but it did not revert me to 4.1.1. Just found your comment in the other thread about modifying the xml file.. I'll try that next. Thanks.

patehi nice
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
That worked at getting the system apps that I had removed back into the /syste/app directory and now the update appears to be installing... Will let you know if it works.
*UPDATE*
Well that worked like a charm, update installed successfully, root access maintained, cwm allowed me to prevent reflash of stock recovery so all is right with the world... Thanks you guys!

Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Thank you! I had missing Amazon_IMDb.apk, Facebook.apk, Kindle.apk, PlusOne.apk files. Copied these to my phone and updated successfully!

Unroot and OTA mobile hotspot

Just thought people might like to know if you unroot via motoroot or pwnmymoto and then install the OTA, the entitlement hack sticks through the update. I only rooted for that reason and now that it stuck I don't need to re-root!
Sent from my XT1080 using Tapatalk

ssgtob1 said:
Just thought people might like to know if you unroot via motoroot or pwnmymoto and then install the OTA, the entitlement hack sticks through the update. I only rooted for that reason and now that it stuck I don't need to re-root!
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Yes you are correct it was this way on the droid razr throughout all the updates that I did. Anyways you can still have the joy in testing and go ahead and root it you can always hide root after rooting.

ssgtob1 said:
Just thought people might like to know if you unroot via motoroot or pwnmymoto and then install the OTA, the entitlement hack sticks through the update. I only rooted for that reason and now that it stuck I don't need to re-root!
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Okay, this is exactly what I would like to do to my Maxx. Don't really use root except for the wireless tether hack. What is the entire process you did if you don't mind me asking? I am currently rooted using pwnmymoto. Does it go something like this:
1. Download update.
2. Place file in correct location.
3. Unroot using pwnmymoto
4. Install update.
5. Enjoy Droid Maxx with tether and newest OTA Update.
Sent from my XT1080 using xda app-developers app

ssgtob1 said:
Just thought people might like to know if you unroot via motoroot or pwnmymoto and then install the OTA, the entitlement hack sticks through the update. I only rooted for that reason and now that it stuck I don't need to re-root!
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Can you tell us more about your setup? do you have a custom recovery? Are there any other system modifications? I am rooted with root my moto, & I have the entitlement hack, but I do not have a custom recovery. Were you pushed ota or did you download it from another source? the information is appreciated.

No customs recovery....I clicked unroot from the menu in motoroot and flashed the update zip from stock recovery. No other system mods.
Sent from my XT1080 using Tapatalk

---------- Post added at 07:23 PM ---------- Previous post was at 06:31 PM ----------
[/COLOR]
DroidJoe said:
Cool! Thats great news. Im going to do it and post results since i, and many otyhers are in the same boat. But, for us noobs out there, can you list the steps with a little more detail? Basically, start with pre-reqs, file download info, correct folder location, etc. I'll do it if you want?
Click to expand...
Click to collapse
I'm impatient: here we go.....this is what I did, it worked for me. As always, I'm not responsible for bricked phones...yada, yada, yada, proceeded at your own risk.
Prereqs: Maxx with original 4.2.2, MotoRoot 1.1 by Jcase, entitlement hack optional for free hotspot, no mod recovery, safestrap or non-stock bootloader installed. (If you do, follow instructions posted by AndrewC 2 posts below. Cheers!)
1. Download update. ( http://forum.xda-developers.com/showthread.php?t=2513563). Thanks Kickbut101.
2. Place file in correct location. (Copied from download file to sdcard file using esfile explorer while rooted)
3. Unroot using motoroot 1.1 (reboots phone, once powered up, you need to power down again).
4. Install update. (First, while holding *down* volume key, then press and hold power 5 seconds. Boots to recovery. Go down one to "recovery" and hit volume up to select. May be tricky. Find sdcard ota update file and hit power to select. Should install. Sit back and enjoy your fav beverage for about 2 or 3 minutes.
5. Enjoy Droid Maxx with tether and newest OTA Update.

I was told that I do not need to unroot if I am rooted via motoroot. Is that true?
If I do have to unroot before the ota, can I reroot afterwards using Motoroot?
Sent from my XT1080 using Tapatalk

Piaband said:
I was told that I do not need to unroot if I am rooted via motoroot. Is that true?
If I do have to unroot before the ota, can I reroot afterwards using Motoroot?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
You have to unroot if you want your phone to not bootloop once you take the OTA. Afterwards you can use RockMyMoto to root again.
Unroot using House of Moto
Root after OTA update using RockMyMoto
Check here to download the OTA

Andrew C said:
You have to unroot if you want your phone to not bootloop once you take the OTA. Afterwards you can use RockMyMoto to root again.
Unroot using House of Moto
Root after OTA update using RockMyMoto
Check here to download the OTA
Click to expand...
Click to collapse
I'm sorry. I don't understand a few things.
Why cant I just unroot using the Motoroot app that I rooted with? Are you sure Motoroot'ed phones need to be unrooted. This was the early root provided by jCase, it doesnt have anything to do with safestrap, the bootloader, or the recovery.
I'm getting some conflicting info here and I don't want to cause myself any headaches when I accept the OTA. I really appreciate the help.
I really wish jCase or someone would go over all of the root methods and how to OTA update with each one. I just feel like there has been a lot of different root methods that have come out.

Piaband said:
I'm sorry. I don't understand a few things.
Why cant I just unroot using the Motoroot app that I rooted with? Are you sure Motoroot'ed phones need to be unrooted. This was the early root provided by jCase, it doesnt have anything to do with safestrap, the bootloader, or the recovery.
I'm getting some conflicting info here and I don't want to cause myself any headaches when I accept the OTA. I really appreciate the help.
I really wish jCase or someone would go over all of the root methods and how to OTA update with each one. I just feel like there has been a lot of different root methods that have come out.
Click to expand...
Click to collapse
If you want to be able to update to the latest OTA then you will have to follow the steps provided in the links to get back to a stock system. There are no if, and, or buts about it. When you used the MotoRoot/PwnMyMoto exploit you wiped out your stock recovery. No recovery=bootloop. The only root methods available are PwnMyMoto and RockMyMoto (will work with new OTA) both by jcase.

Again, not responsible for a bricked phone, but all I had to do was use the motoroot app by Jcase to unroot after putting the ota file on my sdcard. The unroot option reboots to non-root. I powered down and booted into recovery and applied the ota zip file. That was it. No boot loops. I had no system or framework changes, and no moded recovery. Just the entitlement hack. Worked no problem. House of moto is a safe precautionary step to take but it was unnecessary in my case. YMMV.

For some reason I am unable to unroot. I have tried multiple times. I have launched the unroot option from motoroot and rebooted over and over again. I also downloaded pwnmymoto to try there but no luck.
Any one know another way to unroot? I just want to keep the entitlement hack if possible. Worst thing about all this is my phone downloaded the update so I keep getting a message to install it.
Sent from my XT1080 using xda app-developers app

Nathanjb7 said:
For some reason I am unable to unroot. I have tried multiple times. I have launched the unroot option from motoroot and rebooted over and over again. I also downloaded pwnmymoto to try there but no luck.
Any one know another way to unroot? I just want to keep the entitlement hack if possible. Worst thing about all this is my phone downloaded the update so I keep getting a message to install it.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
That's weird. It has worked for me multiple times.
I think you're best option is probably to fxz with saved data. That takes you back to stock. So I don't think it will keep the mobile hotspot.
Sent from my XT1080 using Tapatalk

I just want to post for those of you that rooted via Motoroot v1.1. This was the original root solution provided by Jcase.
I have updated my Maxx without removing root and it worked just fine.
I was rooted via Motoroot v1.1, I have the mobile hotspot hack running, and some apps that use root. No other changes were made to my device.
The update installed perfectly, my device still has root access and the mobile hotspot hack intact.
***warning*** Motoroot is different than the root solutions jCase provided later on that changed the recovery/hboot partitions. If you don't know what you're doing, you might be better off to FXZ to unrooted device before installing the update.

Piaband said:
I just want to post for those of you that rooted via Motoroot v1.1. This was the original root solution provided by Jcase.
I have updated my Maxx without removing root and it worked just fine.
I was rooted via Motoroot v1.1, I have the mobile hotspot hack running, and some apps that use root. No other changes were made to my device.
The update installed perfectly, my device still has root access and the mobile hotspot hack intact.
***warning*** Motoroot is different than the root solutions jCase provided later on that changed the recovery/hboot partitions. If you don't know what you're doing, you might be better off to FXZ to unrooted device before installing the update.
Click to expand...
Click to collapse
i am in the same situation, rooted with just motoroot and i can confirm that i just ran the ota and it went through with no issues and was able to retain root.

Andrew C said:
If you want to be able to update to the latest OTA then you will have to follow the steps provided in the links to get back to a stock system. There are no if, and, or buts about it. When you used the MotoRoot/PwnMyMoto exploit you wiped out your stock recovery. No recovery=bootloop. The only root methods available are PwnMyMoto and RockMyMoto (will work with new OTA) both by jcase.
Click to expand...
Click to collapse
That's not correct: MotoRoot DOES NOT replace the stock recovery - PwmMyMoto DOES.
If you were rooted with MotoRoot - you dont need to do anything to take the update. You can take it even while rooted.
If you were rooted with PwnMyMoto - then yes, you need to unroot and flash the stock recovery.

Anyone have this working on Maxx with 4.4 update, I am unable to locate the entitlement check location.

SDC_Bolts said:
Anyone have this working on Maxx with 4.4 update, I am unable to locate the entitlement check location.
Click to expand...
Click to collapse
Thank baby jesus and buy me a beer.
http://forum.xda-developers.com/showthread.php?p=48680232#post48680232

CrazyRussianXDA said:
That's not correct: MotoRoot DOES NOT replace the stock recovery - PwmMyMoto DOES.
If you were rooted with MotoRoot - you dont need to do anything to take the update. You can take it even while rooted.
If you were rooted with PwnMyMoto - then yes, you need to unroot and flash the stock recovery.
Click to expand...
Click to collapse
Has anyone taken the 4.4 update with motoroot yet? results? I took the camera update with motoroot and still rooted. I like it cause my /system is still write protected and i can still 1 click unroot if need be.

Sprint 4.4.2 is here.

Before downloading the OTA from the below link, please take note:
1. This is an OTA update (not the full firmware). This means that...
2. You should read the whole OP of this thread: http://forum.xda-developers.com/show....php?t=2639102
3. I am not taking responsibility for bricked devices.
4. This ZIP is not flashable via TWRP/CWM/PhilZ...stock recovery is required.
Here is the download link: http://goo.gl/D14Q5X
Thanks to nomad 64 for this.

I went through the update on my device. As it has been noted before, stock recovery is required. However, I did keep root through the process...woot!

Can I flash just stock recovery without flashing anything else, and if yes were can I find it
Sent from my XT1056 using xda app-developers app

nomad64 said:
Ditto. I am putting it on my server now to help mirror.
I went through the update on my device. As it has been noted before, stock recovery is required. However, I did keep root through the process...woot!
Click to expand...
Click to collapse
Just curious... how did you root? unlock your bootloader and use customer recovery and SuperUS? or did you use SlapMyMoto? if Slap... I've seen reports of still having root, but write protection being enabled again so you can't do anything with /system and the like..

I'm on Verizon not Sprint but I still consider this progress, happy and a little jealous of you guys!
Sent from my XT1060 using Tapatalk

charlie-n said:
Can I flash just stock recovery without flashing anything else, and if yes were can I find it
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
Yes. Reference the "Returning to Stock" section of this thread: http://forum.xda-developers.com/showthread.php?t=2603358. You have to download the whole firmware package for sprint, which sucks because you only need one file. After you have done what you need to do with TWRP/CWM, reboot your phone into the bootloader, then simply run
Code:
fastboot flash recovery recovery.img
fastboot reboot
KidJoe said:
Just curious... how did you root? unlock your bootloader and use customer recovery and SuperUS? or did you use SlapMyMoto? if Slap... I've seen reports of still having root, but write protection being enabled again so you can't do anything with /system and the like..
Click to expand...
Click to collapse
I unlocked my bootloader and flashed SuperSU. I live life on the edge!
At the time of the upgrade, I had flashed stock recovery and unfrozen Sprint Zone. I had also completely removed Xposed (uninstalled modules, disabled Xposed, and flashed Xposed-disaper.zip). I still had other root apps installed when I took the upgrade (TitaniumBackup and ROM Toolbox Pro). I have verified that they still work post-upgrade without additional work on my end.

If someone gets a copy of the ota zip faster than i upload it please message me a copy of your link and i will update the original post with it.

Dang it! Where's the AT&T one! First to get the phone, last to get the update.

jeffgt14 said:
Dang it! Where's the AT&T one! First to get the phone, last to get the update.
Click to expand...
Click to collapse
You won't be the last Verizon will haha
Sent from my XT1060 using Tapatalk

nomad64 said:
I unlocked my bootloader and flashed SuperSU. I live life on the edge! .
Click to expand...
Click to collapse
Cool. That is what I expected, and even if you lost root, you can just redo the custom recovery & SuperSU to get root back.

nomad64 said:
Yes. Reference the "Returning to Stock" section of this thread: http://forum.xda-developers.com/showthread.php?t=2603358. You have to download the whole firmware package for sprint, which sucks because you only need one file. After you have done what you need to do with TWRP/CWM, reboot your phone into the bootloader, then simply run
Code:
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
Just to confirm, this won't delete anything from the phone, just go back to stock recovery, correct?

Thanks for posting this just updated my phone
Sent from my XT1056 using Tapatalk

At the risk of sounding like a newbie, what are the steps to perform the update. I am coming from a Galaxy S4 and have only did OTA updates as they came. I just got this Moto X about 3 weeks ago during the $299 off contract price (couldn't resist). I would love to go ahead and do the update. My Moto X is stock, unrooted. Thanks

kbboykin said:
At the risk of sounding like a newbie, what are the steps to perform the update. I am coming from a Galaxy S4 and have only did OTA updates as they came. I just got this Moto X about 3 weeks ago during the $299 off contract price (couldn't resist). I would love to go ahead and do the update. My Moto X is stock, unrooted. Thanks
Click to expand...
Click to collapse
Settings - about phone - software update
MOTO X Slapped

[email protected] said:
Settings - about phone - software update
MOTO X Slapped
Click to expand...
Click to collapse
That, I know. I am asking about this file in the OP initial post, manually updating.

shaya4207 said:
Just to confirm, this won't delete anything from the phone, just go back to stock recovery, correct?
Click to expand...
Click to collapse
Correct. It will put you back on stock recovery and reboot your phone. Nothing in your /system or /sdcard will be touched. This is what I did to get back to stock recovery.

kbboykin said:
That, I know. I am asking about this file in the OP initial post, manually updating.
Click to expand...
Click to collapse
You need to have a completely stock system and the stock recovery installed. I manually flashed with super user still installed just fine but everything has to be completely stock straight out the box. To manually update you just download the zip in the OP.
1 boot into boot loader by holding volume down and power button
2 use volume key to scroll down to recovery press volume key up will put you into stock recovery with the red triangle.
3 to get to the menu screen in stock recovery you must hold volume key up then press power
4 choose to install from SD card and navigate to where the zip downloaded in this screen power button is used to select your choice. I moved the zip to the root of my SD but it usually will be found in downloads.
5 push power button to install ota manually. Be patient it will take a minute
I had it abort on me first try cause I forgot to change my fonts back to stock so be sure you are bone stock no tweaks or even V4A installed with STOCK RECOVERY.
Sent from my XT1056 using Tapatalk

dandan2980 said:
You need to have a completely stock system and the stock recovery installed. I manually flashed with super user still installed just fine but everything has to be completely stock straight out the box. To manually update you just download the zip in the OP.
1 boot into boot loader by holding volume down and power button
2 use volume key to scroll down to recovery press volume key up will put you into stock recovery with the red triangle.
3 to get to the menu screen in stock recovery you must hold volume key up then press power
4 choose to install from SD card and navigate to where the zip downloaded in this screen power button is used to select your choice. I moved the zip to the root of my SD but it usually will be found in downloads.
5 push power button to install ota manually. Be patient it will take a minute
I had it abort on me first try cause I forgot to change my fonts back to stock so be sure you are bone stock no tweaks or even V4A installed with STOCK RECOVERY.
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Thanks, this is what I was looking for. I am completely stock except for apps dl'd from Play Store and Amazon.

kbboykin said:
Thanks, this is what I was looking for. I am completely stock except for apps dl'd from Play Store and Amazon.
Click to expand...
Click to collapse
That's OK with the apps from the play store and amazon just things like exposed modules and viper 4 android have to be uninstalled basically anything that modifies your system cannot be installed. I did have Super user installed when I applied the ota with no problems though
Sent from my XT1056 using Tapatalk

dandan2980 said:
That's OK with the apps from the play store and amazon just things like exposed modules and viper 4 android have to be uninstalled basically anything that modifies your system cannot be installed. I did have Super user installed when I applied the ota with no problems though
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
SuperSU or Superuser, and what version if SuperSU. Last time I checked, SuperSU installed another system file incase the daemon method needed to be used.