Failed to install "cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-bacon" - ONE Q&A, Help & Troubleshooting

An error occurred on my OPO while trying to update the ROM to "cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-bacon".
(Using TWRP 2.8.7.0)
TWRP log:
- script aborted: Package expects build fingerprint of
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL:user/release-keys or
- oneplus/bacon/A0001:5.1.1/LMY48Y/YOG7DAS2K1:user/release-keys;
- this device has
- oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R:user/release-keys.
-
- Error executing updater binary in zip '/sdcard/Download/COS 12.1/cm-bacon-d91bf047f5-to-cee4e8702d-signed.zip'
- Error flashing zip '/sdcard/Download/COS 12.1/cm-bacon-d91bf047f5-to-cee4e8702d-signed.zip'
Build info from Settings/About:
- Android Ver#: 5.1.1
- Model: A0001
- Cyanogen OS Version: 12.1-YOG4PAS3JL
- Build#: LMY48B
Build info from Buiild.Prop:
- ro.build.id=LMY48B
- ro.build.version.release=5.1.1
- ro.build.host=cyanogenmod
- ro.product.brand=oneplus
- ro.product.name=bacon
- ro.build.product=A0001
- ro.build.fingerprint=oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL:user/release-keys
- ...
So the installed version is:
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL
And not as TWRP misidentified:
- oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R
The bottom line - can't install "cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-bacon"!
Any idea how to fix that problem?

I am getting same error while flashing the latest OTA zip, I think it has something to do with Twrp's 2.8.7.0. I'll try again with 2.8.6.0 as Sultan also recommended that.

usman.aaman said:
I am getting same error while flashing the latest OTA zip, I think it has something to do with Twrp's 2.8.7.0. I'll try again with 2.8.6.0 as Sultan also recommended that.
Click to expand...
Click to collapse
Thanks!
Your suggestion helped me solving my problem.
I flashed TWRP 2.8.7.0.5 (the newest version).
Steps to install the new ROM -
1. Backup your Data (Titanium backup or other)
2. reboot to Recovery
3. Wipe cache/dalvik cache/data/system
4. reboot back to Recovery
5. Install the newer ROM
6. reboot to System
7. Finish installation process
8. Restore your Data (Titanium backup or other)
The original issue probably occurred due to TWRP 2.8.7.0 bug.
The issue is solved.

AmnonD said:
Thanks!
Your suggestion helped me solving my problem.
I flashed TWRP 2.8.7.0.5 (the newest version).
Steps to install the new ROM -
1. Backup your Data (Titanium backup or other)
2. reboot to Recovery
3. Wipe cache/dalvik cache/data/system
4. reboot back to Recovery
5. Install the newer ROM
6. reboot to System
7. Finish installation process
8. Restore your Data (Titanium backup or other)
The original issue probably occurred due to TWRP 2.8.7.0 bug.
The issue is solved.
Click to expand...
Click to collapse
You're welcome.
Where did you find 2.8.7.0.5 ?
Can you link me there?
Thanks.

usman.aaman said:
You're welcome.
Where did you find 2.8.7.0.5 ?
Can you link me there?
Thanks.
Click to expand...
Click to collapse
I just Googled "TWRP 2.8.7.0.5".
Link:
https://www.androidfilehost.com/?fid=24269982087010524

I do not know why this version 2.8.7.0.5 worked, because the latest version is only 2.8.7.0, this "5" at the end it's probably because it has a theme installed.

The default.prop inside the TWRP (ramdisk) you used to flash the zip has the ro.build.fingerprint=oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R:user/release-keys
It always checks for build fingerprint in the default.prop inside the installed recovery rather than the build.prop in the installed OS, it maybe because they don't want users to flash the OTA over an incorrect ROM to avoid issues.
The default.prop inside the stock recovery always has the build fingerprint of the installed COS so that the future updates can be flashed over correct COS by checking the previous or the last 2 build fingerprints. After the update is flashed the CM recovery gets updated with the new build fingerprint and is ready for the next future updates.
This is just stupid, why not check the build.prop in the system so that users can use any recovery they want.
Stop forcing us to use everything that is CM -_-

