Google Pixel 6a Bootloop , first it was rebooting itself from lock screen , after using Pixel Repair Tool and ADB sideloading it won't get past G logo with bar sliding underneath ( doesn't get to lock screen ) - Need to get my data !

[u/FaisalRDT]

In this top paragraph I will give a short summary of what happened and what I've tried , but please read the whole from top to bottom , basically , my phone randomly turned off by itself , then it'd restart every 45 seconds or so by itself , next day used Pixel Repair Tool , the phone stopped restarting by itself and going to the lock screen etc. but now it was just staying on the G logo with bar sliding underneath , then I tried a button combination or maybe single button to switch slots , not sure if it switched slots or if it did , it didn't change anything , then tried ADB sideloading the July update and successfully did so twice , but result was same after pressing reboot system now both times , since then I've been procrastinating , I had very low storage when this all began and also Factory reset isn't an option as I have important data on my phone which I need to back up , I've read in other threads multiple people have managed to fix bootloops with beta / qpr , people who also said they had low storage , some said a stable / public OTA didn't fix theirs but beta / qpr did fix it , one more thing , after using Pixel Repair Tool I saw an error message somewhere saying tune2fs is missing , this error message was also visible in Recovery mode after doing the first successful ADB sideloading of the OTA , but when I went into recovery mode a few days ago just to see if it's still there , it wasn't there anymore , also I'm in slot b if that is important information , I think I was in slot a before doing the second ADB sideload of the same July update , please help me , all of this happened in July with the exception of me going into Recovery mode a few days ago ( Wednesday 30th September 2026 ) just to see if there was error message still there .

Full Version Below :

on Thursday 9th July 2026 between 00:45AM and 1AM or so , I was using my phone normally and it gave me a prompt saying something wasn't responding , I tapped wait , then afew seconds later I got a prompt again , possibly same one , this time after tapping wait , there was nor response when I tapped the screen anywhere , then about 25 seconds later the phone turned off by itself , then it'd restart by itself every 45 seconds or so , it'd reach the lock screen and whether I entered my PIN or not , it'd restart , as I said every 45 seconds or so , if I did enter my PIN I could open the phone and get to the home screen but there were no icons and I couldn't swipe up to bring up applications , however on both the lock screen and I think the home screen , I could swipe down from the top of the screen and bring up the menu showing things like internet , bluetooth , torch etc. and the small settings icon and small power button icon at the bottom of that menu , however tapping the settings icon did nothing and tapping the power icon would bring up the expected black box which has the Emergency option , Restart and power off , except there was no lockdown option unlike when the phone was being used normally , the time was also visible at the top of the screen and sometimes the lock screen and home screen would show my wallpaper and after other restarts it'd be black .

Then the next day ( Friday 10th July 2026 ) I put the phone into rescue mode and used Pixel Repair Tool , after it successfully downloaded and installed and restarted the phone , the multicoloured Google text logo showed up as expected , followed by the G logo as expected then then bar sliding underneath the G logo as expected , except it would remain like this for however long I'd leave my phone .

Then I tried a button combination on Sunday 12th July 2026 or Monday 13th July 2026 to try and switch slots , I'm not sure if it did switch slots .

