det.social

BnerdeDanke mit fedipower gelöst <a href="https://mastodon.social/tags/lineageos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lineageos</a> <a href="https://mastodon.social/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> <a href="https://mastodon.social/tags/twrp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#twrp</a> <a href="https://mastodon.social/tags/fediversepower" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediversepower</a>Guten Tag, ich habe lineage OS 14 mit twrp auf Galaxy Tab e geflasht und anschließend mit twrp microg. Hat prima geklappt. Bei Samsung Galaxy S5 neo habe ich lineage 19.1 per twrp geflasht. Danach war twrp durch lineage recovery ersetzt und der bootloader gesperrt. Deshalb kann ich nanodroid microg nicht flashen. Auch twrp bekomme ich per Odin oder ADB nicht geflasht, bootloadet gesperrt. Gibt es dafür Lösungen?

Hacker NewsMicrosoft reports several bootloader vulnerabilities<a href="https://www.microsoft.com/en-us/security/blog/2025/03/31/analyzing-open-source-bootloaders-finding-vulnerabilities-faster-with-ai/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.microsoft.com/en-us/security/blog/2025/03/31/analyzing-open-source-bootloaders-finding-vulnerabilities-faster-with-ai/</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a> <a href="https://mastodon.social/tags/Vulnerabilities" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vulnerabilities</a> <a href="https://mastodon.social/tags/Bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bootloader</a> <a href="https://mastodon.social/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> <a href="https://mastodon.social/tags/Analysis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Analysis</a>

Friedhof der Kuschelbiere 🇺🇦🇮🇱<a href="https://www.heise.de/news/Zollpolitik-der-USA-Wird-das-iPhone-deutlich-teurer-10339481.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.heise.de/news/Zollpolitik-der-USA-Wird-das-iPhone-deutlich-teurer-10339481.html</a>Wäre vielleicht geschickt sich als <a href="https://metalhead.club/tags/iOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iOS</a> Nutzer*in jetzt schonmal über alternative <a href="https://metalhead.club/tags/Hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hardware</a>, <a href="https://metalhead.club/tags/Bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bootloader</a>, <a href="https://metalhead.club/tags/Root" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Root</a> und <a href="https://metalhead.club/tags/CustomOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CustomOS</a> zu informieren. Ist überhaupt kein Hexenwerk und dürfte in den kommenden Jahren wohl anfangen eine größere Rolle zu spielen!

The New Oil<a href="https://mastodon.thenewoil.org/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a> uses <a href="https://mastodon.thenewoil.org/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> to find flaws in <a href="https://mastodon.thenewoil.org/tags/GRUB2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GRUB2</a>, <a href="https://mastodon.thenewoil.org/tags/UBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UBoot</a>, <a href="https://mastodon.thenewoil.org/tags/Barebox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Barebox</a> bootloaders<a href="https://www.bleepingcomputer.com/news/security/microsoft-uses-ai-to-find-flaws-in-grub2-u-boot-barebox-bootloaders/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bleepingcomputer.com/news/security/microsoft-uses-ai-to-find-flaws-in-grub2-u-boot-barebox-bootloaders/</a><a href="https://mastodon.thenewoil.org/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> <a href="https://mastodon.thenewoil.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a>

Mai :v_trans:Yas! It finally works, <a href="https://soc.saiyajin.space/tags/rustboot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rustboot</a> can load elf objects, resolve symbols and execute the the init method contained! Took me longer than I want to admit, mainly bc there was a 4byte bss segment I forgot to map correctly in the linker script that was messing with symbol locations of rustboot.<a href="https://codearq.net/chalk-os/rustboot" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codearq.net/chalk-os/rustboot</a><a href="https://soc.saiyajin.space/tags/osdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#osdev</a> <a href="https://soc.saiyajin.space/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> <a href="https://soc.saiyajin.space/tags/floss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#floss</a> <a href="https://soc.saiyajin.space/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a> <a href="https://soc.saiyajin.space/tags/oss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oss</a> <a href="https://soc.saiyajin.space/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://soc.saiyajin.space/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> <a href="https://soc.saiyajin.space/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://soc.saiyajin.space/tags/software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#software</a> <a href="https://soc.saiyajin.space/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a>

