Sent from my Nexus 7 using Tapatalk 2
I am hoping someone here can answer this:
I have been reading a lot of threads related to 4.2 update. Some says that current ClockworkMod Recovery 188.8.131.52 is not compitable with 4.2, so they recommending to flash the stock recovery (did not see if they meant stock recovery from 4.1.2 or 4.2) and try to manually flash (or try OTA)
I start to think that my OTA fails because when OTA kicks in and asks me to install, I click install and then it boots in to my ClockworkMod Recovery 184.108.40.206, then it fails. I am just dead curious if I flash stock recovery, and go thru normal OTA process and see if it will work.
A couple things.
First, there was an issue with custom recovery starting in 4.1.2. Versions of both CWM and TWRP, up until that point, would NOT work at all with the 4.1.2 bootloader. So many people had to revert to the 4.1.1 bootloader. However, since then, CWM and TWRP released newer versions that were compatible. Those compatible versions should still work with 4.2, but if you try an older version, it will probably have the same issue as 4.1.2.
Second, you will NOT be able to use the OTA update, through the system updater, unless your tablet is almost completely stock. While certain things like root or busybox are irrelevant, having a custom recovery, custom kernel, frozen/removed/modified system apks, modified build.prop, etc. will cause the auto updater to fail. You can however use that OTA update zip file in a custom recovery (manually), but again, all the other items need to be stock. The OTA update is a bunch of patches. Unlike the full image (which you can download now), which is significantly larger, the OTA update doesn't actually have all the new files, it has the information necessary to patch your current files to bring them up to the current version. In order for that patch to work, it needs to verify that they are the correct (4.1.2) version. This is a safety precaution, since patching a modified file would cause significant problems. As such, it verifies the SHA1 checksum of all the files it looks at, and if a single one is either missing or modified, it aborts.
So, assuming that you are only running a custom recovery (and maybe root and busybox), the OTA update should work manually. You can always give it a shot - if it aborts, it will tell you why. You can either find it in /cache if your system downloaded it already, or manually download it to sdcard. Then flash it like any other zip. If it works, great. If it aborts, you can either troubleshoot why (ie: replace the file it doesn't like) or download the full image and flash manually. For people with a lot of customization, the latter option is usually the quickest.
First; THANK YOU!
when it goes thru the OTA update by itself and trying to install 4.2 update, it fails: assert failed apply_patch_check ("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5013504:c48Fe86c73fb.....etc (did not write it down entire message). but says Status 7 at the end.
I never seen this error message before. I understand if it complains about System/app folder, which did not, but complain about EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5013504:c48Fe86c73fb..... no clue whatsoever..
Ok, what that means is that the 'boot' partition (ie: kernel) was modified or is not what it expected to see.
Did you install a custom kernel? Even that stock kernel with the modified ramdisk/init.d support would cause that abort issue.
On the bright side, according to the updater-script, that's the last thing it checks. Since you got that far, it indicates that everything else is kosher.
At this point, I would recommend flashing the stock 4.1.2 boot image. I'm not sure if there is a recovery flashable zip for this, but I assume there is. If not, or if you just want to do it with fastboot, you can download the full 4.1.2 image, open up the tgz, open up the .zip inside of it, put your tablet into bootloader mode and use fastboot to flash boot.img. Ie:
fastboot flash boot boot.img
using the boot.img inside of the 4.1.2 image.
That should restore the kernel/boot to stock, and you should then be able to proceed with the OTA patch update.
---------- Post added at 11:13 AM ---------- Previous post was at 11:11 AM ----------
I just wanted to clarify that the only thing you should need to reflash with 4.1.2 stock is the kernel (boot). Leave everything else alone (system, userdata, recovery, etc.).
|Thread Tools||Search this Thread|