Unable to flash CM update - OnePlus 2 Q&A, Help & Troubleshooting

I've CM13 dated Dec 25 in my OnePlus 2. Nightly build from the below thread.
http://forum.xda-developers.com/oneplus-2/development/6-0-1-unofficial-cyanogenmod-13-0-t3270496
I am trying to update newer CM nightlies uploaded in that thread, but I am facing some problem while flashing.
This is what it says.
Install failed
--Install/data/media/0/cm-13.0-20160108-UNOFFICIAL-oneplus2.zip...
Finding update package...
Opening update package...
E:failed to map file
Installation aborted.
Tried downloading new CM13 file versions and flashing them. Still same error.
Tried flashing an altogether different custom ROM. Still same error.
Tried updating to TWRP recovery and flashed the ROM. Same error!!!
Tried to remove the assert verification for oneplus2 in updater binary script as suggested in some thread. Same error!
Tried both dirty flash as well as clean flash. Still same error!!! :crying:
I am stuck up somewhere. I do not know where and I could not find any solution online.
Can anyone help me out at the earliest?

You can stay on that version for a while since there's no development going on until maybe February or Mars when OnePlus supposedly is going to release Oxygen OS based off Marshmallow.
Skickat från min ONE A2003 via Tapatalk

Related

[Q] i9505 CM11 M8 no system updates

Hi all,
My device is i9505 (international) with CM11 installed (installed via windows installer).
For some reason it tells me that my device is up to date but it is obviously not. I tried installing the latest nightly via recovery (tried TWRP and CWM) but both gave me an error saying there is some kind of signature verification failed.
Does anyone know how to solve this problem?
Thanks in advance,
Nelson
Maybe the app shows only stable version as viable updates? I don't think nightlys are classified as stable.
As for the failed verification, try turning off zip signature verification. This is done from within the recovery.

Laser 2[ZE551KL] Stuck on Lollipop (Unlocked bootloader)

Hello team of professionals!
First, I thank you all for your hard work and development of this device!
I have an issue updating to the latest stock room from Asus.
I had CM13 (Android 6) installed on my Asus Zenfone 2 Laser (ZE551KL).
When I heard that stock marshmallow was released I was interested in installing the ROM.
I tried for several hours to install the update and ended up bricking my phone.
I recovered it by installing the most recent stock Lollipop firmware from Asus' website.
Currently my phone has stock Lollipop with the ROM (UL-Z00T-WW-1.17.40.1531-user)
and stock recovery (attempted to do this so I could upgrade from lollipop to marshmallow)
At this time I am trying to install the most recent (Android 6) update "UL-Z00T-WW-21.40.1220.1615-user.zip" Downloaded from my device's page on Asus' site however I get errors every time I try.
I tried to update via stock android by placing the update zip on my SD card and launching from "System update file detected" notification.
The update restarts my phone, starts installing (With the little android guy) and then fails with the error:
Code:
Can't install this M package (May 17 2015)
Code:
L less than 20160426 build (Dec 1 2015)
Code:
E:Error in /sdcard/updatefile.zip
Code:
(Status 7)
Code:
E: fota_return_code 409
Code:
Installation aborted(EUPDATE_BAD_PARMSE)
When attempting with TWRP:
Code:
Updater process ended with ERROR 7.
Error installing zip file "xxxxxxxxxxx.zip"
Any help would be appreciated
Can you post your build.prop (found /system ) here ? And what is "updatefile.zip" ? Did you renamed the fota (or OTA, as you call it) ?
would this be applicable?
http://forum.xda-developers.com/zen...ne-2-laser-t3399441/post67336853#post67336853

ERROR 3004 while installing any roms via twrp

Hello,
actually I have Xiaomi.eu rom with unlocked bootloader.
I'm trying to install a custom rom to have at least android 7 on my redmi 4 prime, but when I try to flash with twrp, I recive the following message:
E3004: This package is for device: Markw; this device is .
Updater process ended with ERROR: 7
Error installing zip file 'sdcard/…….zip'
I usually save the new rom in SDcard and then install it via twrp
I tried 2 different roms but with the same error.
Installing xiaomi.eu rom, I have no errors
Thanks for you help
BUMP - same here! I have the same problem while installing custom ROMS.
I had the same issue, you need a trebble recovery.
Try with this one. https://androidfilehost.com/?fid=890129502657599344

assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))

can anyone help me!
I get error "assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))"
on twrp when I tried to flash evolution x custom ROM on my poco m3. I thought there might be a problem with the rom so I tried flashing havoc os and the same error showed, I currently have miui 12 EU rom installed.
You have to flash an Android 11 firmware or rom (you can download it from here) before flashing any custom android 12 rom. I just fix it and hope it can be useful with your problem
This worked for me. Thanks a lot.

partition metadata has invalid geometry magic signature error during Lineage OS update.

I'm currently running Lineage OS 18.1 (18.1-20210421-NIGHTLY-gta4xlwifi). I also have Lineage OS recovery 18.1 (20210421) installed.
I'm trying to apply an update unsuccessfully. I've tried downloading a zip to my sd card and applying it using recovery. I receive the following error:
E:[liblp]Logical partition metadata has invalid geometry magic signature.
Quickly after this error it attempts to backup NikGapps and produces a different error:
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
E:Error in /sideload/package.zip (status 1)
I've tried downloading three different nightlys and obtain the same results.
I've also tried updating using the Settings app. Once it reboots into recovery the same error appears.
Can anyone tell me how I can correct this?
Thanks,
Bob
I just upgraded to the microG release from August 12th for this tablet and saw the same error. However, the update worked for me.
Sorry for not really helping, but I thought it's still worth mentionning.

Categories

Resources