Pen Test PartnersAfter scouring the internet, we realised that information on Rockchip MCUs is either scarce or hidden behind NDAs. So in our latest blog, David Lodge looks at the Rockchip boot process. He covers the boot order and how to force the MCU into low-level modes for direct USB access.   He also dives into essential tools like xrock and rkflashtool that let you read and write the MCU’s RAM and flash memory.Read here: <a href="https://www.pentestpartners.com/security-blog/a-dive-into-the-rockchip-bootloader/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.pentestpartners.com/security-blog/a-dive-into-the-rockchip-bootloader/</a><a href="https://infosec.exchange/tags/rockchip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rockchip</a> <a href="https://infosec.exchange/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> <a href="https://infosec.exchange/tags/mcu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mcu</a> <a href="https://infosec.exchange/tags/firmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firmware</a> <a href="https://infosec.exchange/tags/embeddedsystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#embeddedsystems</a> <a href="https://infosec.exchange/tags/reverseengineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reverseengineering</a> <a href="https://infosec.exchange/tags/hardwarehacking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hardwarehacking</a>

Kevin Karhan :verified:<a href="https://troet.cafe/@Josteglitz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Josteglitz</a> <a href="https://mastodon.social/@topio" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@topio</a> ist der <a href="https://infosec.space/tags/Bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bootloader</a> entsperrt?Weil wenn der Hersteller den nicht entsperrt haste nen Problem!

Marcel SIneM(S)US<a href="https://social.tchncs.de/tags/Bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bootloader</a> U-Boot: Sicherheitslücken ermöglichen Umgehen der Chain-of-Trust | Security <a href="https://www.heise.de/news/Bootloader-U-Boot-Sicherheitsluecken-ermoeglichen-Umgehen-der-Chain-of-Trust-10287480.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.heise.de/news/Bootloader-U-Boot-Sicherheitsluecken-ermoeglichen-Umgehen-der-Chain-of-Trust-10287480.html</a> <a href="https://social.tchncs.de/tags/Patchday" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Patchday</a> <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> :tux: <a href="https://social.tchncs.de/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> :android: <a href="https://social.tchncs.de/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>

Kevin Karhan :verified:<a href="https://bildung.social/@andreasgoebel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@andreasgoebel</a> ja, musst dazu nen <a href="https://infosec.space/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> auf dem Stick haben und <a href="https://infosec.space/tags/grub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grub</a> muss den per <a href="https://infosec.space/tags/chainloading" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chainloading</a> ansprechen!<a href="https://infosec.space/tags/Protip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Protip</a>: Entsprechenden Stick als einziges Laufwerk bei Installation einer Sesktop-Distrobanschließen oder beim Installierennderselbennfestlegen, dass auch der Bootloader dort installiert werden soll!

Mai :v_trans:Finished today stage2 of the bios bootprocess in <a href="https://soc.saiyajin.space/tags/rustboot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rustboot</a> , which includes trying to enable the A20 gate so we can actually access RAM above 1MB, and also to switch to 32bit protected mode! Next thing is to finally bootstrap the core of the bootloader that will run in 32bit!<a href="https://codearq.net/chalk-os/rustboot" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codearq.net/chalk-os/rustboot</a><a href="https://soc.saiyajin.space/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> <a href="https://soc.saiyajin.space/tags/osdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#osdev</a> <a href="https://soc.saiyajin.space/tags/oss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oss</a> <a href="https://soc.saiyajin.space/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a> <a href="https://soc.saiyajin.space/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://soc.saiyajin.space/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://soc.saiyajin.space/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://soc.saiyajin.space/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> <a href="https://soc.saiyajin.space/tags/grub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grub</a> <a href="https://soc.saiyajin.space/tags/technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#technology</a>

