Develop Bugs

Stock update probs

i flashed a stock rom from shipped rom collection.. and when i updated the update was found and then it downloded and when it was installing it gave me error
Code:
We have determined that your phone may be running a modified version of its system software.
For your protection, we cannot update your phone.
Please revert back to the official HTc system software to update your phone.
if you did not modify your system software or would like help reverting your system,
please contact us via the support section at www.htc.com
why is this so?

Are you using clockworkmod? Because you must stock recovery!

vbhtt said:
Are you using clockworkmod? Because you must stock recovery!
Click to expand...
Click to collapse
ya using cwm how to gget that stock recovery?

http://forum.xda-developers.com/showthread.php?t=1431969
This Should have the option of 'return to stock recovery'

vbhtt said:
http://forum.xda-developers.com/showthread.php?t=1431969
This Should have the option of 'return to stock recovery'
Click to expand...
Click to collapse
bro i know i tried it .. the download is unavailable..
do yu have it with you? can you upload it to mediafire and sense the link?

vbhtt said:
http://forum.xda-developers.com/showthread.php?t=1431969
This Should have the option of 'return to stock recovery'
Click to expand...
Click to collapse
i flashed the recovery.img from the rom.zip got the recovery back will try update now.. i feel like a SMART ASS haha nywys thanks vbhtt

vbhtt said:
Are you using clockworkmod? Because you must stock recovery!
Click to expand...
Click to collapse
not working still getting the same eror

mhrsolanki2020 said:
not working still getting the same eror
Click to expand...
Click to collapse
You will have to return to the original System image and recovery for the update to work. The update does a system file verification before it will run.
SAMPLE
Code:
# Script Version: G2.4
mount("yaffs2", "MTD", "system", "/system");
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999");
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PG7624000") == "t");,
assert(check_mid("simple", "PG7624000") == "t");
);
assert(getprop("ro.product.device") == "marvel" ||
getprop("ro.build.product") == "marvel");
ui_print("Copying fotaBoot to /data/system for customize reload...");
mount("yaffs2", "MTD", "userdata", "/data");
package_extract_file("fotaBoot", "/data/system/fotaBoot");
ui_print("Verifying current system...");
show_progress(0.100000, 0);
assert(apply_patch_check("/system/app/AccountSyncManager.apk", "0c905b041013e66457dd8e9e3abc5a98a7aaff37", "cc881deb5a9e22c6034d4533aa16d8e59abf6124"));
set_progress(0.000434);
assert(apply_patch_check("/system/app/AccountSyncManager.odex", "54e29e187f645bf4cca610039c0cea19264db3a9", "82d14a73106da8fc8857ddf346f10803eaace65e"));
set_progress(0.000864);
assert(apply_patch_check("/system/app/AdobeReader.apk", "4b631cd33caf62c028025431193c90e74ac2f843", "b4495167bce02c3888bfbd11500b471408a2cd1e"));
set_progress(0.002245);
assert(apply_patch_check("/system/app/AppSharing.apk", "68f72c802abfae89a352e05c84fec8131f297ec2", "1af6b59cba8d4ea078cb5d92d58b4269cd482d23"));
set_progress(0.002364);
assert(apply_patch_check("/system/app/AppSharing.odex", "cdac67b3837582c59f05974100c27214d49d5c60", "dd965ebcb73fc62140ad74e192c52908884315fd"));

