[ROOTED] 4.1.2 not wanting to update to 4.2

bldrgn2043

Active member
Oct 3, 2012
26
0
0
Visit site
I unlocked and rooted my nexus 7 with zero neck's guide but did not flash a custom recovery on it, so it still has the stock recovery. Iv gone into settings > apps > all > google services framework, cleared the data and force stopped it. That will let me download 4.2 again but after I reboot and it goes to install, the little android guy on his back with the red triangle. I have also tried using the side-load method, but google's adb driver wont install on windows 8. I want to update to 4.2 but I don't want to have to wipe it to install the update. Any help would be great.
 

2defmouze

Well-known member
Jul 9, 2011
3,945
1,552
0
Visit site
Sounds like you do not have stock recovery, even though you think you do. Toward the end of Zero's guide is indo on re flashing the stock recovery. Follow that and make sure you use the one from the 4.1.2 image.

Sent from my Galaxy Nexus using Tapatalk 2
 

bldrgn2043

Active member
Oct 3, 2012
26
0
0
Visit site
I installed the stock 4.1.1 recovery on zero neck's guide, then I tried to install the update again and I got the little android guy on his back with the red triangle. This time I looked at the install log and it showed this.
"Finding update package...
Opening update package...
verifying update package...
installing update...
verifying current system...
assert failed: apply_patch_check("/system/etc/audio_effects.conf", "32bb24643c41682d5d7f6684619af9ec0513ff5b", "e66091c592baf2bd3b898c789269c1b0d3c7561d")
Installation aborted."
 

2defmouze

Well-known member
Jul 9, 2011
3,945
1,552
0
Visit site
I installed the stock 4.1.1 recovery on zero neck's guide, then I tried to install the update again and I got the little android guy on his back with the red triangle. This time I looked at the install log and it showed this.
"Finding update package...
Opening update package...
verifying update package...
installing update...
verifying current system...
assert failed: apply_patch_check("/system/etc/audio_effects.conf", "32bb24643c41682d5d7f6684619af9ec0513ff5b", "e66091c592baf2bd3b898c789269c1b0d3c7561d")
Installation aborted."

Sounds like you have changed your system.. You have to be completely stock for the OTA to install, and it's saying you've altered something.

Sent from my Galaxy Nexus using Tapatalk 2
 

rootbrain

Well-known member
Oct 13, 2011
742
70
0
Visit site
Sounds like you have changed your system.. You have to be completely stock for the OTA to install, and it's saying you've altered something.

Sent from my Galaxy Nexus using Tapatalk 2

+1 this. Did you use the Louder mod or change your properties file in anyway? If so, you need to probably wipe and start over, or revert back to stock manually.
 

bldrgn2043

Active member
Oct 3, 2012
26
0
0
Visit site
I haven't changed anything on it just unlocked and rooted it but I'll just wipe and install. It would end up being faster that way anyways.
 

Edwill86

Well-known member
Feb 2, 2011
1,224
82
0
Visit site
I haven't changed anything on it just unlocked and rooted it but I'll just wipe and install. It would end up being faster that way anyways.

Had the same issue going from 4.1.1 to 4.1.2 and now had it happen going to 4.2. I'm rooted with stock. Flashed a kernel. Quick fix is to flash the stock image of the version you have. Using wugs tool kit makes it super easy to do. Then the update will work If u manually flash it or via ota. Its just annoying because it will wipe or device.
Good luck!
 

SteveC

Well-known member
Jan 15, 2010
79
1
0
Visit site
[ROM][11/14][JB 4.2] Stock Rooted (Works!) - JOP40C - Apps De-Odexed! - xda-developers
Download and flash the ROM in that link. It is a rooted stock 4.2 ROM. I wiped cache, dalvik, system and did a factory reset. Works great with none of the issues that are complained about. It's a bit of a pain to have to do the full wipe, but it's a bigger pain to have a not quite working, funky install. I have twrp and can easily restore either 4.1.2 or 4.2 nandroid backups. 4.2 will create a folder called "storage0" or just 0 and previous stuff will be there. You will have to move stuff from 0 to twrp to have the recovery able to find it.
 

rootbrain

Well-known member
Oct 13, 2011
742
70
0
Visit site
Had the same issue going from 4.1.1 to 4.1.2 and now had it happen going to 4.2. I'm rooted with stock. Flashed a kernel. Quick fix is to flash the stock image of the version you have. Using wugs tool kit makes it super easy to do. Then the update will work If u manually flash it or via ota. Its just annoying because it will wipe or device.
Good luck!

Flashing a kernel could change a lot of things, including the build.prop file. Make sure you are on stock. On my Nexus 32 after I upgraded to 4.2 I hated it and went all the way back to 4.1. After starting, I upgraded to 4.1.1, then 4.1.2, then rooted and added CWM recovery. After that I rebuilt my apps and settings, then flashed a custom kernel for performance tweaks.
 

Forum statistics

Threads
943,011
Messages
6,916,882
Members
3,158,773
Latest member
Chelsea rae