TWRP 2.8.7.0 version has a kwnown bug and doesn't flash correctly firmware/modem. TWRP 2.8.6.0 works well and the themed version 2.8.7.0.5 seems to have the fix! Thats all!

Similar problem with TWRP 2.8.7.0.5!
Thank you all for your help!
Now I have a similar issue with TWRP 2.8.7.0.5!
I tried to flash CM-12.1-YOG7DAS2K1.
Current ROM on my OPO - CM-12.1-YOG4PAS3JL
Error details from the TWRP log:
script aborted:
Package expects build fingerprint of
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL:user/release-keys or
- oneplus/bacon/A0001:5.1.1/LMY48Y/YOG7DAS2K1:user/release-keys;
this device has
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS1N0:user/release-keys.​
Is it safe to modify the default.prop file?

Same here
AmnonD said:
Thank you all for your help!
Now I have a similar issue with TWRP 2.8.7.0.5!
I tried to flash CM-12.1-YOG7DAS2K1.
Current ROM on my OPO - CM-12.1-YOG4PAS3JL
Error details from the TWRP log:
script aborted:
Package expects build fingerprint of
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL:user/release-keys or
- oneplus/bacon/A0001:5.1.1/LMY48Y/YOG7DAS2K1:user/release-keys;
this device has
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS1N0:user/release-keys.​
Is it safe to modify the default.prop file?
Click to expand...
Click to collapse
Exactly same error here.
As TWRP has problems with OTA updates, I went back to stock recovery, but installation aborted again.
I have read it would work installing the zip of the fastboot file (cm-12.1-YOG4PAS3JL-bacon-signed-fastboot.zip) and then update via OTA the incremental using stock recovery.
I think I'll wait for the full file for TWRP installation

I succeeded to install the "cm-12.1-YOG4PAS3JL-bacon-signed" after System & Data wipe of previous ROM.
The problem is that TWRP doesn't identify the correct version. It claims that my OPO runs YOG4PAS1N0!
That is the reason for the YOG7DAS2K1 version installation failure.
I'll also wait for the full version.
Thanks.

Still not working, tried TWRP 2.8.6.0, 2.8.7.0, 2.8.7.0.5, and with all the OTA update fails.
Last I tried modifing the OTA by removing the fingerprint check (line 3 from updater-script), reflashed fastboot and did a reinstall with twrp 2.8.7.0, and it worked, system was patched successfully according to twrp, but later it was not bootable, stuck on the 1+ logo.
did a restore to older version, will wait for fastboot version.

Related

Stuck on "unlocked bootloader" after flashing SuperSU on MM

I flashed the following factory firmware image on my XT1541;
Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7
from here and followed the steps on this page to do so.
I updated to MM through OTA, flashed TWRP from here through fastboot, booted in to TWRP and flashed SuperSU v.2.65 from here.
I then reboot the phone and it gets stuck on the white "unlocked bootloader" screen.
I've repeated this process twice now, same thing. :/
Any ideas?
EDIT: I tryed flashing factory 5.1.1 through fastboot again, to get the phone working. But now I can't even do that.
When I enter "fastboot flash partition gpt.bin" I get the following error;
(bootloader) Preflash validation failed
FAILED (remote failure)
If you have a twrp backup from marshmallow, restore system. Then flash superSU 2.62-3 from here http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip.
SuperSU 2.65 don't detect properly the need to install it in systemless mode and try to install in system. V.2.62 is only systemless.
If you don't have the system backup, I don't know how to revert the modifications made by v. 2.65, but it's possible.
Good luck.
coolizard said:
If you have a twrp backup from marshmallow, restore system. Then flash superSU 2.62-3 from here http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip.
SuperSU 2.65 don't detect properly the need to install it in systemless mode and try to install in system. V.2.62 is only systemless.
If you don't have the system backup, I don't know how to revert the modifications made by v. 2.65, but it's possible.
Good luck.
Click to expand...
Click to collapse
Thank you. I did not have a backup, but I was able to flash factory 5.1.1 by skipping gpt.bin.
I then updated to MM through OTA, flashed TWRP and SuperSU v2.62-3.
Is there a reason why later versions of SuperSU do not install systemless on our phone and therefor cause the bootloop?
coolizard said:
If you have a twrp backup from marshmallow, restore system. Then flash superSU 2.62-3 from here http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip.
SuperSU 2.65 don't detect properly the need to install it in systemless mode and try to install in system. V.2.62 is only systemless.
If you don't have the system backup, I don't know how to revert the modifications made by v. 2.65, but it's possible.
Good luck.
Click to expand...
Click to collapse
I had a similar experience with v2.65. I know systemless root is experimental and all the current versions are beta. But I don't understand the reports from others indicating 2.65/2.65/2.67 work just fine on their G3. Is it possible that once 2.62-3 is installed, the later versions will flash properly?
Flash this supersu file , it will remove all latest binaries of supersu. And your phone will start.
https://download.chainfire.eu/204/SuperSU
Then flash supersu2.63 to root.
Astug said:
I flashed the following factory firmware image on my XT1541;
Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7
I updated to MM through OTA
Click to expand...
Click to collapse
Where did you find OTA for XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7? I've flashed this factory image but I haven't received OTA for this build and I haven't found an OTA file on Internet.
Could you share the OTA that you've used?
Osid said:
Where did you find OTA for XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7? I've flashed this factory image but I haven't received OTA for this build and I haven't found an OTA file on Internet.
Could you share the OTA that you've used?
Click to expand...
Click to collapse
Here.
I received the OTA on my phone though.
Astug said:
Here.
I received the OTA on my phone though.
Click to expand...
Click to collapse
The thread linked contains only MY OTA for XT1541 2GB.
Are you really sure that tour source build was LPI23-72.33 ?

