Related
Ok i've searched the forums and am getting more and more confused. I have gingerblur 3.1 installed currently and would like to do the ATT ota update. Can I just download it and install from the system update? Or do I need to wipe the whole phone clean and start over? Thanks and sorry if this is a duplicate.
I am wondering this too...
Sent from my MB860 using XDA Premium App
I'm in the same boat, I got GingerBlur 4.5 installed and I would like to install the Gingerbread 4.5.19 OTA update. Are there proper instructions out there? I can't find any. I'm assuming I may have to go back to Stock 1.8.3 and do an OTA update. But can someone please confirm. Any instructions would help as well. Thanks
The directions I seem to need are...
Un gingerblur
Un root
As an aside, I got notified of the ota and it failed.
Sent from my MB860 using XDA Premium App
goofyj8 said:
I'm in the same boat, I got GingerBlur 4.5 installed and I would like to install the Gingerbread 4.5.19 OTA update. Are there proper instructions out there? I can't find any. I'm assuming I may have to go back to Stock 1.8.3 and do an OTA update. But can someone please confirm. Any instructions would help as well. Thanks
Click to expand...
Click to collapse
Make sure your battery is fully charged so that you don't run out of power during the upgrade process.
To install the upgrade:
Copy the file to the SD Card
Your phone is on the latest Android 2.2 software (Blur_Version.4.1.83.MB860.ATT.en.US)
From the home screen, press Menu, select Settings,
Scroll down and select About Phone.
Select System upgrades.
After a couple of minutes, your device will confirm the upgrade is available.
The Copy prompt will appear. Select “Copy”
The Install upgrade prompt will appear. Select Install Now.
Your device will power off and display installation progress.
IMPORTANT INFORMATION:
Please ensure you are aware of the following information after the installation of the package
It will then power up and stay on the carrier logo for up to 5 minutes before powering on to the home screen.
Please do not interrupt this process.
Contacts and email from Google and MOTOBLUR may take up to 60 minutes to synchronize. The phone may appear slower during this initial synchronization process
I am in the same boat as that guy with gingerblur 4.5 .
I don't have an sd card around me atm so would putting the file on the internal storage work or not?
ALSO if I update this way, will it delete all of my media and apps? thanks
ota update to gingerbread
damonsmith666 said:
I am in the same boat as that guy with gingerblur 4.5 .
I don't have an sd card around me atm so would putting the file on the internal storage work or not?
ALSO if I update this way, will it delete all of my media and apps? thanks
Click to expand...
Click to collapse
please just wait for a dev to answer this question or we may brick or worse lose root forever (ohh noo) seriasly just be calm a work around will be comming soon
I will wait...
Sent from my MB860 using XDA Premium App
same issue here
i tried to install the OTA update, it failed... tried to install it manually and it didn't work either. i tried to install it using android recovery and it didn't work.
Im using gingerblur 4.5
side note,
can any one of you please provide the full name of your system version? mine says "Version.4.1.83.MB860.ATT.en.US ", thing is, I tried to flash a stock sbf to roll back to motoblur, RSDlite fails every time with a message "sec_exception febe 35 35", my phone isn't recognized as 'NS Flash Olympus', it shows 'SE Flash Olympus'.
is there a thread to fix this issue?
thanks!
I figured out how to do it. First I unlocked the bootloader and then followed the directions on here.
http://forum.xda-developers.com/showthread.php?t=1163342
Worked fine
You need to flash back to stock, i.e. flash 4.1.26 or 4.1.57 or 4.1.83. OTA update to 4.1.83 if you are on an earlier version. The update will not work if you are modded in any way. You need to be on stock 4.1.83.
My god, how many times does this have to be said!!!
So let's just say that you are a moron (like me) and just did the OTA over Gingerblur 4.5 and now you have the exclamation point triangle and android on your screen and it does do anything... is it safe to battery pull? or did I just brick my phone?
EDIT: nevermind...
Is there any guide how to flash back?...
Sent from my MB860 using XDA Premium App
Well you could use rsd if you've never installed the GB ota.
Sent from my MB860 using XDA Premium App
Update, now problem
I was on gingerblur 4.5, rooted, sideload enabled.
used RSD to flash 4.1.83 - successful - booted - checked mail - etc...
went to Motorolla.com and DL the official firmware
copy .zip to sd
settings/about/upgrade
let it run
followed instructions to the letter from Motorola
30 minutes now on the Rethink Possible screen - seems like a fail?
Help?
Update - she lives, just needed to wait about 45 minutes
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
I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.
Doogiedoo said:
I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.
Click to expand...
Click to collapse
Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.
I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.
Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).
how did you get rid of superuser on fruitcake?
ghost_og said:
Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.
I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.
Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).
Click to expand...
Click to collapse
Not at all, if it's any use to anyone, feel free to repost it. Also, I had a hardware problem (screen banding) on my atrix and sent it back for repairs. When it was returned, it no longer showed unlocked. The bootloader was still unlocked, but I had to reapply the unlock sbf to get it to show again (before using another rom).
ummkiper said:
how did you get rid of superuser on fruitcake?
Click to expand...
Click to collapse
I still had it installed on fruitcake, but lost it (well, rather lost root access, as the app "superuser" is still there but not functional) when I installed the sbf file initially. I'm not sure if flashing pudding or using the automatic unlock on the fruitcake initially would have worked. I didn't think to try it initially.
Cool,thanks for the info.
Sent from my Nexus One using xda premium
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
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
minjiet said:
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
jalize said:
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
Click to expand...
Click to collapse
Ya, i'm rooted, now the n10 cant boot at all....what can i do?
anyone can show me step by step guide?
Or flash the Factory image with a bit editing. This should do: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app
I got that as well on my N10. Stock, stock recovery rooted. Booting into recovery didn't help. The next morning it was the same thing, but after a while it shut itself off and when I was ready to flash a stock img, had the USB cable plugged into the laptop, I look at the N10 and it's booting just fine, then starts applying the update.
Not helpful I know, but just wanted to let you know it fixed itself, I did nothing. Good luck.
Same problem on stock rooted. Impossible to boot and to switch off the device. I've wait the nexus shut down by himself and after the update have been automaticaly installed on the boot. I'm always rooted. Strange.
Use http://www.afterdawn.com/software/s...l_devices/nexus_root_toolkit.cfm#all_versions app is the best to fix and very easy
Sent from my Nexus 10 using XDA Premium 4 mobile app
---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------
A fixed all my problems, i am on stock with the same problem on jelly bean 4.3, now rooted and again with a custom recovery.
Sent from my Nexus 10 using XDA Premium 4 mobile app
thanks for the help...my n10 back to normal automatically after i plug in charger...weird
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
DEinspanjer said:
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
Click to expand...
Click to collapse
When you cleared cache you lost the update package I believe, so it didn't update, when I received my OTA I had TWRP installed and it went through nicely. Maybe you should try it and then installing Stock Recovery again.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
I have a Nexus 10. I just took and installed the OTA that arriced 08/27/2013. I am not rooted or unlocked. It is only a wifi (not a carrier specific).
I have been sick since i took the first Ota several weeks ago. I was constantly having to reboot because it would drop the connection. Firefox was useless. And above all, I was unable to get Grassland Live wallpaper and Wind Turbine 3D to work.
It all works now!
Sent from my Nexus 10 using xda app-developers app
I just read in another thread that the issue as described is caused by apply the OTA when rooted. Just unroot then apply the OTA update and reboot. Assuming you are using SuperSU., it has an unroot option in the settings panel.
Good luck.