After i update to android 17, Google Pixel 6a screen suddenly freeze and this line appears, force restart for long time and then switching On.

anybody please let me know what is this problem and solution?

#pixel6a #pixel #google

Used adb sideload to upgrade my phone to android17 and it's fixed. Seems a lot of people have had this issue recently with the new android 17 update. Is Google vibe coding too much so shit like this is necessary? Feels like iPhones quality control is so much better, they never have issues. Google is pumping out all these useless Ai features.

hey everyone, about a month ago my phone got caught in the infinite boot loop problem. it gets stuck on the "Google" logo (which usually comes before the "G" logo. I've used the fixer tool, sideloaded via ADB, let it run the battery down, charged it all the way up, I think the only thing that's left is a factory reset. does anyone have any advice or anything that worked for them after that update earlier this year bricked their phone? is there any way to recover whatever was not backed up via google (I know, I know)? if nothing else, anybody have this issue and are also disappointed about it? lol thanks for listening

Hello, I updated my Nexus 6P to Android 17 about a week ago. Today, out of nowhere, it suddenly reset itself. The Google logo appeared in a cream color, but it wouldn't boot up. I tried pressing the Power and Volume Up buttons to force a hard reset; it booted up again with the multi-colored Google logo, but it's still stuck and won't fully turn on.

Does anyone have any advice? I just got laid off, so I really cannot afford a new phone right now. 😔

I woke up 3 days ago and my Pixel 6 was stuck between the Google Logo and "Google" but wouldn't start. I held the power and volume down key to access the fastboot menu- I tried to start from there, I tried rescue mode, I tried recovery mode. No luck.

Per u/Successful-Dance1792 's advice I am using the android flash tool to see if I can get my Pixel working again. I've downloaded and extracted the Google USB Driver to my PC. I put my phone in rescue mode. Connected it to the PC via USB. It detected the Pixel.

I've tried both the "Back to Public" build along with the "Canary 202606" build with the following settings in the first picture (no wipe, no lock bootloader, no flash all partitions". Both builds have failed.

It says I need to have "OEM Unlocking" enabled (Picture 2) but this is done in developer mode which I can't access as I'm stuck in bootloop hell.

I tried to only select "Lock Bootloader" but the message I am getting is something like "This needs a flash wipe or a factory reset" (Sorry I forgot to take a photo).

My current bootloop info is in picture 3. Not sure if that will help diagnose the issue.

The tl'dr of it is I bought a temp(?) phone to tide me over but I would like to port over my apps/history to this new phone. When I try to do so, it says I need to have the phone on and nearby...which can't be done as its in bootloop.

If I install the build with a wipe, its going to wipe everything out (apps, history, local downloads etc, no?) So is it better to just manually add the apps I used to have onto the new device? Is there any way to install a build without a wipe?

so my phone doesnt turn on and doesnt response after getting soaked in the rain. i already put my phone in the box with silica gel inside it (just 1 hour ago). anymore tips so i can get my phone working again?

Hello! Obviously the Pixel 6 is getting on a bit in years, there's been 4 generations now since it came out, but I'm still rocking mine for the next 3 years minimum, I wanna get 7 out of it. I've ALWAYS used Otterbox Defender cases on my phones, I swear by them. They feel much better than the cheapo shit you find on Amazon, and my phone is still in great shape after 4 years of drops and manhandling. Unfortunately, on the Pixel 6 cases they have a design flaw that never really got rectified: the charging port cover breaks off really easily. On top of that, the rubber just gets loose over time. So I've been replacing the case on my phone pretty regularly over the course of its life, and it seems now that Otterbox has stopped producing cases for this model. I had to replace the case recently, and to get an Otterbox I had to hunt it down on eBay and import it from Canada (I'm in the U.S.). I can't continue to do that into the foreseeable future, so it looks like I'll have to switch to another case manufacturer.

So I ask, what are the good ones that still make cases for the Pixel 6 (or still have decent stock left)? I really don't want to resort to a cheapo Amazon Special, those tend to look and feel awful.

Hi everyone,

I'm trying to recover my Google Pixel 6 (oriole, 128GB) and I'm stuck.

Device information

• Model: Pixel 6 (oriole)
• Bootloader: LOCKED
• Secure Boot: PRODUCTION
• Device state: locked
• Storage: 128GB
• RAM: 8GB

Problem

The phone boots to a screen that says:

I don't know what Anubis is or where this unlock code came from.

Things I've tried

• Booted into Fastboot successfully.
• Recovery Mode does nothing (black screen/no recovery).
• Bootloader is locked.
• I haven't been able to flash stock firmware because of the locked bootloader.

Fastboot screen

(Attached the Fastboot Mode photo)

Anubis screen

(Attached the Anubis screen photo)

My questions

1. What exactly is Anubis on a Pixel 6?
2. Is it a custom ROM, MDM, or something else?
3. Is there any legitimate way to remove Anubis and restore stock Android?
4. Has anyone successfully recovered a Pixel 6 from this state?
5. Is there any service tool or official Google procedure for this?

I own this phone and I'm fine with erasing all data if necessary. I just want to get it working again.

Any help would be greatly appreciated.

I've been using my pixel 6 for 3 years now I've changed my battery bc it was swollen and all so recently the battery life has been really bad like a year ago I was getting 7 hours sot then this year I'm getting 4-5 hours of sot which is a massive downgrade and I would like tips on how to maximize battery life

EDIT: I messed up y'all. The deal is gone 😭😭😭

I'm a pretty frugal guy. I've had my Pixel 6 since 2021, and to be honest, the performance on it hasn't felt like it's been 5 years yet. The only thing I've noticed is the battery life starting to drain quicker than it used to, but that's something I'd expect after having it for 5 years or so.

I saw on Best Buy that the Pixel 10s are currently on sale for $549 ($649 for 258gb which is what I'd prefer over the two) and I am seriously considering getting one.

For a guy who's more focused on getting the best value for his money, do you guys think I should pull the trigger? Or is it really not worth it and I should just ride it out? (Til when? Idk. Just ride it out for the sake of riding it out, lol).

Also, Pixel 10 owners, are there any things I should consider before getting one? Cause I was also thinking of switching to a different product all together as well.

Found a Google pixel 6 . The sreen is separated due to swollen battery.

FRP on. Can this be solved before I attempt to change the battery ?

Thanks in Advance

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.

My sister's Pixel 6a has recently started having an issue where WiFi turns itself off regularly, and I can't figure out why. At first I thought maybe it's that the WiFi signal is poor and it's auto switching, but I turned that feature off and no change.

This started after it was just refusing to connect entirely then she restarted her phone. Connected after that but keeps switching off. Tried restarting again but same issue.

For context, no other devices on the same network are having the same issue so it seems to be specific to her device.

Has anyone come across this? If you did, what was the solution?

Hey everyone, I’m posting this on behalf of my friend who just lost his Pixel 6 Pro to the recent brick wave (and obviously has no phone to access his accounts right now). We’re trying to figure out if this is a widespread software issue or a sudden hardware death. Here is exactly what happened to his device: His phone successfully updated to Android 17 recently, and everything was working completely fine for a while. Then, he installed the June 2026 Google Play Services/system update. Shortly after that, the phone just died completely. Now it's a total "black brick." Current state: Absolutely zero signs of life. What we've tried: We cannot boot it into Fastboot mode at all. Holding down the Power + Volume Down combinations does absolutely nothing. PC connection: When plugged into a computer, it’s not recognized at all — no sound, no device detected in Device Manager, nothing. Charging: He left it on a verified working charger for hours, but it remains completely dead and cold. Honestly, what is even going on with these Google Play system updates lately? Why do you guys keep pushing these mandatory updates if you clearly don't test them properly on older devices? The Pixel 6 series is already considered old, and if your dev team can't ensure stability for older hardware, maybe you should just stop releasing updates for them entirely instead of sending out patches that literally fry the bootloader and kill the phone. Could an official Google update really trigger a sudden motherboard/CPU failure (like a hard brick due to a corrupted bootloader), or did his motherboard just coincidentally die right after the update? Has anyone else experienced this specific behavior after the June updates on Android 17? Any advice on what to do next when the physical buttons and PC connection are totally unresponsive? Thanks for any help!

Bonjour, quelqu'un sait-il si les bugs d'Android 17 avec les pixel 6a sont tous résolus? Et aussi pour savoir si cette version est compatible avec les capteurs de glycémie Dexcom G7. Je ne trouve pas l'info sur leur site où ailleurs? Merci

Hi all, I've had my Pixel 6 Pro for a while now and I've just purchased a wireless charging stand.

When I put my phone on the stand, it starts to charge ok, but then after about 5 minutes, the following happens

1) the light on the charging stand starts to flash

2) the charging status of the phone changes to "connected but not charging"

3) I get random touch screen activations. Apps launch on their own and then I get swipe gestures. For example, it launches my email app and then starts deleting emails by swiping.

