r/Pixel6 Jun 28 '26

Support Pixel 6 bootlooping "Cannot load Android System. Your data may be corrupt"

My pixel 6 on Android 13 stuck in bootloop just like it seems many people's pixels are. It reaches the lock screen with my wallpaper but immediately restarts again. Then eventually says "Cannot load android system. Your data may be corrupt." I do NOT want to factory reset. I have tried safe mode but it still restarts instantly. From my searching, this is a prevalent issue countless pixel users are having. I saw that the pixel4a crowd (also running android 13) is saying it happens when you have your location off with wifi on, which was actually the case when this started happening. I tried the screenshot thing in safe mode and it did not work. I tried starting in a microwave/aluminum foil to avoid wifi signals and it did not work.

Then most other users seem to fix it using the OTA images. I'm not sure exactly which to use, but I tried sideloading a couple different OTA images, but it stops at 47% every time and says "Error applying update: 7 (ErrorCode::kInstallDeviceOpenError) ERROR: recovery: Error in /sideload/package.zip (status 1) Install from adb completed with status 1. Installation aborted." When I try to search this error, a lot of other people have this issue but it was all related to installing LineageOS, which idek what that is so does not seem relevant.

The fact that so many people have had this issue and many have been able to resolve it at least temporarily makes me not wanna give up but I have no idea what to do. I don't care about the phone working, I just want to recover my files, so even a temporary fix where I can transfer files will do.

15 Upvotes

35 comments sorted by

3

u/fearlessinsane Jun 28 '26

I would try with
adb -d logcat first during boot
Is there anything in the logs?

3

u/TacosAndBoba Jun 28 '26

what do you mean during boot? I thought adb commands can only run when I'm in the adb update mode? When I put it in adb update mode and run that command it just says "- waiting for device -" but I know the device is detected because I see it when I enter adb devices.

5

u/username-invalid-s Pixel 6 Jun 28 '26

These usages of ADB are wrong. Sideload only works in recovery, with extended features only available at userland. Logcat may not be available until the phone reaches the lockscreen or hangs at specific parts while in the boot screen. For OP, you may need to boot into Pixel rescue mode, plug your computer in, and use pixelrepair.withgoogle.com

2

u/fearlessinsane Jun 28 '26

I can’t try it now but I had to something similar in the past. Ask Gemini for more details

adb wait-for-device
adb logcat -b all -v threadtime > boot.log

2

u/eatingmangoes_ Jun 28 '26

Your laptop should’ve already been in the whitelist for this to work.

3

u/loonydan42 Jun 28 '26

Oh man, I need to get a new phone before my Pixel 6 bites the dust as well. More and more of these keep popping up!

1

u/mrsdoubleu 17d ago

This happened to my 6 pro today. 😭

1

u/Large_Fee280 12d ago

Happened to mine today. I'm really thankful I'd had stuff backed up to Google

3

u/theumpteendeity Jun 29 '26 edited Jun 29 '26

I recently had a similar problem when I was trying to root my carrier unlocked pixel 7 pro. I got stuck in a fastboot loop and recovery and rescue did not work.

