I get a failure when trying to flash a new ROM. I have three different zips (ROMs) on my phone. None of them will install for some reason and I get a failed error and it puts something about an error when updating binary script? How could I fix this on my nexus 4?
If I need to update twrp could I do so without using goomanager to do this? Goomanager won't download the recovery so I have to use another method
You probably need to update to the latest TWRP version. Use the TWRP link in my signature and get the latest version in the "mako" folder.
Use fastboot to flash it, use the command:
fastboot flash recovery twrp.img
(replacing twrp.img with actual file name)
If you don't know how to use fastboot, use the 3rd link for guide on installing custom recoveries.
dreammaster252 said:
I get a failure when trying to flash a new ROM. I have three different zips (ROMs) on my phone. None of them will install for some reason and I get a failed error and it puts something about an error when updating binary script? How could I fix this on my nexus 4?
If I need to update twrp could I do so without using goomanager to do this? Goomanager won't download the recovery so I have to use another method
Click to expand...
Click to collapse
had the same error and resolved it like this:
installed ROM Installer vom play store
installed cwm, and then twrp again from rom installer.. worked perfectly!
BUT WHATCH OUT! i think the error you get is called "error 9".. or something like that, it appears, when you try to install a zip, and the updater-skripts cancels the installation process, e.g., because it is not hte right zip for your phone!
so look at first, if you have the right zip downloaded
Yesterday i got a notification that my KitKat update is ready. I downloaded it restarted the phone as required but the process failed with the below error
/system/lib/hw/power.msm8960.so has unexpected contents
Downloaded the zip file and tried to flash it via TWRP and again got the same error.
Could anybody please let me know the fix. I am rooted with franco kernel r#193
Is the file modified?
Suman_Auddy said:
Yesterday i got a notification that my KitKat update is ready. I downloaded it restarted the phone as required but the process failed with the below error
/system/lib/hw/power.msm8960.so has unexpected contents
Downloaded the zip file and tried to flash it via TWRP and again got the same error.
Could anybody please let me know the fix. I am rooted with franco kernel r#193
Click to expand...
Click to collapse
Just make sure that you have not modified that file.
Also some people had the same issue and it turned out that they had the file renamed to power.msm8960.so.bak, if so
use a file explorer to rename it back to the original (without .bak), and if that still fails, download the file from the factory image and replace it, then try to flash the zip file.
Suman_Auddy said:
Yesterday i got a notification that my KitKat update is ready. I downloaded it restarted the phone as required but the process failed with the below error
/system/lib/hw/power.msm8960.so has unexpected contents
Downloaded the zip file and tried to flash it via TWRP and again got the same error.
Could anybody please let me know the fix. I am rooted with franco kernel r#193
Click to expand...
Click to collapse
same here but i have "framework-res.apk" has unexpected contents.
In order to use OTA, your system files should be stock and unmodified and it looks like you modified that file, my suggestion, is to download the factory image of your current build of 4.3 from here
https://developers.google.com/android/nexus/images#occam
check what version you have, mine was JWR66Y when I upgraded.
then extract the factory image on your desktop and copy and replace "any" file that you have modded (with TWRPs file manager + ADB), before flashing Kitkat OTA zip, (note: when replacing files make sure that system files you replace have the right permissions e.g. chmod 755)
OR you could flash the Kitkat factory image directly instead of the OTA, ONLY IF you know how to do so without wiping your device's data, remember that this can cause you problems later.
Be careful, I hope you had a nandriod backup, before this happened.
Thanks for all your sugeestions, renaming the file worked for me. Flashing the zip file now via TWRP.
Flashing the zip file failed with error error executing updater binary in zip....any suggestion
Suman_Auddy said:
Flashing the zip file failed with error error executing updater binary in zip....any suggestion
Click to expand...
Click to collapse
Please post the whole error message.
I am trying to flash an image onto a zenfone 5 using the recovery. I have tried sideloading and also pushing the zip to the SD card. It just seems to hand randomly.
I then tried checking the uploaded zip file (to /sdcard) by running md5um on it and the value changes each time I run md5sum. I have tried a few versions of the TWRP recovery and the all seem to have the same problem. Is there one that works?
I just rooted my friend's Zenfone 5 with an auto installer. Here's the link on google drive LINK . Just extract the zip and follow instructions in the "help file.txt". It's a script that automates all the commands. I don't remember where I got this from, but if someone else knows, please link the original for credits.
I've put together a guide for building your own LineageOS 17.1 (android 10) using a docker build environment or on your own system. The guide includes environment setup, and installation instructions as well as some troubleshooting and debugging information.
The easy way is as simple as cloning two git repos, getting the docker image, and running build_sargo.sh
The hard way goes into more detail, requires more previous knowledge, and doesn't use the docker but is useful for getting more familiar with the process.
The docker image is one that already existed for building lineageos 16modified to supports lineagsos 17.
It also includes patches that haven't been merged upstream yet that fix bluetooth, a bootloop, and increase battery life.
With some small modifications, this could also be used for the Pixel 3a XL (bonito)
https://github.com/SolidHal/Build-lineageos-sargo
Thanks for this!
Stealth111
SolidHal said:
I've put together a guide for building your own LineageOS 17.1 (android 10) using a docker build environment or on your own system. The guide includes environment setup, and installation instructions as well as some troubleshooting and debugging information.
The easy way is as simple as cloning two git repos, getting the docker image, and running build_sargo.sh
The hard way goes into more detail, requires more previous knowledge, and doesn't use the docker but is useful for getting more familiar with the process.
The docker image is one that already existed for building lineageos 16modified to supports lineagsos 17.
It also includes patches that haven't been merged upstream yet that fix bluetooth, a bootloop, and increase battery life.
With some small modifications, this could also be used for the Pixel 3a XL (bonito)
https://github.com/SolidHal/Build-lineageos-sargo
Click to expand...
Click to collapse
There should be VERY little modification required from sargo to bonito as one is simply a different size than the other. (I'm actually surprised that nobody ever compared the two in terms of hardware (especially since their simultaneous release).
I have built pure lineageos 17 according to https://forum.xda-developers.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063
The esim manager has to be disabled or you have to stop enforcing SELinux.
Download:
https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
anonym12 said:
I have built pure lineageos 17 according to https://forum.xda-developers.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063
The esim manager has to be disabled or you have to stop enforcing SELinux.
Download:
https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
Click to expand...
Click to collapse
If you include gapps in your build, the esim manager should stop crashing. If running gappless, I remove esim and hotword enrollment from the proprietary files.
gee one said:
If you include gapps in your build, the esim manager should stop crashing. If running gappless, I remove esim and hotword enrollment from the proprietary files.
Click to expand...
Click to collapse
Hello!
I have also built & installed lineageos 17 according to the guide above, thanks!
Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
spinxen said:
Hello!
I have also built & installed lineageos 17 according to the guide above, thanks!
Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
Click to expand...
Click to collapse
The issue is the new dynamic partition scheme doesn't leave enough room to install any extra system apps. There is a patch on the Lineage Gerrit, but it hasn't been merged (https://review.lineageos.org/c/LineageOS/android_device_google_bonito/+/261941).
fireclaw722 said:
The issue is the new dynamic partition scheme doesn't leave enough room to install any extra system apps. There is a patch on the Lineage Gerrit, but it hasn't been merged (https://review.lineageos.org/c/LineageOS/android_device_google_bonito/+/261941).
Click to expand...
Click to collapse
Thanks for letting me know, so as of now there is no workaround to get GApps work with this branch after it has been installed?
spinxen said:
Thanks for letting me know, so as of now there is no workaround to get GApps work with this branch after it has been installed?
Click to expand...
Click to collapse
Not that I know of. You either have to create space for G-Apps, or bundle G-Apps with the ROM.
spinxen said:
Hello!
I have also built & installed lineageos 17 according to the guide above, thanks!
Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
Click to expand...
Click to collapse
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
gee one said:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
Click to expand...
Click to collapse
Would you mind to share your zip? Thanks!
spinxen said:
Would you mind to share your zip? Thanks!
Click to expand...
Click to collapse
https://opengapps.org/
anonym12 said:
I have built pure lineageos 17 according to https://forum.xda-developers.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063
The esim manager has to be disabled or you have to stop enforcing SELinux.
Download:
https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
Click to expand...
Click to collapse
gee one said:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
Click to expand...
Click to collapse
This is somewhat above my level of knowledge, if you have a complete build zip with Gapps, do u mind sharing this with me?
How to install?
LioneageOS 17.1 for Poxel 3a: Notes from the front
gee one said:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
Click to expand...
Click to collapse
Because of the issues, I have stuck with those versions that include GApps (invisiblek's simple LineageOS 17.1 works a treat, and is cloneable for those looking to build their own). Until beta 3 of Android 11 drops, I'm running this. Still no TWRP, or root, or anything else. Other than Pixel Launcher, I'm basically running stock Lineage.
Hi guys,
Just built my own image according to the 'easy' method (using docker). Took about 5 hours, and seemed to have gone well, almost no errors
I started out by flashing the Pixel 3a with the lastest Android 10 Factory Image from Google (QQ2A.200305.002, Mar 2020) to be sure it's as clean as possible. Booted into Android 10 once, enabled Developer Settings et cetera.
Then followed the 'Install' steps from https://github.com/SolidHal/Build-lineageos-sargo:
- boot into bootloader (fastboot mode)
- run 'fastboot flash boot boot.img'
- reboot into recovery -> Apply update -> Apply from ADB -> run 'adb sideload lineage-17.1-20200404-UNOFFICIAL-sargo.zip' (in my case)
When entering recovery mode I noticed an error at the botton of the screen: 'E:[libfs_mgr]Failed to mount /data: Invalid argument'. Despite that I could continue and sideload/install my self built lineageos zip, which finished without error (status 0). After installation the phone went back to into recovery mode (as described on the Github guide). Unfortunately, when I continued and picked 'Reboot System Now' I got thrown into the bootloader with enter reason: 'error boot prepare'. Every time the phone boots I see this error now.
Does anybody have a clue what I could be doing wrong? Any help is appreciated, thanks!
Edit: Okay, seems my problem is solved. When flashing the self-built boot.img, in my case I also had to specify which boot part to flash to: boot_a or boot_b. After having done that, booting now works.
Thanks SolidHal for providing your docker file and making it easy to built your own LineageOS 17.1 image!
Working and Running Smoothly
Thanks for posting this.
I was also able to build and install this successfully using the easy method. Yes, it takes a long time and requires an ample amount of memory and storage.
The battery life is excellent compared to the other roms/kernels I've tested so far. Started with a factory flash of Android 10.0.0 (QQ2A.200305.002, Mar 2020) (https://developers.google.com/android/ota). Then I followed the instructions here.
I also had the E:[libfs_mgr] error but it still installed correctly after the second try. Specifying boot_a or boot_b may have been what got this to work for me. Thanks to P1x3l3d.
Rooted by patching the boot image with Magisk (https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783).
P1x3l3d said:
Hi guys,
Just built my own image according to the 'easy' method (using docker). Took about 5 hours, and seemed to have gone well, almost no errors
I started out by flashing the Pixel 3a with the lastest Android 10 Factory Image from Google (QQ2A.200305.002, Mar 2020) to be sure it's as clean as possible. Booted into Android 10 once, enabled Developer Settings et cetera.
Then followed the 'Install' steps from https://github.com/SolidHal/Build-lineageos-sargo:
- boot into bootloader (fastboot mode)
- run 'fastboot flash boot boot.img'
- reboot into recovery -> Apply update -> Apply from ADB -> run 'adb sideload lineage-17.1-20200404-UNOFFICIAL-sargo.zip' (in my case)
When entering recovery mode I noticed an error at the botton of the screen: 'E:[libfs_mgr]Failed to mount /data: Invalid argument'. Despite that I could continue and sideload/install my self built lineageos zip, which finished without error (status 0). After installation the phone went back to into recovery mode (as described on the Github guide). Unfortunately, when I continued and picked 'Reboot System Now' I got thrown into the bootloader with enter reason: 'error boot prepare'. Every time the phone boots I see this error now.
Does anybody have a clue what I could be doing wrong? Any help is appreciated, thanks!
Edit: Okay, seems my problem is solved. When flashing the self-built boot.img, in my case I also had to specify which boot part to flash to: boot_a or boot_b. After having done that, booting now works.
Thanks SolidHal for providing your docker file and making it easy to built your own LineageOS 17.1 image!
Click to expand...
Click to collapse
Did you build in Linux? If so, which version? (I'm not used to building Docker - and especially in Linux - and I'd rather do it right; therefore WHICH version of Linux has everything to do it right is critical.)
PGHammer, I don't think it's going to matter too much what distro you use because you're going to have to install the latest platform-tools and install docker from a repo anyways. Just use something recent. Ubuntu comes to mind if you're not a huge GNU/Linux guy.
I built using Debian Stretch and had no issues other than my ram got all used up so I had to create more swap and add
vm.swappiness=60 to /etc/sysctl.conf
You need 100+GB HDD, 16GB+ RAM, and a fat swap space (I used a 20GB Swap file)
Also someone (anon12?) already posted a ~700MB zip of their build in this thread and I can confirm it works.
barqs_root said:
Also someone (anon12?) already posted a ~700MB zip of their build in this thread and I can confirm it works.
Click to expand...
Click to collapse
How did you you get this to install, I get signature verification failed, error:21. Then abd aborts the installation. I confirmed the integrity of the images with the provided checksum files. I even downgraded back to February's update because I was on Aprils update and thought that maybe that was the issues.
The steps I did are as follows:
Unlock bootloader
Enable debugging
Booting into the boot loader- run ./fastboot flash boot_a boot.img( ./ before is required due to being stuck on windows while I work from home.) Successfully installs to boot_a in 2.5sec.
Booting to recovery
Wipe/factory reset
Apply update from ADB- ./adb sideload lineage-17.1-20200222-UNOFFICIAL-sargo.zip
This is the following errors
E: failed to verify whole-file signature
Update package verification took 35.0 s (result 1).
E: Signature verification failed
E: error: 21
Install from ADB completed with status 2.
Installation aborted.
Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.
honza1 said:
Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.
Click to expand...
Click to collapse
Hm ... unused device?
So it should be on stock firmware with original partition sizes.
Have you check to boot into stock recovery before?
Maybe there is something wrong with this "unused" device.
You can try to flash a recent stock firmware with original pit file to re-partition to stock partition sizes.
On windows pc use Odin for flashing.
When on stock Samsung firmware, try to flash twrp recovery again.