Database Users

OTA Update issues

So I have Unrevoked3, and want to update OTA, I don't need root anymore.
However, when I update it goes to start the update, then I get a yellow triangle with an exclamation point and an android, it just sits there til I pull the battery.
I want to be sure this is just an issue with needing to unroot, and not something else.
If its just an unrooting issue, how do I unroot from Unrevoked3? All the unrooting topics I've found were for toast or simpleroot.
Sent from my PC36100 using XDA App

Btw, the RA is Clockwork recovery.
Sent from my PC36100 using XDA App

Pretty sure all you need to do is put the update on your SD card, flash it, and then you're done. You'll lose root, but it should work that way. YMMV and all that.

I'll try it when I get home, hopefully it'll work.
Sent from my EVO using the Xda App

any word? I too am having the yellow triangle displayed on my screen when trying to install the OTA after doing Unrevoked 3

Nevermind, Im downloading now.
Im also downloading the 1.47 RUU incase I need to start from scratch, which Ive heard works with revoke.. Im just not sure how to reflash the stock recovery image and get rid of Clockwork Mod and Unrevoked.
I ran flash sdcard:update.zip and so far its updating with no issues, will wait for boot up to see if it took.

I think using the ruu is the only way to reset the recovery, anyway thats what I did and d/ling the OTA now.

Worked fine. Booted up took a bit, but Im used to that with all updates, Im now running Android 2.2
As a side, is the FroYo update supposed to wipe apps/settings? Mine werent.

well mine seemed to work, I didn't care about reseting so my process went like this..
completely stock+unrevoked3 root+clockworkmod
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe
OTA d/l and installed over 1.47
ota installed successfully
factory defaulted with 2.2 in place

Im running 2.2, but none of my settings were reset and all my apps are still there.

Does running this : RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe erase all of the phone's previous memory?

freditoj said:
Does running this : RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe erase all of the phone's previous memory?
Click to expand...
Click to collapse
Yes.
It does not erase your sd card tho.

So unrevoked 3 users can't use the Froyo OTA update?

[Q] For OTA Update - Unrooting Necessary?

I remember reading about having to unroot your phone from the Froyo update. I have the Z4root but it only has a root button.
1. Is it advisable to unroot for OTA update?
2. Any resources for Z4unroot?
Thank for helppin' a n00b out.

It is correct that you'll need to have your phone unrooted to receive the update. Are you rooted with z4 now? If so you should be able to click on z4 and have the "unroot" option appear. If it doesn't appear I have no idea where you should go. Did you do a nandroid backup as well? !
Sent from my DROIDX using XDA App

Unrooting has never been necessary. You just need to be on the stock rom without any system apps removed.

How about frozen apps in Titanium Backup... need to unfreeze?

Dr, you're saying leaving phone rooted will not stop ota? I don't want update. Have frozen 2.2.1 updater in titanium and some other bloatware as well. I was informed doing all this would stop update.
Sent from my DROIDX using XDA App

Being rooted will change nothing about the update. I can't speak to how Titanium Backup freezes apps, but I know in the past if someone removed/renamed apps in the /system/apps folder the update failed.
You should google/search this site for answer on how to avoid downloading the update if that's what you want.

What needs to happen in order for you to receive the update is that you must be on stock blur rom that came with the phone as well as not have any programs that prevent it from updating IE bootstrapperx, titanium pro, romwork (or w/e its called) etc. A lot of programs used to do Rome like the ones mentioned above have built in code to tell the ota update to basically go **** itself
Sent from my DROIDX using XDA App

PM me i'll hook you up

I didn't have to unroot when I did the 2.2 OTA update. But just before I updated, I did unfreeze all the crapware I froze with Titanium Backup. Didn't have a single issue. Once I was on 2.2, I froze all the crapware again.

i have never un-rooted my phone for any updates. They always pass fine if rooted. Only fail if you have messed with bloatware or have a bootloader installed. You even keep the Super User App, but it just has lost root rights so it will no longer work until you re root the device

Concerned about rooting

I'm concerned about rooting or modifying my Atrix a second time. My first Atrix that I had rooted stopped working when I tried to update the OS through the wi-fi download of the update. Mid-way through, the Android mascot and the exclamation sign came up and I had to pull the battery. When I rebooted the phone it said the modem failed to start up. I don't know the reason for it but I went to the store and used my insurance to get a fresh one. Since then, I have only sideloaded apps and now with the Gingerbread update I don't have to use a USB cord to install apps anymore. I'm afraid to try to root or modify my Atrix again.

Bagel Bear said:
I'm concerned about rooting or modifying my Atrix a second time. My first Atrix that I had rooted stopped working when I tried to update the OS through the wi-fi download of the update. Mid-way through, the Android mascot and the exclamation sign came up and I had to pull the battery. When I rebooted the phone it said the modem failed to start up. I don't know the reason for it but I went to the store and used my insurance to get a fresh one. Since then, I have only sideloaded apps and now with the Gingerbread update I don't have to use a USB cord to install apps anymore. I'm afraid to try to root or modify my Atrix again.
Click to expand...
Click to collapse
Rooting should not have given you that problem. I've rooted numerous A4g's on froyo and they are all running GB fine after the ota. I also re-rooted them all now that they have GB. No issues. Also if your atrix didn't give you a boot error right when you turned it on you could have manually flashed a build and wouldn't have had to use you insurance.
Sent from my MB860 using XDA App

Alright, that eases my mind. Perhaps I just had some hardware failure.
How does rooting affect everything? Like you said, you are able to update via OTA when rooted and everything is fine. I also have a question about how to root exactly. I saw the sticky but it only mentioned the leaked release of Gingerblur and not the OTA version. Does the information still apply?

Its a little more involved if don't have your bootloader unlocked. Follow the post mramirezusa has about automatic unlocked bootloader and root.
Sent from my MB860 using XDA App

Be sure to read the instructions twice, then read it again for good measure!
Also check out the [HOWTO] Root after sbf flash thread in the dev section
Sent from my MB860 using XDA App

[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] Rooting Confusion on latest OTA Update

I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.

You can't root mf3. You never should have taken the update if you want to be rooted. Cross your fingers that someone finds a way to root the update but I'm not sure you should hold your breath.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

So is doing a stockrom restore back to MDL an option? Then just root that with Motochopper? And disable OTA updates till its figured out?
The real joke here is that to get their built in app-to-sd functionality they give you an update that hogs up another 1GB!

Nope. Can't go back. Just gotta wait it out. Cheers

Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?

TheKog said:
Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?
Click to expand...
Click to collapse
A qfuse is blown when you take the update. It won't let you odin or anything else to go back to an earlier firmware.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app