4.2.1 OTA Update Fails

**marty331** · 11-28-2012, 10:02 AM

So here is the scenario, I'm rooted and running TWRP recovery. I want to get the 4.2.1 update as OTA (or at this point I'll flash it.) So I unrooted and then flashed the original recovery.img back. I then rebooted for good measure. Now I get the 4.2.1 OTA, it starts installing and then....."Error!" pops up on the screen.

I've tried this 3-4 times with the same result. Does anyone have a suggestion to resolve this?

I've also tried re-rooting and installing TWRP and flashing the update that I downloaded from AC and it fails as well.

I must be missing something. Any help would be appreciated.

**2defmouze** · 11-28-2012, 10:16 AM

Give the full error message. Sounds like you've changed something in your system, you must be fully stock to install the OTA.

Sent from my Nexus 4 using Tapatalk 2

**marty331** · 11-28-2012, 11:01 AM

It literally says, 'Error!' with the green Android robot with the red triangle.

**2defmouze** · 11-28-2012, 11:14 AM

Originally Posted by marty331

It literally says, 'Error!' with the green Android robot with the red triangle.

That sounds like you didn't properly flash the stock recovery before trying to install.

Also, what have you changed in your system since unlocking and rooting? You must reverse any alterations you've made.

Sent from my Nexus 4 using Tapatalk 2

**marty331** · 11-28-2012, 11:29 AM

So how should I properly flash stock recovery?

**2defmouze** · 11-28-2012, 11:46 AM

Originally Posted by marty331

So how should I properly flash stock recovery?

fastboot flash recovery recovery.img

Sent from my Nexus 4 using Tapatalk 2

**marty331** · 11-28-2012, 12:20 PM

That's what I did. I've even gone in and renamed recovery-from-boot.back, back to .p. Still getting the error.

I may back up all my data and restore back to factory tonight then update before I put everything back on the phone.

Sent from my Nexus 4 using Android Central Forums

**2defmouze** · 11-28-2012, 12:24 PM

Originally Posted by marty331

That's what I did. I've even gone in and renamed recovery-from-boot.back, back to .p. Still getting the error.

I may back up all my data and restore back to factory tonight then update before I put everything back on the phone.

Sent from my Nexus 4 using Android Central Forums

You could do that.. You still haven't commented on whether you changed anything in the system that would be causing the OTA to fail....

Also decide if it's worth the hassle right now.. Literally the only change in 4.2.1 that I'm aware of is the fixed People December bug.

Sent from my Nexus 4 using Tapatalk 2

**jpprice** · 11-28-2012, 12:28 PM

Did you happen to change any system files or add any system apps or anything? That will cause it to error out. It needs to be completely stock in order for it to work.

**marty331** · 11-28-2012, 12:54 PM

The only change I made was replacing the MMS.apk. I backed that out also and still got the error. I will try to back it out once more.

**2defmouze** · 11-28-2012, 12:57 PM

Originally Posted by marty331

The only change I made was replacing the MMS.apk. I backed that out also and still got the error. I will try to back it out once more.

Well there you go. You need to remove whatever mms you put in there and replace it with the stock one. That's why I asked that first, lol.

Sent from my Nexus 4 using Tapatalk 2

**marty331** · 11-28-2012, 01:12 PM

Would having additional alarm tones and notification tones cause this to fail? I have added one of each and they are in /system/media/audio/alarms % /notifications

**marty331** · 11-28-2012, 01:39 PM

OK I got tired of messing with it, I flashed stock and got the update. I appreciate the advice!

**2defmouze** · 11-28-2012, 02:07 PM

Originally Posted by marty331

Would having additional alarm tones and notification tones cause this to fail? I have added one of each and they are in /system/media/audio/alarms % /notifications

