Hi!
I've created CWM installable ZIP which updates only modem.
Updater script 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("------------------------------------------------------");
show_progress(0.100000, 0);
ui_print("GT-I9195XXUBMJ7 modem update - by LackoGyerek");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
show_progress(0.100000, 50);
write_raw_image("/tmp/modem.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem"),
delete("/tmp/modem.bin"));
show_progress(0.100000, 100);
ui_print("Done!");
ui_print("------------------------------------------------------");
But unfortunately the script fails at the assert(package_extract_file()) line...
Download the whole update package here.
Can anybody check it and find out, what is wrong?
Note: Modem binary is taken form latest GT-I9195XXUBMJ7 official firmware. I only renamed the NON-HLOS.bin to modem.bin.
ladislav.heller said:
Hi!
I've created CWM installable ZIP which updates only modem.
Updater script 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("------------------------------------------------------");
show_progress(0.100000, 0);
ui_print("GT-I9195XXUBMJ7 modem update - by LackoGyerek");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
show_progress(0.100000, 50);
write_raw_image("/tmp/modem.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem"),
delete("/tmp/modem.bin"));
show_progress(0.100000, 100);
ui_print("Done!");
ui_print("------------------------------------------------------");
But unfortunately the script fails at the assert(package_extract_file()) line...
Download the whole update package here.
Can anybody check it and find out, what is wrong?
Note: Modem binary is taken form latest GT-I9195XXUBMJ7 official firmware. I only renamed the NON-HLOS.bin to modem.bin.
Click to expand...
Click to collapse
Try attached updater binary
citymen34 said:
Try attached updater binary
Click to expand...
Click to collapse
The same error. Message is following:
Code:
assert failed: write_raw_image("/tmp/modem.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem")
E:Error in /external_sd/Install/Temp/CWM_I9195XXUAMJ1_modem.zip
(Status 7)
Installation aborted.
ladislav.heller said:
The same error. Message is following:
Code:
assert failed: write_raw_image("/tmp/modem.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem")
E:Error in /external_sd/Install/Temp/CWM_I9195XXUAMJ1_modem.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
try
package_extract_file("modem.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
or
package_extract_file("modem.bin", "/dev/block/mmcblk0p1");
If You see on Log by MobileOdin attached the partition from modem is like this:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat
See also the ScreenShot by DiskInfo.
If You replace /modem by /firmware may be... work. Like the /efs, like the /system... (and is a vfat file, not a ext4).
Now the modem /firmware is a Filesystem
Filesystem Size Used Free Blksize
/system 1.46G 1.37G 95.1M 4096
/data 5.42G 455M 4.97G 4096
/cache 196M 4.20M 192M 4096
/persist 7.88M 4.04M 3.85M 4096
/efs 13.4M 4.16M 9.26M 4096
/firmware 64.0M 47.3M 16.7M 16384
/mnt/shell/container 5.40G 455M 4.95G 4096
May by like /system:
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
For /modem /firmware:
run_program("/sbin/busybox", "mount", "/firmware");
package_extract_dir("NON_HLOS", "/firmware"); --> _dir because we have /firmware/image/...many files.
Or something same this.
I'd like to contribute for G2 beginner users from Latam., which mostly have D802 regional variants (like Brazil D805 or Argentina D806), and many of those have been asking me how to flash D802 roms.
Specially with the recent burst of Lollipop roms made available.
To clarify:
D805/6 is essentially the same hardware as D802 (same SoC (cpu), board, etc.), with some slight packaging and peripheral/radio variations.
Most software should work interchangeably, with exception of modem/baseband firmware.
However many ROMS fail to flash on those phones, because the dev. sometimes put validation code in the setup script, to ensure you're flashing the right version.
That script checks the phone model, and rejects D805/6.
To make your D802 rom flashable in your D805/6, unzip the following file in the rom zip:
Code:
\META-INF\com\google\android\updater-script
Edit it in a text editor, and look for a line in the beginning like:
Code:
assert(getprop("ro.product.device") == "d802" || getprop("ro.build.product") == "d802" || getprop("ro.product.device") == "g2" || [. . . . . . ]
REMOVE that single line, save the file, and finally replace it in the same location of the zip, and you are ready to flash.
PLEASE MAKE FULLY SURE YOU ARE FLASHING A D802 ROM, AND THAT IT DOESN'T INCLUDE A MODEM
rodrigofd said:
I'd like to contribute for G2 beginner users from Latam., which mostly have D802 regional variants (like Brazil D805 or Argentina D806), and many of those have been asking me how to flash D802 roms.
Specially with the recent burst of Lollipop roms made available.
To clarify:
D805/6 is essentially the same hardware as D802 (same SoC (cpu), board, etc.), with some slight packaging and peripheral/radio variations.
Most software should work interchangeably, with exception of modem/baseband firmware.
However many ROMS fail to flash on those phones, because the dev. sometimes put validation code in the setup script, to ensure you're flashing the right version.
That script checks the phone model, and rejects D805/6.
To make your D802 rom flashable in your D805/6, unzip the following file in the rom zip:
Code:
\META-INF\com\google\android\updater-script
Edit it in a text editor, and look for a line in the beginning like:
Code:
assert(getprop("ro.product.device") == "d802" || getprop("ro.build.product") == "d802" || getprop("ro.product.device") == "g2" || [. . . . . . ]
REMOVE that single line, save the file, and finally replace it in the same location of the zip, and you are ready to flash.
PLEASE MAKE FULLY SURE YOU ARE FLASHING A D802 ROM, AND THAT IT DOESN'T INCLUDE A MODEM
Click to expand...
Click to collapse
does this process support other models too?? like f320l? if not kindly tell pls how to thanks
tengo que borrar esto: assert(getprop("ro.product.device") == "d802" || getprop("ro.build.product") == "d802" || getprop("ro.product.device") == "g2" || ?? lo que sigue [. . . .] no me figura nada....a que te referis con eso?
aromano91 said:
tengo que borrar esto: assert(getprop("ro.product.device") == "d802" || getprop("ro.build.product") == "d802" || getprop("ro.product.device") == "g2" || ?? lo que sigue [. . . .] no me figura nada....a que te referis con eso?
Click to expand...
Click to collapse
Please write in english or we will be banned by the forum..
I mean that the exact line might vary from rom to rom, but the goal is to remove the entire line that begins with assert( .... )
rodrigofd said:
Please write in english or we will be banned by the forum..
I mean that the exact line might vary from rom to rom, but the goal is to remove the entire line that begins with assert( .... )
Click to expand...
Click to collapse
ok...for example these one take a look...
assert(getprop("ro.product.device") == "d802" || getprop("ro.build.product") == "d802" || getprop("ro.product.device") == "g2" || getprop("ro.build.product") == "g2" || getprop("ro.product.device") == "galbi" || getprop("ro.build.product") == "galbi" || getprop("ro.product.device") == "d800" || getprop("ro.build.product") == "d800" || abort("This package is for device: d802,g2,galbi,d800; this device is " + getprop("ro.product.device") + ".");
if ! is_mounted("/system") then
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
endif;
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh") == "0" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data", "");
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh") == "0" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
delete("/system/bin/otasigcheck.sh");
unmount("/system");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "restore");
delete("/system/bin/backuptool.sh");
delete("/system/bin/backuptool.functions");
unmount("/system");
show_progress(0.050000, 5);
show_progress(0.200000, 10);
package_extract_file("boot.img", "/tmp/boot.img");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
assert(run_program("/system/bin/loki.sh") == 0);
delete("/system/bin/loki.sh");
unmount("/system");
ui_print("=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-");
ui_print(" \ ) ( )\ ) )\ ) ");
ui_print(" (()/ ( ( )\ ( (()/((()/( ");
ui_print(" (_)) ((_) (_)_) /((_)(_)) (_)) ");
ui_print(" | | (_) / _ \ (_))( |_ _| | \ ");
ui_print(" | |__ | || (_) || || | | | | |) | ");
ui_print(" |____||_| \__\_\ \_,_||___| |___/ ");
ui_print("=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-");
ui_print(" <%%% Liquid-lollipop %%%> ");
ui_print(" <%%% By LiquidSmooth %%%> ");
ui_print("=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-");
aromano91 said:
ok...for example these one take a look...
assert(getprop("ro.product.device") == "d802" || getprop("ro.build.product") == "d802" || getprop("ro.product.device") == "g2" || getprop("ro.build.product") == "g2" || getprop("ro.product.device") == "galbi" || getprop("ro.build.product") == "galbi" || getprop("ro.product.device") == "d800" || getprop("ro.build.product") == "d800" || abort("This package is for device: d802,g2,galbi,d800; this device is " + getprop("ro.product.device") + ".");
if ! is_mounted("/system") then
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
endif;
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh") == "0" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data", "");
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh") == "0" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
delete("/system/bin/otasigcheck.sh");
unmount("/system");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "restore");
delete("/system/bin/backuptool.sh");
delete("/system/bin/backuptool.functions");
unmount("/system");
show_progress(0.050000, 5);
show_progress(0.200000, 10);
package_extract_file("boot.img", "/tmp/boot.img");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
assert(run_program("/system/bin/loki.sh") == 0);
delete("/system/bin/loki.sh");
unmount("/system");
ui_print("=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-");
ui_print(" \ ) ( )\ ) )\ ) ");
ui_print(" (()/ ( ( )\ ( (()/((()/( ");
ui_print(" (_)) ((_) (_)_) /((_)(_)) (_)) ");
ui_print(" | | (_) / _ \ (_))( |_ _| | \ ");
ui_print(" | |__ | || (_) || || | | | | |) | ");
ui_print(" |____||_| \__\_\ \_,_||___| |___/ ");
ui_print("=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-");
ui_print(" <%%% Liquid-lollipop %%%> ");
ui_print(" <%%% By LiquidSmooth %%%> ");
ui_print("=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-");
Click to expand...
Click to collapse
Remove the first line.
Your first line should then be:
if ! is_mounted("/system") then
I never had to modify a single line for my D806 to flash any of the 200(?) ROMs and variants I already tried. Just flashing any for D802 ROM/Kernel/Recovery (anything but the baseband) actually work.ed each time. For which ROM you had to modify the installer script for?
Regards
Floodland said:
I never had to modify a single line for my D806 to flash any of the 200(?) ROMs and variants I already tried. Just flashing any for D802 ROM/Kernel/Recovery (anything but the baseband) actually work.ed each time. For which ROM you had to modify the installer script for?
Regards
Click to expand...
Click to collapse
For flash D802 roms on D806.
Or just flash d802 recovery
Floodland said:
I never had to modify a single line for my D806 to flash any of the 200(?) ROMs and variants I already tried. Just flashing any for D802 ROM/Kernel/Recovery (anything but the baseband) actually work.ed each time. For which ROM you had to modify the installer script for?
Regards
Click to expand...
Click to collapse
There are indeed some roms that include that validation on their flash scripts... e.g. the sample in this thread is for LiquidSmooth rom series...
my question is if I install zip stock of 802? I have a D806
Sorry. Both Liquidsmooth both 3.2 and 4.0 install perfectly without modifications with the D802 build on our D806, the same at any other ROM which supports D802, except if they try to flash a baseband (I think none of the lastest 300 releases do that anyway). System, recovery and kernels are compatible. I did not dare to replace the bootloader with the latest one from D802, it should work as well, but I know it the boot loader is the phone Achilles heel, so I do not want to spend hours trying to revert something that already works.... As far as I know, there are no advantages in updating it either. I am happy pressing vol. down power to access recovery
Tip: D805 basebands do work for our D806. I do have better signal reception using Brazil modem in our sad networks.
is it possible to intall officail cm12.1 of d802 model in d805 ??
Downloaded Alpha 02/02 but when I try and install it I get:
This is for device: A001; this device is bacon.
Error executing binary in zip '/tmp/mr_update.zip'
Of course has to do with updater script.
I did download YoshiShaPow's unofficial and compared the two scripts and they are different.
My question, both below, can I just copy Yoshi's to PA and install PA that way. Yoshi's does do more but not exactly sure what.
Yoshi's:
assert(getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" || getprop("ro.product.device") == "A0001" || getprop("ro.build.product") == "A0001" || abort("This package is for device: bacon,A0001; this device is " + getprop("ro.product.device") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
show_progress(0.750000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "restore");
delete("/system/bin/backuptool.sh");
delete("/system/bin/backuptool.functions");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
PA's:
assert(getprop("ro.product.device") == "A0001" || getprop("ro.build.product") == "A0001" || abort("This package is for device: A0001; this device is " + getprop("ro.product.device") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
show_progress(0.750000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
Why don't you just update your recovery, because that's what fixes your issue?
This has been covered in many places, one of which being the official bug tracker.
#stayparanoid
Pirateghost said:
Why don't you just update your recovery, because that's what fixes your issue?
This has been covered in many places, one of which being the official bug tracker.
#stayparanoid
Click to expand...
Click to collapse
Thanks, my recovery is twrp 2.8.4. using multirom version for the OnePlus. Yoshi's installs fine PA gives error that's why I am thinking in this case it's sript issue. Trying to resolve this bcz would like to use updated PA ROM Yoshi's are several updates behind recent PA.
Probably just me but my search through bug tracker should problems w/KitKat ROMs not much showing for Lollipop project.
Will have to search bit more here in XDA for resolution have to finish getting automobile back on the road for now.
silvagroup said:
Thanks, my recovery is twrp 2.8.4. using multirom version for the OnePlus. Yoshi's installs fine PA gives error that's why I am thinking in this case it's sript issue. Trying to resolve this bcz would like to use updated PA ROM Yoshi's are several updates behind recent PA.
Probably just me but my search through bug tracker should problems w/KitKat ROMs not much showing for Lollipop project.
Will have to search bit more here in XDA for resolution have to finish getting automobile back on the road for now.
Click to expand...
Click to collapse
The problem is MultiRom then.
if you want to bypass it, just remove the assert altogether, it isnt required.
FYI: all lollipop stuff is wrapped up in one section of the bug tracker:
https://paranoidandroid.atlassian.net/browse/AOSPALP
in particular the issue on recovery:
https://paranoidandroid.atlassian.net/browse/AOSPALP-32
Thanks.
For curiosities sake and better understanding if assert can be removed can't the A001 in the script also be changed to Bacon. Sorry for what are probably stupid questions but this is out of my current knowledge base.
Yes. You can do that too.
#stayparanoid
Yes thanks did it and it worked fine. Using PA right now.
silvagroup said:
Yes thanks did it and it worked fine. Using PA right now.
Click to expand...
Click to collapse
Hello, sorry for my noob question, but what did you do to fix the problem?
I got the exact same problem now..
I tried the ''MultiROM Uninstaller'' - didn't work.
I tried reflashing TWRP - didn't work.
If you could make a step by step guide, I will be veryy greatful
TheDechev said:
Hello, sorry for my noob question, but what did you do to fix the problem?
I got the exact same problem now..
I tried the ''MultiROM Uninstaller'' - didn't work.
I tried reflashing TWRP - didn't work.
If you could make a step by step guide, I will be veryy greatful
Click to expand...
Click to collapse
A. Get rid of multirom and use straight TWRP
Or
B. Edit the updater script in the ROM to remove the assert line. (There are lots of tutorials out there for this)
#stayparanoid
TheDechev said:
Hello, sorry for my noob question, but what did you do to fix the problem?
I got the exact same problem now..
I tried the ''MultiROM Uninstaller'' - didn't work.
I tried reflashing TWRP - didn't work.
If you could make a step by step guide, I will be veryy greatful
Click to expand...
Click to collapse
Really easy, just change every instance of A0001 in PA updater script to bacon and your ready to rock and roll.
Hi guys, I'm going to show you how to port Lineage 14.1 Samsung S4 I9506 to E330 SKL Korean Edition,
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Click to expand...
Click to collapse
Download Step
First, you need to download notepad++, the Lineage rom in the orignal post, also don't forget to download Google apps (OpenGapps).
Pre-Flash Step
After downloading the rom, open it, then browse to META-INF/com/google/android, extract "updater-script" file then open the extracted file with Notepad++, Replace "ks01ltexx" with:
"ks01lteskt" if your phone is E330S
"ks01ltektt" if your phone is E330K
"ks01ltelgt" if your phone is E330L
Example: E330S update-script file:
Code:
assert(getprop("ro.product.device") == "ks01lte" || getprop("ro.build.product") == "ks01lte" || getprop("ro.product.device") == "ks01lteskt" || getprop("ro.build.product") == "ks01lteskt" || getprop("ro.product.device") == "GT-I9506" || getprop("ro.build.product") == "GT-I9506" || abort("E3004: This package is for device: ks01lte,ks01lteskt,GT-I9506; this device is " + getprop("ro.product.device") + ".");); ui_print("Target: samsung/ks01lteskt/ks01lte:5.0.1/LRX22C/I9506XXUDPG2: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/platform/msm_sdcc.1/by-name/system", "/system", ""); run_program("/tmp/install/bin/backuptool.sh", "backup"); unmount("/system"); if is_mounted("/data") then package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey"); 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"); else mount("f2fs", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data", ""); package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey"); 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"); unmount("/data"); endif; show_progress(0.750000, 0); ui_print("Patching system image unconditionally..."); block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") || abort("E1001: Failed to update system image."); show_progress(0.020000, 10); mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/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/platform/msm_sdcc.1/by-name/boot"); show_progress(0.200000, 10); set_progress(1.000000);
Note: You need to check which version in TWRP recovery if it is E330L or E330S or E330K not in about phone menu!
Now, you need to reformat the file to prevent any CWM errors, in Notepad++, go to Edit Menu>EOL Conversion> Convert to UNIX Format. Edit Menu again, Blank Operations> Remove Unbecessary Blank and EOL. Edit Menu>Blank Operation>TAB To Space.
Then save the file and put it in the archive again (replace the old one). Go back to the main directory then go to system folder, extract build.prop and replace ks01ltexx with the suitable version as explained before. save it, replace the old one with the edited one.
Flash Step
All you have to do is to follow the instructions in the original post.
Note: Do not flash Modem/Bootloader !