Tera Tike said:
You will have to return to the original System image and recovery for the update to work. The update does a system file verification before it will run.
SAMPLE
Code:
# Script Version: G2.4
mount("yaffs2", "MTD", "system", "/system");
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999");
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PG7624000") == "t");,
assert(check_mid("simple", "PG7624000") == "t");
);
assert(getprop("ro.product.device") == "marvel" ||
getprop("ro.build.product") == "marvel");
ui_print("Copying fotaBoot to /data/system for customize reload...");
mount("yaffs2", "MTD", "userdata", "/data");
package_extract_file("fotaBoot", "/data/system/fotaBoot");
ui_print("Verifying current system...");
show_progress(0.100000, 0);
assert(apply_patch_check("/system/app/AccountSyncManager.apk", "0c905b041013e66457dd8e9e3abc5a98a7aaff37", "cc881deb5a9e22c6034d4533aa16d8e59abf6124"));
set_progress(0.000434);
assert(apply_patch_check("/system/app/AccountSyncManager.odex", "54e29e187f645bf4cca610039c0cea19264db3a9", "82d14a73106da8fc8857ddf346f10803eaace65e"));
set_progress(0.000864);
assert(apply_patch_check("/system/app/AdobeReader.apk", "4b631cd33caf62c028025431193c90e74ac2f843", "b4495167bce02c3888bfbd11500b471408a2cd1e"));
set_progress(0.002245);
assert(apply_patch_check("/system/app/AppSharing.apk", "68f72c802abfae89a352e05c84fec8131f297ec2", "1af6b59cba8d4ea078cb5d92d58b4269cd482d23"));
set_progress(0.002364);
assert(apply_patch_check("/system/app/AppSharing.odex", "cdac67b3837582c59f05974100c27214d49d5c60", "dd965ebcb73fc62140ad74e192c52908884315fd"));
Click to expand...
Click to collapse
ya i know.. i flashes boot.img system.img and recovery.img from the rom.zip i extracted from ruu

The downloaded file must be on the sd card. It must be something like OTA_update...........zip check if its flashable. Check if you can do something with that. You may have to search for it.

vbhtt said:
The downloaded file must be on the sd card. It must be something like OTA_update...........zip check if its flashable. Check if you can do something with that. You may have to search for it.
Click to expand...
Click to collapse
The only file I. Found is com.android.vending.updater-20120221-061703.tar.gz

It should be in the download folder. You downloaded it ota right? I suggest you search manually and not use the search function of your file manager

vbhtt said:
It should be in the download folder. You downloaded it ota right? I suggest you search manually and not use the search function of your file manager
Click to expand...
Click to collapse
yeah bro.. i searched it everywhere on sd card .. no where not even in download folder..

Have you enabled show hidden files in your file manager? Filenames that start with a '.' are generally hidden
Sent from my iPod touch using Tapatalk

vbhtt said:
Have you enabled show hidden files in your file manager? Filenames that start with a '.' are generally hidden
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
yeap saw.. nothing there.

Maybe the system deleted it after if found out? Do you get a notification that an update is available in the status bar?
Sent from my iPod touch using Tapatalk

vbhtt said:
Maybe the system deleted it after if found out? Do you get a notification that an update is available in the status bar?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
yep i do... and when i select it.. it starts downloading... and then nothing the same error comes..

Just after it downloads, it asks whether you want to install it right? Click no and then search for it.
Sent from my iPod touch using Tapatalk

vbhtt said:
Just after it downloads, it asks whether you want to install it right? Click no and then search for it.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
it doesnt asks me nyting as such it just starts itself up

Did you try unrooting?
Factory data reset?
Try the 'fastboot oem lock' command
Cant think of anything else...
Sent from my iPod touch using Tapatalk

Modem update from CWM

