Database Users

Error installing CyanogenMod

I have an HTC Magic, and have just managed to downgrade hboot/spl and install a custom recovery.
But now, when i'm trying to install CM 6 (not the RC), i get a verification error..
Starting recovery..
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
Build : RA-hero-v1.6.2
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.ril.ecc.HTC-WWE=999
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.u70000.20090827.103405
ro.build.version.incremental=eng.u70000.20090827.103405
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Thu Aug 27 10:35:04 CST 2009
ro.build.date.utc=1251340504
ro.build.type=user
ro.build.user=u70000
ro.build.host=Android-X02
ro.build.tags=test-keys
ro.product.model=HTC Hero
ro.product.brand=htc_wwe
ro.product.name=htc_hero
ro.product.device=hero
ro.product.board=hero
ro.product.manufacturer=HTC
ro.product.locale.language=
ro.product.locale.region=
ro.board.platform=msm7k
ro.build.product=hero
ro.build.description=2.73.405.5 146733 CL#61267 release-keys
ro.build.changelist=61267
ro.product.ua=
ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:1.5/2.73.405.5/61267:user/test-keys
keyguard.no_require_sim=1
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep=1
wifi.interface=tiwlan0
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
wifi.supplicant_scan_interval=45
ro.sf.lcd_density=160
ro.com.google.locationfeatures=1
persist.service.mount.playsnd=0
settings.display.autobacklight=1
settings.display.brightness=102
ro.ril.def.agps.mode=2
ro.com.google.networklocation=1
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_sound=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-htc
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-hero-v1.6.2
ro.factorytest=0
ro.serialno=HT95WKF11405
ro.bootmode=recovery_manual
ro.baseband=6.35.08.29
ro.carrier=HTC-Nor
ro.bootloader=1.76.2007
ro.hardware=sapphire
ro.revision=128
ro.cid=HTC__Y13
init.svc.recovery=running
init.svc.adbd=running
I:Set boot command ""
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:
I:Set boot command ""
Enabling USB-MS : ./dev/block/mmcblk0
USB Mass Storage enabled
USB-MS enabled!
Press HOME to disable,
and return to menu
Disabling USB-MS : .USB Mass Storage disabled
USB-MS disabled!
I:Set boot command ""
I:Set boot command ""
Install : SDCARD:update-cm-6.0.0-DS-signed.zip ?
Press HOME to confirm,
any other key to abort.
Install from sdcard...
Finding update package...
I:Update location: SDCARD:update-cm-6.0.0-DS-signed.zip
Opening update package...
I:Update file path: /sdcard/update-cm-6.0.0-DS-signed.zip
Verifying update package...
I:Verified META-INF/CERT.RSA
I:Verified META-INF/MANIFEST.MF
<VERIFIED A LOT OF FILES>
I:Verified system/media/audio/ui/KeypressStandard.ogg
I:Verified system/lib/libGLESv1_CM.so
Installing update...
I:read: ui_print Welcome to CyanogenMod-6.0.0-DS!
Welcome to CyanogenMod-6.0.0-DS!script aborted: assert failed: getprop("ro.product.device") == "trout" || getprop("ro.build.product") == "trout" || getprop("ro.product.board") == "trout" ||
getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire" || getprop("ro.product.board") == "sapphire"
I:read: ui_print
I:read: ui_print assert failed: getprop("ro.product.device") == "trout" || getprop("ro.bassert failed: getprop("ro.product.device") == "trout" || getprop("ro.bI:read: uild.product") == "trout" || getprop("ro.product.board") == "trout" ||
E:unknown command [uild.product")]
I:read: ui_print getprop("ro.product.device") == "sapphire" || getprop("ro.build. getprop("ro.product.device") == "sapphire" || getprop("ro.build.I:read: product") == "sapphire" || getprop("ro.product.board") == "sapphire"
E:unknown command [product")]
I:read: ui_print
E:Error in /sdcard/update-cm-6.0.0-DS-signed.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I have no idea what to to, as i have never installed CM before.
the fastboot specs are:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Aug 21 2009, 18:19:15
help is much appreciated ^_^

It should not give any errors...
But you could always remove the error giving line from the install script..
Then resign the rom and flash it.

i'm sorry, i am a real noob on this, is it any chance you can do it for me? thanks.
EDIT: i tried once, but it got corrupted

You have to resign it.
Or it will get corrupted as the error gives you...
Or you could flash clockwork recovery instead of amon_ra... and deactivate the signing check.

thanks, i'll try that and report back

okay, now i reflashed the recovery with ROM Manager, pressed install from SD(in rom manager) and selected the CM rom(unmodified). it reboots, runs backup, everything looks good, and then the same error repeats itself until it sends me back to the recovery menu, where it is there for about 5 seconds, and then my phone reboots normally. all data is flashed.
how do i deactivate the signing check? or is there another solution?

EDIT... sorry just found that clockwork recovery does not work with the 6.35 radio...
**** it... i'll do it..
Give me link to the rom you want.

THANK YOU!
http://khsk.uberitz.net/cm/update-cm-6.0.0-DS-signed.zip
that's it. i need an EB1 kernel patch and google apps too(thats what cyanogenmod wiki said), dunno if they need to be changed too ..
link for google apps: http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-tiny-20101020-signed.zip
the EB1, though i dunno if it supports 6.35.x: http://briancrook.ca/android/cm-por...d.zip[/url
thanks SO much for doing this! :D

I found the problem...
You have 1.76.2007 spl...
This rom only works for old spl/radio...
Code:
getprop("ro.bootloader") == "1.33.2005" ||
getprop("ro.bootloader") == "1.33.2003AF" ||
getprop("ro.bootloader") == "1.33.0004" ||
getprop("ro.bootloader") == "1.33.2004" ||
getprop("ro.bootloader") == "1.33.3004" ||
getprop("ro.bootloader") == "1.33.0005" ||
getprop("ro.bootloader") == "1.33.2005" ||
getprop("ro.bootloader") == "1.33.3005" ||
getprop("ro.bootloader") == "1.33.0006" ||
getprop("ro.bootloader") == "1.33.2006" ||
getprop("ro.bootloader") == "1.33.3006" ||
getprop("ro.bootloader") == "1.33.0007" ||
getprop("ro.bootloader") == "1.33.2007" ||
getprop("ro.bootloader") == "1.33.3007" ||
getprop("ro.bootloader") == "1.33.0008" ||
getprop("ro.bootloader") == "1.33.2008" ||
getprop("ro.bootloader") == "1.33.3008" ||
getprop("ro.bootloader") == "1.33.0009" ||
getprop("ro.bootloader") == "1.33.2009" ||
getprop("ro.bootloader") == "1.33.0010" ||
getprop("ro.bootloader") == "1.33.2010" ||
getprop("ro.bootloader") == "1.33.0011" ||
getprop("ro.bootloader") == "1.33.2011" ||
getprop("ro.bootloader") == "1.33.3011" ||
getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013");

so i can downgrade via the instructions in this thread, and then install CM as normal?

No... use my tool to downgrade... MUCH EASIER :0)
Find it in my signature... Fastboot commander (magic).
Just find the magic 32A tab... then choose "flash old"...
It will flash a combo... so you also have the right recovery :0)
Then flash the rom, EBI1 and then gapps from recovery.

If you ever want to revert back to new radio.. then just choose "flash new" :0)

thanks, now i just have to make rapidshare stop hating me.. can't you upload to mediafire or something?

Done.............

okay, i just want to make sure about this.. what are the chances that ill brick my phone upgrading the radio? because im not sure if my magic supports the old radio..

I will never suggest to upgrade/downgrade your radio if i'm not sure that you device can support it.
Checking the op, i could see that you have the same device as i have... and i made the tool and tested my self... It will work :0)