OSTechNixGRUB Project Update 2025 by Daniel Kiper, a GRUB Upstream Maintainer <a href="https://floss.social/tags/Grub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Grub</a> <a href="https://floss.social/tags/GRandUnifiedBootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GRandUnifiedBootloader</a> <a href="https://floss.social/tags/Bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bootloader</a> <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://floss.social/tags/Opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Opensource</a> <a href="https://ostechnix.com/grub-project-update-2025/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ostechnix.com/grub-project-update-2025/</a>

Marcel SIneM(S)US<a href="https://social.tchncs.de/tags/FOSDEM25" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSDEM25</a>: Booten ohne <a href="https://social.tchncs.de/tags/Bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bootloader</a> | heise online <a href="https://www.heise.de/news/FOSDEM-25-Booten-ohne-Bootloader-10267072.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.heise.de/news/FOSDEM-25-Booten-ohne-Bootloader-10267072.html</a> <a href="https://social.tchncs.de/tags/FOSDEM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSDEM</a> <a href="https://social.tchncs.de/tags/FOSDEM2025" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSDEM2025</a> <a href="https://social.tchncs.de/tags/Grub2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Grub2</a> <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> :tux:

Mai :v_trans:Worked the last couple of days on a <a href="https://soc.saiyajin.space/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> in <a href="https://soc.saiyajin.space/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> ; got the bootsector working and even managed to write an clunky elfloader that sucessfully loads ELF relocateables, relocates the symbol and then executes them! Next thing is to rewrite it in a proper rusty style and then integrate it into the bootloader so I can start bootstraping the module system, very exciting!<a href="https://codearq.net/chalk-os/rustboot" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codearq.net/chalk-os/rustboot</a>Edit: link should work now<a href="https://soc.saiyajin.space/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> <a href="https://soc.saiyajin.space/tags/oss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oss</a> <a href="https://soc.saiyajin.space/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://soc.saiyajin.space/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a> <a href="https://soc.saiyajin.space/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://soc.saiyajin.space/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://soc.saiyajin.space/tags/technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#technology</a> <a href="https://soc.saiyajin.space/tags/osdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#osdev</a> <a href="https://soc.saiyajin.space/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> <a href="https://soc.saiyajin.space/tags/grub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grub</a>

vermadenNew 𝗙𝗿𝗲𝗲𝗕𝗦𝗗 𝗔𝗹𝗼𝗻𝗴𝘀𝗶𝗱𝗲 𝗪𝗶𝗻𝗱𝗼𝘄𝘀 (FreeBSD Alongside Windows) article on <a href="https://vermaden.wordpress.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://vermaden.wordpress.com/</a> blog.<a href="https://vermaden.wordpress.com/2025/02/02/freebsd-alongside-windows/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://vermaden.wordpress.com/2025/02/02/freebsd-alongside-windows/</a><a href="https://mastodon.bsd.cafe/tags/verblog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#verblog</a> <a href="https://mastodon.bsd.cafe/tags/boot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#boot</a> <a href="https://mastodon.bsd.cafe/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> <a href="https://mastodon.bsd.cafe/tags/desktop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#desktop</a> <a href="https://mastodon.bsd.cafe/tags/dual" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dual</a> <a href="https://mastodon.bsd.cafe/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a> <a href="https://mastodon.bsd.cafe/tags/install" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#install</a> <a href="https://mastodon.bsd.cafe/tags/laptop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#laptop</a> <a href="https://mastodon.bsd.cafe/tags/windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#windows</a> <a href="https://mastodon.bsd.cafe/tags/zfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zfs</a>

Colin FinckThe second part of my <a href="https://hachyderm.io/tags/WinDbg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WinDbg</a> deep-dive into the <a href="https://hachyderm.io/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a> <a href="https://hachyderm.io/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> is up: Get ready for a decades-old registry structure, unique sorting algorithms, and lots of corner cases. The result is a modern Rust replacement for Mark Russinovich's LoadOrder tool: <a href="https://colinfinck.de/posts/nt-load-order-part-2/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://colinfinck.de/posts/nt-load-order-part-2/</a>

