• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root 2.3.340 Update Failed - Help

lexluthor

Android Expert
I'm trying to do the OTA update of 2.3.340 and it's failing.

I had previously unrooted 2.3.15 early on using a fairly manual method. I had frozen some apps using titanium.

Prior to the running the OTA, I unfroze all of the frozen apps.

Since I have a Titanium backup, it wouldn't be the worst thing if I have to blow it all up to get the OTA.

Can I sbf back to a previous version and then get the OTA?

What version do I go back to? Does 2.3.320 allow me to get the OTA?

How do I do it?
 
I need some help also. I'm in worse situation though. I removed apps but didn't back it up before I did. I also don't know how to SBF. Don't know what I am going to do now.
 
I have bootloader 30.03 by the way.

I'm thinking of sbf'ing the offiical 2.2 (2.3.15). Is that a good way to go here?
 
I just tried to unroot, then went into system>privacy>system reset. It reset alright! I checked out my app drawer and it still didn't have things like city id and all the other apps I deleted before. I tried the update and it still failed. Did I need to give it more time to download those apps?
 
No, system reset like you did won't bring back those apps.

I think an sbf will, but I'm hoping someone can confirm that an sbf will bring me back to 100% stock.
 
Lex, which update you running, if your on .320 you cannot go back to .315. I think that's the correct numbers, sorry still waking up!!
 
If you are at 2.3.15 you can SBF with 2.3.15 SBF if you are on 2.320 do not use 2.3.15 or you will have a brick.. clear you cacah in recovery and then try and update that should fix you problem...
 
If you are at 2.3.15 you can SBF with 2.3.15 SBF if you are on 2.320 do not use 2.3.15 or you will have a brick.. clear you cacah in recovery and then try and update that should fix you problem...
I cleared the cache in recovery mode and the update still didn't work. Previously I had cleared the cache using a cache cleaner app.

So, if I have bootloader 30.03 with 2.3.15 official, I can download this
http://www.mydroidworld.com/forums/droid-x-discussion/5151-droid-x-2-2-full-sbf-leaked-download-now.html
and install via sbf.

Then I'll be back at 100% stock, previous OTA, with all the bloatware, no root, etc and then I can just OTA with today's 2.3.340 update?
 
I cleared the cache in recovery mode and the update still didn't work. Previously I had cleared the cache using a cache cleaner app.

So, if I have bootloader 30.03 with 2.3.15 official, I can download this
http://www.mydroidworld.com/forums/droid-x-discussion/5151-droid-x-2-2-full-sbf-leaked-download-now.html
and install via sbf.

Then I'll be back at 100% stock, previous OTA, with all the bloatware, no root, etc and then I can just OTA with today's 2.3.340 update?

yes but make sure the sbf say 2.3.15 and after you can use z4root to root. make sure your phone is charged 70% min before flashing
 
If youre bootloader is 30.03, you're safe to flash with 2.2 sbf.

No need to unroot first to get the OTA.

Here's your Motorola drivers: USB and PC Charging Drivers - Motorola USA
Which drivers do I download? There's Motorola 4.7.1 Driver with Motoconnect and then PC Driver 1 and PC Driver 2 below.

Oh, and after the cache clear, it's not that the OTA failed, it's telling me I'm up to date, but I'm still have 2.3.15. Before the cache clear, the update check worked. Weird.

Is there an update.zip on my phone from the previous OTA fail that I could install from recovery mode? I don't see it on the sdcard and a root explorer search doesn't find it.
 
Which drivers do I download? There's Motorola 4.7.1 Driver with Motoconnect and then PC Driver 1 and PC Driver 2 below.

Oh, and after the cache clear, it's not that the OTA failed, it's telling me I'm up to date, but I'm still have 2.3.15. Before the cache clear, the update check worked. Weird.

Is there an update.zip on my phone from the previous OTA fail that I could install from recovery mode? I don't see it on the sdcard.

i would wait to sbf verizon is having 3g problems give it some time and then sbf if it still won't download
 
i would wait to sbf verizon is having 3g problems give it some time and then sbf if it still won't download
It downloaded earlier, that wasn't the problem. It just failed. Then I did a clear cache in recovery mode as suggested by someone earlier and now it doesn't even see there's an update available. I'm on wifi too. Doubt any of that has to do with Verizon's 3G problems this morning.
 
It downloaded earlier, that wasn't the problem. It just failed. Then I did a clear cache in recovery mode as suggested by someone earlier and now it doesn't even see there's an update available. I'm on wifi too. Doubt any of that has to do with Verizon's 3G problems this morning.

It has already download to you phone ?
 
It has already download to you phone ?
Yes, it did earlier, but then the update failed.

Now, after clearing the cache, it says my device is update to date when I try to check for update.

I'm assuming it's something in my phone that's screwed up, but is it possible they pulled the update? Can anyone else who hasn't updated currently get the update? I'm sure we'd have seen lots of posts about that if that was the case though.
 
It downloaded earlier, that wasn't the problem. It just failed. Then I did a clear cache in recovery mode as suggested by someone earlier and now it doesn't even see there's an update available. I'm on wifi too. Doubt any of that has to do with Verizon's 3G problems this morning.

Is that why my internet went down right before I went to bed! I just started to overclock and thought that was it. I woke up and its back and fast as ever!!
 
Yes, it did earlier, but then the update failed.

Now, after clearing the cache, it says my device is update to date when I try to check for update.

I'm assuming it's something in my phone that's screwed up, but is it possible they pulled the update? Can anyone else who hasn't updated currently get the update? I'm sure we'd have seen lots of posts about that if that was the case though.

I saw this problem before I am looking for it now, go to files and look aournd I think it's stored on you phone. If not I think you might have to sbf
 
Back
Top Bottom