Yes.... Any change you made to the stock system.. Adding or subtracting any file from /system/**** counts as changing the system.

Sent from my Nexus 4 using Tapatalk 2

**marty331** · 11-28-2012, 03:37 PM

Is there any way to do a compare to find changes?

Sent from my Nexus 4 using Android Central Forums

**2defmouze** · 11-28-2012, 04:05 PM

Originally Posted by marty331

Is there any way to do a compare to find changes?

Sent from my Nexus 4 using Android Central Forums

No, just need to remember what you are changing if you intend on reversing them to take an OTA later, and leave yourself a way to change them back. If you have a bad memory just keep a list somewhere as you change anything

Sent from my Nexus 4 using Tapatalk 2

**shades#AC** · 11-28-2012, 10:29 PM

Hello, sorry for hijacking the thread. But I'm experiencing the same issue.

I was running 4.2 on my Galaxy nexus, it wasn't even rooted. One of two things caused the device to get stuck on the google Logo, it could be after I attempted to root (though it did boot once) or it could be after using an LCD density changer (<----silly mistake).
Regardless, in attempt to get the device working again, I resorted to re-flashing the system.img downloaded from the stock roms provided by google. I used the 4.2 version.
After that the device booted as if nothing happened, all my data and settings were intact and soon after, a System Update was available. In the details of the update it said it was 4.2 and it was only about 900 KB. Since I'm still using the stock recovery image and have the stock system.img, one would assume there should be no issue. Unfortunately, it starts to run the update and at around 30% it stops with Error!.
Still waiting for the OTA to show up again.

Any help would be appreciated.
Sorry for the long post, but I thought a bit of history might help.
Thanks in advance
Summary:
Galaxy Nexus, Stock Recovery, Unlocked bootloader, stock system.img
OTA around 900K fails.

**2defmouze** · 11-29-2012, 05:17 AM

Originally Posted by shades#AC

Hello, sorry for hijacking the thread. But I'm experiencing the same issue.

I was running 4.2 on my Galaxy nexus, it wasn't even rooted. One of two things caused the device to get stuck on the google Logo, it could be after I attempted to root (though it did boot once) or it could be after using an LCD density changer (<----silly mistake).
Regardless, in attempt to get the device working again, I resorted to re-flashing the system.img downloaded from the stock roms provided by google. I used the 4.2 version.
After that the device booted as if nothing happened, all my data and settings were intact and soon after, a System Update was available. In the details of the update it said it was 4.2 and it was only about 900 KB. Since I'm still using the stock recovery image and have the stock system.img, one would assume there should be no issue. Unfortunately, it starts to run the update and at around 30% it stops with Error!.
Still waiting for the OTA to show up again.

Any help would be appreciated.
Sorry for the long post, but I thought a bit of history might help.
Thanks in advance
Summary:
Galaxy Nexus, Stock Recovery, Unlocked bootloader, stock system.img
OTA around 900K fails.

Honestly its hard to speculate.. as in the earlier case it appears the update is not satisfied that you are stock. Given the issue you had and fixed its impossible to guess at what exactly you would need to change to correct it, at least for me. I would just do a full factory image restore, if getting the OTA right now is that important for you. You can backup what you need to your computer first.

Sent from my Nexus 4 using Tapatalk 2

**marty331** · 11-29-2012, 09:34 AM

Originally Posted by 2defmouze

No, just need to remember what you are changing if you intend on reversing them to take an OTA later, and leave yourself a way to change them back. If you have a bad memory just keep a list somewhere as you change anything

Sent from my Nexus 4 using Tapatalk 2

Yes a list is in order. Here is what I ended up doing.

Backed up data and apps with Titanium Backup.
Copied that backup to my computer, Ubuntu.
Restored back to factory, used the guide you posted.
Received the OTA to 4.2.1.
Rerooted and reinstalled Titanium Backup.
Copied my backed up data and apps back up N4.
Restored data and apps with Titanium Backup.

Total time 20 min.

Sent from my Nexus 4 using Android Central Forums

**2defmouze** · 11-29-2012, 10:32 AM

Originally Posted by marty331

Yes a list is in order. Here is what I ended up doing.

Backed up data and apps with Titanium Backup.
Copied that backup to my computer, Ubuntu.
Restored back to factory, used the guide you posted.
Received the OTA to 4.2.1.
Rerooted and reinstalled Titanium Backup.
Copied my backed up data and apps back up N4.
Restored data and apps with Titanium Backup.

Total time 20 min.

Sent from my Nexus 4 using Android Central Forums

Fantastic... Glad you got through it easily and kept your backups, nice job

Sent from my Nexus 4 using Tapatalk 2

**Adam Breckels** · 12-09-2012, 02:00 AM

I was stuck with the same issue... I'm a total n00b but I finally figured it out.

Here's what I did.

Using only Nexus Root Toolkit 1.6 ()
1. Unlock - (didn't lose any data)
2. Root - (didn't lose any data)
3. Go through hell trying to figure out why it was erroring out...
4. Clicked "Flash Stock + Unroot" and pointed to the ROM I downloaded to PC from Google Dev page ()
5. Allowed it to wipe all data (manually backed up long before doing anything) - (lost all data... obviously)
6. Allowed it to restore the factory image as if I had it all along... Presto. 4.2.1 upgraded from 4.1.1.

After I figured it out, it made sense. You can likely use the backup/restore options too, but I prefer a fresh device, and just allowed my apps to download again from google. Since I use dropbox/gservers & my desktop to keep everything, there really wasn't any issue. I don't have call logs or texts, but that doesn't matter to me.

Hope this helps. Remember, I'm a n00b to Android (switched from iOS about 2.5 weeks ago and the GN I got was the first Android device I've ever laid finger prints on). Be nice please and thanks for all the near-hit tips!

Cheers!

**marty331** · 12-09-2012, 07:03 AM

Adam,
Thanks for the help but toolkits (imho) should never be used. The only if you read the thread you'll see I resolved the issue.

Sent from my Nexus 7 using Android Central Forums

**digitalslacker** · 12-09-2012, 07:30 AM

Originally Posted by marty331

Adam,
Thanks for the help but toolkits (imho) should never be used. The only if you read the thread you'll see I resolved the issue.

Sent from my Nexus 7 using Android Central Forums

Toolkits save you time. I think doing something the easy way is fine so long as you know and understand the right way for when you get in a bind.

Sent from my Nexus 7 using Tapatalk 2

**2defmouze** · 12-10-2012, 05:54 AM

Originally Posted by digitalslacker

Toolkits save you time. I think doing something the easy way is fine so long as you know and understand the right way for when you get in a bind.

Sent from my Nexus 7 using Tapatalk 2

Blasphemy! Toolkits are the devil!

Sent from my Nexus 4 using Tapatalk 2

**digitalslacker** · 12-10-2012, 07:36 AM

Originally Posted by 2defmouze

Blasphemy! Toolkits are the devil!

Sent from my Nexus 4 using Tapatalk 2

LOL, right! I was probably drunk when I said that.

I just use them because I'm lazy and don't wanna type a bunch of commands and go download the right images. I've been coding for a long time, doing "leet" things in command prompt for the sake of doing them lost it's appeal 10 years ago. I'll take a GUI that I don't have to maintain that's as good as anything I can write any day.