Mia's magical placeI like technology, games, and cats. This is my personal blog where I write about my interests, experiences, projects and personal stuff.2026-10-31T00:00:00Zhttps://miasmagicalplace.neocities.org/MiaThreat modeling for normal people2026-10-31T00:00:00Zhttps://miasmagicalplace.neocities.org/guides/threat-modeling/<h2>Who this is for</h2>
<p>Hiii!!! This one is for everyone, honestly, because it's the guide the other guides assume you've read. If you've ever wondered "should I actually be worried about this?" while reading a privacy article, this is for you. You need zero technical knowledge, so don't worry about it. Just ten minutes and a willingness to answer a few questions about your own life. Grab a coffee, I'll wait! :3</p>
<h2>The short version</h2>
<p>Threat modeling is answering six questions, ideally in writing:</p>
<ol>
<li>What do I want to protect?</li>
<li>Who do I want to protect it from?</li>
<li>How bad are the consequences if I fail?</li>
<li>How likely is it that I need to protect it?</li>
<li>How much trouble am I willing to go through?</li>
<li>Who are my allies?</li>
</ol>
<p>Do that once, put a date in your calendar to come back to it, and you get a short list of the threats you actually take seriously. Then every other guide on this blog becomes easier, because you'll know which parts apply to YOU. That's the whole thing, everything else is detail!! :3</p>
<h2>How it actually works</h2>
<p>Basically, a threat model is a list of the most probable threats to your security and privacy. You can't protect yourself against every possible attacker, so you focus on the most probable ones. EFF's definition is my favorite: it's a way of thinking about the sorts of protection you want for your data, so you can decide which potential threats you're going to take seriously.</p>
<p>The key insight is that trying to protect all your data from everything, all the time, is impractical and exhausting, you'd burn out in a week and give up. A threat model keeps you sane by making trade-offs explicit. And everything here is a trade-off: the more secure something is, the more inconvenient it generally is. There's high security, but never full security. Once you accept that, the whole topic stops being scary!!</p>
<p>Also, your answers are allowed to be boring. "I'm mostly worried about my bank account and my cat Alfonso photos" is a legitimate threat model! Privacy Guides makes this point with a great example: a lawyer in a national security case will go to great lengths to protect their messages, while a mom emailing her daughter funny cat videos doesn't need the same protections. Same tools, totally different models. Neither one is wrong!!</p>
<h2>Doing it yourself</h2>
<p>Grab a notebook or a text file. Answer in order, keep it short, and DON'T overthink. Ten minutes is plenty!! :3</p>
<h3>Step 1: What do I want to protect?</h3>
<p>An asset is just something you value. In digital terms: emails, contacts, messages, photos, location history, documents, passwords, and the devices themselves. Write them down, and for each one note where it lives (phone, laptop, some cloud account) and who can already see it.</p>
<h3>Step 2: Who do I want to protect it from?</h3>
<p>An adversary is whoever might want your stuff, keep it realistic. Common ones are: random scammers and phishers, an ex or a nosy relative, your employer, a thief who steals your laptop, advertisers and data brokers, and possibly the government. It can even include people you trust who might leak your data by being careless with their own security! This list is private, so be honest.</p>
<h3>Step 3: How bad are the consequences if I fail?</h3>
<p>For each asset, imagine the worst realistic outcome: My email gets taken over, and the attacker resets my other accounts; My laptop gets stolen, and my tax documents are gone; My location history leaks, and someone knows where I live. Then rate each one: catastrophic, annoying, or meh.</p>
<h3>Step 4: How likely is it that I need to protect it?</h3>
<p>Risk is about likelihood, and it goes hand in hand with capability. Your phone provider has the capability to see your call records, but the risk of them posting those online to ruin your reputation is low. A phishing email aimed at your bank login, on the other hand, is a very real, very common threat!! Cross out what nobody is realistically after, and keep what is both plausible and bad.</p>
<h3>Step 5: How much trouble am I willing to go through?</h3>
<p>Write down what you'll actually do: maybe a password manager and two-factor authentication, but definitely NOT a homelab and NOT memorizing six random words. That's fine!! Your plan has to survive contact with your actual life, otherwise it's useless.</p>
<h3>Step 6: Who are my allies?</h3>
<p>The sixth question comes from EFF: who can help? Privacy is a team sport. Your partner, a techy friend, a sibling who also cares, basically people who can watch out for you. Just remember that the people in your life can also be the weak link, so treat this as a reason to talk about security, not to hide from it!!</p>
<h3>Step 7: Set a review date</h3>
<p>Your situation changes: new job, new house, a breakup, a new bank. Put a reminder in your calendar for six months from now to re-read this list and check whether it still matches your life. EFF also says to mark a date on your calendar to come back to your plan, and six months is just my own rule of thumb!!</p>
<h2>What can go wrong</h2>
<ul>
<li><strong>You try to protect everything.</strong> The number one failure mode, seriously. If your plan is "everything, from everyone", go back to Step 4 and be meaner!!</li>
<li><strong>You copy a whistleblower's threat model.</strong> You are NOT Edward Snowden, and that's a GOOD thing. The tools for that level (Tails, Qubes, burner everything) will make your life miserable for threats you don't have. Steal ideas, but do your own homework!!</li>
<li><strong>You buy tools before doing the thinking.</strong> A VPN does not fix a password reuse problem. Model first, tools second!!</li>
<li><strong>You forget that the boring threats are the real ones.</strong> Year after year, the Verizon Data Breach Investigations Report finds the human element in most breaches (62% in the 2026 edition), with phishing and stolen credentials showing up constantly. The 2026 edition also says that exploiting software vulnerabilities is now the most common way in (31%). Keep in mind that the report counts breaches at organizations, not people like us, so I'm borrowing the lesson, not the numbers. For most of us, the highest-value defenses are a password manager, two-factor authentication, AND installing your updates, not exotic software!! I'll write a guide about password managers, phishing, and 2FA soon, but for now, just know that those three things are the most effective defenses for normal people like us.</li>
<li><strong>You never revisit it.</strong> A threat model from last year is stale. Life changes, so the model changes. Set that reminder!!</li>
</ul>
<h2>Where to read more</h2>
<ul>
<li><a href="https://ssd.eff.org/module/your-security-plan">EFF: Your Security Plan</a>, the classic walkthrough of the six questions, friendly and thorough.</li>
<li><a href="https://ssd.eff.org/glossary/threat-model">EFF glossary: threat model</a>, the one paragraph definition, handy to bookmark.</li>
<li><a href="https://www.privacyguides.org/en/basics/threat-modeling/">Privacy Guides: Threat Modeling</a>, the first stop on their knowledge base, with the trade-off framing and a worked example about protecting your house.</li>
<li><a href="https://www.privacyguides.org/en/basics/common-threats/">Privacy Guides: Common Threats</a>, a menu of the threats normal people actually face, great when you're stuck on Step 2.</li>
<li><a href="https://www.verizon.com/business/resources/reports/dbir/">Verizon Data Breach Investigations Report</a>, the annual data on how breaches actually happen, to keep your priorities honest.</li>
</ul>
<p>That's all for now!! I hope this takes some pressure off, honestlyß. Security is a process, not a purchase, and now you have a plan that fits your actual life. Love y'all :3</p>
Long time no see2026-10-25T00:00:00Zhttps://miasmagicalplace.neocities.org/posts/Personal/Long-time-no-see/<p>Hiii! As you may have noticed, I haven't been writing in this blog for a while. I know it's been a long time since my last entry (almost 3 months ._.), and I'm really sorry for that. I just haven't had the energy to write anything, but here I am!</p>
<h2>What happened</h2>
<p>During those 3 months I asked myself a lot of questions, such as "Is it normal that I'm so distracted?" or "Why do I feel so tired all the time?". For this reason, I went to a neuropsychiatrist, and after a few tests (and weeks), I was diagnosed with ADHD and autism. I was really surprised by this, but at the same time it made a lot of sense. I finally understand the reason for so many things in my life, such as the inability to continue with my projects, the constant distraction and so on. Right now I'm waiting for therapy to start, and I hope it will help me a lot. I also want to say that I'm not sad about this diagnosis. I'm actually happy, because now I understand myself better and I can work on improving myself :3</p>
<h2>What about the blog</h2>
<p>I'm going to slowly continue working on this blog, so I'll keep writing and changing things, but it is not easy to do so: I find it really difficult to write about myself, and I also find it very difficult to start writing again after some inactivity. So this time I won't promise anything here, no plans, no nothing, just know that this blog is not dead and that I will keep working on it, even if slowly.</p>
<h2>What about the chat??</h2>
<p>As some of you may have noticed, the chatbox feature has been disabled for some time now, and there are a few reasons for this. The first reason is that I'm not able to moderate it: if someone spams something at 3 AM, it'll remain there until I wake up, and I don't want that to happen. The second reason is that, temporarily, I don't have the energy to maintain it, and I don't want anything to go wrong. I may re-enable it in the future, but for now it'll remain disabled.</p>
<h2>What have I learned in those 3 months</h2>
<p>I learned that this is a hobby, and that I don't have to force myself to write if I don't feel like it. I also learned that I should not compare myself to others, and that I should not feel bad if I don't write as much as I want to. I also learned that it's okay to take a break, and that it's okay to not be perfect.</p>
<p>That's all for now. Have a nice Sunday, and see you in the next entry! :3</p>
New theme2026-08-03T00:00:00Zhttps://miasmagicalplace.neocities.org/posts/Personal/New-theme/<p>Hiii! I'm back with a new entry, and this time it's about the new theme for the blog! I've been working on it for a while, and it's finally ready to be shared with everyone.
It took me a lot of time and effort, but I think it was worth it. Try it out and let me know!</p>
<h2>Why I decided to change the theme</h2>
<p>I wanted to change it because the old one was really... uhh... modern, which is something I wanted to avoid entirely. I wanted something unique, something I could call my own, so here we are!</p>
<h2>What I changed</h2>
<p>I changed a lot of things, but the main ones are:</p>
<ul>
<li>The color scheme: I wanted something softer and more colorful, so I went with a pastel palette. I think it looks really nice and gives the blog a more cheerful vibe.</li>
<li>The layout: I wanted something different from the usual blog layouts, so I went with a layout that adapts depending on the size of your screen. It looks really nice on my phone too :)</li>
<li>The fonts: I changed those too (they're called Permanent Marker, Special Elite and Caveat, if you're curious!), and while I was in there I stopped loading them from Google Fonts and put them directly to Neocities. That means opening my blog doesn't hand your IP address to Google any more. I felt a bit silly writing a whole guide about getting Google off your phone while my own site would be pinging them on every single page ._.</li>
</ul>
<h2>Two themes!!</h2>
<p>Remember when I said I wanted to add more themes so people could choose how the blog looks? I actually did it! There's a button up in the header that says <strong>change theme :3</strong>, click it and the whole site swaps over. One is the new pixel-art scene, the other is a simpler pink one for when you want something calmer. It also remembers which one you picked, so it'll still be there next time you visit!
Which one do you use? Tell me in the shoutbox, I really want to know!! :3</p>
<h2>Some hidden stuff (go find it!)</h2>
<p>I added a few little things you'd only notice if you went looking for them, so I'm just going to tell you where they are :3</p>
<ul>
<li>Move your mouse around. There are sparkles following your cursor!</li>
<li>Hover over the category names. Every single one does something different: <strong>Transition</strong> sweeps through the trans flag colors, <strong>Travel</strong> turns into a sunset, <strong>Cybersecurity</strong> goes full green-on-black terminal, <strong>Tech</strong> glitches out, and <strong>Personal</strong> melts into handwriting with a little heart at the end.</li>
<li>My favorite one: hover over <strong>Privacy</strong> and watch the word scramble itself into gibberish. I'm <em>way</em> too proud of that one.</li>
</ul>
<p>All of this only happens in the new theme, and if you've told your system you prefer reduced motion, none of it moves at all. I didn't want to make anyone dizzy!</p>
<h2>Where's the guestbook????</h2>
<p>I've put the guestbook idea on hold for now. I want to focus on the blog itself, but I'll definitely add it in the future! That way, you'll be able to leave comments and messages instead of using the shoutbox, which I'm self-hosting but which no one is using ._.</p>
<h2>To conclude</h2>
<p>That's all for now! I hope you like the new theme, and I hope it makes your time on the blog a bit nicer! I'll keep working on it and improving it, so stay tuned for more updates! Thanks for reading, and see you in the next entry!</p>
Slow development2026-07-27T00:00:00Zhttps://miasmagicalplace.neocities.org/posts/Personal/Second-entry/<p>Hiii!!! First of all I'm really sorry for having left this blog like this for a while. I know it's been a bit of a mess, and I really wanted to keep up with writing, but honestly, I've been finding it <strong>so incredibly difficult</strong> to work on it.</p>
<h2>I'm just really tired</h2>
<p>I want to be honest here: I'm continuously tired. Like, <em>all the time</em>. And even though I'm putting in a lot of effort and giving it my absolute best, I'm finding everything so, so difficult. Even stuff that <em>should</em> be easy feels like climbing a mountain. It's not that I'm losing interest, no, definitely not! I still love this blog and everything it represents. But doing literally <em>anything</em> in my life right now is just... really hard.</p>
<h2>But I'm not stopping!</h2>
<p>I'm going to continue working on this slowly, at my own pace. I promise you that. I'm also working on completely redoing the CSS of the website so I can add some new themes for everyone to choose from. That's going to take some time, but I'm excited about it!</p>
<h2>The GrapheneOS guide</h2>
<p>Oh, and I almost forgot, I put <em>all</em> my effort into writing the GrapheneOS guide for everyone. I really hope you all find it useful! It was a lot of work, but I wanted to make it as complete and helpful as possible. You can read it <a href="https://miasmagicalplace.neocities.org/guides/GrapheneOS/">here</a>.</p>
<p>That's it for now. Thanks for sticking with me while I take things slow.</p>
How to install GrapheneOS on a Pixel phone2026-07-26T00:00:00Zhttps://miasmagicalplace.neocities.org/guides/GrapheneOS/<h2>Who this is for</h2>
<p>GrapheneOS is a security and privacy-focused mobile operating system based on Android. This guide is for anyone who wants to install GrapheneOS on a compatible Pixel phone. To follow this guide you should have basic familiarity with using a computer and following instructions! :3</p>
<h2>The short version</h2>
<ol>
<li>Check if your Pixel phone is compatible with GrapheneOS (see the list below).</li>
<li>Back up your data, as installing GrapheneOS will erase everything on your device.</li>
<li>Enable OEM unlocking in Developer Options.</li>
<li>Follow Method 1 (web installer) below, it takes about 10-20 minutes.</li>
</ol>
<h2>How it actually works</h2>
<p>GrapheneOS is designed to enhance the security and privacy of your device by implementing various security features and hardening the Android operating system. It replaces the stock Android OS on your Pixel phone, providing a more secure (and private!!) environment for your data and communications. The installation process involves unlocking the bootloader, flashing the GrapheneOS image, and setting up your device from scratch.</p>
<h2>Why use it?</h2>
<p>Stock Android ships tied to Google services that constantly phone home, while GrapheneOS changes the trust model. In this way you get:</p>
<ul>
<li>No Google services by default, and, if you want them, you can easily install them! They'll run inside a sandboxed environment, basically like a normal app without special privileges (no system-level access, which is VERY GOOD).</li>
<li>Granular permissions, basically the ability to control network access per app, revoke sensor access, and use Storage Scopes and Contact Scopes, making an app believe it has full access while only seeing what you explicitly allow.</li>
<li>Vanadium browser, one of the most secure mobile browsers available on the market thanks to integration with the OS.</li>
<li>Per-connection MAC randomization and no leaked hardware identifiers!</li>
<li>Hardened memory and exploit protection, basically a hardened memory allocator, and on 8th gen and later Pixels, you also get hardware memory tagging (so-called ARM MTE) enabled by default to catch a lot of exploits!</li>
<li>The ability to set a duress PIN/password, which if entered wipes the whole device, auto-reboot timer that returns the phone to a more secure state after inactivity called "Before First Unlock", and the ability to disable the USB-C port at hardware level.</li>
<li>Verified boot and attestation, so you can confirm cryptographically the hardware, firmware and OS are genuine using its specific Auditor app.</li>
</ul>
<h2>Doing it yourself</h2>
<p>Before you start, please be sure you have a Pixel phone! While writing this guide the following models are supported: Pixel 10a, Pixel 10 Pro Fold, Pixel 10 Pro XL, Pixel 10 Pro, Pixel 10, Pixel 9a, Pixel 9 Pro Fold, Pixel 9 Pro XL, Pixel 9 Pro, Pixel 9, Pixel 8a, Pixel 8 Pro, Pixel 8, Pixel Fold, Pixel Tablet, Pixel 7a, Pixel 7 Pro, Pixel 7, Pixel 6a, Pixel 6 Pro and Pixel 6. <strong>If you have a model not listed here, it means GrapheneOS does not support it anymore, and you should buy a newer model! I'm not responsible for any damage or loss if you proceed anyway!!!</strong></p>
<p><strong>Recommended for new buyers:</strong> Pixel 8 and later, because these have a 7-year support guarantee from launch and support hardware memory tagging (MTE). The Pixel 6 and 6 Pro reach their minimum OEM support end in October 2026, so avoid them for a fresh purchase. And <strong>PLEASE AVOID</strong> carrier-locked variants, as they don't support unlocking the bootloader, which is required to install GrapheneOS.
I trust you that you have a Pixel phone, so let's get started! :3</p>
<h2>Prerequisites</h2>
<p>You need a <strong>compatible Pixel phone</strong>, a <strong>USB-C cable</strong> (the one that came with the phone is best), and a computer with at least <strong>2 GB free RAM and 32 GB free storage</strong>. Install from bare metal, <strong>not</strong> a virtual machine. Also, <strong>back up your data</strong>, since installing wipes the device completely!</p>
<p>Now, after doing all of that, you need to <strong>enable developer options</strong> on your Pixel phone. To do this, go to Settings → About phone → tap Build number 7 times. Then go back to Settings → System → Developer options, and enable <strong>OEM unlocking</strong>.</p>
<p>If you have a <strong>Pixel 6a</strong>, heads up: OEM unlocking won't work on the factory stock OS. You need to update to the June 2022 release or later via OTA, then factory reset. After that it should work fine!</p>
<p>Let's begin the installation process! :3</p>
<h2>Method 1: Using the official Web installer (recommended)</h2>
<p>This is the recommended path for most people, because it is, in fact, very easy and fast to do. To do so, you don't need to know how to use a terminal, because it runs entirely in a supported browser using WebUSB. It even works from another Android phone, a Chromebook, or GrapheneOS itself!!
To use this method, you need to use a supported browser, which are: Chromium (not the Ubuntu Snap build), Vanadium, Google Chrome, Microsoft Edge, or Brave (with Brave Shields disabled). Do <strong>not</strong> use Incognito/private mode, since it won't have enough storage to extract the release.</p>
<p><strong>Steps:</strong></p>
<ol>
<li>Complete the prerequisites and enable OEM unlocking (above).</li>
<li><strong>Boot into the bootloader (fastboot mode).</strong> Reboot the phone while holding <strong>Volume Down</strong> until you see a red warning triangle and the words <strong>"Fastboot Mode"</strong>. Do <strong>not</strong> press the power button to pick "Start", the phone must stay paused in fastboot mode.</li>
<li><strong>Connect the phone</strong> to the computer with the USB-C cable. (On Windows 10/11 a generic driver is used automatically for the Pixel 4a 5G and later.)</li>
<li>Open the official web installer at <strong>grapheneos.org/install/web</strong>.</li>
<li>Press <strong>Unlock bootloader</strong>. Confirm on the phone with the volume keys to change the selection and the power button to accept. <em>This wipes all data.</em></li>
<li>Press <strong>Download release</strong> to fetch the factory images for your device.</li>
<li>Press <strong>Flash release</strong> and wait. The installer handles the firmware, reboots, and OS flashing automatically. <strong>Do not touch the phone</strong> until it finishes.</li>
<li>Press <strong>Lock bootloader</strong> to re-lock, and confirm on the phone. <em>This wipes data again</em> and enables full verified boot, so do it before setting up the phone.</li>
<li>Boot into GrapheneOS. Once you're in, go to Settings → System → Developer options and turn <strong>off</strong> OEM unlocking. This hardens the device!</li>
</ol>
<p>That's it!!! Most people are done in 10-20 minutes.</p>
<h2>Method 2: Using the command line (for the nerds)</h2>
<p>This one is for you if you prefer doing things the traditional way or if your setup doesn't support WebUSB. It works on Windows 10/11, recent macOS (Sonoma/Sequoia/Tahoe), Arch, Debian 12/13, and Ubuntu 22.04/24.04/25.04. Please follow the steps in order, don't skip or reorder anything!!</p>
<p>Throughout this section, replace <code>DEVICE_NAME</code> with your device codename (for example <code>tokay</code> for Pixel 9, <code>shiba</code> for Pixel 8, etc.) and <code>VERSION</code> with the current release version from the GrapheneOS releases page.</p>
<div class="guide-callout">
<label for="pixel-model-select">Not sure of your device codename? Pick your model:</label>
<select id="pixel-model-select">
<option value="">Choose your Pixel model…</option>
<option value="stallion">Pixel 10a</option>
<option value="rango">Pixel 10 Pro Fold</option>
<option value="mustang">Pixel 10 Pro XL</option>
<option value="blazer">Pixel 10 Pro</option>
<option value="frankel">Pixel 10</option>
<option value="tegu">Pixel 9a</option>
<option value="comet">Pixel 9 Pro Fold</option>
<option value="komodo">Pixel 9 Pro XL</option>
<option value="caiman">Pixel 9 Pro</option>
<option value="tokay">Pixel 9</option>
<option value="akita">Pixel 8a</option>
<option value="husky">Pixel 8 Pro</option>
<option value="shiba">Pixel 8</option>
<option value="felix">Pixel Fold</option>
<option value="tangorpro">Pixel Tablet</option>
<option value="lynx">Pixel 7a</option>
<option value="cheetah">Pixel 7 Pro</option>
<option value="panther">Pixel 7</option>
<option value="bluejay">Pixel 6a</option>
<option value="raven">Pixel 6 Pro</option>
<option value="oriole">Pixel 6</option>
</select>
<p>Device codename: <code id="pixel-codename-value" class="code-pill">—</code></p>
</div>
<script>
(function () {
var select = document.getElementById('pixel-model-select');
var value = document.getElementById('pixel-codename-value');
select.addEventListener('change', function () {
value.textContent = select.value || '—';
});
})();
</script>
<h3>Step 1: Open a terminal</h3>
<p>Use a single terminal for the whole process. On Windows, use a <strong>regular (non-admin) PowerShell</strong>, not the legacy Command Prompt. You also need to remove PowerShell's <code>curl</code> alias for this session:</p>
<pre><code class="language-powershell">Remove-Item Alias:Curl
</code></pre>
<h3>Step 2: Get <code>fastboot</code> (platform-tools)</h3>
<p>You need <code>fastboot</code> version <strong>35.0.1 or newer</strong> on your PATH. Here's how to get it depending on your OS!</p>
<p><strong>On Arch Linux</strong> you can just use the distro package:</p>
<pre><code class="language-bash">sudo pacman -S android-tools
</code></pre>
<p><strong>On Debian/Ubuntu</strong> the packaged version is broken and outdated (classic), so use the official standalone platform-tools instead:</p>
<pre><code class="language-bash">sudo apt install libarchive-tools
curl -O https://dl.google.com/android/repository/platform-tools_r35.0.2-linux.zip
echo 'acfdcccb123a8718c46c46c059b2f621140194e5ec1ac9d81715be3d6ab6cd0a platform-tools_r35.0.2-linux.zip' | sha256sum -c
bsdtar xvf platform-tools_r35.0.2-linux.zip
</code></pre>
<p><strong>On macOS:</strong></p>
<pre><code class="language-bash">curl -O https://dl.google.com/android/repository/platform-tools_r35.0.2-darwin.zip
echo 'SHA256 (platform-tools_r35.0.2-darwin.zip) = 1820078db90bf21628d257ff052528af1c61bb48f754b3555648f5652fa35d78' | shasum -c
tar xvf platform-tools_r35.0.2-darwin.zip
</code></pre>
<p><strong>On Windows:</strong></p>
<pre><code class="language-powershell">curl -O https://dl.google.com/android/repository/platform-tools_r35.0.2-win.zip
(Get-FileHash platform-tools_r35.0.2-win.zip).hash -eq "2975a3eac0b19182748d64195375ad056986561d994fffbdc64332a516300bb9"
tar xvf platform-tools_r35.0.2-win.zip
</code></pre>
<p>Now add the tools to your PATH for this session. On Linux/macOS:</p>
<pre><code class="language-bash">export PATH="$PWD/platform-tools:$PATH"
</code></pre>
<p>On Windows:</p>
<pre><code class="language-powershell">$env:Path = "$pwd\platform-tools;$env:Path"
</code></pre>
<p>Check that it works by running:</p>
<pre><code class="language-bash">fastboot --version
</code></pre>
<p>If it prints the version, you're good! :3</p>
<h3>Step 3: Linux-only setup</h3>
<p>If you're on Linux, you need to allow flashing as a non-root user with udev rules:</p>
<pre><code class="language-bash"># Arch
sudo pacman -S android-udev
# Debian / Ubuntu
sudo apt install android-sdk-platform-tools-common
</code></pre>
<p>If you get a "device already in use" or "claimed" error later, stop <code>fwupd</code>:</p>
<pre><code class="language-bash">sudo systemctl stop fwupd.service
</code></pre>
<h3>Step 4: Boot into the bootloader and unlock</h3>
<p>Boot the phone while holding <strong>Volume Down</strong> until you see <strong>"Fastboot Mode"</strong> with the red triangle, then connect it to your computer. Now unlock the bootloader:</p>
<pre><code class="language-bash">fastboot flashing unlock
</code></pre>
<p>Confirm on the device using the volume keys to select and power button to accept. <strong>This wipes all data.</strong></p>
<h3>Step 5: Download and verify the factory images</h3>
<p>First, get the signing key:</p>
<pre><code class="language-bash">curl -O https://releases.grapheneos.org/allowed_signers
</code></pre>
<p>Then download the factory images and signature for your device:</p>
<pre><code class="language-bash">curl -O https://releases.grapheneos.org/DEVICE_NAME-install-VERSION.zip
curl -O https://releases.grapheneos.org/DEVICE_NAME-install-VERSION.zip.sig
</code></pre>
<p>Now verify the download! On Linux/macOS:</p>
<pre><code class="language-bash">ssh-keygen -Y verify -f allowed_signers -I contact@grapheneos.org -n "factory images" -s DEVICE_NAME-install-VERSION.zip.sig < DEVICE_NAME-install-VERSION.zip
</code></pre>
<p>On Windows:</p>
<pre><code class="language-powershell">cmd /c 'ssh-keygen -Y verify -f allowed_signers -I contact@grapheneos.org -n "factory images" -s DEVICE_NAME-install-VERSION.zip.sig < DEVICE_NAME-install-VERSION.zip'
</code></pre>
<p>If it prints <code>Good "factory images" signature</code>, you're good. <strong>If verification fails, DO NOT continue.</strong> Something went wrong with the download and you should try again.</p>
<h3>Step 6: Extract and flash</h3>
<p>Extract the archive. On Linux:</p>
<pre><code class="language-bash">bsdtar xvf DEVICE_NAME-install-VERSION.zip
</code></pre>
<p>On macOS/Windows:</p>
<pre><code class="language-bash">tar xvf DEVICE_NAME-install-VERSION.zip
</code></pre>
<p>Move into the extracted folder:</p>
<pre><code class="language-bash">cd DEVICE_NAME-install-VERSION
</code></pre>
<p>Now run the flashing script! On Linux/macOS:</p>
<pre><code class="language-bash">bash flash-all.sh
</code></pre>
<p>On Windows:</p>
<pre><code class="language-powershell">./flash-all.bat
</code></pre>
<p>Wait for it to finish completely. It flashes firmware, reboots, and flashes the OS on its own. <strong>Don't touch the phone until it's done.</strong></p>
<p><strong>Linux tip:</strong> if flashing fails because <code>/tmp</code> is too small (it's often memory-backed), use a local temp directory:</p>
<pre><code class="language-bash">mkdir tmp && TMPDIR="$PWD/tmp" ./flash-all.sh
</code></pre>
<h3>Step 7: Lock the bootloader</h3>
<p>Re-lock to enable full verified boot:</p>
<pre><code class="language-bash">fastboot flashing lock
</code></pre>
<p>Confirm on the device. <strong>This wipes data again</strong>, which is why you lock before setting up the phone, not after.</p>
<p>And that's it for the command line method! :3</p>
<h2>After installation</h2>
<p>You're almost done!! Here's what to do now:</p>
<ul>
<li><strong>Boot GrapheneOS.</strong> Select <strong>Start</strong> in the bootloader with the power button.</li>
<li><strong>Disable OEM unlocking.</strong> Go to Settings → System → Developer options and turn <strong>off</strong> OEM unlocking. This hardens the device.</li>
<li><strong>Verify your install (optional but recommended).</strong> On 6th gen and later Pixels you can compare the on-screen verified-boot key hash against the official hash for your model, and use the <strong>Auditor</strong> app (with a second Android device) for hardware-backed attestation. Basically it confirms everything is genuine and not tampered with!</li>
<li><strong>Set up your apps.</strong> Use the Aurora Store for anonymous Play Store downloads, F-Droid for open source apps, or install sandboxed Google Play if you need push notifications and certain services.</li>
<li><strong>Harden further.</strong> Consider setting up a duress PIN, the auto-reboot timer, disabling USB when locked, and per-app network permissions. You don't have to do all of this at once, but it's nice to know it's there!</li>
</ul>
<h2>What can go wrong</h2>
<ul>
<li><strong>Bad USB cable or hub.</strong> This is the number one cause of install failures, seriously. Use the cable that came with the phone and plug it directly into your computer, not through a hub. If flashing keeps failing or disconnecting, try a different cable or a different port (rear ports on desktops are more reliable).</li>
<li><strong>WebUSB not working.</strong> Make sure you're using a supported browser (Chromium, Chrome, Edge, Brave with Shields off, or Vanadium). Firefox and Safari do NOT support WebUSB. Also don't use Incognito/private mode!!</li>
<li><strong>OEM unlocking greyed out.</strong> This usually means your device is carrier-locked. Some carriers permanently disable bootloader unlocking at the factory level. If this is the case, there's basically nothing you can do, you need a carrier-agnostic device. On a Pixel 6a specifically, update to at least the June 2022 release and factory reset first.</li>
<li><strong>Flashing fails on Linux because /tmp is too small.</strong> Your <code>/tmp</code> is probably memory-backed. Create a local temp directory and use <code>TMPDIR="$PWD/tmp" ./flash-all.sh</code> instead.</li>
<li><strong>"device already in use" error on Linux.</strong> Stop the <code>fwupd</code> service with <code>sudo systemctl stop fwupd.service</code> and try again.</li>
<li><strong>Phone stuck in a boot loop after flashing.</strong> This almost always means the bootloader was locked before flashing completed properly. Boot back into fastboot mode (hold Volume Down during reboot), unlock the bootloader again, re-flash, and <strong>make sure</strong> flashing finishes completely before locking.</li>
<li><strong>Verification fails when checking the download.</strong> Don't proceed!! Delete the files and download them again. Could be a corrupted download or a network issue.</li>
</ul>
<h2>A few realistic caveats</h2>
<p>Look, GrapheneOS is great, but there are some things you should know:</p>
<ul>
<li><strong>NFC/tap-to-pay</strong> (Google Wallet) generally won't work, so keep your physical cards handy.</li>
<li><strong>Some banking apps</strong> may refuse to run. Most work fine with sandboxed Google Play though, and the bank's website is usually a fine fallback!</li>
<li><strong>You need a Pixel.</strong> If you're on another brand, GrapheneOS is simply not an option today. Sorry!!</li>
</ul>
<h2>Where to read more</h2>
<ul>
<li><a href="https://grapheneos.org/">GrapheneOS official site</a>, the source of truth for everything, including installation, features, and FAQ.</li>
<li><a href="https://grapheneos.org/usage">GrapheneOS usage guide</a>, how to actually use GrapheneOS after installation, including setting up apps and sandboxed Google Play.</li>
<li><a href="https://grapheneos.org/faq">GrapheneOS FAQ</a>, answers to common questions about compatibility, features, and security.</li>
<li><a href="https://grapheneos.org/contact#community">GrapheneOS community chat</a>, if you get stuck, ask here. They're active and helpful, just make sure you try the guide yourself first and describe the specific step where you're stuck!</li>
</ul>
First entry2026-07-21T00:00:00Zhttps://miasmagicalplace.neocities.org/posts/Personal/Welcome/<h2>Hi!</h2>
<p>I'm Mia, and this is my first-ever entry in this blog! I hope I'll keep up with entries, but I have a lot of stuff to do.
I'm not expecting anyone to actually read these; I'm doing all of this as a <strong>hobby</strong>, not as an actual job.</p>
<h2>What to expect from this blog</h2>
<p>I'll be writing about my personal life, my hobbies, and some tech stuff. I might also write about some of my projects, but I don't know if I'll do that, it takes a lot of time. My goal is to write at least one entry per week, but I don't know if I'll be able to do that. We'll see!</p>
<h2>Future plans</h2>
<p>I have many ideas for this blog; specifically, I want to add the following features, in implementation order:</p>
<ul>
<li>A guestbook where people can leave comments and messages.</li>
<li>A contact form so people can contact me directly.</li>
<li>More themes so people can choose the look of the blog.</li>
<li>A diary section where I can write about my day-to-day life.</li>
</ul>
<p>I may even add a chat feature, but it depends on how much time I have. I may write about it in a specific entry if I decide to do it.</p>
<h2>Why I started this blog</h2>
<p>I developed (and am still developing) this blog after I saw neocities.org, a website that allows you to create your own website and find other blogs too! I looked at MANY blogs, and the one that actually gave me inspiration was <a href="https://petrapixel.neocities.org/">Petra Pixel's blog</a>, which is very well designed and has a lot of useful and interesting content!
I developed a first draft of this blog in 2025, but after some time I lost interest and stopped working on it. The problem was a lack of inspiration and motivation, as well as the capacity to do so. I wanted to make it <strong>perfect</strong>, but I realized that perfection is impossible and that I should just do my best and keep improving it over time. That's all, really. I'm just here to have fun, write about stuff I like, and maybe even learn something new along the way.</p>
<h2>Why the name "Mia's magical place"</h2>
<p>I am still thinking about a name; this one, for now, sounds good! I may change it as soon as I decide to buy a domain for this blog, but for now it will stay like this.</p>
<h2>Finally, a disclaimer</h2>
<p>I might write about some sensitive topics, so if you're not comfortable with that, please don't read this blog. I don't want to hurt anyone, but I also don't want to censor myself. I may create a specific section for sensitive content if I decide to write about it.</p>
<p>That's all for now. I hope you enjoy my blog!</p>