eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

192
active users

#bootloop

0 posts0 participants0 posts today

Yesterday, I ran a firmware update on Linux: "sudo #fwupdmgt update” which showed an intel ME update I ran.

Device: Lenovo #T490.

Since then, I can't boot my #Linux (#NixOS) anymore. Instead, I have a strange boot-loop into the BIOS.

Up-to-date details: md.darmstadt.ccc.de/s/WcxbmDtw (reload for updates!)

If you have any ideas I might try, please do let me know.

HedgeDoc logo
md.darmstadt.ccc.deT490 boot loop 2025-08-08 - HedgeDoc# T490 boot loop 2025-08-08 Issue caused by: On NixOS stable (latest), I did a "sudo fwupdmgt upda
Continued thread

What I'm still missing is a custom #recovery that can actually do any useful stuff (especially full #backup).

My device has recovery as a #ramdisk in vendor_boot, and there are some prebuilt vendor_boot images with #twrp around, which I don't want to use directly because there's also an init-boot ramdisk in there that needs patching for root with #magisk ... and as far as I understood now, these ramdisks are userland only, using the shared #kernel from the boot partition, so it's unlikely a recovery built for #HyperOS1 (#Android 14, #Linux 5) will work with #HyperOS2 (Android 15, Linux 6).

What I *did* try nevertheless was modifying my vendor_boot using Magisk's #magiskboot utility, replacing ONLY the recovery ramdisk. It resulted in #bootloop trying to boot the normal system, so there seems to be something I still don't understand (I *thought* this ramdisk would only ever be loaded when booting to recovery).

For now, I'll live with the useless stock #Xiaomi recovery. Attempting to do my own build of twrp or orangefox really is too much hassle 🙈

Mein selbst zusammen-gehacktes/kompiliertes #OpenWrt für den TP-Link WR841 v10 mit 16 MB Flash (statt vom Hersteller 4 MB) geht leider ständig in eine #Bootloop und startet nicht richtig, vermutlich weil es es das root-Dateisystem unter /dev/mtdblock4 nicht mounten kann.

Zurücksetzen/Reset hab ich schon mehrfach probiert;
- OpenWrt mit sysupgrade neu installieren
- mit firstboot alles resetten.
Hat nix gebracht.

Kann mir da jemand helfen?

Im #Failsafe-Modus kann ich es zum Glück starten.

Apple zieht iOS 18.4 und watchOS 11.4 Betas für mehrere Geräte zurück
Apple hat die Betaversionen von iOS 18.4, iPadOS 18.4 und watchOS 11.4 für mehrere Geräte zurückgezogen. Besonders betroffen sind die Apple Watch Series 6 und me
apfeltalk.de/magazin/news/appl
#iPad #iPhone #News #Apple #AppleBetaProgramm #AppleWatchSeries6 #BetaUpdate #Bootloop #IOS184 #IPadOS184 #IPhone12 #Softwareprobleme #WatchOS114

#Garmin watch owners, beware! There is a problem with a GPS coordination file that can brick your watch. Until it's resolved, avoid any GPS activities and/or turn the watch connectivity completely off.
My model is affected. 😕

UPDATE: Garmin has replaced the corrupted file with a fixed on their servers. If you have an affected model, but your device hasn't gotten into the boot loop, you're advised to go the Garmin Connect app and enforce the device sync to download the fixed file. The article has been updated accordingly.

#GarminGPS #BootLoop

dcrainmaker.com/2025/01/garmin

DC Rainmaker · Garmin Watches Are Crashing When Trying to Start GPSHere I was just minding my own business trying to take photos for my Instinct 3 review, when some, but not all, of the watches kept crashing and rebooting every time I opened up the sport menu. Little did I