Friedhof der Kuschelbiere 🇺🇦🇮🇱<a href="https://stadt-bremerhaven.de/xiaomi-fuehrt-neue-regeln-fuer-das-entsperren-des-bootloaders-ein/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://stadt-bremerhaven.de/xiaomi-fuehrt-neue-regeln-fuer-das-entsperren-des-bootloaders-ein/</a>You know, wenn man einen <a href="https://metalhead.club/tags/Code" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Code</a> braucht um den <a href="https://metalhead.club/tags/Bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bootloader</a> entsperren zu können öffnet das <a href="https://metalhead.club/tags/Missbrauch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Missbrauch</a> durch den <a href="https://metalhead.club/tags/Hersteller" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hersteller</a> Tür und Tor. Was <a href="https://metalhead.club/tags/Xiaomi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xiaomi</a> da gerade abzieht erwarte ich beim <a href="https://metalhead.club/tags/Fairphone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fairphone</a> zwar nicht, immerhin ist auf Fairphones keine zusätzliche <a href="https://metalhead.club/tags/Werbung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Werbung</a> geschaltet, es hat trotzdem ein unangenehmes <a href="https://metalhead.club/tags/Geschm%C3%A4ckle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geschmäckle</a>....

Friedhof der Kuschelbiere 🇺🇦🇮🇱Ich habe mich für mein <a href="https://metalhead.club/tags/Fairphone5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fairphone5</a> jetzt gegen e/OS/ und für <a href="https://metalhead.club/tags/CalyxOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CalyxOS</a> entschieden. Der <a href="https://metalhead.club/tags/Bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bootloader</a> ist bereits offen (ich finde es immer eher grenzwertig wenn man um den Bootloader zu öffnen einen Code anfragen muss) und das <a href="https://metalhead.club/tags/Phone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Phone</a> hat <a href="https://metalhead.club/tags/Root" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Root</a>. Morgen geht es dann daran <a href="https://metalhead.club/tags/CustomKernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CustomKernel</a> und <a href="https://metalhead.club/tags/ROM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ROM</a> zu flashen!

Jens Brückner 😷 :debian:Neuartiges Erlebnis. <a href="https://social.tchncs.de/tags/Stromausfall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Stromausfall</a> im Stadtteil. <a href="https://social.tchncs.de/tags/usv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#usv</a> Neustart. <a href="https://social.tchncs.de/tags/server" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#server</a> <a href="https://social.tchncs.de/tags/boot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#boot</a> <a href="https://social.tchncs.de/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> Genau in diesem Moment <a href="https://social.tchncs.de/tags/bang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bang</a> krabaff peng, Maschine aus, black screen of death. Also jetzt ist doch alles kaputt, inne Fritten!? Nicht nur die Knie werden weich, es zieht einem den Boden unter den Füßen weg. Mein Kumpel Philipp sagt, Netzteil von be quiet! mit <a href="https://social.tchncs.de/tags/OPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OPP</a> (Überlastungsschutz) und <a href="https://social.tchncs.de/tags/OCP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OCP</a> (Überstromschutz), Kabel abziehen, 30 Minuten warten.Alle Strippen dran — und das Ding läuft wieder!

Felix SingerHaving some wine and working on integrating <a href="https://fosstodon.org/@barebox" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@barebox</a> as a second stage <a href="https://chaos.social/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a> into <a href="https://chaos.social/tags/coreboot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coreboot</a>.Happy new year all.

MarkGFor those thinking of getting a phone and putting LineageOS on it, do note that some phones do not allow the bootloader to be unlocked.Here is a list of phones and whether or not they allow the bootloader to be unlocked (note, modern phones, rather than older models):<a href="https://github.com/melontini/bootloader-unlock-wall-of-shame?tab=readme-ov-file" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/melontini/bootloader-unlock-wall-of-shame?tab=readme-ov-file</a><a href="https://mindly.social/tags/LineageOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LineageOS</a> <a href="https://mindly.social/tags/bootloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootloader</a>

Recent searches

Search options

Administered by:

Server stats:

#bootloader