Can someone please help me understand why I wasn't able to install the update?
Log:
:Switching packages (TWRP) I:Set page: 'action_page' I:Skipping screen timeout threads: TW_NO_SCREEN_TIMEOUT is set Processing AOSP recovery commands... I:command is: 'install' and I:value is: '/cache/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip' I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'vfat' I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'vfat' I:Trying to find zip '/cache/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip' on '/data/media/0'... I:Looking for zip at '//d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip' I:Looking for zip at '/data/media/0///d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip' Installing zip file '/cache/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip' Installing '/cache/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip'... Checking for MD5 file... I:Cannot find file /cache/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip.md5 Skipping MD5 check: no MD5 file found. I:Zip does not contain SELinux file_contexts file in its root. Verifying current system... failed to stat "/system/app/Books.apk": No such file or directory file "/system/app/Books.apk" 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: "/system/app/Books.apk" has unexpected contents. "/system/app/Books.apk" has unexpected contents. E:Error executing updater binary in zip '/cache/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip' E:Error installing zip file '/cache/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip' Done processing script file I:Set page: 'main' I:Set page: 'clear_vars' I:Set page: 'main2' I:TWFunc::Fixup_Time: Setting time offset from file /data/system/time/ats_2, offset 1398993337810 I:Switching packages (TWRP) I:Set page: 'advanced' I:Set page: 'confirm_action' I:Set page: 'action_page.
Now I don't get the OTA anymore.
Thanks.
Sent from my Nexus 5 using Tapatalk
are you rooted and modified anything with your system? and i mean anything, even a build.prop edit. xposed?
You removed Google books. Restore it.
Sent from my Nexus 5 using Tapatalk
I use Xposed framework and I'm rooted. What should I do about it? Restoring books won't really help I guess since I'm not getting OTA anymore
Sent from my Nexus 5 using Tapatalk
You have to be bone stock unmodified to install the ota
sent from my hammerhead
Crap... Any manual to unroot, unlock and flash stock recovery?
Sent from my Nexus 5 using Tapatalk
ldubs said:
You have to be bone stock unmodified to install the ota
sent from my hammerhead
Click to expand...
Click to collapse
this is not true.
gil80 said:
Crap... Any manual to unroot, unlock and flash stock recovery?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's right there in the General thread. Stickied and everything just for you.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
gil80 said:
I use Xposed framework and I'm rooted. What should I do about it? Restoring books won't really help I guess since I'm not getting OTA anymore
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
or, to make things easier, find a rooted/stock 4.4.3 rom and flash it via your custom recovery. no need with the headache of everything else that way. if there arent any around(im pretty sure there are) then wait a day or two, there will be
edit..
heres a stock rooted rom http://forum.xda-developers.com/google-nexus-5/development/flashable-stock-4-4-3-supersu-t2771010
But then I have to configure everything from scratch
Sent from my Nexus 5 using Tapatalk
gil80 said:
But then I have to configure everything from scratch
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
maybe you can make it better this time
you can try dirty flashing, just make a backup in case.
gil80 said:
But then I have to configure everything from scratch
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Or you could just not bother. Sounds like 4.4.3 isn't worth the effort anyway. I'm staying on 4.4.2 since I have no significant issues. We'll see what Google I/O brings.
gil80 said:
But then I have to configure everything from scratch
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi
http://forum.xda-developers.com/showthread.php?p=53178646
Tapatalk-kal küldve az én Nexus 5-el
I have a similar problem. Cant figure out from the logs why the update failed.
First the OTA failed. Then I downloaded the zip and tried to install, that failed as well.
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:using /data/media for /sdcard.
-- Installing: /sdcard/0/Download/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
Finding update package...
I:Update location: /data/media/0/Download/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
Opening update package...
Installing update...
Verifying current system...
contents of partition "/dev/block/platform/msm_sdcc.1/by-name/boot" didn't match EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8835072:21095d6f3675a00248692ada237aa3bf11659588:8908800:a3bd726fbabaa1dbc2a31e8baf6cb44508177d43
file "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8835072:21095d6f3675a00248692ada237aa3bf11659588:8908800:a3bd726fbabaa1dbc2a31e8baf6cb44508177d43" 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: "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8835072:21095d6f3675a00248692ada237aa3bf11659588:8908800:a3bd726fbabaa1dbc2a31e8baf6cb44508177d43" has unexpected contents.
"EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8835072:21095d6f3675a00248692ada237aa3bf11659588:8908800:a3bd726fbabaa1dbc2a31e8baf6cb44508177d43" has unexpected contents.
E:Error in /data/media/0/Download/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
(Status 7)
Installation aborted.
I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.
I:using /data/media for /sdcard.
I:using /data/media for /sdcard.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
Rebooting...
I:using /data/media for /sdcard/0/clockworkmod/.recovery_version.
sayantandas said:
I have a similar problem. Cant figure out from the logs why the update failed.
First the OTA failed. Then I downloaded the zip and tried to install, that failed as well.
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:using /data/media for /sdcard.
-- Installing: /sdcard/0/Download/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
Finding update package...
I:Update location: /data/media/0/Download/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
Opening update package...
Installing update...
Verifying current system...
contents of partition "/dev/block/platform/msm_sdcc.1/by-name/boot" didn't match EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8835072:21095d6f3675a00248692ada237aa3bf11659588:8908800:a3bd726fbabaa1dbc2a31e8baf6cb44508177d43
file "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8835072:21095d6f3675a00248692ada237aa3bf11659588:8908800:a3bd726fbabaa1dbc2a31e8baf6cb44508177d43" 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: "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8835072:21095d6f3675a00248692ada237aa3bf11659588:8908800:a3bd726fbabaa1dbc2a31e8baf6cb44508177d43" has unexpected contents.
"EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8835072:21095d6f3675a00248692ada237aa3bf11659588:8908800:a3bd726fbabaa1dbc2a31e8baf6cb44508177d43" has unexpected contents.
E:Error in /data/media/0/Download/d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
(Status 7)
Installation aborted.
I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.
I:using /data/media for /sdcard.
I:using /data/media for /sdcard.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
Rebooting...
I:using /data/media for /sdcard/0/clockworkmod/.recovery_version.
Click to expand...
Click to collapse
do you have a custom kernel?
Use Wugfresh's Nexus Root Toolkit:
http://nexus5.wonderhowto.com/how-t...ndroid-4-4-3-without-losing-any-data-0155334/
colorado_al said:
Use Wugfresh's Nexus Root Toolkit:
http://nexus5.wonderhowto.com/how-t...ndroid-4-4-3-without-losing-any-data-0155334/
Click to expand...
Click to collapse
NO. just no.
I'm having the same problem. Twrp is telling me that dev/block/platform/msm_sdcc.1/by-name/boot has unexpected content. I did have elementalx kernel installed, but I flashed the stock 4.4.1-4.4.2 kernel before I tried to install the 4.4.3 update.
I thought you had to be totally stock to actually be able to install the ota. You can get it if you're not stock, but it won't install. In this case, I think what's holding you up is that you have a custom recovery.
Sent from my Nexus 5 using Tapatalk
cbutt said:
I thought you had to be totally stock to actually be able to install the ota. You can get it if you're not stock, but it won't install. In this case, I think what's holding you up is that you have a custom recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
That's wrong though. You can install an ota update through a custom recovery, and is pretty normal too. You can't however have a custom kernel or modified system files.
Hello when I try to flash a Rom on my device I have this output:
Installing '/external_sd/OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31 (1).zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: This package is for "OnePlus" devices; this is a "".
This package is for "OnePlus" devices; this is a "".
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31 (1).zip'
Error flashing zip '/external_sd/OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31 (1).zip'
Updating partition details...
Iata backup size is 0MB, free: 11664MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
Click to expand...
Click to collapse
any idea?
Thank you very much
PieerotGG said:
Hello when I try to flash a Rom on my device I have this output:
any idea?
Thank you very much
Click to expand...
Click to collapse
Hello,
Are you on latest bootloader? If not, please update it.
Flash the TWRP based on latest bootloader in bluspark kernel thread.
Regards
Vatsal,
Forum Moderator.
So I tried to install LineageOS on my Honor 8. I unblocked the Bootloader and I am currently able to get into TWRP and Fastboot Mode. I did change the filesystem for the cache system and data as described in this video: w w w. youtube.com /watch?v=X7yDPszoQ5s to enable the encrypted folders.
When I try to install any ROM I am getting the following Errors in red:
E: unknown command (log)
Updater process ended with ERROR: 7
Error installing zip file 'romname'
Also:
Skipping MD5 check: no MD5 file found
could not detect filesystem for /dev/block/bootdevice/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
patching system image uncoditionally...
E1001: Failed to update system image.
When trying to flash img files via this guide
https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203
flashing vendor and system fails
ERecovery will download a ROM but gets error "authentication failed"
Now installed TWRP and wipe fails to wipe vendor and system partition saying
Failed to mount /vendor (invalid argument)
any ideas?
Hi,
I've a Pixel (sailfish) that I'm trying to load TWRP and Magisk, and I'm unable to flash the recovery image as the bootloader page shows "Device is LOCKED", even though I've already enabled OEM unlock in Developer Settings. How do I unlock the bootloader?
goister said:
Hi,
I've a Pixel (sailfish) that I'm trying to load TWRP and Magisk, and I'm unable to flash the recovery image as the bootloader page shows "Device is LOCKED", even though I've already enabled OEM unlock in Developer Settings. How do I unlock the bootloader?
Click to expand...
Click to collapse
Enabling the OEM Unlock option is the first step but it doesn't unlock the phone. It merely enables unlocking the phone. You have to use a specific adb command to unlock the phone. Since the command varies with models and I am not familiar with your phone, please search for the correct command on Google.
Thanks. I'm following this page - https://www.xda-developers.com/how-to-install-twrp/
I managed to unlock it with fastboot, but I can't seem to flash the recovery. I downloaded the TWRP image from https://dl.twrp.me/sailfish/twrp-3.7.0_9-0-sailfish.img.html and renamed it to twrp.img. I then performed the following steps as per the instructions from xda above:
booted to bootloader with adb reboot bootloader
Temporarily booted to TWRP with fastboot boot twrp.img
Copied TWRP image file to device with adb push twrp.img /sdcard
Go to Advanced->Install Recovery Ramdisk, select twrp.img and swipe to install
I get the following error
Updating partition details...
Failed to mount '/system_root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
...done
Unpacking Boot...
Backing up Boot...
Unpacking /sdcard/twrp.img...
Repacking Boot...
/sbin/magiskboot decompress /tmp/repakorig/ramdisk.cpio /tmp/repackorig/ramdisk-1.cpio process ended with ERROR: 1
Error repacking image.
I tried to mount vendor partition, wipe and format the device and retry step 4 and made it a bit further (no more failed to mount '/system_root' and '/vendor' errors, as below, but still fails.
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done
Unpacking Boot...
Backing up Boot...
Unpacking /sdcard/twrp.img...
Repacking Boot... /sbin/magiskboot decompress /tmp/repakorig/ramdisk.cpio /tmp/repackorig/ramdisk-1.cpio process ended with ERROR: 1 Error repacking image.
Any suggestions?
goister said:
Go to Advanced->Install Recovery Ramdisk, select twrp.img and swipe to install
Click to expand...
Click to collapse
You can download both the .img and the .zip files. After booting using the .img file, instead of step 4 above, you can try Install from the booted TWRP and navigate to where the .zip file is and simply install it. That is what the TWRP page for Pixel recommends:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
Click to expand...
Click to collapse
Damn...why did the xda instructions say otherwise?
OK so I managed to reflash to stock image again after the boot loop, and then I followed the TWRP instructions. I was prompted to enter the device password when booting up to TWRP temporarily, and was able to get to TWRP once I entered my device PIN.
After I installed the zip file, I get the following screen:
Installing zip file '/sdcard/twrp.zip'
Updating partition details...
...done
Attempting to decrypt FBE for user 0...
User 0 Decrypted successfully
Data successfully decrypted
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/system root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Installing zip file '/sdcard/twrp.img'
Unmounting system...
########################################
# TWRP Installer for A/B devices #
########################################
Unpacking the installer...
Running image patcher on boot_a...
Running image patcher on boot_b...
Image patching complete!
Done installing TWRP!
*** NOTE: You are now unrooted! ***
Updating partition details...
Failed to mount '/system root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
...done
After this, it reboots to Android fine, but whenever I try to reboot to recovery, it goes to the white screen with the Google logo, then reboots to Android.
I'm using the latest TWRP for sailfish - twrp-installer-3.7.0_9-0-sailfish.zip.
Any ideas why?