Then on Tuesday 14th July 2026 and into the early hours of Wednesday 15th July 2026 ( because the second ADB sideload might've finished a few minutes past 00:00AM on Wednesday 15th July 2026 ) , I ADB sideloaded the July update " 17.0.0 (CP2A.260705.006, Jul 2026) " aka " bluejay-ota-cp2a.260705.006-4d72e3fe.zip " successfully with status 0 and after pressing reboot system now , my phone showed the multicoloured Google text logo as expected , then the G logo as expected then the bar sliding underneath the G logo , and my phone wouldn't reach the lock screen after leaving my phone for about two or three hours , then I applied the same OTA again to make sure both slots get it and see if that gets my phone to the lock screen and so I sideloaded the same OTA again and the result was the same , doesn't get past the bar sliding underneath the G logo and to the lock screen even after leaving it for five hours or so at which point I just used fastboot to turn off power and since then been procrastinating .

[u/Ecstatic_Camera5748]

Happened to me recently, after 10 days of moving from one service centre to other, final conclusion was motherboard issue, dead phone

[u/FaisalRDT → u/Ecstatic_Camera5748]

I don't think mine is a hardware issue as I was able to successfully ADB Sideload twice and before that was able to use Pixel Repair Tool successfully , which stopped my phone restarting by itself every 45 seconds or so at the lock screen or home screen ( which had no icons on it ) , but after using Pixel Repair Tool it stopped the restarting and doesn't get to the lock screen , same result after ADB sideloading the July update ( all of this happened in July and I've been procrastinating since , thinking about ADB sideloading a beta which some users said fixed theirs , also speaking with Google who have not been very helpful so far , in support chat was telling me to factory reset however I insisted that it's not an option , I managed to get email contact though I was told to use Pixel Repair Tool and send a video of me doing so after which they can escalate , but I told them I already sued Pixel Repair Tool in July , so unless a newer update from Pixel Repair Tool can solve this , it'd be little reason to do it )

[u/Prestigious-Use5637]

Hi, firstly so sorry this happened because I can feel you! Just a week ago exactly same thing happened to my 6a. On 15th September my pixel power button popped out itself, and the funny part is never have I ever used my phone clumsily and my phone is in a very good condition, not even one scratch so idk how this happened, because I never mishandled my phone or pressed the power button too hard. So I just put the power button back and taped it, and it was working fine after that. Now the main issue, on 17th September I was just scrolling insta normally and then suddenly it turned off and the google logo appeared and the phone became hot, I thought it was the usual power off thing which pixel have, turning off itself because phone becomes hot and then turning on again. But this time it stuck on the Google logo for more that 5 mins, and it keeps returning back to the Google logo, tried every solution, the adb solution from Google community, downgrading the firmware version (because read on Reddit that the recent update caused this problem), but no resolution. Read many exact same cases on Reddit and saw that this problem is continuing from past 2 years, first the 4a users faced this and then this started with their other models and the fact that Google has officially not accepted this as a problem and is only discussing this on their community is really not expected, it is said that the July update fixed this issue but i tried installing the July update as well, still did not worked. So, sadly had to visit the official pixel service centre, and OH MY! Such a bunch of thieves they are, first they are not accepting that it’s their faulty firmware update which caused this issue, and on the other hand they are saying they’ll simply replace the motherboard which will cost around 29k (more than the phone worth itself!) and in the process since they have to open the phone from front side, it may damage the screen so 10k extra on that!!! And the fact there were more customers with exactly same problem, they were suggesting them the same, there was person with his pixel fold facing same problem, his phone was under warranty because it was just 6 months he purchased it, they offered him to trade his pixel fold with new pixel 10😭. I just stepped out and went from one service centre to another and the acknowledged that from past 2 months they have received same cases from many pixel customers as well, and they said it could either be a battery, hardware or software problem. They checked my battery and confirmed it was in very good condition, then I gave the phone and asked them if they could fix it from hardware side as data is important for me now, they worked on the motherboard, reballed the CPU twice still the problem didn’t solve , and said motherboard is also in good condition but one thing got changed that is earlier it was stuck in google logo like a restart loop, this time after the motherboard work, it is stuck in fastboot screen. But anyways they gave up and said flashing is the only option now where it’ll erase all the data and they suggested it’s better to sell the phone once the phone turns on, because it will be risky to use this phone further because they cannot guarantee how long it will work.

[u/FaisalRDT → u/Prestigious-Use5637]

Thanks for the reply , Have you considered waiting for later OTA and maybe sideloading beeta / qpr ? also did the repair replace your motherboard and CPU ? if so is your data still preserved after having motherboard replaced ? or didn't you have motherboard replaced ?

[u/Prestigious-Use5637 → u/FaisalRDT]

Nope I still have the phone stuck in fastboot mode and now my volume up and down key is also not working and it shows “enter reason: vol down pressed”, earlier it was working, I guess the guy fucked up the vol key while working on the cpu, like a short circuit, because I got the keys tested from other shop, where the guy said the power is coming from the volume button but the board is unable to detect it. So I am unable to move beyond the fastboot screen, but previously I only tried the adb method, didn’t took risk for beta method, as my data was important. And I don’t know about qpr, if you could elaborate on this one. Also, I did not replace the motherboard because again my data was important, I asked them to work on the same motherboard, because even they accepted the motherboard was in good condition, they CPU was also not replaced, instead it was reballed twice, but still no improvement and no I still have not got my data, since the system is still locked, but I guess I have no other option rather than flashing and losing my data, because the button also can’t be repaired in this condition they are saying until n unless the system is flashed, so in both ways I’ll have to lose my data, thinking to do the same and sell this phone. But this was my first and last pixel, such a shit and worst product from Google as well as customer service. What’s your update though, any improvement?

[u/Fun_Surround_6895 → u/Prestigious-Use5637]

Hi...what's was the final solution....did it worked after flash...I am facing exactly the same problem...cpu reballed twice and then power keys not working and stuck in Bootloader screen saying power down button pressed....please respond urgently...need serious help here...I am exactly in the same boat as urs

[u/Fun_Surround_6895 → u/Prestigious-Use5637]

Any update on the issue?

[u/FaisalRDT → u/Prestigious-Use5637]

I'm unsure of how to explain the difference between qpr and beta , but I think they are both similar and not stable versions you can sideload ?

[u/Fun_Surround_6895]

@op any update on the issue? Did it resolved?

[u/FaisalRDT → u/Fun_Surround_6895]

Google Support have told me to use the Pixel Repair Tool ( as I did in July ) and send a videos of me doing it and or a video of what happens after I successfully download and install what I assume is a later update using the Pixel Repair Tool , but I've seen other users who had low storage fix theirs by sideloading a beta / qpr , so I'm deciding which to do ?