Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
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.

Administered by:

Server stats:

224
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#ramdisk

0 posts0 participants0 posts today
Felix Palmen :freebsd: :c64:<p>What I'm still missing is a custom <a href="https://mastodon.bsd.cafe/tags/recovery" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>recovery</span></a> that can actually do any useful stuff (especially full <a href="https://mastodon.bsd.cafe/tags/backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backup</span></a>).</p><p>My device has recovery as a <a href="https://mastodon.bsd.cafe/tags/ramdisk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ramdisk</span></a> in vendor_boot, and there are some prebuilt vendor_boot images with <a href="https://mastodon.bsd.cafe/tags/twrp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>twrp</span></a> 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 <a href="https://mastodon.bsd.cafe/tags/magisk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>magisk</span></a> ... and as far as I understood now, these ramdisks are userland only, using the shared <a href="https://mastodon.bsd.cafe/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kernel</span></a> from the boot partition, so it's unlikely a recovery built for <a href="https://mastodon.bsd.cafe/tags/HyperOS1" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HyperOS1</span></a> (<a href="https://mastodon.bsd.cafe/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Android</span></a> 14, <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> 5) will work with <a href="https://mastodon.bsd.cafe/tags/HyperOS2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HyperOS2</span></a> (Android 15, Linux 6).</p><p>What I *did* try nevertheless was modifying my vendor_boot using Magisk's <a href="https://mastodon.bsd.cafe/tags/magiskboot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>magiskboot</span></a> utility, replacing ONLY the recovery ramdisk. It resulted in <a href="https://mastodon.bsd.cafe/tags/bootloop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bootloop</span></a> 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).</p><p>For now, I'll live with the useless stock <a href="https://mastodon.bsd.cafe/tags/Xiaomi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Xiaomi</span></a> recovery. Attempting to do my own build of twrp or orangefox really is too much hassle 🙈</p>
Kajo 📷 :mastolove:<p>Gibts hier jemanden, der <a href="https://social.tchncs.de/tags/IodeOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IodeOS</span></a> über deren <a href="https://social.tchncs.de/tags/Installer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Installer</span></a> bzw. <a href="https://social.tchncs.de/tags/manuell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>manuell</span></a> auf seinem <a href="https://social.tchncs.de/tags/SHIFTphone6mq" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SHIFTphone6mq</span></a> (oder anderem <a href="https://social.tchncs.de/tags/ShiftPhone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ShiftPhone</span></a>) erfolgreich installiert hat?</p><p>Momentan ist bei meinem <a href="https://social.tchncs.de/tags/SHIFT6mq" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SHIFT6mq</span></a> der <a href="https://social.tchncs.de/tags/BootLoader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BootLoader</span></a> <a href="https://social.tchncs.de/tags/unlocked" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>unlocked</span></a>, es lebt ein <a href="https://social.tchncs.de/tags/LineageOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LineageOS</span></a> drauf und ich hab <a href="https://social.tchncs.de/tags/Magisk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Magisk</span></a> geflashed (<a href="https://social.tchncs.de/tags/Ramdisk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ramdisk</span></a> Yes, Zygisk: No).</p><p>Bedenken hab ich nur bzgl. den A/B-Partitionen bzw. dass ich dahingehend was falsch mache(n könnte).</p><p>:BoostOK:</p><p>1/2</p>
ExploreLive feeds
About