lineageos4microg / docker-lineage-cicd

Docker microservice for LineageOS Continuous Integration and Continous Deployment
https://hub.docker.com/r/lineageos4microg/docker-lineage-cicd
GNU General Public License v3.0
490 stars 194 forks source link

Builds bootlooping for `hotdogb`, `kebab` & `instantnoodlep` #668

Open petefoth opened 3 weeks ago

petefoth commented 3 weeks ago

The new builds for these devices are failing to boot. After an hour or so of attempting to boot the broken build, the devices revert to the previous working build

Devices affected:

Originally posted by @BurhanBudak in https://github.com/lineageos4microg/docker-lineage-cicd/issues/658#issuecomment-2295141166

petefoth commented 3 weeks ago

Similar problems reported in LOS reddit for

olokelo commented 3 weeks ago

I'm so grateful to the community for reporting issues with Hotdogb so fast. Had I upgraded earlier and my personal phone would have been borked.

Corbachini33 commented 3 weeks ago

Add lemonade to the list of devices having bootloops after the new update. Hope it comes back after an hour hahah

UPDATE: As other people had said previously, I left the phone bootloop for a while (I believe around 40 min) and it ended up reverting to July build.

UPDATE 2: Updated another Oneplus 9 (lemonade) I have with lineage os + mindthegapps (non lineageos4microg) to the 20240819 and had no issues.

aidanchappuis commented 3 weeks ago

Experiencing this with lemonadep as well.

fixxi commented 3 weeks ago

The new builds for these devices are failing to boot. After an hour or so of attempting to boot the broken build, the devices revert to the previous working build

Devices affected:

* OnePlus 7T `hotdogb`

* OnePlus 8T `kebab`

* OnePlus 8T Pro `instantnoodlep`

