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.
Related
Hi guys, yesterday I tryied for the first time to update franco kernel's last update via FKU Beta and as a resoult my phone won't start anymore. When i power it on it get stuck on the boot logo (the one right after the cyanogen logo with powered by android). I can access to TWRP and i can access to adb but usb debugging it's turned off I think (is it possible to verify it?).
Inside the phone there is a very recent TWRP backup (yes, I tryied already to restore it from TWRP but no changes) and a Titanium Backup of all my apps. Is it possible to save it somewhere? What can I do to fix my phone?
Pleeeease help me Thanks in advice!
Which partitions are backed up in your TWRP backup?
Transmitted via Bacon
ok I flashed my phone from scratch so now I have r33 on it.
I restored an old backup but now I can't update to r38!
That's the log of twrp
Installing '/sdcard/Download/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
about to run program [/tmp/otasigcheck.sh] with 1 args
failed to stat "/system/bin/thermal-engine": No such file or directory
script aborted: assert failed: apply_patch_check("/system/bin/thermal-engine","b94fc36a478b73d2d44133a4369d10e1b060bf5e","605b06e559abced4cdbafe02dc5ea14d69c89cd9")
assert failed: apply_patch_check("/system/bin/thermal-engine","b94fc36a478b73d2d44133a4369d10e1b060bf5e","605b06e559abced4cdbafe02dc5ea14d69c89cd9")
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip'
Error flashing zip '/sdcard/Download/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip'
Updating partition details...
I:mount '/data/media/0' '/sdcard' process ended with RC=0
Iata backup size is 6070MB, free: 42239MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
I:mount '/data/media/0' '/sdcard' process ended with RC=0
Click to expand...
Click to collapse
You had Franco kernel installed at some point? The remnants are screwing with the OTA. You need to clean flash with a full wipe.
Transmitted via Bacon
yes I had franco so i made a clean flash of r33, wiped cache and dalvik then i tryied to flash r38 with that error
Wiping cache and dalvik isn't enough, you need to wipe system/data/cache/dalvik cache, then install clean 33R, then you can take the 38R update. Or you could just flash the full recovery flashable version of 38R after wiping system/data/cache/dalvik cache, that's probably the easier solution.
Transmitted via Bacon
Hi,
I'm new user of this site. I would like present my problem and I hope that you can Help me.
I have HTC Desire S and I would update it with Lollipop. I have read that for upgrade, I can install cyanogen mod 12.
On my desire I have ClockworkMod Recovery v5.0.2.0;
I have downloaded:
- cm-12-20150611-UNOFFICIAL-saga.zip
- gapps-5.0.x-20150404-minimal-edition-signed.re
but I have this message:
<Status 0>
Installation aborted.
--Installing: /sdcard/cm-12-201506-11-UNOFFICIAL-saga.zip
Finding update package...
Opening update package...
Installing update...
Warning: No file_contextscould not detect filesystem for /dev/block/platform/msm_sdcc.2/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.2/by-name/system at /system: No such file or directory
unmount of /system failed: no such volume could not detected filesystem for /dev/block/platform/msm_sdcc.2/by-name/userdata, assuming f2fs mount: failed to umount /dev/block/platform/msm_sdcc.2/by-name/userdata at /data: No such device unmount of /data failed: no such volume E: Error in /sdcard/cm-12-20150611-UNOFFICIAL-saga.zip
<Status 0>
Installation aborted.
update ur recovery to the latest TWRP recovery then the rom will install.
Hello,
I'm making a port of a ROM and when I flash it with TWRP (Latest Release) it says he can't symlink.
I get the log and I seen the system partition is full (The ROM size is about 1,8 GO)
Code:
failed to mkdir /system/app/OpenWnn/lib: No space left on device
symlink: failed to symlink /system/app/OpenWnn/lib to /system/lib/libWnnEngDic.so: making parents failed
symlink: failed to symlink /system/app/OpenWnn/lib to /system/lib/libWnnEngDic.so: No such file or directory
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/updatus.zip'
Error flashing zip '/sdcard/updatus.zip'
Updating partition details...
I:Data backup size is 0MB, free: 26545MB.
My question is: Can I extend system partition ?
Thanks,
Marwanpro
iam getting the below specified error while updating the Rom cm-13.0- NIGHTLY-otus to cm-14.1-20161216-NIGHTLY-otus on Motorola E 2015 3G.
i tried update it via recovery and cm updater but getting same error..
i got this error :
Installing '/data/media/0/cmupdater/cm-14.1-20161216-NIGHTLY-otus.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.
Target: 1481879506
Target: 1481879506
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory
mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
unmount of /system failed; no such volume
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Patching system image unconditionally...
performing update
open "/dev/block/bootdevice/by-name/system" failed: No such file or directory
script aborted: E1001: Failed to update system image.
Patching system image unconditionally...
E1001: Failed to update system image.
E:unknown command [log]
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/data/media/0/cmupdater/cm-14.1-20161216-NIGHTLY-otus.zip'
E:Error installing zip file '/data/media/0/cmupdater/cm-14.1-20161216-NIGHTLY-otus.zip'
Done processing script file
any help.. Thanx
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?