ah, good. because i downgraded my SPL from S-ON and hboot 1.76.2009..
but since i did install the engineer spl, i suppose it works
EDIT: it didnt. i got this error:
"hboot" flash FAILURE.
FLASH OF OLD FILES FAILURE - SPL FAILURE.
then tried to flash new again, got this error:
"radio" flash FAILURE.
FLASH OF NEW FILES FAILURE - RADIO FAILURE.
EDIT2: unplugged and restarted into fastboot. it shows:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Aug 21 2009, 18.19.15
trying to boot normally, it gets into a boot loop. i can still get into fastboot and recovery(clockwork works!), so i dont think im bricked.

Easy now... and keep you comments in one thread or i will get confused...
YOU ARE NOT BRICKED!
You can fix this easy.
But lets agree on that you write on the fastboot commander thread where it's relevant.
See my reponse there

Hi,
It seems im in same error as you are.
Can you take a look at my thread.
http://forum.xda-developers.com/showthread.php?t=828300
Im almost done, stuck at flash the last 3 files according to instructions.
------------------------
17. After phone powers off, reboot into recovery by holding Home + Power keys.
.
18. Using the trackball, select "Flash ZIP from SD Card" and flash the following files.
Select the home key to confirm each file
a)update-cm-6.0.0-DS-signed.zip
b)bc-6.0.0-ebi1-signed.zip
c)gapps-mdpi-tiny-20100816-signed.zip
.
19. After the last file has finished flashing reboot the phone normally.
It can take anywhere from 5-15 min for the first boot.
--------------------------
thanks.

