[MeMO Pad 7 General] lambdadroid:
Has someone had problems with the inbuilt recovery of the device like this? I tried to install the update using the inbuilt recovery like described in http://xdaforums.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965

/cache/recovery/command:

boot-recovery
--update_package=/data/update.zip
--wipe_cache
reboot

It's generally working fine, but no matter which update I'm trying to install I always get an error and find this in the log later:

...
Command: "/sbin/recovery" "--update_package=/data/update.zip" "--wipe_cache" "boot-recovery " "reboot"
...
I:Install package /data/update.zip
update_package path=/data/update.zip
Finding update package...
I:Update location: /data/update.zip
Opening update package...
sysutil: Unable to open '/data/update.zip': Permission denied
E:failed to map file
E:Install of /data/update.zip failed with status 2
I:Recovery fail file /cache/recovery/recoveryfail created
Installation aborted.
E:Delete /data/update.zip failed (Permission denied)
I:Saving locale "en_US"

I also tried to change the permissions of the update I copied to /data/update.zip but even with all permission flags set this is still happening...

I installed the update yesterday, I was rooted and had a few apps frozen so something of this was the cause that the update was originally failing. The device will only try to download the update once, if the installation fails you need to do it manually instead. I think if you're rooted you can generally either install updates with the inbuilt recovery (didn't work for me, not sure if that's a general problem) or using the temp CWM recovery from http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (use the public trial release and trigger 4).

If you're rooted you will most likely need to install a clean version again first (you can root again after the update):

Download the clean firmware from http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.17_KK-user.zip and copy it to your sdcard

Install it using the temp CWM recovery by selecting it in "Install zip", this will take a while (don't worry, it doesn't show progress for some reason but it should finish)

After you've done this you can install the update like you just did with the firmware, you can download the update directly from ASUS: http://fota.asus.com/delta_package/...-user-WW-12.10.1.24-user-WW-20150624-1029.zip

When installing the update using the temp CWM I got a really weird error like

Package expects build fingerprint of asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.17-20150505:user/release-keys or asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.24-20150623:user/release-keys; this device has asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.17-

I checked the version and it was actually correct so I'm not sure what was going wrong there, so I simply removed the check from the updater script and then it worked fine. I opened the update ZIP, edited META-INF/com/google/android/updater-script in it and removed these lines:

if check_version()=="5.0" then
getprop("ro.build.fingerprint") == "asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.17-20150505:user/release-keys" ||
getprop("ro.build.fingerprint") == "asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.24-20150623:user/release-keys" ||
abort("Package expects build fingerprint of asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.17-20150505:user/release-keys or asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.24-20150623:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
else
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.17-20150505:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.24-20150623:user/release-keys");
endif;

After the update you can simply root again by installing UPDATE-SuperSU-v2.46.zip on your device again. At least that's how I got it working. At the end I spent more then 4 hours on this update and it wasn't really worth it, there don't seem to be any major changes that would have been worth to install it, IMO :p

I tried to use it on my device but it's not working for some reason. I'm on Linux so I wasn't able to test it directly, however I think these commands should basically do the same as your script for trigger 4:

fastboot oem start_partitioning
fastboot flash /tmp/recovery.zip ./cwm.zip
fastboot flash /tmp/recovery.launcher ./recovery.launcher
fastboot flash /system/bin/logcat ./recovery.trigger
fastboot oem stop_partitioning

I don't see any error, fastboot seems to accept all the commands without any problem but the CWM recovery will simply not start like it did before. The public trial release you posted earlier is working fine, even after the update I installed yesterday. Not sure if I'm just doing something wrong - though.