Moto X Pure Edition XT1575 -- systemless root -- OTA updates fail

TWRP 3.0.2-0
SuperSu Pro 2.78
Android 6.0 Marshmallow build MPH24.49-18
I have systemless rooted my phone as per the instructions at http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
although, it didn't work without some tweaking... Unfortunately I don't remember what steps I took to get it working.
I am not sure of the process form here. Now that I have root, am I supposed to flash boot_orig.img permanently or just when I want to update?
I have tried:
fastboot flash boot boot_orig.img
but I loose wifi and can't download.
I have tried letting the OTA fail with the boot.img flashed, then reflashed with boot_orig.img and tried to install the update zip file via TWRP, but that fails.
I made a TWRP backup before I started rooting and for every major step after that, so I can start fresh if need be.
[EDIT]
I noticed on this thread, http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 , the following comment:
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with each other. The installer for this experiment will not clean up old root files.
- Flash stock /system (and /vendor and /oem, if present)
- Flash the attached boot image
- Flash the attached SuperSU ZIP in TWRP
Click to expand...
Click to collapse
Could this be the problem? If so, How do I "flash stock /system (and /vendor and /oem, if present)"?
Any help appreciated...

[SOLVED] twrp keeps encrypting [SOLVED]

Hello people,
I've some efs problems so decided to flash stock rom until its fixed (its not fixed yet) so then i flashed twrp and rooted with magisk later when i went in the recovery i found out it was encrypted
So i did a full format and it was fixed so i booted back to my rom and same day i found out again it was encrypted i don't want to format my phone everytime when i boot to the system,
I am rooted with magisk and i even tried the no verity 6.0 file also no luck
Try to Root withSuperSU not with magisk
Then try using the newest version of twrp
GeloXD said:
Then try using the newest version of twrp
Click to expand...
Click to collapse
I am on the newest version i will try supersu instead of magisk
I fixed it, it only happens when I am on stock rom installing a custom rom did help it
Thanks a lot for your support guys

[Pixel 3a][Android 11][ROOTED][TWRP 3.6.0] Install OTA without reverting to stock

