Complete Custom ROM Installation Guide
Transform your Android experience - Install privacy-focused, security-enhanced custom ROMs to revive and enhance your device.
๐ Essential Resources โ
- ๐ Main Rooting Guide - Universal rooting principles and safety
- ๐ Bootloader Unlocking - Required first step
- ๐ ๏ธ Custom Recovery - Installation prerequisite
- โ FAQ & Troubleshooting - Solutions for common issues
Table of Contents โ
- Understanding Custom ROMs
- Prerequisites and Requirements
- ROM Selection Guide
- Installation Process
- Post-Installation Setup
- Troubleshooting Guide
- Staying Updated
- Whatโs Next?
Understanding Custom ROMs โ
Custom ROMs are alternative Android distributions that replace your deviceโs stock firmware, offering enhanced privacy, performance, and customization.
Why Choose Custom ROMs? โ
- Extended device lifespan - updates beyond OEM EOL
- Enhanced privacy - reduced tracking/telemetry
- Bloatware-free - clean system without vendor apps
- Performance gains - better battery, responsiveness
- Deep customization - theming, features, system tweaks
- Faster security patches - community-maintained
- Optional Google services - choose microG/sandboxed Play/none
ROM Categories โ
Privacy & Security Focused: โ
- GrapheneOS - Maximum security for Pixel devices (relockable bootloader)
- CalyxOS - Privacy-first with optional Sandboxed Google Play
General Use & Features: โ
- LineageOS - Most popular, widest device support
- Pixel Experience - Pixel-like UX for non-Pixel devices
- crDroid - Feature-rich with heavy customization
- PixelOS / ArrowOS - Lightweight, clean, frequent updates
- iodรฉOS - Privacy-focused with built-in ad/tracker blocking
Gaming & Performance: โ
- Evolution X - Balanced features and performance
- Project Sakura - Performance-focused builds
Notes:
- GrapheneOS is Pixel-only and supports secure bootloader re-locking. Most other ROMs require leaving the bootloader unlocked; do NOT relock unless the ROM explicitly supports AVB re-lock.
Critical Warnings โ
โ ๏ธ Custom ROM Risks
- Warranty implications - may void warranty depending on region (statutory warranty rights may still apply in some jurisdictions)
- Brick risk - wrong images or wrong partition can hard-brick
- App compatibility - Banking/government apps rely on Play Integrity and may refuse to run
- Your responsibility - updates, security patches, backups, and recovery
- Bootloader re-locking - relocking on unsupported ROMs can hard-brick; only relock when ROM explicitly supports AVB 2.0 with proper vbmeta signing
Prerequisites and Requirements โ
Essential Prerequisites โ
- Unlocked bootloader
- Custom recovery (TWRP/OrangeFox) or ROMโs own recovery
- Compatible ROM - for your exact device codename/variant
- Backup everything - consider both a NANDroid (if supported) and app/data backups
- Stock firmware on hand - for emergency restore (EDL/Odin/Mi Flash/fastboot images)
Required Tools โ
- Latest Android Platform Tools (ADB/Fastboot) from Google
- USB drivers (Windows): OEM or Google USB Driver
- Custom recovery image/installer ZIP (device-specific)
- ROM ZIP/Images + optional GApps (see notes below)
- A computer (Windows/macOS/Linux) and reliable USB cable
Device Preparation โ
- Charge to 70%+
- Use a quality USB cable/port
- Back up user data (Photos, 2FA/keys, eSIM details where applicable)
- Note device info: model, region, codename, current firmware/Android version
- Disable screen lock before recovery if your recovery canโt decrypt data
- Remove Google/Samsung/Xiaomi accounts where FRP/anti-theft may interfere
ROM Selection Guide โ
Decision Matrix โ
| Need | Recommended ROM | Why |
|---|---|---|
| Maximum privacy | GrapheneOS (Pixel) | Hardware-backed security, strict app sandboxing, relockable |
| Privacy + broad app compatibility | CalyxOS | Privacy defaults with optional Sandboxed Play |
| Most devices | LineageOS | Broadest device support, mature updates |
| Pixel UX | Pixel Experience / PixelOS | Pixel look-and-feel on non-Pixel devices |
| Customization | crDroid / Evolution X | Granular feature set |
| Lightweight performance | ArrowOS | Clean, lean builds |
GApps notes:
- LineageOS recommends MindTheGapps; NikGapps also popular.
- OpenGApps is not maintained for the newest Android versions on many devices.
- Many ROMs ship in โvanillaโ (no GApps) and โwith GAppsโ variants. Match to your preference.
Device Compatibility Check โ
Find your device: โ
- CustomROMBay.org
- XDA Forums
- Official ROM websites
Verify model/codename: โ
- Settings โ About Phone โ Model
- adb shell getprop ro.product.device (codename)
- fastboot getvar product
- Beware of regional/carrier variants (e.g., SM-G991B โ SM-G991U)
- Xiaomi anti-rollback (ARB) can brick if you flash older firmware - always match required base firmware
Installation Process โ
There are two primary install flows:
- Recovery-based (TWRP/OrangeFox/Lineage Recovery) via Install or ADB Sideload
- Fastboot-based (images/graphical web installers) - common for Pixels/GrapheneOS
Step 1: Create Complete Backup โ
Backups on modern devices: โ
- TWRP/OrangeFox NANDroid may not fully support dynamic partitions on every device; verify your recoveryโs backup/restore capability.
- Consider Seedvault (LineageOS), Swift Backup (root), or manual data backups.
- Never wipe persist/modem/EFS; losing these can break WiโFi, sensors, IMEI.
Actions: โ
- Boot to recovery
- If supported: Recovery โ Backup โ Select boot/system/data/vendor (avoid super unless advised)
- Copy backups to PC or external storage
Step 2: Download ROM Files โ
- ROM ZIP/images for your exact device/codename
- GApps (if needed; e.g., MindTheGapps for LineageOS or NikGapps)
- Required firmware/vendor packages (Xiaomi/OnePlus often require specific base firmware)
- Optional: Magisk/KernelSU/APatch, custom kernel, modules
Verify downloads:
- Prefer SHA-256 over MD5
- Check release signatures/digests when provided
- Ensure Android version/firmware requirements match your device
Step 3: Prepare Device โ
- Transfer ROM and add-ons to device/SD card or prepare to ADB sideload from PC
- Boot to recovery
- On dynamic partition devices, some operations require fastbootd:
- From bootloader: fastboot reboot fastboot (enters fastbootd)
Step 4: Wipe / Format โ
โ ๏ธ Data Loss Warning
Switching ROM families or coming from stock usually requires a full โFormat Dataโ (not just factory reset), which erases internal storage. Back up first.
- Factory reset for minor updates/dirty flash (same ROM family)
- Full clean install:
- In TWRP/OrangeFox: Wipe โ Format Data (type yes)
- Advanced Wipe: System, Data, Cache, Dalvik/ART Cache
- Do NOT wipe persist/modem/EFS
Note: Recovery decryption varies by device. If your recovery canโt decrypt /data, use ADB sideload or external SD/OTG.
Step 5: Flash Custom ROM โ
Recovery install (typical):
- Install โ Select ROM ZIP โ Swipe/confirm
- Immediately flash GApps (if using a vanilla ROM). GApps must be flashed before first boot.
- Flash add-ons: Magisk (root), KernelSU (kernel-based root), custom kernels, etc.
ADB sideload (LineageOS/others): โ
- In recovery: Apply Update โ Apply from ADB
- On PC: adb sideload rom.zip
- Then: adb sideload gapps.zip (if needed)
- Then: adb sideload addons (e.g., Magisk ZIP if supported by your recovery)
Fastboot images (Pixel/GrapheneOS/Some ROMs): โ
- Use the vendorโs install script or web installer (see ROM-specific section)
- For dynamic partitions, the script may reboot to fastbootd automatically
- Never mix init_boot/boot images incorrectly; follow device-specific docs
AVB/vbmeta (advanced): โ
- Only disable verity/verification if your device/ROM instructions explicitly say so.
- Incorrect vbmeta steps can cause boot failure or brick.
A/B slots: โ
- Generally handled by the installer/recovery. For manual fastboot:
- fastboot getvar current-slot
- fastboot set_active a or b
- Some images support _ab targets (e.g., fastboot flash boot_ab boot.img)
Step 6: First Boot & Setup โ
- First boot can take 5โ20 minutes; donโt interrupt
- Complete setup wizard
- Validate basics: WiโFi, mobile data, calls/SMS, camera, sensors, fingerprint, NFC, Bluetooth, GPS
- For eSIM: activation may be cleared by wipes; check with your carrier before wiping
ROM-Specific Installation โ
GrapheneOS (Pixel Only) โ
Web Installer method:
- Visit https://grapheneos.org/install/web
- Use Chrome/Chromium (WebUSB)
- Follow the guided process (handles fastboot/fastbootd, images, and slotting)
- No custom recovery required
Benefits: Maximum security posture, verified boot, hardened toolchain, Sandboxed Google Play (optional)
Bootloader: Can safely relock on GrapheneOS. Do not relock on ROMs that donโt explicitly support it.
LineageOS (Most Devices) โ
Standard method:
- Download official builds: https://download.lineageos.org/
- Use Lineage Recovery or TWRP/OrangeFox per device guide
- ADB sideload recommended by Lineage docs
- Use MindTheGapps (recommended) or a compatible GApps package if needed
- Seedvault backup integration available
Benefits: Broad support, stable updates, trustable infrastructure
Pixel Experience / PixelOS โ
- Pixel Experience: https://download.pixelexperience.org/
- PixelOS: search official site or XDA thread for your device
Notes:
- Some builds include GApps; others are โvanillaโ
- Install via recovery/ADB sideload; follow device thread instructions
- Monthly security patches common
Post-Installation Setup โ
Essential Configuration โ
- Run updates (Settings โ System โ Updater)
- Restore data (Seedvault, Swift Backup, app-native backups)
- Review permissions and privacy settings
- Configure IMS (VoLTE/VoWiFi/5G) if your carrier/ROM supports it
Privacy Optimization โ
- Disable telemetry/analytics in ROM and apps
- Private DNS (e.g., dns.adguard.com, 1.1.1.1, NextDNS)
- Consider F-Droid, Obtainium, Aurora Store for privacy-friendly app sourcing
- Use a reputable firewall (e.g., NetGuard) and limit background activity
- Be mindful: aggressive adblocking/VPNs may break push notifications; exclude FCM if needed
App Installation โ
- F-Droid - open-source apps
- Aurora Store - access Play Store without Google account
- APKMirror - verify signatures; prefer official dev sources where possible
Banking/Government Apps โ
- Many now enforce Play Integrity API (hardware-backed attestation).
- Magisk DenyList helps hide root from selected apps; Shamiko and โPlay Integrity Fixโ modules exist but may violate app ToS and are not guaranteed to work.
- Respect local laws and app ToS. If mission-critical, consider a non-rooted, stock or relockable-secure ROM profile/device.
Troubleshooting Guide โ
Common Installation Issues โ
Bootloop / Stuck on logo: โ
- Confirm correct ROM for exact codename/variant
- Format Data (not just wipe) if switching ROM families
- Reflash ROM + correct GApps
- Ensure required base firmware/vendor is installed
- Check active slot; try switching slots
- Last resort: restore backup or reflash stock
Decryption issues in recovery: โ
- Use the ROMโs recovery + ADB sideload
- Remove screen lock before flashing (if safe)
- Update to a recovery build that supports your Android version
Missing features (camera/IMS/sensors): โ
- Flash/update required vendor/firmware package
- Check device thread for proprietary blobs/camera fixes
- IMS provisioning varies; some ROMs include toggle/tools
Performance/battery issues: โ
- Clean flash if coming from a different ROM
- Let the ROM settle 1โ3 charge cycles (indexing)
- Update kernel/ROM; consider a known-stable kernel for your device
- Reduce animations; restrict misbehaving apps
Play Integrity/SafetyNet: โ
- Many custom setups wonโt pass strong integrity. Basic/weak may be achievable.
- Passing strong integrity on unlocked devices is typically not possible by design.
Recovery Solutions โ
Emergency Recovery: โ
- Boot to bootloader/fastboot
- For dynamic partitions: fastboot reboot fastboot (fastbootd) if needed
- Flash stock images (Pixel: flash-all; Xiaomi: Mi Flash; Samsung: Odin)
- Qualcomm EDL (9008) is last resort; research carefully or seek professional help
Backup Restoration: โ
- Boot to recovery
- Restore NANDroid (if supported/consistent with current partition layout)
- Or reflash ROM and restore app data from Seedvault/Swift Backup
Staying Updated โ
Update Strategies โ
Manual updates:
- Track official releases/Telegram/XDA/GitHub
- Dirty flash within same ROM family is usually fine for monthly updates
- Clean flash for major Android version jumps or when advised
OTA updates:
- Many ROMs support seamless A/B OTAs
- LineageOS/Pixel Experience often include an Updater app
- If using custom recovery, ensure OTA compatibility (virtual A/B may sidestep recovery entirely)
Community Resources โ
- XDA Developers - device forums, guides, kernels
- r/LineageOS - user discussions
- GitHub Issues - bugs and development
- FAQ & Troubleshooting
- Join Community
Official Resources:
๐ก Custom ROM Success Tips
- Always keep a known-good backup and stock firmware handy
- Read your deviceโs XDA/official thread end-to-end before flashing
- Use the ROM-recommended recovery and GApps
- Never relock your bootloader unless the ROM explicitly supports AVB re-lock
- Verify checksums/signatures for every download
Need more help? Visit our FAQ section or check the main rooting guide for additional troubleshooting and techniques.
Congratulations! Youโve installed a custom ROM.
Whatโs Next? โ
- Add Root Access - Magisk (Zygisk), KernelSU (kernel-based), APatch
- Custom Kernels - performance/battery tuning
- LSPosed Modules - modern Xposed-compatible modules (Zygisk/LSPosed)