* OnePlus 8T `instantnoodlep`(see  https://xdaforums.com/t/lineageos-for-microg.3700997/post-89669749)

Originally posted by @BurhanBudak in #658 (comment)

just a little correction, the last two lines should read:

petefoth commented 3 weeks ago

Just a little correction, the last two lines should read: ...

Thanks - corrected.

Just a thought, I wonder whether any of the failing devices had Magisk (or another add-on) installed before the update. Please add your answers below

Devicee Magisk installed
OnePlus 7T hotdogb Yes/No
OnePlus 8T kebab Yes/No
OnePlus 8T Pro instantnoodlep Yes/No
OnePlus 8T instantnoodle Yes/No
OnePlus 9lemonade Yes/No
OnePlus 9 Prolemonadep Yes/No
petefoth commented 3 weeks ago

Another post in LOS Reddit about OnePlus 8t 'bricked' with a fresh install of the latest official LOS build https://old.reddit.com/r/LineageOS/comments/1ex2qzi/oneplus_8t_bricked/

fixxi commented 3 weeks ago

OnePlus 8 Pro instantnoodlep no add-ons reverted back to previous build 21-20240709-microG-instantnoodlep

Corbachini33 commented 3 weeks ago

Oneplus 9 lemonade, no magisk

n-hawi commented 3 weeks ago

Oneplus 8T kebab no magisk

petefoth commented 3 weeks ago

OK - magisk isn't the problem :(

Corbachini33 commented 3 weeks ago

Another one that might have the same issue, base lineage os and posted Aug 02.

https://xdaforums.com/t/lineage-os-update-issue.4684473/

The problem might be upstream and intermittent. My other Oneplus 9 updated fine.

aidanchappuis commented 3 weeks ago

Might be a little late, but if it helps, my lemonadep had magisk.

Issue existed both for the OTA and flashing the build directly as a clean install.

samsapti commented 3 weeks ago

OnePlus 8T (kebab) here. No add-ons.

So, I didn't know it would rollback by itself, so I ended up wiping and reinstalling everything. Both OTA and clean install had the bootloop issue. I actually tried to switch slot (a/b) via fastboot before wiping to hopefully be able to boot back into the old version, but it didn't work, it just failed to boot and then rebooted back into recovery and told me it couldn't boot.

At least I can confirm that SeedVault works :D

petefoth commented 3 weeks ago

A user in the XDA Forum thread appears to have found a solution:

https://xdaforums.com/t/lineageos-for-microg.3700997/post-89671565

My interpretation of that post s the the key step was the 'Flashing additional partitions' step, beforeflashing recovery.

If you need more information about this, I suggest asking by responding to that post in XDA

cstuht commented 2 weeks ago

Hi, didn't know it would rollback itself either.

Tried solution from user in XDA Forum without success:

adb sideload lineage-21.0-20240820-microG-lemonadep.zip

failed with the following error:

Supported API: 3
Finding update package...
Verifying update package...
Update verification took 75.1 s (result 0).
Installing update...
Step 1/2
Error applying update: 7 (ErrorCode: kInstallDeviceOpenError)
ERROR:  recovery: Error in /sideload/package.zip (status 1)

Install completed with status 1.
Installation aborted.

Errors from /tmp/recovery.log:

[  114.996999] 05-27 02:19:41.693   805   805 E libprocessgroup: [ERROR:task_profiles.cpp(814)] Failed to read task profiles from /etc/task_profiles.json
[  114.997023] 05-27 02:19:41.693   805   805 E libprocessgroup: [ERROR:task_profiles.cpp(787)] Loading /etc/task_profiles.json for [805] failed
[  114.997056] 05-27 02:19:41.693   805   805 W libprocessgroup: [WARN:task_profiles.cpp(1059)] Failed to find OtaProfiles task profile
[  114.997253] 05-27 02:19:41.693   805   805 E update_engine_sideload: [ERROR:update_attempter_android.cc(1073)] prefs_->GetInt64(kPrefsPreviousSlot, &previous_slot) failed.
[  114.997543] 05-27 02:19:41.694   805   805 E update_engine_sideload: [ERROR:snapshot.cpp(2807)] Open failed: /metadata/ota: No such file or directory
[  115.373387] 05-27 02:19:42.070   805   805 E update_engine_sideload: [ERROR:fstab.cpp(704)] [libfstab] ReadFstabFromFileCommon(): failed to read file: '/system/etc/fstab.postinstall': No such file or directory
[  115.379187] 05-27 02:19:42.075   805   805 E update_engine_sideload: [ERROR:snapshot.cpp(212)] An update is already in progress, cannot begin a new update
[  115.379212] 05-27 02:19:42.075   805   805 E update_engine_sideload: [ERROR:dynamic_partition_control_android.cc(977)] Cannot begin new update.
[  115.379272] 05-27 02:19:42.076   805   805 E update_engine_sideload: [ERROR:snapshot.cpp(224)] Cannot cancel update after it has completed or started merging
[  115.379288] 05-27 02:19:42.076   805   805 E update_engine_sideload: [ERROR:dynamic_partition_control_android.cc(548)] snapshot_->CancelUpdate() failed.
[  115.379315] 05-27 02:19:42.076   805   805 E update_engine_sideload: [ERROR:delta_performer.cc(919)] Unable to initialize partition metadata for slot A ErrorCode::kSuccess
[  115.379337] 05-27 02:19:42.076   805   805 E update_engine_sideload: [ERROR:delta_performer.cc(459)] Failed to parse manifest
[  115.379355] 05-27 02:19:42.076   805   805 E update_engine_sideload: [ERROR:download_action.cc(227)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
[  115.379402] 05-27 02:19:42.076   805   805 E update_engine_sideload: [ERROR:delta_performer.cc(1552)] Failed to submit transaction in checkpointing
[  115.383917] 05-27 02:19:42.080   805   805 E update_engine_sideload: [ERROR:snapshot.cpp(2807)] Open failed: /metadata/ota: No such file or directory
[  115.486303] ERROR:   recovery: Error in /sideload/package.zip (status 1)

Desperately waiting for the next release which I hope to be able to sideload as OTA update.

middleflesh commented 2 weeks ago

OnePlus 7T Pro hotdog is also affected. Upgrade hangs at boot animation. Clean install hangs at boot animation. Reverted back to previous update works, although, regrettably, all data was lost from the broken update. No addons. Only lineageos-microg.zip.

petefoth commented 2 weeks ago

Added hotdog to the list of devices to be rebuilt

petefoth commented 2 weeks ago

Also reported in lmi.

tsterbak commented 2 weeks ago

My Xiaomi 9 Lite (pyxis) also bootloops after OTA update.

petefoth commented 1 week ago

Ran out of time to get new builds working before September build run starts: builds were failing upstream too until very recently. Let's see what happens with the September build run

cstuht commented 1 week ago

I ended up doing a factory reset. As LineageOS has enabled internal microg support for me there is no to need to use lineageos4microg any more. Installed vanilla lineage-21.0-20240819, then microg and upgraded to lineage-21.0-20240826-nightly without any issues.

ivangal2 commented 6 days ago

oneplus 9 - lemonade, no magisk, bootlooped for an hour, reverted luckily automatically to July build (i believe it tried the new version in one slot, after x unsuccessful tries it reverted to the former slot). God bless the A/B partitions. :pray: