Introduction to Modern Android Partitioning and Custom ROMs

The landscape of Android device modification has significantly evolved, particularly with the introduction of Android 9 (Pie) and subsequent versions. Modern Android devices, especially those launched with Android 10 or later, predominantly utilize a `system_as_root` architecture alongside dynamic partitions within a `super partition`. This fundamental shift in how the operating system and user data are structured has a profound impact on the process of flashing custom ROMs, kernels, and recoveries.

Historically, `system` and `root` were separate entities, allowing for easier manipulation of the `system` partition. With `system_as_root`, the `system` partition itself serves as the root filesystem, simplifying A/B (seamless) updates but complicating direct flashing methods. Furthermore, the `super partition` concept replaces a multitude of fixed-size partitions (like `system_a`, `system_b`, `vendor_a`, `vendor_b`, `product_a`, `product_b`) with a single, large dynamic partition that can be resized on the fly. This guide aims to demystify these changes and provide a comprehensive, expert-level tutorial for successfully installing custom ROMs on modern `system_as_root` devices.

Understanding system_as_root and Super Partitions

The Evolution of system_as_root

In older Android versions, the `ramdisk` (which contains the root filesystem) was separate from the `system` partition. With `system_as_root`, the `system` partition is mounted as the root filesystem. This design was initially introduced for devices with A/B partitioning to streamline updates and reduce storage overhead. The `ramdisk` is now part of the `boot` image (or the `recovery` image on some devices), and its primary role is to initialize the kernel and mount the `system` partition as root.

Dynamic Partitions and the Super Partition

The `super partition` is a significant architectural change that arrived with Android 10 and Project Treble’s modularization efforts. Instead of having discrete partitions for `system`, `vendor`, `product`, `odm`, etc., all these partitions are now logical partitions residing within a single `super partition`. This allows for:

• Dynamic Resizing: Partitions can be resized during OTA updates without requiring a full repartitioning of the device.
• A/B Updates: Facilitates seamless updates by allowing updates to be applied to an inactive slot while the user continues to use the active slot.
• Reduced Complexity: Simplifies the partition layout from the OEM’s perspective.

For custom ROM flashing, this means you can no longer directly `fastboot flash system` or `fastboot flash vendor`. Instead, flashing tools or custom recoveries must interact with the dynamic partition manager (DPG) to allocate space and write images to the correct logical partitions within the `super partition`.

Prerequisites for Flashing

Before you begin, ensure you have the following:

• Backup Your Data: Unlocking the bootloader and flashing a custom ROM will wipe all data on your device. Backup everything important!
• ADB & Fastboot Tools: Set up Android Debug Bridge (ADB) and Fastboot on your computer.
• Unlocked Bootloader: Your device’s bootloader must be unlocked. This usually voids your warranty and will factory reset your device.
• Custom Recovery (e.g., TWRP): Download a `system_as_root` and `super partition` compatible custom recovery image specific to your device model. Often, this is a custom boot image or a dedicated `recovery` partition image.
• Custom ROM, GApps, Magisk: Download the custom ROM ZIP file, an appropriate GApps package (if the ROM doesn’t include them), and the Magisk ZIP file (for root, optional). Ensure they are compatible with your device and Android version.
• Sufficient Battery: Your device should be charged to at least 70% to prevent interruptions.

Step-by-Step Flashing Guide for system_as_root Devices

Step 1: Unlocking the Bootloader

Warning: This step will factory reset your device and void your warranty.

1. Enable Developer Options on your device by tapping ‘Build number’ seven times in ‘About phone’.
2. Go to ‘Developer Options’ and enable ‘OEM Unlocking’ and ‘USB Debugging’.
3. Connect your device to your computer via USB. Authorize the computer if prompted.
4. Open a terminal or command prompt on your computer and verify ADB connection:

   adb devices

5. Reboot your device into bootloader (fastboot) mode:

   adb reboot bootloader

6. Verify fastboot connection:

   fastboot devices

7. Unlock the bootloader. The command may vary by OEM. For most Google/OnePlus devices:

   fastboot flashing unlock

   Some devices may require `fastboot flashing unlock_critical` for certain partitions.

8. Confirm the unlock on your device’s screen using the volume keys and power button.
9. Your device will now wipe all data and reboot. You will need to set it up again to proceed, but you can skip most steps as you’ll be flashing a custom ROM. Reboot back into bootloader mode after initial setup.

Step 2: Flashing Custom Recovery (e.g., TWRP)

