Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If you have a boot loop after flashing LineageOS, a LineageOS install failed message, or a Pixel stuck on the boot screen after installing LineageOS, stop flashing and identify the exact failure state first. The correct recovery image, firmware, package and command sequence depend on the Pixel model, device codename and LineageOS release.
The documented example in this guide is the official installation procedure for Google Pixel 4a (sunfish) running LineageOS 22.2. Do not apply its firmware requirement or flashing commands to another Pixel. Record the phone’s model and codename, LineageOS build, last successful step and every error shown on the computer or in recovery before retrying.
Start by identifying what actually failed
A phone that cannot be detected in fastboot needs a different remedy from a package rejected by recovery or a system that restarts during its first boot. Use the screen that remains visible and the exact message as your starting point.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →| What you see | Failure stage | What to record | First action |
|---|---|---|---|
| Bootloader or fastboot screen remains visible | Computer connection or bootloader stage | Output of fastboot devices, cable and port used, host operating system |
Check the USB data path and host setup before changing software |
| Computer sees fastboot, but the expected recovery does not start | Recovery image or boot target stage | Exact image named by the device guide and the screen reached after booting it | Return to the exact device page and verify its recovery image and prescribed target |
| Recovery opens but rejects the LineageOS package | Package, firmware or device-build stage | Full recovery error, package filename, model/codename and required firmware | Stop; verify the package and firmware against the model-specific guide |
| Transfer appears to stop at a percentage | ADB sideload reporting stage | Percentage, terminal message and the result displayed on the phone | Judge success from recovery’s result, not the percentage alone |
| LineageOS logo appears, then the phone restarts repeatedly | First system boot | Whether data was formatted, firmware version, recovery used and every completed instruction | Re-check the complete device-specific sequence before repeating anything |
Do not continue after a step fails. The official LineageOS device documentation explicitly says, “Do not continue after something fails!” Continuing can replace useful evidence with additional, unrelated errors.
#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]
Confirm the Pixel model, codename and LineageOS build
Before using any image or command, write down all three identifiers:
- The commercial model name, such as Google Pixel 4a.
- The device codename, such as
sunfishfor the Pixel 4a covered by the cited instructions. - The exact LineageOS release and build, such as LineageOS 22.2 for that guide.
“Pixel” is not a single installation target. Different generations can use different recovery images, firmware baselines, partition procedures and package names. A command that is correct for one codename can fail on another or, worse, write an incompatible image. If you cannot establish the codename from the phone’s documentation or the official device page, do not guess from the model’s marketing name.
Also record whether the failure occurred while booting fastboot, starting recovery, sideloading the ZIP or entering the installed system. That sequence determines which part of the official guide must be checked. Screenshots or a verbatim copy of the error are more useful than a description such as “it did not work.”
PC 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 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteCheck the required firmware before retrying
For the Google Pixel 4a (sunfish) instructions for LineageOS 22.2, the required firmware version is Android 13. That requirement is specific to that device page; it is not a universal firmware rule for Pixels or for every LineageOS release.
Do not infer the required firmware from the LineageOS version number. The release may be newer while the installation page still requires a particular Android firmware baseline. Locate the firmware requirement on the exact page for your codename and release, then compare it with the phone before attempting another install.
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]
The official documentation warns: “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!” Treat that as a stop condition. If your model’s guide specifies a different version, follow that guide rather than substituting Android 13.
If fastboot cannot see the Pixel
A fastboot connection problem is a host-to-phone communication failure. It is separate from a boot loop caused by an incorrect ROM, firmware or recovery. First leave the phone at its bootloader/fastboot screen and run:
Recommended Free Tools
fastboot devicesThe command should return a device entry. If it returns nothing, or the terminal reports a connection error, work through the physical and host checks below before changing any partitions.
Check the cable and USB path
- Use a known data-capable cable, not a cable intended only for charging.
- Try a different USB port directly on the computer.
- If the current path is USB-C, try the USB Type-A 2.0 cable or USB hub approach suggested by the Pixel 4a installation page when connection trouble occurs.
- Remove unnecessary adapters and docking hardware while testing.
- Confirm that the connector is fully seated on both ends.
A different cable can make an undetected fastboot device visible, but it cannot repair an incompatible LineageOS package or firmware. Once fastboot devices works, return to the exact device guide; do not improvise a flash sequence merely because the connection is restored.
Check the computer’s setup
Host configuration is operating-system dependent. Windows users should verify the Android USB driver setup required by the official installation instructions. Linux and macOS users should verify the permissions and host setup described by the relevant official documentation. Keep the original error and the output of fastboot devices when asking for help; “the phone is not detected” without that context is difficult to diagnose.
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]
If the expected recovery does not start
Recovery is not interchangeable across Pixel generations. The Pixel 4a page directs users to install or boot the recovery image provided on that page and to confirm that Lineage Recovery starts. Other recoveries may not work with the documented procedure.
- Return to the installation page for your exact codename and LineageOS release.
- Compare the recovery image you downloaded with the image linked on that page. Check the filename and release rather than relying on a similarly named file found elsewhere.
- Follow the page’s prescribed method and target for installing or booting recovery.
- Confirm visually that Lineage Recovery starts before attempting the next installation step.
Do not copy a recovery, boot or other partition command from another Pixel guide. Partition layouts and boot targets are model-specific, and the device-specific instructions do not establish a universal command that is safe for every Pixel. If recovery still does not open, stop at that stage and seek help with the exact model, image name and fastboot output.
If recovery rejects the LineageOS package
A rejection in recovery generally means the package, device identity, firmware state or installation sequence does not match what the guide expects. Capture the complete error exactly as shown. Then verify these items in order:
- Device match: the package is for your Pixel codename, not merely for a similar-looking Pixel model.
- Release match: the package belongs to the LineageOS version named by the installation page you are following.
- Firmware: the phone meets the required firmware version for that page. For the documented Pixel 4a/sunfish LineageOS 22.2 procedure, that is Android 13.
- Recovery: Lineage Recovery from the exact page is running.
- Data state: the required data format step was completed in recovery.
- Sequence: every instruction before the first system boot was completed in the order specified.
Do not solve a package rejection by trying random ZIPs, an older recovery or a command copied from a forum post for another device. If the guide’s package still fails after those checks, preserve the error text and escalate rather than cycling through unverified images.
Format data when the device guide requires it
The Pixel 4a installation flow includes formatting data in recovery before sideloading LineageOS. Formatting is not the same as simply deleting a downloaded file or performing an ordinary restart. It changes the phone’s data state and can erase user data, so make sure any recoverable files have already been copied off the device.
Use the exact menu labels and order displayed in the device-specific LineageOS instructions. If the guide for another Pixel uses different wording or a different point in the sequence, follow that guide instead. If you are unsure whether the format completed, stop and verify the recovery screen rather than proceeding to first boot.
Understand the ADB sideload percentage message
A sideload transfer can appear to stop before reaching 100 percent even when the operation has succeeded. The cited LineageOS documentation records a known adb sideload behavior in which a successful transfer may stop at 47% and show a read-command message.
Therefore, 47% is not by itself proof of failure. Check the result printed on the phone in Lineage Recovery and read the complete terminal message. A recovery success result and the documented 47% behavior are different from an explicit verification, signature or package error. Record both sides before deciding what to do next.
If recovery reports an actual failure, do not repeatedly resend the same package without checking the model, release, firmware and data-format steps. Repetition does not correct a mismatch and can obscure which attempt produced which error.
If the Pixel is stuck on the boot screen or keeps restarting
A Pixel stuck on the boot screen after installing LineageOS is a first-boot failure, but the cause cannot be identified from the animation alone. Re-check the installation as a sequence:
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]
- Confirm the commercial model and codename.
- Confirm the LineageOS release and package were intended for that codename.
- Confirm the firmware requirement. For the documented Pixel 4a/sunfish LineageOS 22.2 guide, verify Android 13.
- Confirm that the provided Lineage Recovery was used and actually started.
- Confirm that data formatting was completed in recovery.
- Confirm that sideloading produced a success result on the phone, even if the computer displayed 47%.
- Confirm that all remaining instructions on the device page were completed before choosing the first system boot.
If one of these facts is unknown, return to the relevant step in the official guide instead of assuming the phone is permanently damaged. A boot loop after an incomplete sequence can look identical to a boot loop caused by firmware mismatch, so the exact error and completed steps matter.
Use the official sequence for the documented Pixel 4a example
For Google Pixel 4a (sunfish) with LineageOS 22.2, the documented flow has these high-level stages:
- Verify the required Android 13 firmware before installation.
- Install or boot the recovery image supplied by the Pixel 4a device page.
- Check that Lineage Recovery starts.
- Format data in recovery as instructed.
- Sideload the LineageOS ZIP using the command and filename specified by that page.
- Read the recovery result and distinguish a real error from the known 47% sideload reporting behavior.
- Complete the remaining instructions on the device page.
- Only then boot the installed system.
This is a description of the cited Pixel 4a procedure, not a universal Pixel recipe. The exact recovery target, filenames, firmware and order for another model must come from that model’s current LineageOS installation page.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What not to do while troubleshooting
- Do not continue past a failed step; the official documentation specifically instructs you to stop.
- Do not treat every Pixel as the same device.
- Do not substitute Android 13 firmware unless your exact device page requires it.
- Do not flash a recovery or partition image because its filename looks familiar.
- Do not diagnose a boot loop from a sideload percentage alone.
- Do not assume a new USB cable fixes an operating-system or firmware mismatch.
- Do not repeat a failing command while changing several variables at once; you will lose the ability to identify the cause.
When and how to escalate
Escalate when fastboot or recovery is available but the exact device guide does not resolve the failure, or when the guide’s required image and firmware checks pass but recovery still reports an error. Use LineageOS support channels and include:
- Pixel model and codename.
- LineageOS version and exact package filename.
- Firmware version.
- Whether Lineage Recovery started.
- Whether data formatting completed.
- Output from
fastboot devices, if relevant. - The full recovery and terminal messages, including the sideload percentage.
- The last step that completed successfully.
Do not ask for or apply a generic “unbrick” procedure without identifying the device. A model-specific recovery path may be safe for one Pixel and wrong for another. Keeping the phone in the state that produced the error preserves information that support volunteers can use.
Quick Recap
Pre-retry checklist
- Identity: model and codename confirmed.
- Build: LineageOS release and package match the exact device page.
- Firmware: required version verified; Android 13 applies only to the cited Pixel 4a/sunfish LineageOS 22.2 instructions.
- Connection:
fastboot devicesdetects the phone when fastboot is required. - Recovery: image comes from the exact device page and Lineage Recovery starts.
- Data: required format completed and important files backed up.
- Sideload: recovery result read on the phone; 47% alone not treated as failure.
- Sequence: every pre-boot instruction completed before starting the installed system.
- Evidence: full errors and the last successful step saved for escalation.
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.
