Help 4.2.2 Not installing

[beefamato]

I'm on 4.1.1 stock rooted. I've received the 4.2.2 update and tried to install it a few times. I have the stock recovery and it begins to install, but gets about halfway through and then stops. The sad android is sad.

Is there a way to know what is failing and fix it?

 

[Unforgiven]

Have you frozen any bloatware (vzw apps) or flashed a custom recovery or kernel?

 

[beefamato]

Thanks for looking.

Stock recovery.

No frozen bloatware.

I did have a different kernel, but I reflashed the stock one that I extracted from google factory images (found here).

Like I said, I hit "install now" and it starts installing the 4.2.2 update I received OTA in the stock recovery, but about halfway through the progress bar, it turns to the sad android on its back.

 

[Unforgiven]

Hmm, something is amiss. That link looked like it went to the 4.1.1 toro kernel, so you should be fully stock. Let me look around.

 

[beefamato]

Here is text from the end of the last recovery log. Any ideas?

Finding update package...
I:Update location: /cache/5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip
Opening update package...
I:2 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1604 bytes; signature 1586 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
installing samsung updater extensions
installing samsung updater extensions for toro
Verifying current system...
contents of partition "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot" didn't match EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4470784:fbd13c778b34fdb7917c1ccee6389aa9b13a92bd:4505600:a62e93d5d96d19351ce2ce330bbcdccb248395fb
file "EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4470784:fbd13c778b34fdb7917c1ccee6389aa9b13a92bd:4505600:a62e93d5d96d19351ce2ce330bbcdccb248395fb" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4470784:fbd13c778b34fdb7917c1ccee6389aa9b13a92bd:4505600:a62e93d5d96d19351ce2ce330bbcdccb248395fb")
assert failed: apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4470784:fbd13c778b34fdb7917c1ccee6389aa9b13a92bd:4505600:a62e93d5d96d19351ce2ce330bbcdccb248395fb")
E:Error in /cache/5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip
(Status 7)
Installation aborted.

 

[Unforgiven]

contents of partition "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot" didn't match

that looks like you don't have the stock bootloader or maybe you got bad download and the MD5 didn't match.

 

[beefamato]

Hrm. Any guesses on how to fix?

 

[jhawkkw]

Was the custom kernel franco by any chance?

 

[beefamato]

It was, actually. How did you know? Trying a thousand different things ended up messing up the architecture of my SD partition, and so updating became a huge problem. I even installed a ROM, but so much was jacked from different kernels and recoveries that it was a convoluted mess.

I ended up wiping the whole thing (SD and all) and freshly installing 4.2.2 from Google's image that they just released. It was some work, but I'm glad to have a nice, crisp, fresh install.

 

[jhawkkw]

It was, actually. How did you know? Trying a thousand different things ended up messing up the architecture of my SD partition, and so updating became a huge problem. I even installed a ROM, but so much was jacked from different kernels and recoveries that it was a convoluted mess.

I ended up wiping the whole thing (SD and all) and freshly installing 4.2.2 from Google's image that they just released. It was some work, but I'm glad to have a nice, crisp, fresh install.

Yeah, that was what I was going to recommend. The reason I could tell it was Franco is because franco kernel changes the ramdisk when it is flashed in order to operate correctly. It's the only one that does that and as a result can cause a lot of issues when changing kernels.

 

[umataro42]

Have you frozen any bloatware (vzw apps) or flashed a custom recovery or kernel?

Sorry if this is sort of in the wrong section, but I was wondering, if you're flashing a ROM update, do they also check for frozen or forcibly removed "stock" apps like the OTA does? Or will it vary by ROM?

Just wondering if I can remove some unused apps on a custom ROM and not worry about errors the next time there's an update to flash.