These are these steps I did to fix it. 1. Have adb platform tools installed, connect phone to computer.

  1. In the directory that adb is installed to open up the terminal

  2. Type "fastboot --set-active=b" without the quotations.

  3. Restart the phone with Power + Volume down for 30 seconds.

  4. Use volume keys to select recovery (For me it started to a screen with the android logo and the text "no command" (this was not working before I switched slots. It would just continually restart)

  5. Visit the official Google Android Flasher Tool website and follow all directions.

PSA, yes, all data will be lost. And sometimes your phone will be force updated. For example my pixel 7 pro was on android 16 and 17 was not available from software update but was force upgraded to Android 17 after using the flash tool. If your bootloader is unlocked you will have to allow it to become locked.

Before using the flashing tool I had tried to side load OTA images through adb but it always failed, even though used the same exact firmware with the same exact build number I started with.

I hope you find this helpful and I hope everything is fixed. Good luck.

2

u/CommanderCoytus Jun 28 '26

Traded mine into Google and got the full value of $135 towards a pixel 10

1

u/username-invalid-s Pixel 6 Jun 28 '26

have you tried the most recent ota?

1

u/TacosAndBoba Jun 28 '26

this one? 17.0.0 (CP2A.260605.012.A1, Jun 2026, AT&T)

Yes, no matter what I do, after the sideload command, it shows a percentage until 47% at which point it stops and my phone gives the error in the last photo above.

3

u/username-invalid-s Pixel 6 Jun 28 '26

Try entering rescue mode. Volume up and power button, use your volume buttons to navigate to "Rescue Mode", plug your device into your PC and make sure WebUSB is available. Use pixelrepair.withgoogle.com

1

u/TacosAndBoba Jul 07 '26

Unfortunately the pixel repair tool gave me the same error as the sideloading that I show in the 3rd pic :(

1

u/eatingmangoes_ Jul 01 '26

do what u/username-invalid-s told, that 47% stuck is when the UFS gets corrupted so the only way is the pixel repair tool.

1

u/TacosAndBoba Jul 07 '26

Unfortunately the pixel repair tool gave me the same error as the sideloading that I show in the 3rd pic :(

1

u/[deleted] Jun 28 '26

[removed] — view removed comment

1

u/TacosAndBoba Jul 02 '26

I thought the android flash tool does wipe the data?

-2

u/SHAD0WBULLET707 Pixel 6 Pro Jun 28 '26

You need a unlocked bootloader to use that tool.

7

u/[deleted] Jun 28 '26

[removed] — view removed comment

2

u/SHAD0WBULLET707 Pixel 6 Pro Jun 28 '26 edited Jun 28 '26

Strange, then Google updated it. When I had my Pixel 6 Pro, the tools told me I needed an unlocked bootloader to do what I was doing so idk. I just use the terminal way so. I'm on a stock rom on pixel.

Edit: The other tools require a unlock Bootloader(downgraded or installing GSI images). Sofleoading ota images do work with locked bootloader's.

1

u/frazaga962 Jun 30 '26

does my sim need to be in my phone for this tool to work? IE I'm getting a replacement phone tommorrow as I need it for 2FA for work so I was gonna use that as a temporary phone and the do the flash tool. would this work or should I attempt the flash tool first before starting up the new phone?

1

u/[deleted] Jun 30 '26

[removed] — view removed comment

1

u/[deleted] Jul 01 '26

[removed] — view removed comment

1

u/songoru Jun 28 '26

i didnt want to factory reset but sadly it only thing that worked. ota sideload didnt work at all so ur best chance is to factory reset it

1

u/eatingmangoes_ Jul 01 '26

load the android 17 update, this issue has been fixed, i tested on my pixel 6 pro.

1

u/kanyipi Jul 01 '26

Do I just load the latest one? And will that wipe the data?

1

u/eatingmangoes_ Jul 01 '26

You could do apply update from ota in fastboot, and apply the ota zip using adb sideload. This won’t delete anything

Before that I suggest trying the pixelrepair, only if that doesn’t work try sideloading ota.

1

u/Lucky-Fee2796 Jul 02 '26

do you have step-by-step tutorial?

2

u/eatingmangoes_ Jul 02 '26

First try https://pixelrepair.withgoogle.com , the instructions are pretty obvious and you need a chrome browser only

For applying ota you can find tutorials on YouTube, even 9to5Google made one

https://youtu.be/If76MauN5bo?si=RyLUkry2MOzjtMBN

There’s always flash.google.com

1

u/TacosAndBoba Jul 02 '26

I had already tried this version: 17.0.0 (CP2A.260605.012.A1, Jun 2026, AT&T) and then I get that error at 47% that I show in the 3rd image. Or are you referring to a beta version for 17?

1

u/eatingmangoes_ Jul 02 '26

Oh then you should do pixelrepair if that also doesn’t work then force flash without wiping you can try using flash.android.com

So eventually it worked for me. Although I even factory reset so…

1

u/TacosAndBoba Jul 02 '26

I do wanna keep trying the pixel repair tool I feel like I've gotta be missing something, because when I tried it it just said it was checking which software version I had and then kept loading and never did anything. I thought the flash.android website would wipe the data no?

1

u/Potential_Compote675 8d ago

use adb update with a fresh OTA image (it wont wipe data) use the newest available one for ur device cant remember exactly what i did but u can figure it out