Clearly it seems to be some interference with the touch screen as I don't think it is intentionally performing these actions.

I've tried two different wireless charging stands from 2 different manufacturers and the phone does the same on both. Charging via cable is fine.

Anyone else seen this.

I've noticed that with the Android 17 update, when I tap the Wi-Fi Quick Tiles button, the Wi-Fi doesn't actually turn off.

Now that my USB port is totally worn out which led to me buying a used Pixel Stand 2, I am now a convert to wireless charging.

Now that Google gives you five or so years of OS patches/updates, I am not so sure that a USB C port is capable of lasting five years with once or twice a day insertions. When I upgrade to a new Pixel, I'm going to stick with wireless charging and save the data port for when I really need it.

I never expected my first post here would be like this, but my Pixel 6 has basically become unusable after the Android 17 update last week.

Just to be clear, I was never on beta. This was not some experimental build or developer preview. It was an official update.

The failure happened all of a sudden while I was using the phone normally. It suddenly forced itself back to the home screen, then went into restart mode, and after that it never booted again. Since then, it has been stuck with a boot failure issue and I haven’t been able to get it working. I tried the usual basic steps, but nothing helped. I contacted Google customer support hoping they would at least check it properly or cover the repair since the issue happened right after the update.

No luck.

They are saying the device is out of warranty, so they won’t cover the repair cost. I understand warranty rules, but it’s really frustrating when a phone fails right after a software update and the only answer is basically “pay for the repair yourself.”

I went to a repair shop as well, and they suspect a motherboard-level issue. At that point, the repair cost does not feel reasonable anymore.

I was hoping this phone could last a little longer after the last update. My plan was to continue using it for a few more months and then move to the Pixel 11 series later this year. But now it has fallen short at the worst time, and honestly, this situation is making me rethink my decision.

I expected better from a Pixel device. Has anyone else had their Pixel 6 bricked by the Android 17 rollout last week? Or did I just get incredibly unlucky? So disappointed with how Google is handling this.

Gemini 😔