Modem update from CWM simply doesn't work!
I tried already everything! Result is: Script runs without error but no change, the baseband version is still the old.
My last update script (no errors, but doesn't work) is following:
Code:
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" ||
getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" ||
getprop("ro.product.device") == "i9195" || getprop("ro.build.product") == "i9195" ||
getprop("ro.product.device") == "GT-I9195" || getprop("ro.build.product") == "GT-I9195");
ui_print("------------------------------------------------------");
ui_print("I9195 modem update by LackoGyerek");
show_progress(0.150000, 0);
package_extract_dir("tools", "/tmp");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mkfs.vfat", "/dev/block/platform/msm_sdcc.1/by-name/modem");
run_program("/tmp/busybox", "mkdir", "-p", "/tmp/modem");
run_program("/tmp/busybox", "mount", "-w", "-t", "auto", "/dev/block/platform/msm_sdcc.1/by-name/modem", "/tmp/modem");
package_extract_dir("modem", "/tmp/modem");
set_perm_recursive(0, 1000, 0771, 0771, "/tmp/modem/image");
run_program("/tmp/busybox", "umount", "/tmp/modem");
ui_print("Installation complete!");
show_progress(1.000000, 0);
ui_print("------------------------------------------------------");
The update package above uses the unpacked NON-HLOS.bin content. Can be easily unpacked with DiskInternals Linux Reader tool.
Already tried with/without formatting of modem partition.
Also tried the edify command
Code:
package_extract_file("NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
Method below was checked too:
Code:
busybox dd if=./NON-HLOS.bin of=/dev/block/platform/msm_sdcc.1/by-name/modem
Result of dd command:
Code:
97923+1 records in
97923+1 records out
50136832 bytes (47.8MB) copied, 6.765573 seconds, 7.1MB/s
And finally this method:
Code:
package_extract_dir("modem","/tmp");
write_raw_image("/tmp/NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
delete("/tmp/NON-HLOS.bin");
All above with the same result: No error during flash, but baseband version not changed.
Any idea, how to update modem via recovery?

If you check the contents of the flashed NON-HLOS.bin you should find that it has indeed been changed.
The version listed in about device doesn't update unless you flash with Odin twice

Whosat said:
If you check the contents of the flashed NON-HLOS.bin you should find that it has indeed been changed.
The version listed in about device doesn't update unless you flash with Odin twice
Click to expand...
Click to collapse
Trust me, I checked it!
Followíng command used to check:
Code:
busybox dd if=/dev/block/platform/msm_sdcc.1/by-name/modem | strings | grep "I9195"
The above always returned the old baseband version string.
And yes, the Odin solution works also for me but I'm searching for a CWM flash solution. No luck yet...

News: I've found this XDA thread, where user says:
The only Write operation permitted on a flash memory device is to
change a bit from a one to a zero. If the reverse operation is needed, then
the block must be erased (to reset all bits to the one state).
Click to expand...
Click to collapse
Maybe this is the solution. Before flashing modem, the whole modem partition must be erased.

Guys, it's really interesting. It seems, that modem partition on our device is write protected. We simply can't erase/format it or write anything to it from recovery (or we don't know the correct way).
I did the following: Went to TWRP recovery, which has built in command line terminal. My goal was to format modem partition. Normally this can be done using following command:
Code:
busybox mkfs.vfat -v /dev/block/platform/msm_sdcc.1/by-name/modem
Cmd executed successfully, but modem partition was NOT formatted.
After restart of phone I checked the mobile data functionality, everything worked and still works without problem.

This is the script form a GT-I9500 CWM-flashable modem.
Code:
ui_print("----Samsung Galaxy S4----");
ui_print("-----GT-I9500-ONLY-----");
ui_print("-----Android 4.2.2------");
ui_print("------STOCK Modem-----");
ui_print("-created-by-DjeMBeY-XDA-");
show_progress(0.150000, 0);
assert(package_extract_file("Djembey/modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p13"),
delete("/tmp/modem.bin"));
ui_print("Installation complete!");
show_progress(1.000000, 0);
Seems like it uses write_raw_image straight to the partition.

Whosat said:
This is the script form a GT-I9500 CWM-flashable modem.
Code:
ui_print("----Samsung Galaxy S4----");
ui_print("-----GT-I9500-ONLY-----");
ui_print("-----Android 4.2.2------");
ui_print("------STOCK Modem-----");
ui_print("-created-by-DjeMBeY-XDA-");
show_progress(0.150000, 0);
assert(package_extract_file("Djembey/modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p13"),
delete("/tmp/modem.bin"));
ui_print("Installation complete!");
show_progress(1.000000, 0);
Seems like it uses write_raw_image straight to the partition.
Click to expand...
Click to collapse
Yes, I saw that. Already tried but as the other methods: Script executes successfully, but modem is not updated.
You can also try if you want, here is my example.
The script in my package is following:
Code:
package_extract_dir("modem","/tmp");
[B]write_raw_image[/B]("/tmp/NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
delete("/tmp/NON-HLOS.bin");
Note: assert() command is not necessary.

Stuck in Recovery Mode....!!

Hi Xda This is owais khatri here,,
I haved watch whole xda but still not found help...
I have download all bin total.... 9 bins from xda and 2 from Amazon web site...
i have Adb and fastboot whole correct and recognze device,
bin download most of them is Cant read bin and 2 are running but at end they show (( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
HURTINGGG..
plz help meeee,,,,

owais khatri said:
(( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
Click to expand...
Click to collapse
Put the BIN file in the same folder where your ADB files are.
Use the exact name of the BIN file in the command line or rename it to a short & simple name, like your example above (e.g. "update.bin")
(Don't use ZIP files if you work with the official Amazon recovery, it can only process BIN files.)
Did you modify the build.prop on your device? What was the last OS version you had installed?

stuck at fire system recovery
Bingo Bronson said:
Put the BIN file in the same folder where your ADB files are.
Use the exact name of the BIN file in the command line or rename it to a short & simple name, like your example above (e.g. "update.bin")
(Don't use ZIP files if you work with the official Amazon recovery, it can only process BIN files.)
Did you modify the build.prop on your device? What was the last OS version you had installed?
Click to expand...
Click to collapse
i had same problem please someone who help me

owais khatri said:
Hi Xda This is owais khatri here,,
I haved watch whole xda but still not found help...
I have download all bin total.... 9 bins from xda and 2 from Amazon web site...
i have Adb and fastboot whole correct and recognze device,
bin download most of them is Cant read bin and 2 are running but at end they show (( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
HURTINGGG..
plz help meeee,,,,
Click to expand...
Click to collapse
Do you still have Safestrap installed? What happens when you try to reboot?

owais khatri said:
Hi Xda This is owais khatri here,,
I haved watch whole xda but still not found help...
I have download all bin total.... 9 bins from xda and 2 from Amazon web site...
i have Adb and fastboot whole correct and recognze device,
bin download most of them is Cant read bin and 2 are running but at end they show (( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
HURTINGGG..
plz help meeee,,,,
Click to expand...
Click to collapse
How are you connecting to the device? In Safestrap or Amazon Recovery? You should be able to sideload the Amazon official update via the Amazon Recovery no matter what condition your build.prop is in.
Download the official Amazon update bin for your device
Boot into Amazon Recovery by holding down Volume Down+Power
Select "Sideload update from ADB"
Run adb sideload <name of update file>.bin
Recommend you do a factory reset afterwards to be safe
Assuming all is well you can reroot now and go back to whatever custom image you desire

I have Amazon fire phone but it continuesly going on recovery mode after update and resetting

[Question] Error E1001: Failed to update system image, ERROR 7

Hi.
This is my first time working with ROMs, wanted to see if I could unpack and repack them and have them work, so I would know if my later changes cause problems. I've noticed if I unzip a ROM, then zip it again, without any changes made, I get this error within a few seconds of starting the flash. If I don't unpack and repack the zip, it flashes fine.
I use the Android Kitchen, to unpack/repack, and signed the zip. Anyone know what's going on?
Did a full wipe with TWRP before flash attempt.
Code:
Starting ADB Sideload feature...
Target: google/occam/mako:5.1.1/LMy48M/2167285:user/release-keys
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Thank you,
Josh

Edit your updater-script
find this line
Code:
.... package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
change to :
Code:
.... package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
Just replace " ||" with ";" and delete line abort("blablabla"):

adislice said:
find this line
Code:
.... package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
change to :
Code:
.... package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
Just replace " ||" with ";" and delete line abort("blablabla"):
Click to expand...
Click to collapse
hey man when i deleted that line my phone booted in fastboot mode

I solved this by installing the latest version of TWRP and Oxygen OS.

Can anyone please help me correct error 7 with the following updater-script
The error i get is :
Installing zip file '/external_sd/lineage-15.1
20180524-UNOFFICIAL-Ocm.zip
Checking for Digest file...
Target: htc/ocmdtwl_01405/htc_ocmdtwl:8.0.0/OPR6.
170623.013/1010171.4:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/
by-name/system
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/lineage-15.
-20180524-UNOFFICIAL-ROm,zip'
Updating partition details...
... done
assert(getprop("ro.product.device") == "htc_ocm" || getprop("ro.build.product") == "htc_ocm" ||
getprop("ro.product.device") == "htc_ocndugl" || getprop("ro.build.product") == "htc_ocndugl" ||
getprop("ro.product.device") == "htc_ocmdtwl" || getprop("ro.build.product") == "htc_ocmdtwl" ||
getprop("ro.product.device") == "ocm" || getprop("ro.build.product") == "ocm" || abort("E3004: This package is for device: htc_ocm,htc_ocndugl,htc_ocmdtwl,ocm; this device is " + getprop("ro.product.device") + ".");
ui_print("Target: htc/ocmdtwl_01405/htc_ocmdtwl:8.0.0/OPR6.170623.013/1010171.4:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
show_progress(0.650000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.100000, 0);
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
if (getprop("ro.boot.mid") == "2Q4D20000" || getprop("ro.boot.mid") == "2Q4D10000") then
ui_print("This is a DS device - renaming radio props");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
rename("/vendor/lib64/libril-qc-ltedirectdisc.so", "/system/vendor/lib64/libril-qc-ltedirectdisc.so");
rename("/vendor/lib64/libril-qc-qmi-1.so", "/system/vendor/lib64/libril-qc-qmi-1.so");
rename("/vendor/lib64/libril-qc-radioconfig.so", "/system/vendor/lib64/libril-qc-radioconfig.so");
rename("/vendor/lib64/libril-qcril-hook-oem.so", "/system/vendor/lib64/libril-qcril-hook-oem.so");
unmount("/system");
endif;
set_progress(1.000000);
Any help is appreciated :s

Try using sideload insted of sd
i had the same error and i could do nothing...then I thought my sd maybe giving the error so i tried the sideload mode and believe me..........it worked
option 2:-if u have backed up your rom (or by anyhow if you can) try flashing another (in my case...an older) version of twrp. it also worked for me. would be glad if this helps you.
---------- Post added at 11:30 PM ---------- Previous post was at 11:05 PM ----------
[/COLOR]
SL.Pirate said:
i had the same error and i could do nothing...then I thought my sd maybe giving the error so i tried the sideload mode and believe......me it worked
but...at the moment i am having another problem...i'd appreciate if someone could help. the rom has been installed correctly (I guess) but...when it reboots,it says encryption unsuccessful. ther'es a key sayng reset phone but nothing happens after pressing it.i tried wiping all the partitions and reinstalling the rom and no use.
Click to expand...
Click to collapse
Solved...had some matters with the data partition.

SL.Pirate said:
Solved...had some matters with the data partition.
Click to expand...
Click to collapse
Such as?
I'm stuck at the same place as you were...

For the posterity :
in TWRP go to advanced > terminal, then create /cache/recovery with
mkdir /cache/recovery
solved the problem for me
Source : https://android.stackexchange.com/q...ineage-16-samsung-galaxy-note-2-gt-n7100-t03g

6mon said:
Such as?
I'm stuck at the same place as you were...
Click to expand...
Click to collapse
it said 'ENCRYPTION UNSUCCESSFULL'
if the samething happens to you....go to twrp,select wipe,advanced wipe and select (only) the data partition. then you gotta select repair or change file system select change file system and then select the correct format for the partition.(in and most of the cases...it is the EXT4 format.go ahead and reboot your device.this should probably work.If not...try other formats also from bottom to to. (HINT:-see what other partitions are formatted to).This should probably work if thats the case.

worked for me .thanks alot

It works!
6mon said:
For the posterity :
in TWRP go to advanced > terminal, then create /cache/recovery with
mkdir /cache/recovery
solved the problem for me
Source : https://android.stackexchange.com/q...ineage-16-samsung-galaxy-note-2-gt-n7100-t03g
Click to expand...
Click to collapse
Thank you so much! Before doing this, my Lenovo Vibe K5 Plus (A6020) wasn't able to install any ROM, but it's over! Now I can install custom ROMs with no flaws :good:

Worked for me as well and much easier than editing the update script. Thanks a lot!

If youre still getting error 7 e1001 then try this.
Boot twrp
Tap advanced tab
Tap file manager/explorer
Tap on /system
Tap + icon on the folder in bottom right corner to modify
Tap chmod 755 to enable r/w for system part.
Try to install again.
That is what worked for me

6mon said:
For the posterity :
in TWRP go to advanced > terminal, then create /cache/recovery with
mkdir /cache/recovery
solved the problem for me
Source : https://android.stackexchange.com/q...ineage-16-samsung-galaxy-note-2-gt-n7100-t03g
Click to expand...
Click to collapse
did the trick for me. Whoever has Error 7 / Error 1001 issues, try this first cant hurt!

6mon said:
For the posterity :
in TWRP go to advanced > terminal, then create /cache/recovery with
mkdir /cache/recovery
solved the problem for me
Source : https://android.stackexchange.com/q...ineage-16-samsung-galaxy-note-2-gt-n7100-t03g
Click to expand...
Click to collapse
Posterity works!!! I found your post by googling and it solved my issue, thanks again!

I have the same issue on S4 mini, but /cache/recovery/ dir is present.

Hello
I am having this issue installing /e/ os on samsung J5 J500F.
I tried making directory /cache/recovery and addind read and write rights to /system but it did not work.
I also tried different version of the os and build as well as different version of TWRP.
I tried removing the assert line in the updater script but the zip file generated then in refused by twrp, It gets me the error "invalid zip file format".
I tried making the zip file with winrar or 7zip using either relatie paths or absolute path, but i still get the same error.
Would someone have an idea ?
Thanks !

Sometimes it is caused due to corrupted file. While transferring file through MTP it is likely to corrupt large files. I had the same problem. Then I tried copying file while in TWRP (sure it is also MTP) and it worked.

HatMan22 said:
Sometimes it is caused due to corrupted file. While transferring file through MTP it is likely to corrupt large files. I had the same problem. Then I tried copying file while in TWRP (sure it is also MTP) and it worked.
Click to expand...
Click to collapse
Hello, thank you very much for your advice, I copied all files through TWRP, so it is probably coming from something else.
I tried downloading the file and and also flashing some other builds or different versions but I still get "failed to update system image error"

Gabriel-Roger said:
Hello, thank you very much for your advice, I copied all files through TWRP, so it is probably coming from something else.
I tried downloading the file and and also flashing some other builds or different versions but I still get "failed to update system image error"
Click to expand...
Click to collapse
Do you have latest TWRP installed? Old TWRP may also cause this issue.

Update to MIUI 11 Couldn't verify error

Couldn't verify the package
I downloaded the full recovery package
miui_ONCLITEGlobal_V11.0.2.0.PFLMIXM_a43848d5f6_9. 0.zip
Form here
https://bigota.d.miui.com/V11.0.2.0.PFLMIXM/miui_ONCLITEGlobal_V11.0.2.0.PFLMIXM_a43848d5f6_9.0.zip
When I try to install it manually I get this error
How to manually update without loosing data?
Thanks in advance

Download full zip,open it
Find META-INF/com/google/android/updater-script
Delete
getprop("ro.product.device") == "onc" || abort("E3004: This package is for "onc" devices; this is a "" +
Flash in recovery
Maybe work