[Concept] OEM Image flasher [AOSP on the Go] - Sony Cross-Device General

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 )

Related

[GUIDE] Fix status 6 while flashing ROMs

I assume at least half of Android users get Error status 6 while flashing ROMs. This can be explained in 2 reasons.
Number 1:The developer of the ROM was too stupid to fix this mistake
Click to expand...
Click to collapse
or
Number 2: You are tying to port a ROM and those errors come to you
Click to expand...
Click to collapse
So lets start fixing.
Extract the ROM. Open META-INF com google android and open with Notepad++ updater-scipt.
Find the line called mount("ext4", "EMMC", "/dev/block/some kind of Letters and Numbers ", "/system");
This command is telling the device to mount the system from a path. Each device has a different path.
The path is those some kind of letters and numbers up bellow.
Those numbers and letters are different for every device.
So maybe the letters are not correct and it can't find the path to mount the data.
What we need to do is change the path. For the path that is for your device.
Easiest way to do this is to find a ROM meant and tested for your device, open updater-script, got to the same line and replace the path.
Example change mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system"); to mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
Click to expand...
Click to collapse
You may also find these two lines
format("ext4", "EMMC", "/dev/block/some kind of letters and numbers", "0", "/system");
mount("ext4", "EMMC", "/dev/block/some kind of letters and numbers", "/system");
The first line is telling the device to format the data.
The second line is telling the device to mount the data
The error is similar to the error up.
You need to change the path for the data
But the path for the data is different for the path for the system
So go to the same path on the ROM for your device and change the code
But remember the codes for the data and for the system are not the same.
Example Change format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0", "/system"); and
mount("ext4", "EMMC", "/dev/block/mmcblk0p29", "/system"); to format("ext4", "EMMC", "/dev/block/mmcblk0p20", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p20", "/system");
Click to expand...
Click to collapse
And the errors should be fixed.
Post a reply there is still an error.
Leave a tnx or donate if I helped.
i've tried your solution for the cm7.2 rc3 aa-oc-firekernel rom for Galaxy Ace.
After having a status 7 error i removed the lines containing assert... etc.
now I'm gettin the status 6 error and i've modified the format and mount lines.
I've looked in 2 similar roms which can be flashed (one of 'm is my current rom).
the other one is the rom i've used before, so both work.
these roms start as follows:
Code:
format("ext4", "EMMC", "/dev/block/stl12", "0");
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
package_extract_dir("system", "/system");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
the update-script from the rom I'd like to flash starts like this:
Code:
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/stl12", "0");
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
package_extract_dir("recovery", "/system");
package_extract_dir("system", "/system");
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
a bit different but the format and mount lines are indentical.
I can't figure out why I'm keep getting this status 6 error.
can you help me with it?
DutchArjo said:
i've tried your solution for the cm7.2 rc3 aa-oc-firekernel rom for Galaxy Ace.
After having a status 7 error i removed the lines containing assert... etc.
now I'm gettin the status 6 error and i've modified the format and mount lines.
I've looked in 2 similar roms which can be flashed (one of 'm is my current rom).
the other one is the rom i've used before, so both work.
these roms start as follows:
Code:
format("ext4", "EMMC", "/dev/block/stl12", "0");
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
package_extract_dir("system", "/system");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
the update-script from the rom I'd like to flash starts like this:
Code:
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/stl12", "0");
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
package_extract_dir("recovery", "/system");
package_extract_dir("system", "/system");
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
a bit different but the format and mount lines are indentical.
I can't figure out why I'm keep getting this status 6 error.
can you help me with it?
Click to expand...
Click to collapse
if you get a Status 7 error then you have to flash the rom using different recovery.
hope I helped, if yes then plz hit the thx button.:good:
i'm getting Status 6 error with this
Code:
assert(getprop("ro.product.device") == "mako" || getprop("ro.build.product") == "mako" || abort("E3004: This package is for device: mako; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: google/occam/mako:7.1/NDE63X/2167285: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/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("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/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/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);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
ui_print("flashing substratum");
package_extract_file("Substratum.apk", "/system/app/Substratum/Substratum.apk");
set_perm_recursive(0, 0, 0644, "/system/app/Substratum/Substratum.apk");
set_perm_recursive(0, 0, 0644, "/system/build.prop");
unmount("/system");
set_progress(1.000000);
i just added extra flashing process..
placed files in zip but getting error
i added extra lines from here
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
ui_print("flashing substratum");
package_extract_file("Substratum.apk", "/system/app/Substratum/Substratum.apk");
set_perm_recursive(0, 0, 0644, "/system/app/Substratum/Substratum.apk");
set_perm_recursive(0, 0, 0644, "/system/build.prop");
unmount("/system");
set_progress(1.000000);
please reply asap..

Unsupported bootloader for Blisspoprom 4.0 - T530

Hello everyone!
After finally figuring out how to boot into TWRP on the norwegian version of this device, I was crazy with exitement about flashing blisspoprom, but I get this error message:
This package supports bootloader (s) T530XXU1B0D8, T530NUUEU1B0E5; this device has bootloader T530XXU1B0G2
I have flashed a lot of devices, but I haven't really looked into bootloaders., as I've never encountered this problem before.
Is it possible to replace the bootloader on my device at all? Or are there version of the ROM out there that supports my bootloader?
N00b questions, indeed, but it's proven quite hard to find information on google searches on this subject, and everything I've found seems to be device specific. I tried to flash stock with bootloader update checked in Odin, but that didnæt change the bootloader number...
Open the rom file in 7zip or WinRar, go to META-INF/com/Google/Android and open the updater-script with notepad++. Delete the first line of the updater-script (it should have the word "assert" in it ". Save it and now try flashing the rom
thisisapoorusernamechoice said:
Open the rom file in 7zip or WinRar, go to META-INF/com/Google/Android and open the updater-script with notepad++. Delete the first line of the updater-script (it should have the word "assert" in it ". Save it and now try flashing the rom
Click to expand...
Click to collapse
Thank you sir! Much appreciated.
I got the file open in Notepad, would it be awfully blunt of me to ask you how much of this I need to delete? There's two lines starting with "assert" so I thought It would be safest to ask.
"assert(getprop("ro.product.device") == "matissewifi" || getprop("ro.build.product") == "matissewifi" || abort("This package is for device: matissewifi; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "T530XXU1BOD8" || getprop("ro.bootloader") == "T530NUUEU1BOE5" || abort("This package supports bootloader(s): T530XXU1BOD8, T530NUUEU1BOE5; this device has bootloader " + getprop("ro.bootloader") + ".");
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);
....
MadBigMadBoatMan said:
Thank you sir! Much appreciated.
I got the file open in Notepad, would it be awfully blunt of me to ask you how much of this I need to delete? There's two lines starting with "assert" so I thought It would be safest to ask.
"assert(getprop("ro.product.device") == "matissewifi" || getprop("ro.build.product") == "matissewifi" || abort("This package is for device: matissewifi; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "T530XXU1BOD8" || getprop("ro.bootloader") == "T530NUUEU1BOE5" || abort("This package supports bootloader(s): T530XXU1BOD8, T530NUUEU1BOE5; this device has bootloader " + getprop("ro.bootloader") + ".");
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);
....
Click to expand...
Click to collapse
Delete the following:
"assert(getprop("ro.product.device") == "matissewifi" || getprop("ro.build.product") == "matissewifi" || abort("This package is for device: matissewifi; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "T530XXU1BOD8" || getprop("ro.bootloader") == "T530NUUEU1BOE5" || abort("This package supports bootloader(s): T530XXU1BOD8, T530NUUEU1BOE5; this device has bootloader " + getprop("ro.bootloader") + ".");
Click to expand...
Click to collapse
Leave everything beginning with package_extract_dir("install", '/tmp/install");
Also just making sure, you are using the latest version of BlissPop, correct? Located here, you want the one named BlissPop-v4.0.1-matissewifi-UNOFFICIAL-20150917-1958.zip (note you want the one dated 20150917, not the one dated 20150912).
Also I'd recommend using notepad++ rather than regular notepad, idk if that's absolutely necessary, just a recommendation
thisisapoorusernamechoice said:
Delete the following:
Leave everything beginning with package_extract_dir("install", '/tmp/install");
Also just making sure, you are using the latest version of BlissPop, correct? Located here, you want the one named BlissPop-v4.0.1-matissewifi-UNOFFICIAL-20150917-1958.zip (note you want the one dated 20150917, not the one dated 20150912).
Also I'd recommend using notepad++ rather than regular notepad, idk if that's absolutely necessary, just a recommendation
Click to expand...
Click to collapse
Flashing!
4.0 for now, didn't want to wait for another download. I'll try 4.0.1 if there's any hithches. And, regular notepad seems to have done the trick, I hadn't heard of ++ before but I'll check it out.

Hey Can I Get Some Help Please...

Ok, so I have a Samsung Galaxy S5 Verizon 6.0.1 rooted bootloader unlocked and I have removed the "asserts" from the updater-script for lineage os 14.1 and I still get error 7 can I get some help?
ui_print("Target: 1490201755");
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);
Lilon said:
Ok, so I have a Samsung Galaxy S5 Verizon 6.0.1 rooted bootloader unlocked and I have removed the "asserts" from the updater-script for lineage os 14.1 and I still get error 7 can I get some help?
ui_print("Target: 1490201755");
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);
Click to expand...
Click to collapse
It's probably something stupid I'm missing please help of possible.
Lilon said:
Ok, so I have a Samsung Galaxy S5 Verizon 6.0.1 rooted bootloader unlocked and I have removed the "asserts" from the updater-script for lineage os 14.1 and I still get error 7 can I get some help?
ui_print("Target: 1490201755");
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);
Click to expand...
Click to collapse
Flash this lineage14.1 klte. It works perfectly on G900V.
https://mirrorbits.lineageos.org/full/klte/20170920/lineage-14.1-20170920-nightly-klte-signed.zip
Tested by me.
enmanuel255 said:
Flash this lineage14.1 klte. It works perfectly on G900V.
https://mirrorbits.lineageos.org/full/klte/20170920/lineage-14.1-20170920-nightly-klte-signed.zip
Tested by me.
Click to expand...
Click to collapse
OK I'll try it out thanks
enmanuel255 said:
Flash this lineage14.1 klte. It works perfectly on G900V.
https://mirrorbits.lineageos.org/full/klte/20170920/lineage-14.1-20170920-nightly-klte-signed.zip
Tested by me.
Click to expand...
Click to collapse
OK so I tried but still didn't work...
Lilon said:
OK so I tried but still didn't work...
Click to expand...
Click to collapse
Well... The problem is not on the ROM is in your phone or recovery.
So. You tried to reinstall the official full firmware using the pit file.
https://www.androidfilehost.com/?fid=961840155545596807
re-unlock the bootloader and try again?
enmanuel255 said:
Well... The problem is not on the ROM is in your phone or recovery.
So. You tried to reinstall the official full firmware using the pit file.
https://www.androidfilehost.com/?fid=961840155545596807
re-unlock the bootloader and try again?
Click to expand...
Click to collapse
OK I'll try thanks man
Lilon said:
OK I'll try thanks man
Click to expand...
Click to collapse
I forget. You don't need to set pit file in odin3.
PIT file is include in the firmware.

