Related
i have a problem with RTL script under CWM.
if some can help me to fix the script for CWM it will be great.
here is the script for stock recovery:
assert(getprop("ro.product.device") == "GT-S5830" ||
getprop("ro.build.product") == "GT-S5830" ||
getprop("ro.product.device") == "GT-S5570" ||
getprop("ro.build.product") == "GT-S5570" ||
getprop("ro.product.device") == "GT-S5670" ||
getprop("ro.product.product") == "GT-S5670"||
getprop("ro.product.device") == "GT-B7510" ||
getprop("ro.product.product") == "GT-B7510"
);
show_progress(0.100000, 0);
show_progress(0.500000, 0);
# format("MTD", "system");
#mount("MTD", "system", "/system");
ui_print(" - deleting old system files...");
delete_recursive("/system/app");
delete_recursive("/system/fonts");
delete_recursive("/system/framework");
delete_recursive("/system/lib");
delete_recursive("/system/xbin");
ui_print(" - unpacking system files...");
package_extract_dir("system", "/system");
ui_print(" - settin files permissions...");
set_perm(0, 0, 04755, "/system/xbin/sqlite3");
set_perm(0, 0, 04755, "/system/xbin/su-v1");
set_perm(0, 0, 04755, "/system/xbin/su-v2");
set_perm(0, 0, 04755, "/system/xbin/su-v3");
set_perm(0, 0, 04755, "/system/xbin/su");
set_perm(0, 0, 04755, "/system/xbin/sh");
set_perm(0, 0, 04755, "/system/xbin/busybox");
ui_print("Install complete, reboot...");
#unmount("/system");
izador said:
i have a problem with RTL script under CWM.
if some can help me to fix the script for CWM it will be great.
here is the script for stock recovery:
Code:
assert(getprop("ro.product.device") == "GT-S5830" ||
getprop("ro.build.product") == "GT-S5830" ||
getprop("ro.product.device") == "GT-S5570" ||
getprop("ro.build.product") == "GT-S5570" ||
getprop("ro.product.device") == "GT-S5670" ||
getprop("ro.product.product") == "GT-S5670"||
getprop("ro.product.device") == "GT-B7510" ||
getprop("ro.product.product") == "GT-B7510"
);
show_progress(0.100000, 0);
show_progress(0.500000, 0);
# format("MTD", "system");
#mount("MTD", "system", "/system");
ui_print(" - deleting old system files...");
delete_recursive("/system/app");
delete_recursive("/system/fonts");
delete_recursive("/system/framework");
delete_recursive("/system/lib");
delete_recursive("/system/xbin");
ui_print(" - unpacking system files...");
package_extract_dir("system", "/system");
ui_print(" - settin files permissions...");
set_perm(0, 0, 04755, "/system/xbin/sqlite3");
set_perm(0, 0, 04755, "/system/xbin/su-v1");
set_perm(0, 0, 04755, "/system/xbin/su-v2");
set_perm(0, 0, 04755, "/system/xbin/su-v3");
set_perm(0, 0, 04755, "/system/xbin/su");
set_perm(0, 0, 04755, "/system/xbin/sh");
set_perm(0, 0, 04755, "/system/xbin/busybox");
ui_print("Install complete, reboot...");
#unmount("/system");
Click to expand...
Click to collapse
Look here. You need to add into your script commands to mount and umount system, so replace
Code:
#mount("MTD", "system", "/system");
with
Code:
run_program("/sbin/busybox", "mount", "/system");
and
Code:
#unmount("/system");
with
Code:
run_program("/sbin/busybox", "umount", "/system");
and it should work (not tested).
PabloPL said:
Look here. You need to add into your script commands to mount and umount system, so replace
Code:
#mount("MTD", "system", "/system");
with
Code:
run_program("/sbin/busybox", "mount", "/system");
and
Code:
#unmount("/system");
with
Code:
run_program("/sbin/busybox", "umount", "/system");
and it should work (not tested).
Click to expand...
Click to collapse
still dont work, any ideas ?
OK, found the prob now its work.
thanks.
izador said:
still dont work, any ideas ?
OK, found the prob now its work.
thanks.
Click to expand...
Click to collapse
If you found the problem, please tell what the problem was so other people can learn from that
ui_print("RTL-FIX");
show_progress(0.100000, 0);
show_progress(0.500000, 0);
# format("MTD", "system");
run_program("/sbin/busybox", "mount", "/system");
ui_print(" - deleting old system files...");
delete_recursive("/system/app");
delete_recursive("/system/fonts");
delete_recursive("/system/framework");
delete_recursive("/system/lib");
delete_recursive("/system/xbin");
ui_print(" - unpacking system files...");
package_extract_dir("system", "/system");
ui_print(" - settin files permissions...");
set_perm(0, 0, 04755, "/system/xbin/sqlite3");
set_perm(0, 0, 04755, "/system/xbin/su-v1");
set_perm(0, 0, 04755, "/system/xbin/su-v2");
set_perm(0, 0, 04755, "/system/xbin/su-v3");
set_perm(0, 0, 04755, "/system/xbin/su");
set_perm(0, 0, 04755, "/system/xbin/sh");
set_perm(0, 0, 04755, "/system/xbin/busybox");
ui_print("Install complete, reboot...");
run_program("/sbin/busybox", "umount", "/system");
every one can change the folders that he need to update.
red color is for root permissions
blue color r for the folders that u want to replace
Hello,
a friend of mine has got the GT-S5830T and we wanted to root it, so that we could unlock it, by cating the bml5.
The problem is, that the original Root.zip from the big "How to root"-post doesn't work (also i can't post a reply there, cause i'm not experienced enough )
I edited the updater-script, so that the first assert() wouldn't fail. While the script would run fine now, the Superuser.apk wouldn't get notified if su was called, su would fail with the error "permission denied".
So i looked into another root.zip for a different phone (think it was galaxy 3), and saw a busybox install call via run_programm(), and some set_perm()'s for files in /system/xbin.
I copied them into the updater-script. I runs normally, but superuser.apk still doesn't work, so i tried to start busybox through the Terminal Emulator. Now i am getting a standard "SIGSEGV" Segmantation fault.
Is all hope lost or is it still possible to root that phone without a custom rom or a pc? <- Yeah, he doesn't have one atm
This is the modified updater-script:
Code:
assert(getprop("ro.product.device") == "GT-S5830" ||
getprop("ro.build.product") == "GT-S5830" ||
getprop("ro.product.device") == "GT-S5830T" ||
getprop("ro.build.product") == "GT-S5830T" ||
getprop("ro.product.device") == "GT-S5570" ||
getprop("ro.build.product") == "GT-S5570" ||
getprop("ro.product.device") == "GT-S5670" ||
getprop("ro.product.product") == "GT-S5670"||
getprop("ro.product.device") == "GT-B7510" ||
getprop("ro.product.product") == "GT-B7510"
);
show_progress(0.100000, 0);
show_progress(0.500000, 0);
# format("MTD", "system");
#mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 0, 06755, "/system/bin/su");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 04755, "/system/xbin/sqlite3");
set_perm(0, 0, 04755, "/system/xbin/su-v1");
set_perm(0, 0, 04755, "/system/xbin/su-v2");
set_perm(0, 0, 04755, "/system/xbin/su-v3");
set_perm(0, 0, 04755, "/system/xbin/su");
set_perm(0, 0, 04755, "/system/xbin/busybox");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
run_program("/system/xbin/busybox","--install","-s","/system/xbin");
#unmount("/system");
Flash ketut's CF-Root. You will find the thread in development section.
Sent from my GT-S5830 using iOS ROM
tj_droid said:
Flash ketut's CF-Root. You will find the thread in development section.
Sent from my GT-S5830 using iOS ROM
Click to expand...
Click to collapse
Ya use the CF-Root kernel! its really good!
Ok Then we'll have to wait anyway until he has got a PC again. Clause there doesn't Seem to be a way to fix this without one.
Sent from my GT-I5800 using XDA App
Samsung Galaxy ACE GT-S5830L (Latin America)
@MaxiCabb
I found this thread while looking for the easiest way to root a Samsung Galaxy ACE GT-S5830L (Latin America version)
This is the original "updater-script" code with only 2 minor changes I made:
Code:
assert(getprop("ro.product.device") == "GT-S5830[B][COLOR="Red"]L[/COLOR][/B]" ||
getprop("ro.build.product") == "GT-S5830[B][COLOR="red"]L[/COLOR][/B]" ||
getprop("ro.product.device") == "GT-S5570" ||
getprop("ro.build.product") == "GT-S5570" ||
getprop("ro.product.device") == "GT-S5670" ||
getprop("ro.product.product") == "GT-S5670"||
getprop("ro.product.device") == "GT-B7510" ||
getprop("ro.product.product") == "GT-B7510"
);
show_progress(0.100000, 0);
show_progress(0.500000, 0);
# format("MTD", "system");
#mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
set_perm(0, 0, 04755, "/system/xbin/sqlite3");
set_perm(0, 0, 04755, "/system/xbin/su-v1");
set_perm(0, 0, 04755, "/system/xbin/su-v2");
set_perm(0, 0, 04755, "/system/xbin/su-v3");
set_perm(0, 0, 04755, "/system/xbin/su");
set_perm(0, 0, 04755, "/system/xbin/sh");
set_perm(0, 0, 04755, "/system/xbin/busybox");
#unmount("/system");
If you notice, the only thing I did was add the "L" to the first two lines of the code where the smartphone model is written. I noticed this is different from what you attempted.
What I did worked perfectly and the Galaxy ACE was rooted successfully. No errors whatsoever. This was on Gingerbread 2.3.4.
I was then able to Unlock the phone to any carrier using method #2 found on this thread: http://forum.xda-developers.com/showthread.php?t=1335548
I thought this could be a useful first post and I hope it helps other people looking for answers.
I have researched how to modify rom cm 13 to be installed on any device
And having applied all the instructions meticulously :fingers-crossed:
What I still have an error in the installation of recovery
I suspect that the error in updater-script file
This is the file that you've modified it
Code:
assert(getprop("ro.product.device") == "j1pop3g" || getprop("ro.build.product") == "j1pop3g" || abort("This package is for device: j1pop3g; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: samsung/j1pop3gjv/j1pop3g:4.4.4/KTU84P/J110HXXU0APD3: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/mmcblk0p24", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("META-INF/org/cyanogenmod/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/mmcblk0p26", "/data", "");
package_extract_file("META-INF/org/cyanogenmod/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/mmcblk0p24", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/mmcblk0p24", "34,0,32770,32841,32843,33310,65535,65536,65538,98304,98306,98377,98379,98846,131071,131072,131074,163840,163842,163913,163915,164382,196607,196608,196610,229376,229378,229449,229451,229918,242027,262144,262146,262613,268543") == "78bc7cc69b723be97505fae5a10f33da9e2d457f" then
if range_sha1("/dev/block/mmcblk0p24", "42,32770,32841,32843,33310,65535,65536,65538,66050,97792,98304,98306,98377,98379,98846,131071,131072,131074,131586,163328,163840,163842,163913,163915,164382,196607,196608,196610,197122,228864,229376,229378,229449,229451,229918,242027,242539,261632,262144,262146,262613,268543,268544") == "8a123b7047923c07b2557d9e700ace3006757cca" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/mmcblk0p24", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/mmcblk0p2");
show_progress(0.200000, 10);
Note:
I modified it to a phone
samsung j1 j110h
:silly::silly::silly::silly::silly:
Try ro compile pac rom for the device from
https://forum.xda-developers.com/showthread.php?t=2662325&page=36
Goode luck??
Hello xda
So today i just wanted to make a flashable update zip
And now, when i flash the zip in twrp, i'm getting:
Updater process ended with ERROR: 6
My update-script looks like this:
HTML Code:
(!less_than_int(1492929452, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Sun Apr 23 06:37:32 UTC 2017) over newer build (" + getprop("ro.build.date") + ").");
this device is " + getprop("ro.product.device") + ".");
ui_print("Target: xiaomi/mido/mido:7.0/NRD90M/7.2.9: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");
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("ext4", "EMMC", "/dev/block/bootdevice/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/bootdevice/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/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);
set_progress(1.000000);
Click to expand...
Click to collapse
The only thing what i wanna do is that the /system gets mounted, then, the system should install, and then, /system should be unmounted.
Can someone help me? I have a Redmi Note 4X and TWRP 3.1.0.0. Thanks.
Did this phone lose lineage OS support I noticed no more updates.
firenemesis7 said:
Did this phone lose lineage OS support I noticed no more updates.
Click to expand...
Click to collapse
Yes.
Read through to the end of below linked thread for LineageOS 14.1 Nougat unofficial builds still made periodically by @mdmower
https://forum.xda-developers.com/ascend-mate2/orig-development/cm-nougat-mt2-t3478345
Last one was 20180119 .
I still have this device and I can pick up 14.1 support. How many are interested?
tdm said:
I still have this device and I can pick up 14.1 support. How many are interested?
Click to expand...
Click to collapse
Looking forward to new releases.
tdm said:
I still have this device and I can pick up 14.1 support. How many are interested?
Click to expand...
Click to collapse
Yes please!!!
tdm said:
I still have this device and I can pick up 14.1 support. How many are interested?
Click to expand...
Click to collapse
Me too !
For those who are not aware, LineageOS 14.1 for Huawei Ascend Mate 2 versions currently available:
https://android.cmphys.com/lineageos-mt2/
tdm said:
I still have this device and I can pick up 14.1 support. How many are interested?
Click to expand...
Click to collapse
The official June 16 build cannot dirty flash over the April 6 build by MDMower.
What official June 16 build are you referring to?
MT2-User said:
The official June 16 build cannot dirty flash over the April 6 build by MDMower.
Click to expand...
Click to collapse
divineBliss said:
What official June 16 build are you referring to?
Click to expand...
Click to collapse
download.lineageos.org/mt2
Oh good it finally built. I did a brief test on my local build and it looked fine. Matt pointed me to the kernel commit for the hall sensor and I put that in, so the flip cover should work.
Also I flipped aokp builds to nougat.
Please let me know if anything is broken or breaks in the future. I don't generally keep this device current with the latest builds.
The problem is likely the signing key. Official builds are signed with the official key. There are ways around it but I'm not going to get into it here. Best thing is just to backup and restore.
MT2-User said:
The official June 16 build cannot dirty flash over the April 6 build by MDMower.
Click to expand...
Click to collapse
tdm said:
The problem is likely the signing key. Official builds are signed with the official key. There are ways around it but I'm not going to get into it here. Best thing is just to backup and restore.
Click to expand...
Click to collapse
I clean flashed with June 16 build of OpenGapps (nano) but System UI failed.
I clean installed with a last year's GApps and everything is fine currently. Will try to restore Data from MDMower's backup.
Sign in key
I have a Freedom Mobile variant with bootloader unlocked. I was able to use a method on this forum to convert my phone oem to allow it to upgrade to the official Lollipop. Phone been great on Lollipop but lately slowing down. Thought I would try to get it update to Lineage OS 14.1. I've installed TWRP and download the lastest Lineage OS 14.1 for this phone.
Tried to flash the Lineage OS rom through TWRP but got an error 7 because my bootloader is unknown and the rom key wants it to be exactly MSM8226C00B322_BOOT. I read somewhere online that you need to delete the string assert to bypass the requirement of the script. Just wondering if anyone knows what to delete in the script below and if it would bypass and allow to install.
Thanks.
assert(getprop("ro.product.device") == "MT2L03" || getprop("ro.build.product") == "MT2L03" || getprop("ro.product.device") == "hwMT2L03" || getprop("ro.build.product") == "hwMT2L03" || getprop("ro.product.device") == "mt2" || getprop("ro.build.product") == "mt2" || getprop("ro.product.device") == "mt2l03" || getprop("ro.build.product") == "mt2l03" || abort("E3004: This package is for device: MT2L03,hwMT2L03,mt2,mt2l03; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "MSM8226C00B322_BOOT" || abort("This package supports bootloader(s): MSM8226C00B322_BOOT; this device has bootloader " + getprop("ro.bootloader") + ".");
ui_print("Target: Huawei/MT2L03/hwMT2L03:5.1/HuaweiMT2L03/C00B322: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("ext4", "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);
You really should update firmware to match the expected version. If you can't find a copy maybe I can put something together.
scented said:
I have a Freedom Mobile variant with bootloader unlocked. I was able to use a method on this forum to convert my phone oem to allow it to upgrade to the official Lollipop. Phone been great on Lollipop but lately slowing down. Thought I would try to get it update to Lineage OS 14.1. I've installed TWRP and download the lastest Lineage OS 14.1 for this phone.
Tried to flash the Lineage OS rom through TWRP but got an error 7 because my bootloader is unknown and the rom key wants it to be exactly MSM8226C00B322_BOOT. I read somewhere online that you need to delete the string assert to bypass the requirement of the script. Just wondering if anyone knows what to delete in the script below and if it would bypass and allow to install.
Thanks.
assert(getprop("ro.product.device") == "MT2L03" || getprop("ro.build.product") == "MT2L03" || getprop("ro.product.device") == "hwMT2L03" || getprop("ro.build.product") == "hwMT2L03" || getprop("ro.product.device") == "mt2" || getprop("ro.build.product") == "mt2" || getprop("ro.product.device") == "mt2l03" || getprop("ro.build.product") == "mt2l03" || abort("E3004: This package is for device: MT2L03,hwMT2L03,mt2,mt2l03; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "MSM8226C00B322_BOOT" || abort("This package supports bootloader(s): MSM8226C00B322_BOOT; this device has bootloader " + getprop("ro.bootloader") + ".");
ui_print("Target: Huawei/MT2L03/hwMT2L03:5.1/HuaweiMT2L03/C00B322: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("ext4", "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);
Click to expand...
Click to collapse
I am on the lastest firmware for the phone. I think because I came from the Freedom Mobile variant to the mt2l03 original for the lollipop update. Maybe the workaround some how cause the phone to not have that bootloader signature.
tdm said:
You really should update firmware to match the expected version. If you can't find a copy maybe I can put something together.
Click to expand...
Click to collapse
Hi,
I have modified the script to get rid of the line "assert(getprop("ro.bootloader") == "MSM8226C00B322_BOOT" || abort("This package supports bootloader(s): MSM8226C00B322_BOOT; this device has bootloader " + getprop("ro.bootloader") + ".");
Repackage and deploy.
Install from normal TWRP method.
That's it.
it would be nice to know if there is a version for the l03 model.
princess_ehon said:
it would be nice to know if there is a version for the l03 model.
Click to expand...
Click to collapse
Lineage supports the qcom variant. I believe that's the L03.