I recently updated my device from v20 to v21 via OTA. Since the update, when I power on my computer, it keeps rebooting several times before eventually connecting to Wi-Fi and allowing me to log in. Have you ever encountered this issue or know what might be causing it?
boot loop, is a known occurrence for some users following the FydeOS v21 OTA update.
Potential causes and troubleshooting steps include:
GApps Interference: Updating FydeOS with Open GApps installed can cause the Android subsystem to fail or loop. To resolve this, it is generally recommended to uninstall GApps before an update or reinstall them immediately after.
Bootloader Conflicts: The v21 update introduced changes to how rEFInd and boot files are handled. In some cases, old bootloader files (like those from Ventoy) can conflict with the new version. Clearing previous refind folders or performing a clean install using Rufus has resolved similar boot errors for others.
Wi-Fi Chip Compatibility: Since your device only stabilizes after connecting to Wi-Fi, there may be a delay in the firmware initialization for your specific network card. Checking for a v21-SP1 update, which fixed similar Wi-Fi bugs for other devices, is recommended.
Hardware Limitations: Older devices or those with discrete GPUs (NVIDIA/AMD) might struggle with the new Android subsystem initialization in v21, leading to reboots.
Recommended Next Steps:
Attempt to reinstall GApps via the FydeOS App Store if they were active during the update.
If the loop persists, a clean installation of v21 using the latest image from the FydeOS Download Page is the most reliable fix.
Are you using Open GApps or a dual-boot setup with another operating system?
Than you very much ARyaAN. I would try to install v21.0-SP1 but I can’t find a way to download it. Is there a link to download the image and mount it with Rufus ?
If the system runs normally from a USB drive but encounters issues only after being installed on the internal disk, the problem is likely related to the bootloader. In most cases, this indicates a boot configuration issue.
Did you set up a multi-boot installation on this device?