Hello!
I am on an older version of Android 11 and I would like to install the latest Android 11 OTA without losing root and TWRP.
I know that I could just manually flash the lasted Android 11 firmware, then re-install TWRP and Magisk, but this would mean losing all data and having to reinstall apps, restore backups, etc...
So I was wondering if there were a quicker way to install OTA updates without losing data and root.
I know that there are many articles on the subject but they all refer to a previous version of TWRP and Magisk. Because TWRP 3.6.0 sports a completely revamped codebase I would like to know what is the latest recommended method if any.
This is my system info:
Android 11 sargo-rq1a.201105.002-factory-2433e0c0
Magisk v23
TWRP 3.6.0-11_0
Japan region
PS I do not intend to update to Android 12 yet
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
reyqn said:
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
Click to expand...
Click to collapse
The flashall script will still remove TWRP and root though, right?
blksith0 said:
The flashall script will still remove TWRP and root though, right?
Click to expand...
Click to collapse
Yeah it does, you have to reflash them after
It's annoying that we can't choose the OTA android installs, it has to be the latest one. On some phones you can choose a local file, but I didn't find a way to do so with a pixel 3a.
If you were able to do this, in theory you could just flash the magisk module for twrp retention and preflash magisk on the unactive partition after installing the ota but before rebooting. Then just reboot and you keep everything.
I'm not ready to update to android 12 either (gravitybox, twrp), but I'll try then...
LastStarDust said:
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
Click to expand...
Click to collapse
I don't understand. Just flash the Full Factory OTA zip in TWRP. That won't remove any data. And you can just check the box to "Automatically flash TWRP after zip" so that you'll keep whatever TWRP you're using. Then you just have to reboot recovery (so that you're on the updated slot) and flash the Magisk APK in TWRP. Reboot and profit.
P.S. This post belongs in Q&A.
Captain_Throwback said:
I don't understand. Just flash the Full Factory OTA zip in TWRP
Click to expand...
Click to collapse
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
reyqn said:
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
Click to expand...
Click to collapse
That 'recommendation' is specific to incremental OTAs. Also, it not generally being supported isn't the same as it not being recommended.
TWRP will install the zip to the inactive slot, and then when you reboot, the device will automatically boot into the updated slot.
Thanks for the precisions, I'll know for the next time. TWRP really is awesome
hi everyone, i flashed pixel 3a to android 12 and now my imei is 004400.... and no service ..... what should i do?

Question Install official RUI updates from TWRP?

So, I rooted my phone, for which I needed to unlock the bootloader and install TWRP. Now, when I want to install an update on my phone, it downloads and when I want to install it, it jumps to TWRP recovery instead of the phone's recovery, so I can't update my phone. Does anyone know how can I install the updates from TWRP?
Else, reinstall the default recovery. (Only the recovery, not the entire OS since that would un-root my phone)
Thanks.
Edit: After it boots to TWRP, it apparently tries to install the update, since I can see it on the log, but when I reboot my phone it has not installed. It errors: "E3994: This package is for "2169B" devices; this is a "". Updater process ended with ERROR: 1. Error installing zip file '/data/ota_package/OTA/.otaPackage/my_manifest_RMX3370_11.F.04_3040_202302282047.44.36402b59_all.zip'
Edit 2: After failing to install it, it prompts me to re-download it and re-install it, but it jumped from ~500MB update to 4.76GB update.
( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )
SanOne+1 said:
( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )
Click to expand...
Click to collapse
Your guide is incorrect and will definitely put the device into bootloop.
** The twrp link that you shared doesn't allow system updates to install, it is just a A13 compatable twrp recovery.
1) What if that person has not created any twrp backup of all system partitions? According to his explanation, I'm pretty sure he has not created any backup of the partitions.
2) only flashing recovery image and installing the update will again put the device into bootloop because as confirmed by the OP that his device is rooted and due to root the boot image of the device gets modified so it will put the device into bootloop.
3) unless the OP has stock boot and recovery images at his disposal he should not attempt to install the update to avoid bootloop.
** Kindly avoid sharing incorrect information you aren't sure about the correct procedure.
procedure that I follow to flash updates :
1) in magisk - uninstall magisk - restore images
2) boot device into bootloader and flash stock boot and recovery.
3) boot device and install update.
4) put device again in bootloader and flash twrp and within twrp flash magisk and reboot.
I haven't found any easier way than this. If anyone has, kindly put it below.
There's a way
Rui 4.0 Android 13 f.02
So, any verdict on this new update for the people that did update to it?
forum.xda-developers.com
Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)
Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Xemi_KryTeT.pl said:
Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)
Click to expand...
Click to collapse
Which rom r u running and is it good?
Sabirsayed09 said:
Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Which rom r u running and is it good?
Click to expand...
Click to collapse
Latest stock (4.0), I'm not going to flash custom roms for now

Categories

Resources