If your Pixel is in a boot loop after flashing LineageOS, first identify the exact failure stage instead of flashing another image at random. A phone that remains in fastboot, a recovery that rejects a package, and a system that repeatedly restarts require different checks. The documented procedure used here is specifically for the Google Pixel 4a (codename sunfish) running LineageOS 22.2. Other Pixel models and LineageOS releases can require different firmware, image names, recoveries and commands.
Write down the model and codename, LineageOS version, last successful step, exact screen and every error message. Then use the branch below that matches what you can still access.
As an Amazon Associate I earn from qualifying purchases.
Identify the failure before changing anything
Do not treat every black screen or restart as the same problem. Connect the symptoms to the stage at which installation stopped.
| What you see | Likely stage | First action |
|---|---|---|
| The phone shows the bootloader or fastboot screen, but the computer sees nothing | USB/host detection | Run fastboot devices, then check the data path, drivers or permissions. |
| Fastboot works, but the expected Lineage Recovery does not start | Recovery image or boot procedure | Return to the exact device page and verify that its linked recovery image and prescribed target were used. |
| Recovery starts but rejects the LineageOS package | Firmware, package, device build or transfer problem | Check the required firmware, exact build and the complete sideload error. |
| The package installs, but Android restarts repeatedly or never leaves the startup animation | First-system-boot problem | Check firmware, data formatting and every pre-boot instruction before attempting another install. |
Take a photo or copy the exact text before leaving a screen. “Failed” without the accompanying line is not enough to select a safe remedy.
#1 Best Overall
- Attention-grabbing design meets the latest evolution of the Google Pixel Camera on the new Google Pixel 11 Pro XL; Gemini Intelligence helps manage details so you can live in the moment[1]; and the phone is available in two sizes
- Unlocked Android phone gives you the flexibility to change carriers and choose your own data plan: Works with Google Fi, Verizon, T-Mobile, AT&T, and other major carriers[2]
- Stay informed without looking at your screen: When your phone is face down, Pixel HiLight gently alerts you with subtle glowing lights when your favorite contacts are calling or you’re talking with Gemini; exclusive to Google Pixel 11 Pro phones
- Magic Capture catches the moment as you live it: With just one tap, Pixel 11 Pro captures video and photos, and automatically edits, crops, and unblurs a curated collection, ready to share – and you get the memory of how it felt to be in the moment
- Two new cameras for more brilliant photos: A larger telephoto sensor captures 30% more light for clear, beautiful photos and videos, even in the dark[3]; Pixel’s longest zoom ever helps you capture details from impressive distances[4]
The Pixel model and codename determine the instructions
LineageOS installation pages are written for a particular device. The official page covered here is for the Google Pixel 4a, codename sunfish, LineageOS 22.2. Its image names, firmware requirement, recovery and sequence must not be copied to a Pixel 4, 4a 5G, 5, 6 or another generation. Even two phones sold under a similar name can use different partitions and boot procedures.
Before retrying, open the current LineageOS installation page for your exact model and verify all of these items:
- The marketing model and codename match the phone in your hand.
- The LineageOS release matches the ZIP you downloaded.
- The page’s required firmware version is installed on the phone before LineageOS installation begins.
- The recovery image and the flash or boot target are the ones linked on that page.
- The host-computer setup and remaining steps are written for your operating system.
If any item is uncertain, stop. Do not substitute a command from another Pixel guide or from a forum post. The LineageOS documentation explicitly says, Do not continue after something fails!
Check firmware before you flash again
For the Pixel 4a sunfish LineageOS 22.2 instructions, the required firmware version is Android 13. That requirement is independent of the fact that LineageOS 22.2 is a newer release. Installing with the wrong firmware can prevent installation, cause crashes after installation or permanently damage the device.
Do not generalize Android 13 to another Pixel. The correct version for a different model or release must come from that model’s own official page. If the page requires a firmware update, complete that requirement using the documented method before repeating recovery or sideload steps. If you cannot establish which firmware is present, do not guess based on the Android version you remember using; return to the device-specific prerequisites.
Rank #2
- Google Pixel 10a is a durable, everyday phone with more[1]; snap brilliant photography on a simple, powerful camera, get 30+ hours out of a full charge[2], and do more with helpful AI like Gemini[3]
- Unlocked Android phone gives you the flexibility to change carriers and choose your own data plan; it works with Google Fi, Verizon, T-Mobile, AT&T, and other major carriers
- Pixel 10a is sleek and durable, with a super smooth finish, scratch-resistant Corning Gorilla Glass 7i display, and IP68 water and dust protection[4]
- The Actua display with 3,000-nit peak brightness shows up clear as day, even in direct sunlight[5]
- Plan, create, and get more done with help from Gemini, your built-in AI assistant[3]; have it screen spam calls while you focus[6]; chat with Gemini to brainstorm your meal plan[7], or bring your ideas to life with Nano Banana[8]
If fastboot cannot see the Pixel
A connection failure is different from a boot loop. If the phone is visibly in fastboot but the computer returns no device, changing the ROM or formatting data will not repair the USB path.
- Leave the phone on its fastboot or bootloader screen and connect it directly to the computer.
- Run
fastboot devices. A detected device should produce an identifier; an empty result means the host has not established a fastboot connection. - Disconnect and try another known-good, data-capable cable. The Pixel 4a installation page specifically suggests trying a USB Type-A 2.0 cable or a USB hub when connection problems persist. A charging-only cable is not suitable.
- Try a different physical USB port, avoiding a loose adapter or an unpowered hub unless the documented troubleshooting path calls for a hub.
- Apply the host setup for your operating system. Windows may need the correct USB drivers; Linux and macOS may need the permissions or setup described by the official host instructions.
Once fastboot devices detects the phone, continue with the exact command sequence on the device page. Do not infer the next partition or image from the fact that fastboot now works. A working USB connection only proves that the computer can communicate with the bootloader.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What a cable change can and cannot fix
A different cable, port or hub can resolve a missing fastboot connection or an interrupted transfer. It cannot correct an incorrect device build, mismatched firmware, wrong recovery image, incomplete data format or a damaged installation. If fastboot already detects the phone, spend your time checking the software prerequisites instead of repeatedly buying or swapping cables.
If Lineage Recovery is missing or looks wrong
The recovery environment is part of the device-specific procedure. The Pixel 4a guide instructs you to install or boot the provided Lineage Recovery and verify that Lineage Recovery actually starts. It also warns that other recoveries may not work for the installation.
Use this recovery branch when fastboot detects the phone but you see the stock recovery, an unexpected custom recovery, an immediate return to the bootloader or an error before the LineageOS package can be selected.
Rank #3
- Google Pixel 10 Pro is the ultimate Pixel experience, featuring advanced AI with Gemini, unbelievable camera quality, impeccable design in two sizes, and the next-gen Google Tensor G5 chip[1]
- Unlocked Android phone gives you the flexibility to change carriers and choose your own data plan[2]; it works - Google Fi, Verizon, T-Mobile, AT&T, and other major carriers
- Get a head start on syncing your data before it even arrives: After you purchase your new Pixel, look for an email that explains how to transfer your photos, videos, passwords, and more in just a few quick steps[11]
- Pixel’s pro camera system makes everything look amazing, even in low light; capture more of the scene with advanced Google AI models, and bring out incredible details with 100x Pro Res Zoom, stunning 50 MP images, and super steady videos in 8K[10]
- Pixel 10 Pro is built with durable aluminum and Corning Gorilla Glass Victus 2 for scratch and drop resistance; the 6.3-inch Super Actua display with 3,300-nit peak brightness is easy on the eyes, even in direct sunlight[3,13,18]
- Stop at the failure screen and record its text.
- Reopen the exact guide for your model and codename.
- Compare the recovery file you used with the file linked on that page, including the release and device name.
- Repeat only the guide’s prescribed install or boot action for that recovery. Do not replace a recovery target with
boot,recoveryor another partition merely because a command from a different Pixel appears similar. - Confirm visually that Lineage Recovery starts before proceeding to data formatting or package installation.
If the exact recovery still will not start, preserve the error and seek help rather than improvising partition flashes. A recovery that appears to start but is not the one required by the page can make later errors misleading.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If recovery rejects the LineageOS package
When recovery opens but installation stops with a verification, compatibility or other package error, check the inputs in this order:
- Device build: the ZIP must be for the exact codename, not merely a similar Pixel model.
- Release: the ZIP and the installation page must refer to the same LineageOS version.
- Firmware: for the documented Pixel 4a case, Android 13 is required before installation.
- Transfer: confirm that the file reached recovery completely and that the reported error is not being mistaken for a normal sideload-progress message.
- Sequence: confirm that the required data formatting and preceding steps were completed in the order shown on the page.
Do not bypass a package rejection by forcing an image from another model or by continuing to the first boot. The official documentation’s warning is explicit: Failing to install the correct firmware version prior to installation may result in failure to install LineageOS, unexpected crashes post-installation, or permanent damage to your device!
That warning is tied to the device guide; it is not a reason to assume every Pixel uses Android 13 firmware.
Format data and complete the sequence before the first boot
On the cited Pixel 4a procedure, the expected flow includes starting Lineage Recovery, formatting data in recovery, sideloading the LineageOS ZIP and finishing the remaining instructions before booting the installed system. Formatting data removes the existing user data and is not a harmless troubleshooting toggle.
If you skipped the format, interrupted it, or rebooted into Android before completing the page’s remaining steps, return to the exact guide and redo the sequence from the appropriate point. Do not repeatedly format data without first confirming that the firmware, recovery and package all match. A wipe cannot repair a wrong build or a wrong recovery.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use the page’s own menu labels and commands. Different Pixel generations can place images on different partitions or require different preparation, so this article intentionally does not provide a universal recovery-flash command.
If the Pixel is stuck on the boot screen after installing LineageOS
A first-boot loop means the installation reached the system-start stage, but it does not identify the cause by itself. On the Pixel 4a procedure, check the following before attempting another flash:
- Verify that the phone is really a
sunfishPixel 4a and that the installed package is the LineageOS 22.2 build for that codename. - Verify that the required Android 13 firmware was installed first.
- Confirm that the official Lineage Recovery was used and that it started successfully.
- Confirm that data formatting completed in recovery.
- Review every instruction between the package sideload and the first system boot. An omitted final step can leave an otherwise valid package unable to start.
If the device can still enter recovery or fastboot, keep it there while you collect the information above. Do not keep forcing restarts or flash random images in an attempt to escape the animation. If recovery reports a specific error, use that error and the exact device page to choose the next action.
Distinguish a normal long first boot from a loop
Do not diagnose solely from elapsed time or the logo. A loop is repeated restarts or repeated returns to the same boot screen. A phone that remains on one screen without restarting may have a different problem. Record whether the animation restarts, whether the device returns to the bootloader and whether recovery remains available; those observations determine which installation stage is still working.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Do not diagnose sideload failure from the percentage alone
The cited documentation records a known adb sideload behavior in which a successful transfer can stop at 47% and display a read-command message. That percentage is not, by itself, proof that the package failed.
Best Value
- Google Pixel 10 is the everyday phone unlike anything else; it has Google Tensor G5, Pixel’s most powerful chip, an incredible camera, and advanced AI - Gemini built in[1]
- Unlocked Android phone gives you the flexibility to change carriers and choose your own data plan[2]; it works with Google Fi, Verizon, T-Mobile, AT&T, and other major carriers
- Unlocked Android phone gives you the flexibility to change carriers and choose your own data plan[2]; it works - Google Fi, Verizon, T-Mobile, AT&T, and other major carriers
- The upgraded triple rear camera system has a new 5x telephoto lens - up to 20x Super Res Zoom for stunning detail from far away; Night Sight takes crisp, clear photos in low-light settings; and Camera Coach helps you snap your best pics[3]
- Pixel 10 is designed - scratch-resistant Corning Gorilla Glass Victus 2 and has an IP68 rating for water and dust protection[21]; plus, the Actua display - 3,000-nit peak brightness is easy on the eyes, even in direct sunlight[4]
Judge the result from the phone’s recovery screen:
- Read the complete message shown on the device, not only the computer’s progress line.
- Check whether recovery reports that installation completed or returned an error.
- Only after recovery confirms success should you continue with the remaining device-page steps.
- If recovery reports failure, copy the exact text and stop rather than retrying indefinitely.
A cable problem can interrupt a transfer, but replacing the cable does not make an incompatible package valid. Resolve the specific recovery message against the exact model guide.
A safe retry sequence for the documented Pixel 4a case
Use this sequence only when the phone is the Google Pixel 4a (sunfish) and the target is the LineageOS 22.2 build covered by the official instructions. For every other Pixel, substitute that model’s own sequence.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →- Confirm identity: record the model, codename and LineageOS release.
- Confirm prerequisites: verify the required Android 13 firmware for this Pixel 4a guide and complete any prerequisite update it specifies.
- Establish fastboot: use
fastboot devices; if there is no result, fix the cable, port or host setup first. - Use the linked recovery: install or boot the Lineage Recovery provided by the page and verify that it opens.
- Format data: perform the data-format step in Lineage Recovery, understanding that it erases user data.
- Sideload the matching ZIP: use the exact package and command shown on the page. Treat a 47% computer-side message as inconclusive until recovery states the result.
- Finish the page: complete every remaining instruction before selecting the first system boot.
- Observe the result: if Android starts, set it up; if it loops or returns an error, stop and preserve the evidence for escalation.
When to stop and ask for support
Escalate when fastboot or recovery is available but the exact device guide does not resolve the failure, or when the error does not clearly identify a recoverable step. Include:
- Pixel model and codename.
- LineageOS version and exact package name.
- Firmware version required by and installed for that guide.
- The last step that succeeded.
- The complete recovery, fastboot or host error text.
- Whether the phone can still enter fastboot and Lineage Recovery.
- What cable, port and host operating system were used when detection failed.
Use LineageOS support channels and follow their request for logs or photos. Do not apply a supposed universal “unbrick” procedure: partition layouts, firmware and recovery requirements vary by Pixel model, and an unverified command can turn a recoverable installation error into permanent damage.
Quick Recap
Checklist before you press reboot
- Model and codename match the guide.
- LineageOS release matches the package.
- Required firmware version is confirmed for that model.
- Fastboot detection is stable.
- Recovery is the official image linked for that device.
- Data formatting completed as instructed.
- Sideload result was judged from recovery, not only a percentage.
- All remaining pre-boot instructions are complete.
- Any failure has been recorded before continuing.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