For `system_as_root` devices, TWRP often comes as a `boot.img` that temporarily replaces your device’s `boot` image, allowing you to flash. Some newer devices have a dedicated `recovery` partition.

1. Download the correct TWRP image for your specific device model. Let’s assume it’s `twrp.img`.
2. Ensure your device is in fastboot mode.
3. Flash the TWRP image.
   • If it’s a dedicated recovery image:

     fastboot flash recovery twrp.img

   • If it’s a boot image (common for `system_as_root`):

     fastboot flash boot twrp.img

   • Alternatively, you might just temporarily boot it without flashing:

     fastboot boot twrp.img

     This is safer for initial tests, but you’ll need to re-boot it each time.

4. Immediately after flashing (or booting), use the volume keys to navigate to ‘Recovery Mode’ and press the power button to select it. This is crucial to prevent the stock ROM from overwriting TWRP on the next boot.
5. TWRP will likely ask for your password to decrypt data. Enter your device’s lock screen PIN/password.

Step 3: Performing a Nandroid Backup (Optional but Recommended)

Once in TWRP, navigate to ‘Backup’. Select all critical partitions (Boot, System Image, Vendor Image, Data, EFS if available). Swipe to begin the backup. Store this backup on an external SD card or transfer it to your computer.

Step 4: Preparing for Flashing (Wipes)

This is a critical step to ensure a clean installation and prevent boot loops. In TWRP:

1. Go to ‘Wipe’.
2. Select ‘Advanced Wipe’.
3. Check ‘Dalvik / ART Cache’, ‘Cache’, ‘System’, ‘Vendor’, and ‘Data’. DO NOT select ‘Internal Storage’ unless you’ve backed up everything important or explicitly want to format it.
4. Swipe to Wipe.
5. Go back to ‘Wipe’ and select ‘Format Data’. Type ‘yes’ to confirm. This removes encryption and fully formats the data partition.

Step 5: Flashing the Custom ROM

With `system_as_root` and dynamic partitions, `adb sideload` is often the most reliable method.

1. In TWRP, go to ‘Advanced’ > ‘ADB Sideload’. Swipe to start sideload.
2. On your computer, navigate to the directory where you downloaded your custom ROM ZIP file.
3. Initiate the sideload:

   adb sideload .zip

4. Wait for the process to complete. This can take several minutes. Do not disconnect your device.

Step 6: Flashing GApps (Optional)

If your custom ROM doesn’t include Google Apps, you’ll need to flash them immediately after the ROM, before rebooting.

1. After the ROM sideload completes, in TWRP, again go to ‘Advanced’ > ‘ADB Sideload’. Swipe to start.
2. On your computer, initiate the GApps sideload:

   adb sideload .zip

3. Wait for completion.

Step 7: Flashing Magisk (Optional – for Root)

If you want root access, flash Magisk after GApps (or directly after the ROM if no GApps).

1. After GApps (or ROM) sideload, in TWRP, go to ‘Advanced’ > ‘ADB Sideload’. Swipe to start.
2. On your computer, initiate the Magisk sideload:

   adb sideload Magisk-vXX.X.zip

3. Wait for completion.

Step 8: Rebooting and Initial Setup

Once all flashing is complete, go back to the main menu in TWRP and select ‘Reboot’ > ‘System’.

• The first boot into a new custom ROM can take significantly longer (5-15 minutes). Be patient.
• If your device boots up successfully, proceed with the initial Android setup.
• If you encounter a bootloop, refer to the troubleshooting section.

Troubleshooting Common Issues

• Bootloop after flashing: This usually means something went wrong with the ROM or GApps. Reboot to TWRP and perform a clean wipe (System, Vendor, Data, Cache, Dalvik) and re-flash the ROM and GApps. If issues persist, try a different ROM version or verify ROM integrity.
• `adb sideload` errors: Ensure your ADB drivers are up-to-date and your device is correctly recognized. Try restarting both your computer and device.
• TWRP not mounting partitions: This often happens if you didn’t decrypt your data or if TWRP is not fully compatible with your device’s encryption scheme. Ensure you entered your lock screen password/PIN when prompted.
• Error about super partition size: This indicates an issue with dynamic partition management, often due to an incompatible recovery or a corrupted ROM file. Double-check your recovery version and ROM integrity.

Conclusion

Flashing custom ROMs on modern Android devices with `system_as_root` and `super partition` architecture requires a deeper understanding of the underlying system changes. By following these detailed steps, understanding the purpose of each command, and ensuring you have the correct, compatible files for your specific device, you can successfully install a custom ROM. Always proceed with caution, back up your data, and remember that device modification carries inherent risks.