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
480 stars 189 forks source link

latest guacamole build broken, please delete #633

Closed ristein closed 1 month ago

ristein commented 1 month ago

as described here https://github.com/lineageos4microg/docker-lineage-cicd/issues/631 there are issues in the build of guacamole (oneplus 7 pro) from yesterday (20240524). Would be great if someone could delete that file to save some users from breaking their phone. Issues I have:

ristein commented 1 month ago

Also it would be great to have an update today that fixes this if possible

MicahBird commented 1 month ago

I agree, I just tested stock lineage and their latest build (lineage-21.0-20240520-nightly-guacamole) and it works as expected!

ristein commented 1 month ago

@MicahBird you don't happen to have an idea if it is possible to rescue current install? Clean install always takes hours for me :disappointed:

petefoth commented 1 month ago

I've no idea what's caused the problems, and no idea how to fix them. I'll delete the build when I get back to my computer

MicahBird commented 1 month ago

@MicahBird you don't happen to have an idea if it is possible to rescue current install? Clean install always takes hours for me 😞

I hear ya... Hmm, until another up to date (functional) build is provided we're kinda stuck... If there was a new update, it would be as simple as Boot into Recovery > Apply Update > Apply from ADB. You could try to switch your A/B slot and hope that one of them has the previous OTA update, but proceed at your own risk. If you absolutely need to recover data, you can always flash TWRP recovery and exfiltrate your data that way!

petefoth commented 1 month ago

I've removed the latest build, and started a new clean build. If the problems were caused by an unclean build environment, a new build might fix things. I can't test any builds as I don't have access to one of these phones

ristein commented 1 month ago

thank you a lot. I was just typing to ask you. Once finished, can I check it via "adb -d sideload ...zip"? Or do I need to flash other partitions as well?

petefoth commented 1 month ago

Should be OK to flash it using adb sideload I think, but I don't have any experience with OnePLus phones. If just sideloading the ROM .zip file doesn't work, you could try following the LOS installation instruction, flashing additional partitions using fastboot to flash dtbo.img and vbmeta.ing, (see https://wiki.lineageos.org/devices/guacamole/install/#flashing-additional-partitions), then flashing the recover sing fastboot (see https://wiki.lineageos.org/devices/guacamole/install/#installing-lineage-recovery-using-fastboot)

MicahBird commented 1 month ago

I can confirm that all you need to do is an adb sideload from recovery! No need to flash the other partitions!

ctag commented 1 month ago

Warning to other users like me who don't know what they're doing.

Downloaded the new files and checked the sha256sums, though was a little confused that the modified date wasn't today.

I tried booting into recovery and sideloading just the new lineage OS zip, but got ERROR: recovery: Denying OTA because it's SPL downgrade.

I then booted to fastboot and flashed the dtbo, vbmeta, and boot images by following the lineageos guide. And then sideloaded the OS zip again. This time the sideload completed, I skipped installing extra packages, and went to reboot to system. The phone came back to recovery with this message:

Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

MicahBird commented 1 month ago

Ayyyyy, I also came across ERROR: recovery: Denying OTA because it's SPL downgrade but it was because I was trying to foolishly downgrade to Lineage OS 20 🤣

Your probably running into that error because you need to perform a factory reset from recovery in order to clean up the mess that the (now deleted) May 24th update caused... Hope that helps!

Edit: @ctag I was able to successfully clean flash lineage-21.0-20240507-microG-guacamole.zip, let me know if you need any assistance!

ctag commented 1 month ago

Thank you @MicahBird! A factory data reset worked.

Now to contemplate my lack of effort in making backups before this :face_with_head_bandage:

petefoth commented 1 month ago

OK the new build is available. Please let me know how you get on with it

MicahBird commented 1 month ago

Beautiful! I'm installing the update now, I'll keep y'all posted on how it goes!

MicahBird commented 1 month ago

🎊 🎊 Three cheers for @petefoth! 🎊 🎊

I can confirm the latest build (lineage-21.0-20240525-microG-guacamole) is safe and fixes the watch issue presented in #631! Thank you so much @petefoth for making all the builds!! 🙇 I could only dream of building Android from source...

petefoth commented 1 month ago

OK. Still no idea what was wrong with the previous build, and sorry for the inconvenience it caused.

@ristein @ctag If you have a chance, please can you try the latest build? I wont close this issue yet, until I'm sure the build works for ore than one user ;)

ristein commented 1 month ago

working here too. Thanks a lot!

others please remember to also flash magisk or other mods after rom

petefoth commented 1 month ago

OK it works for two people - that will do :) Closing