[Q] How to install the new android update??

Hey guys,
I have a problem with installing the new (dutch) Android 2.2 update.
If i'm trying to install the new update there is coming a lot of text in ClockWorkMod en it ends with this:
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
I have toggled signature verification off, but that did'nt worked.

+1 from me. I get the same thing and am a little confused.
What must be done in order for the update to be installed?

This is the full error report:
Code:
Starting recovery on Mon Dec 20 13:18:48 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (240 x 320)
ClockworkMod Recovery v2.5.0.1
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=ECLAIR
ro.build.display.id=koush_buzz-eng 2.1-update1 ECLAIR eng.koush.20100714.210216 test-keys
ro.build.version.incremental=eng.koush.20100714.210216
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Wed Jul 14 21:03:06 PDT 2010
ro.build.date.utc=1279166586
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-OSx86.local
ro.build.tags=test-keys
ro.product.model=HTC Buzz (EU)
ro.product.brand=generic
ro.product.name=koush_buzz
ro.product.device=buzz
ro.product.board=buzz
ro.product.cpu.abi=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=buzz
ro.build.description=koush_buzz-eng 2.1-update1 ECLAIR eng.koush.20100714.210216 test-keys
ro.build.fingerprint=generic/koush_buzz/buzz/buzz:2.1-update1/ECLAIR/eng.koush.20100714.210216:eng/test-keys
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT06KPY01746
ro.bootmode=recovery
ro.baseband=3.35.19.25
ro.carrier=HTC-Dutch
ro.bootloader=0.80.0002
ro.hardware=buzz
ro.revision=129
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Set boot command ""
Signature Check: Enabled
Signature Check: Disabled
Script Asserts: Enabled
-- Installing: SDCARD:download/OTA_Buzz_Froyo_HTC_WWE_2.22.405.1-1.37.405.1_release_160253md3o2yhu6sxs3txn.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:download/OTA_Buzz_Froyo_HTC_WWE_2.22.405.1-1.37.405.1_release_160253md3o2yhu6sxs3txn.zip
Opening update package...
I:Update file path: /sdcard/download/OTA_Buzz_Froyo_HTC_WWE_2.22.405.1-1.37.405.1_release_160253md3o2yhu6sxs3txn.zip
Installing update...
I:Trying update-binary.
script aborted: assert failed: getprop("ro.cid") == "00000000" ||
getprop("ro.cid") == "11111111" || getprop("ro.cid") == "22222222" ||
getprop("ro.cid") == "33333333" || getprop("ro.cid") == "44444444" ||
getprop("ro.cid") == "55555555" || getprop("ro.cid") == "66666666" ||
getprop("ro.cid") == "77777777" || getprop("ro.cid") == "88888888" ||
getprop("ro.cid") == "99999999" || getprop("ro.cid") == "HTC__001" ||
getprop("ro.cid") == "HTC__E11" || getprop("ro.cid") == "HTC__N34" ||
getprop("ro.cid") == "HTC__203" || getprop("ro.cid") == "HTC__102" ||
getprop("ro.cid") == "HTC__405" || getprop("ro.cid") == "HTC__Y13" ||
getprop("ro.cid") == "HTC__A07" || getprop("ro.cid") == "HTC__304" ||
getprop("ro.cid") == "HTC__032"
assert failed: getprop("ro.cid") == "00000000" || getprop("ro.cid") == "11111111" || getprop("ro.cid") == "22222222" || getprop("ro.cid") == "33333333" || getprop("ro.cid") == "44444444" || getprop("ro.cid") == "55555555" || getprop("ro.cid") == "66666666" || getprop("ro.cid") == "77777777" || getprop("ro.cid") == "88888888" || getprop("ro.cid") == "99999999" || getprop("ro.cid") == "HTC__001" || getprop("ro.cid") == "HTC__E11" || getprop("ro.cid") == "HTC__N34" || getprop("ro.cid") == "HTC__203" || getprop("ro.cid") == "HTC__102" || getprop("ro.cid") == "HTC__405" || getprop("ro.cid") == "HTC__Y13" || getprop("ro.cid") == "HTC__A07" || getprop("ro.cid") == "HTC__304" || getprop("ro.cid") == "HTC__032"
E:Error in /sdcard/download/OTA_Buzz_Froyo_HTC_WWE_2.22.405.1-1.37.405.1_release_160253md3o2yhu6sxs3txn.zip
(Status 7)
Installation aborted.
I:Set boot command ""

I've got exactly the same problem trying to install the version for Greece. The filename is: OTA_Buzz_Froyo_HTC_WWE_2.22.405.1-1.37.405.1_release_160253md3o2yhu6sxs3txn.zip
(I don't know if it is legal to upload this file somewhere)
I tried playing with signature checking (if I didn't disable it, it would stop with a another error message saying that it cannot verify the whole zip or something like that).
I also played with the script assertion option but nothing changed. My log seems identical to the one posted above.
Any ideas?

it seems that it's needed to change the final of that update file ,
remove those letters from final and install there after the update
i just did it this way

I just did that and did not work. I even renamed the whole thing and got the same thing

Exatly the same here, played around with sig too with no luck. get the same status 7 error

Same here,i cant install the new official update.My buzz is routed and i think maybe is that a problem or not?

Seems like that ro.cid is not set on your phone.

sorry but iam new in this,what is ro.cid?

I guess we have to do this: http://forum.xda-developers.com/showpost.php?p=8926494&postcount=8
I'm gonna try that and i'll post the result.

I am not 100% sure but i found at pastebin a copy of a build.prop
Code:
#
ro.hardware=buzz
#
ro.revision=128
#
ro.cid=11111111
#
ro.emmc=0
#
init.svc.choice_fn=stopped
#
init.svc.adbd=running
#
init.svc.recovery=running
#
adb.connected=1
.
.
.
Maybe you can fix it by starting a adb shell then type
Code:
echo ro.cid=11111111 >> /system/build.prop
But you need to make /system partition writeable.

sdevos13 said:
I guess we have to do this: http://forum.xda-developers.com/showpost.php?p=8926494&postcount=8
I'm gonna try that and i'll post the result.
Click to expand...
Click to collapse
are u succes in your try?

I didn't tryed it yet.
I re-rooted my HTC Wildfire with the newest Unrevoked because of the changelog on: http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
Code:
Changelog
unrevoked3 has been through the following versions:
v3.22:
Fix for latest Incredible OTA.
New Mac OS X build infrastructure; let us know if it broke for you.
Switched to in-house reimplementation of rageagainstthecage for better reliability.
I'm downloading the update again, and i'll post the result.

its an update from 1.25.162.1 to 2.24.162.1
you have to have 1.25.162.1 installed before this update works. hacking need to be done to aplay this.
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "vodafone_de/htc_buzz/buzz/buzz:2.1-update1/ERE27/229476:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "vodafone_de/htc_buzz/buzz/buzz:2.2.1/FRG83D/298713:user/release-keys");

Rooting with the newest Unrevoked does not solve the problem

stock rom
just flash a stock and reupdate, should be work, i will try too..
shipped roms?
please post if works.. (I will do)

omiblack said:
just flash a stock and reupdate, should be work, i will try too..
shipped roms?
please post if works.. (I will do)
Click to expand...
Click to collapse
you have to have 1.25.162.1 installed before this update works. hacking need to be done to aplay this.
and you will loose your root if you flash an ruu and then this patch.. its NOT safe..

I have exactly the same problem.
I do not know what to do next.

danne_jo said:
you have to have 1.25.162.1 installed before this update works. hacking need to be done to aplay this.
and you will loose your root if you flash an ruu and then this patch.. its NOT safe..
Click to expand...
Click to collapse
So even if we install the RUU rom and than the Android 2.2 update, it won't work?
I'm out of ideas xD

[Concept] OEM Image flasher [AOSP on the Go]

I make it short. Actually are Xperia Devices unable to run AOSP without using fastboot to flash the OEM Images from SONY. I wanted to create a empty ZIP containing a Updater Script who flashes the OEM Images after placing them into the ZIP. The Problem is that i was unable to find the OEM Partition. Is anyone aware of it? I'm searching for the "/dev/block/platform/*/by-name/" to use a command like this "package_extract_file("boot.img", file_getprop("/tmp/config", "boot"));"
And for the People who are wondering why the ZIP has to be empty. There are two Reasons. First, all Devices need own Images, besides that they are getting updated from Time to Time.
The second thing is the Legal Stuff. SONY added a Agreement before You can download the Images. Every User has to accept that, otherwise would we get trouble with them.
Just to clear that out already. Hope we can quickly make the flashing more handy for the Future!
And Dear Moderators, pls don't move this Thread. It will be edited and extended after creating the ZIP to share it right here!

Why not just add /oem flash image to ota-zip (or twrp?)?
Miustone said:
I make it short. Actually are Xperia Devices unable to run AOSP without using fastboot to flash the OEM Images from SONY....
And Dear Moderators, pls don't move this Thread. It will be edited and extended after creating the ZIP to share it right here!
Click to expand...
Click to collapse
{make otapackage} works 100% on xz1 Xperiadev natural aosp; it even comes with an odd aosp/recovery embedded : thus better to FIRST make clean +make bootimage and save it to avoid final embedded recovery. The /vendor img is also included in the ota zip.
If you want to add addon.d support check my Los15 "extracted" https://forum.xda-developers.com/an...zip-custom-t3173316/post76455910#post76455910
Than just repack the final ota zip package with them (including Los15 update-binary).
If you want WidevineDRM L3 (check XZ1 attached txt) you need to add specifics drm/vendors in /vendor prior to build; alternatively for Magisk users, you can instead repack them in final ota zip, but they will only be active after Magisk install. Source https://github.com/DirtyUnicorns/an...3d1555c#diff-daceb2a2ce86bd2430773e29f2b3db5e
To avoid Firebase analytics in Webview , I also suggest using Lineage15 pre-pack 66 version (arm64) https://github.com/LineageOS/android_external_chromium-webview/tree/lineage-15.1/prebuilt
Don't forget MicroG patches https://forum.xda-developers.com/showpost.php?p=75320072&postcount=4319 ...
Code:
[SIZE="1"][I]'bolded is added'[/I]
getprop("ro.product.device") == "poplar" || abort("E3004: This package is for \"poplar\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Sony/aosp_g8341/poplar:8.1.0/OPM2.171019.029/nn04300157:userdebug/dev-keys");
[B]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");
[/B]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.");
[B]mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
[/B]
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.");
[B]mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/vendor", "/vendor", "");
package_extract_dir("vendor", "/vendor");
unmount("/vendor");
[/B]show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
[/SIZE]
EDIT @Miustone , aosp xperiadev mostly use /odm instead of /oem for /dev/block/bootdevice/by-name/oem (sda63 on xz1), but fastboot always -> oem
(1000Thx @jerpelea )

kccat6 twrp fails upgrade to 15.1 updater-script issues

Folks.
I am sure this has been fixed before but I cannot find it using Google-fu or XDA searches.
I have a S5 G901f running Lineage OS 14.1 [14.1-20180615-NIGHTLY-kccat6]
I want to upgrade to 15 so I downloaded the nightly image file from here: hxxxps://download.lineageos.org/kccat6
I got the Feb 15 and Feb 8 versions just to make sure.
lineage-15.1-20190215-nightly-kccat6-signed.zip
lineage-15.1-20190206-nightly-kccat6-signed.zip
They fail on TWRP twrp-3.2.3-0-kccat6.img with Error Code 7, because my phone fails to report any device at all, it reports as null. [Note there is also a non fatal error reporting no Digest file found but I believe that's not the issue.
So I edited the update-script to remove the device check: vis
I removed this totally:
assert(getprop("ro.product.device") == "kccat6xx" || getprop("ro.build.product") == "kccat6xx" ||
getprop("ro.product.device") == "kccat6" || getprop("ro.build.product") == "kccat6" || abort("E3004: This package is for device: kccat6xx,kccat6; this device is " + getprop("ro.product.device") + ".");
ui_print("Target: samsung/kccat6xx/kccat6:6.0.1/MMB29M/G901FXXS1CPLA:user/release-keys");
Click to expand...
Click to collapse
But then TWRP fails with Error 6, which is almost certainly to do with this line later in update-script:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
Click to expand...
Click to collapse
and then I guess this one would fail:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
Click to expand...
Click to collapse
So, boys and girls, how do I edit the updater-script to make it work, or is there a variant TWRP that I can use which somehow fixes this?
Your kind advice is very welcome, and if I have posted incorrectly, please steer me aright..

lineageOSsuccefuly installled after adapting to axon 7 a2017g and asking about error6

Hi guys i succefuly installed lineageOS 14.1 after some changes and skipping two errors(error7 and error6) to adapt it on my phone axon7 a2017G ;
i want to know why on error6 i deleted (lines 3-4-5-6-7)!! what's the problem on those lines to adapt it on our phone axon 7 a2017g ! i mean we delete those instructions to adpat it in axon 7 a2017G .
this is the script-updater made at beginning :
1.assert(getprop("ro.product.device") == "ailsa_ii" || getprop("ro.build.product") == "ailsa_ii" || getprop("ro.product.device") == "axon7" || getprop("ro.build.product") == "axon7" || abort("E3004: This package is for device: ailsa_ii,axon7; this device is " + getprop("ro.product.device") + ".");
2.assert(axon7.verify_trustzone("TZ.BF.4.0.1-00325") == "1");
3.ui_print("Target: ZTE/P996A01_N/ailsa_ii:7.1.1/NMF26V/20170420.050245:user/release-keys");
4.ifelse(is_mounted("/system"), unmount("/system"));
5.package_extract_dir("install", "/tmp/install");
6.set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
7.set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
8.mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
9.run_program("/tmp/install/bin/backuptool.sh", "backup");
10.1unmount("/system");
11.if is_mounted("/data") then
12.package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
13.run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
14.else
15.mount("f2fs", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
16.package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
17.run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
18.unmount("/data");
19.endif;
20.show_progress(0.750000, 0);
21.ui_print("Patching system image unconditionally...");
22.block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
23.show_progress(0.020000, 10);
24.mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
25.run_program("/tmp/install/bin/backuptool.sh", "restore");
26.unmount("/system");
27.show_progress(0.050000, 5);
28.package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
29.show_progress(0.200000, 10);
30.set_progress(1.000000);