error 6 twrp while flashing pixel rom

i'm using moto g4 plus and i want to flash PixelExperience_harpia-9.0-20190604-0631-OFFICIAL rom
it first showed error 7 and then i deleted the assert code
then i flashed and it showed error 6
i had accidentally wiped my whole internal storage along with back up file how do i restore it or how do i fix the error 6????? im using twrp pls tell i dont want my phone to get bricked
this is my current code of updater system.
this device is " + getprop("ro.product.device") + ".");
ui_print("Target: motorola/harpia/harpia:7.1.1/NPIS26.48-36-5/12:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
ui_print("----------------------------------------------");
ui_print(" Pixel Experience");
ui_print(" by jhenrique09");
ui_print("----------------------------------------------");
ui_print(" Android version: 9");
ui_print(" Build id: PQ3A.190605.003");
ui_print(" Build date: 20190604-0631");
ui_print(" Security patch: 2019-06-05");
ui_print(" Device: harpia");
ui_print("----------------------------------------------");
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", "/system");
unmount("/system");
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.br", "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", "/system");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/modem", "/firmware", "");
ui_print("Extracting modem firmware");
run_program("/sbin/sh", "/tmp/install/bin/extract_firmware.sh");
ui_print("Firmware extracted");
unmount("/firmware");
unmount("/system");
set_progress(1.000000);

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);

Categories

Resources