Flashing a phone replaces its operating system at the partition level, fixing bootloops and corrupted firmware that a factory reset can’t touch. We tested all three major flash tools on a Samsung Galaxy A54, a Redmi Note 12 (MediaTek), and a Pixel 7a over the past month, and documented every step below. Only flash your own device or one you have explicit written permission to modify.
- Odin is for Samsung, SP Flash Tool for MediaTek, and Fastboot for Pixel and Snapdragon phones
- Using HOME_CSC instead of plain CSC in Odin preserves app data during a Samsung flash
- Never flash preloader.bin in SP Flash Tool as it hard-bricks MediaTek devices permanently
- First boot after flashing takes 3-7 minutes and must not be interrupted
- Flashing voids your warranty on most brands except Fairphone
#Stock vs. Custom ROM Flashing
Flashing overwrites the firmware stored in your phone’s internal partitions: bootloader, recovery, system, and sometimes radio/modem. A factory reset only wipes user data and leaves the OS intact, but a flash replaces the OS itself. That’s why flashing fixes corrupted system partitions and bootloops that survive factory resets.
Stock ROM flashing reinstalls the official manufacturer firmware. This is the safest option and the one we recommend trying first. According to Samsung’s firmware flashing community guide, over 80% of Galaxy bootloop cases resolve with a clean stock reflash using Odin.
Custom ROM flashing replaces the stock OS with a community-built alternative like LineageOS or GrapheneOS. This requires unlocking your bootloader and installing a custom recovery first.
Important: Flashing should only be performed on devices you own. Modifying someone else’s phone without their consent violates both manufacturer terms of service and potentially local laws. If you’re having trouble with a phone that isn’t yours, contact the manufacturer or your carrier for official support.
#How Do You Back Up Before Flashing?
A flash wipes everything: contacts, photos, app data, messages. Back up before you start.
Use Google One backup at Settings > Google > Backup and verify the backup completed. For SMS messages, Google One doesn’t always capture everything. Use a dedicated Android SMS recovery tool to export critical messages first. In our testing on the Galaxy A54, Google One restored about 92% of app data after a flash, but authenticator codes and app-specific logins were lost.
Also back up these items:
- Authenticator app codes (export before you lose access)
- WhatsApp chats via WhatsApp’s built-in Google Drive backup
- Any 2FA recovery codes saved in notes apps
Don’t skip this step. No flash tool can recover overwritten data.
#Unlocking the Bootloader
Most Android phones ship with a locked bootloader. You can’t flash custom firmware without unlocking it, and the unlock itself wipes all data on the device.
Enable Developer Options by tapping Build Number seven times in Settings > About Phone. Then enable OEM Unlocking in Developer Options and run fastboot flashing unlock.
Brand-specific differences matter. Samsung devices don’t use fastboot for bootloader unlocking at all. Xiaomi requires submitting an unlock request through their website and waiting 7-30 days before the unlock activates. In our testing, the Xiaomi unlock wait was exactly 14 days for the Redmi Note 12.
Warranty warning: Unlocking the bootloader voids your warranty on Samsung, Google, Xiaomi, and most other brands. A Tom’s Guide analysis of phone warranties found that only Fairphone and a few niche manufacturers explicitly permit bootloader unlocking without warranty consequences. If your phone is still under warranty, consider whether the flash is worth losing that coverage.
#Which Flash Tool Do You Need?
Your chipset determines your tool. Using the wrong one fails at best and bricks the device at worst.
Odin is for Samsung Galaxy phones and tablets exclusively. It’s an internal Samsung tool that was leaked years ago and is now widely available. You load four firmware files (BL, AP, CP, CSC) into their corresponding slots and click Start.
SP Flash Tool handles MediaTek-based devices, including budget phones from Tecno, Infinix, Ulefone, and some Xiaomi models. Check Settings > About Phone > Processor to confirm a MediaTek chip. The SP Flash Tool tutorial on MobiFirms recommends always unchecking preloader.bin before flashing. We followed this advice on our Redmi Note 12 and the flash completed in 12 minutes without issues.
Fastboot works for Google Pixel, most OnePlus devices, and Qualcomm Snapdragon phones. You don’t need third-party software. Google’s official Platform Tools package includes everything. For Pixel phones, the official factory images come with a flash-all script that handles the entire process automatically.
#Flashing With Odin (Samsung)
Download firmware for your exact model number from SamFW. Not “Galaxy S23” but the specific variant like SM-S911B.
Boot into Download Mode by holding Volume Down + Volume Up while connecting USB, then load each file into Odin and click Start. Our Galaxy A54 flash finished in 8 minutes. The extracted zip contains four files: BL (bootloader), AP (system), CP (modem), and CSC (carrier settings), and each goes into its matching Odin slot.
Key tip: Use the HOME_CSC file instead of plain CSC if you want to preserve app data. Plain CSC wipes everything. Most guides don’t mention this distinction clearly.
Odin shows a green PASS banner when done. If you see FAIL, the most common cause is wrong firmware or an interrupted USB connection. Don’t unplug during the flash.
#Flashing With SP Flash Tool (MediaTek)
Install MediaTek USB drivers first. Without them, SP Flash Tool can’t detect your phone.
Extract your firmware and open SP Flash Tool. Click Scatter-loading and select the scatter file from your firmware folder. Uncheck preloader from the partition list. Select Download Only mode.
Power off your phone completely, click Download in SP Flash Tool, then connect via USB while holding Volume Down. A green circle means success. In our testing with the Redmi Note 12, the entire flash took 12 minutes with Download Only mode.
If SP Flash Tool throws a BROM ERROR, it usually means your USB drivers aren’t installed correctly or your USB cable doesn’t support data transfer. According to XDA Developers’ SP Flash Tool troubleshooting threads, BROM errors account for roughly 60% of first-time flash failures on MediaTek devices.
#Flashing With Fastboot (Pixel and Snapdragon)
Download the factory image from Google’s official Factory Images page for Pixel, or your manufacturer’s equivalent for other brands.
Extract the zip, boot your device into Fastboot mode with adb reboot bootloader, and run the included flash script. For Pixel devices, the flash-all.sh (Mac/Linux) or flash-all.bat (Windows) script automates everything. The flash took 11 minutes on our Pixel 7a.
For manual partition flashing, the command is fastboot flash system system.img. Flash each partition individually if the script fails or if you need selective partition replacement.
#Post-Flash Setup and Troubleshooting
First boot takes 3-7 minutes. Don’t force-restart during this window.
Once you reach the setup screen, sign into your Google account and let Google One restore your apps. Test calls, mobile data, Wi-Fi, camera, and GPS. If NFC or Bluetooth aren’t working, you may have flashed firmware for the wrong regional variant.
If the phone gets stuck in a bootloop after flashing, re-enter Download Mode or Fastboot and reflash with verified stock firmware. For severe cases where the phone won’t respond, Android repair software sometimes provides additional recovery options. Samsung users dealing with a Galaxy S10 that won’t turn on after a flash should try a clean reflash with the correct regional stock firmware first.
Phones showing a process system not responding error after flashing usually have a firmware mismatch between the system and modem partitions. Reflashing the complete firmware package fixes it.
#Custom ROMs: LineageOS, GrapheneOS, and CalyxOS
Custom ROM flashing follows the same basic flow but requires installing a custom recovery like TWRP first.
The XDA Developers guide on custom ROM installation is the reference most experienced flashers use. The process: unlock bootloader, flash TWRP via Odin or Fastboot, boot into TWRP, create a Nandroid backup, wipe system/data/cache, flash the ROM zip, flash GApps if needed, and reboot.
In 2026, LineageOS supports 180+ devices officially. GrapheneOS runs exclusively on Pixel phones and focuses on privacy. CalyxOS supports Pixel and Fairphone devices. Check the LineageOS device wiki before committing to confirm your phone is supported.
For less invasive customization, Android root software gives elevated permissions without replacing the OS. SIM unlock code generators may unlock carrier-locked devices without flashing.
If you’ve lost access to the Google account tied to a flashed device, FRP bypass tools can help. Only use these on your own device.
#Bottom Line
Identify your chipset first since that determines whether you need Odin, SP Flash Tool, or Fastboot. Download firmware for your exact model number, back up everything, unlock the bootloader, then flash. The most common failure is using wrong firmware, so verify the model match before hitting Start. Only flash devices you own, and accept that unlocking the bootloader voids your warranty on most brands.
#Frequently Asked Questions
Will flashing void my warranty?
Yes, on most brands. Samsung, Google, and Xiaomi all treat bootloader unlocking as a warranty-voiding action. Fairphone is one of the few exceptions. Check your manufacturer’s specific policy before proceeding, because some brands will still honor hardware warranties even after software modifications if the hardware defect is clearly unrelated to the flash.
Can I go back to stock firmware after a custom ROM?
Yes. Download the official stock firmware for your model, boot into Download Mode or Fastboot, and reflash using the appropriate tool. Your data gets wiped again, but the phone returns to full stock operation and passes SafetyNet checks.
What’s the difference between flashing and factory resetting?
Factory reset wipes user data but leaves the OS untouched. Flashing replaces the OS itself across multiple partitions. If a factory reset solves your problem, don’t flash.
How long does flashing take?
The flash itself takes 5-15 minutes. First boot adds 3-7 minutes. Budget 30-45 minutes total.
Do I need a computer?
Yes. All three tools require a computer connected via USB. There’s no reliable way to do a full system flash without a PC.
What if my phone won’t turn on after flashing?
Boot back into Download Mode or Fastboot and reflash with verified stock firmware. If the device won’t enter any recovery mode at all, you may need a JTAG or specialized hardware tool for recovery. For Samsung bootloops specifically, check XDA’s device-specific subforum where most models have dedicated unbrick threads written by people who’ve recovered the same phone.
Is flashing legal?
Flashing your own device is legal in most countries. In the US, the 2014 Unlocking Consumer Choice and Wireless Competition Act protects your right to modify your own phone’s software. However, flashing a device you don’t own or bypassing carrier locks on phones you’re still making payments on can violate terms of service or local laws. Always flash only your own fully-paid-off devices.