Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
- Pick a username
- Email Address
- Password
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
I downloaded the latest LineageOS for my latest Device, from Dumplings SF.
firmware, recovery, vendor files.
What I get all the time is that error message «E1001: Failed to update system image» and that he can’t mount the vendor partition.
Any ideas ? PS: I can’t even flash back to latest Oneplus ROM (or even older roms)….
Update:
Meanwhile I use TWRP from «cheeseburgerdumplings» for 8.1 on what lineageOS and the «/vendor» partition is no more tried to be mounted.
What I figure out as well, is that if I go with adbs command to know if the filesystem is encrypted or not:
adb shell getprop ro.crypto.state
tells me «encrypted»
Now the big question, which filesystems are encrypted, all ?
And which partition or FS does not have to be encrpyted?
Here is the «recovery.log»:
https://pastebin.com/raw/tKMStdSF
Screenshot:
ERROR: 1 — E1001: Failed to update system image.
Hi, I am using an LG VS995 phone, in a recent update I got an error trying to upgrade. Before the update, I wiped all the partitions (except the SD card partition).
File usage:
-
twrp-3.5.1_9-0-vs995
-
lineage-18.01-20210914-nightly-vs995-signed
I get the error:
E1001: Failed to update system image.
Updater process ended with ERROR: 1
Previous versions can still update normally, however, this error appears from version 2021-09-14.
How to fix this error?
Open
Issue created Nov 14, 2020 by Ghost User@ghost1
[hlte] Installation aborted: «E1001: Failed to update system image» on 16GB SM-N9005
Device info
Device: Samsung Galaxy Note 3 (N9005)
Variant: TGY (16GB)
Codename: hlte
Build: lineage-17.1-20201114-nightly-hlte-signed.zip
Recovery: lineage-17.1-20201114-recovery-hlte.img
What happened?
When trying to upgrade from 16 to 17.1 or install 17.1 from scratch, both TWRP 3.4.0-1
and LineageOS Recovery 20201114 will show «E1001: Failed to update system image»,
while Installing official LineageOS 16 (and unofficial LineageOS 17.1) showed no error.
A common issue for 16GB model
This problem seems to affect 16GB model, which was only released in Greater China
(China, Hong Kong, Macau and Taiwan), as I’ve read other 16GB owers reporting the
same error on XDA.
N9005 TGY (HK): /galaxy-note-3/general/rom-lineageos-17-1-t4175207/page4 (33)
N9005 BRI (TW): /galaxy-note-3/development/rom-lineageos-17-1-t4044269/page31 (308)
N9006 CHN/CHU (CN): /galaxy-note-3/help/install-lineageos-17-1-n9006-t4178721 (1 and 2)
In short, for 16GB model:
LineageOS 16 (official): succeeded
LineageOS 17.1 (unofficial): succeeded
LineageOS 17.1 (official): failed
Hope HLTE maintainers can look into this issue
The following logs were from lineage-17.1-20201114-recovery-hlte.img
LineageOS 17.1 installation log
— Install /storage/emulated/lineage-17.1-20201114-nightly-hlte-signed.zip …
Finding update package…
Opening update package…
Verifying update package…
Update package verification took 8.4 s (result 0).
Installing update…
Target: samsung/hltexx/hlte:5.0/LRX21V/N9005XXSGBRI2:user/release-keys
Patching system image unconditionally…
E1001: Failed to update system image.
E:Error in /sideload/package.zip (status 7)
Install completed with status 1.
Installation aborted.
Installing update…
unknown fuse request opcode 2016
SElinux: Skipping /product_file_contexts: empty file
SELinux: Skipping /odm_file_contexts: empty file
SELinux: Loaded file_contexts
Target: samsung/hltexx/hlte:5.0/LRX21V/N9005XXSGBRI2:user/release-keys
Extracted file «/tmp/install/bin/backuptool.functions»
Extracted file «/tmp/install/bin/backuptool.sh»
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
Backup/restore is not possible. Partition is probably empty
Patching system image unconditionally…
performing update
blocking version is 4
maximum stash entries 0
using existing stash /cache/recovery/
/cache/recovery/last_command doesn’t exist.
erasing 215091 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execut command [erase 6,271658,294400,295426,556544,557569,588800]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E:Error in /sideload/package.zip (status 7)
LineageOS 16 installation log (for comparision)
— Install /storage/emulated/lineage-16.0-20201003-nightly-hlte-signed.zip …
Finding update package…
Opening date package…
Verifying update package…
Update package verification took 9.3 s (result 0).
Installing update…
Target: samsung/hltexx/hlte:5.0/LRX21V/N9005XXSGBRI2:user/release-keys
Patching system image unconditionally…
script succceeded: result was [1.000000]
Installing update…
unknown fuse request opcode 2016
SElinux: Skipping /product_file_contexts: empty file
SELinux: Skipping /odm_file_contexts: empty file
SELinux: Loaded file_contexts
Target: samsung/hltexx/hlte:5.0/LRX21V/N9005XXSGBRI2:user/release-keys
Extracted file «/tmp/install/bin/backuptool.functions»
Extracted file «/tmp/install/bin/backuptool.sh»
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
grep: /postinstall/tmp/addon.d/*sh: No such file or directory
/tmp/addon.d/50-lineage.sh[43]: can’t create temporary file : No such file or directory
umount: /system: Device or resource busy
Patching system image unconditionally…
performing update
blocking version is 4
maximum stash entries 0
using existing stash /cache/recovery/
/cache/recovery/last_command doesn’t exist.
erasing 128310 blocks
writing 1024 blocks of new data (multiple lines)
writing 840 blocks of new data
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 898 blocks
wrote 255690 blocks; expected 255690
stashed 0 blocks
max alloc needed was 4096
deleting stash
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
umount: /system: Device or resource busy
mount: ‘/dev/block/mmcblk0p23′->’/system’: Device or resource busy
/tmp/addon.d/50-lineage.sh[43]: can’t create temporary file : No such file or directory
umount: /system: Device or resource busy
Install completed with status 0.
/device hlte
/version lineage-17.1
/date 2020-11-14
I have read the directions
I downloaded the latest LineageOS for my latest Device, from Dumplings SF.
firmware, recovery, vendor files.
What I get all the time is that error message «E1001: Failed to update system image» and that he can’t mount the vendor partition.
Any ideas ? PS: I can’t even flash back to latest Oneplus ROM (or even older roms)….
Update:
Meanwhile I use TWRP from «cheeseburgerdumplings» for 8.1 on what lineageOS and the «/vendor» partition is no more tried to be mounted.
What I figure out as well, is that if I go with adbs command to know if the filesystem is encrypted or not:
adb shell getprop ro.crypto.state
tells me «encrypted»
Now the big question, which filesystems are encrypted, all ?
And which partition or FS does not have to be encrpyted?
Here is the «recovery.log»:
https://pastebin.com/raw/tKMStdSF
Screenshot:
I downloaded the latest LineageOS for my latest Device, from Dumplings SF.
firmware, recovery, vendor files.
What I get all the time is that error message «E1001: Failed to update system image» and that he can’t mount the vendor partition.
Any ideas ? PS: I can’t even flash back to latest Oneplus ROM (or even older roms)….
Update:
Meanwhile I use TWRP from «cheeseburgerdumplings» for 8.1 on what lineageOS and the «/vendor» partition is no more tried to be mounted.
What I figure out as well, is that if I go with adbs command to know if the filesystem is encrypted or not:
adb shell getprop ro.crypto.state
tells me «encrypted»
Now the big question, which filesystems are encrypted, all ?
And which partition or FS does not have to be encrpyted?
Here is the «recovery.log»:
https://pastebin.com/raw/tKMStdSF
Screenshot:
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
- Pick a username
- Email Address
- Password
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
-
#1
I have tried to install today the new update of xiaomi.eu rom via twrp and it has ended with an error:
E1001: Failed to flash system partition.
and its failing mounting /vendor, /product and /odm all of three with invalid argument error.
Now my Xiaomi Mi10Ultra keeps rebooting all time and i cant do anything more that enter in flashbood mode or recovery mode… It is there any option to fix it via recovery mode?
Thanks in advance, i’m very noop user at this level, until now all the updates has been installed succesfully, this error never happens to me…
-
#2
I have tried to install today the new update of xiaomi.eu rom via twrp and it has ended with an error:
which twrp have you used?
-
#3
which twrp have you used?
I really don’t know… if you can tell me how to extract that info i will post it.
By the other side i have tried to install the first xiaomi.eu rom for xiaomi mi 10 ultra posted here via fastboot amd i had an error with on partition, it’s like the partition doesn’t exists…
-
#4
By the other side i have tried to install the first xiaomi.eu rom for xiaomi mi 10 ultra posted here via fastboot amd i had an error with on partition, it’s like the partition doesn’t exists…
storsecbak partition <- this partition has the error no such partition
-
#5
By the other side i have tried to install the first xiaomi.eu rom for xiaomi mi 10 ultra posted here via fastboot amd i had an error with on partition, it’s like the partition doesn’t exists…
are you able to boot into twrp? if yes, you can check the version. there should be a banner with version number
-
#6
are you able to boot into twrp? if yes, you can check the version. there should be a banner with version number
Here again, I had make some photos, hope they have the information you need.
Thanks in advance for the help mate!
-
69D39F98-916A-40F0-947D-CE868A686166.jpeg
870 KB
· Views: 96
-
A0E6B964-9D96-4492-8195-3BC55BD7C1A2.jpeg
1.4 MB
· Views: 93
-
#7
Here again, I had make some photos, hope they have the information you need.
Thanks in advance for the help mate!
from what I see, you are using an old twrp, it is not compatible with android 12 / MIUI 13.
for example I used twrp 3.6.2 from skkk for installing ROM that you tried to install.
there is actually a very good installation guide.
[HowTo] Install Recovery image
How to install a xiaomi.eu recovery image Because of more and more working TWRP or OrangeFox on MIUI13 Android12 a little How To and here we go …. Unlock your device (only once) — you need to unlock bootloader -> a small [howto] to unlock bootloader Install Tools and Drivers — install USB…
xiaomi.eu
in this guide you will find the link and instructions how to install twrp
and here you can download latest twrp
for mi 10 ultra you will need
[REC_BOOT]3.6.2_12-Mi10Ultra_v6.3_A12-cas-skkk_23dba73f.zip
-
#8
Hi guys,
the mentioned download site does not work, could somebody please share the 3.6.2_12-Mi10Ultra_v6.3_A12-cas-skkk_23dba73f.zip with me via Google drive ?