Status Update
Comments
sa...@google.com <sa...@google.com>
ve...@google.com <ve...@google.com> #2
ve...@google.com <ve...@google.com> #3
If you are using Pixel 6 and above
Check if you can go to fastboot mode by pressing the Power button + Volume up button for 30 sec.
If yes, then backup and flash the device (
If not, follow the RMA process.
Please reach out to our RMA support team (
ja...@gmail.com <ja...@gmail.com> #4
oo...@gmail.com <oo...@gmail.com> #5
You need to stand behind your products and be curious enough to want to investigate the issue and help customers resolve them. I am sitting here with a $1000 brick that Google refused to help me with. I gave up until I found this thread........
ra...@gmail.com <ra...@gmail.com> #6
I tried to reset a Pixel 6 with Android 15 on it to joint an MDM soloution.
ia...@gmail.com <ia...@gmail.com> #7
I fixed my Pixel 6a. Bootloader was locked and OEM unlocking was off.
I sent it to the authorized repair centre and they told me that the motherboard needs replacing. I rejected the repair. When I got my phone back, I realised the bootloader was unlocked. I used the Android Flash Tool and flashed the latest public build. Working as good as new!
te...@gmail.com <te...@gmail.com> #8
pc...@gmail.com <pc...@gmail.com> #9
az...@gmail.com <az...@gmail.com> #10
ar...@gmail.com <ar...@gmail.com> #11
Selling mine for parts or throwing the google pixel 6 pro in the trash thats where it belongs
al...@gmail.com <al...@gmail.com> #12
vv...@google.com <vv...@google.com> #13
Please follow the below steps and try to flash the latest beta build (AP31.240617.010 ,
-
Press vol down+power to boot the device to fastboot mode, then press vol down x 3 times and power button 1 time to enter the rescue mode. (If the screen shows that "Your device is corrupt", press the power button one more time to proceed). After a while, the device will enter the rescue mode screen. (
https://screenshot.googleplex.com/899G3mYvTQmVcHj ) -
Open
https://pixelrepair.withgoogle.com/steps and navigate to the steps, it will tell you to factory reset & reinstall OTA AP31.240617.010 (https://screenshot.googleplex.com/45BPzcjhvD5iMhQ ) -
Wait until the process is complete. After this step, the bootloader still notifies that the device is corrupted, but it can boot the device up/enter the android home screen. (
https://screenshot.googleplex.com/BPJE7uKniFtHCnU )
(Supported on the unlocked device only)
- Boot the device back to fastboot mode and run the following commands:
$ fastboot snapshot-update cancel
$ fastboot -w
$ fastboot reboot
- The "Your device is corrupt" notice will be gone and the device can boot up normally.
al...@gmail.com <al...@gmail.com> #14
If the software is not officially released by Google, please consider changing back to the latest public version by
NOT WORKING
kr...@gmail.com <kr...@gmail.com> #15
pc...@gmail.com <pc...@gmail.com> #16
Please follow the below steps and try to flash the latest beta build (AP31.240617.010 ,
Press vol down+power to boot the device to fastboot mode, then press vol down x 3 times and power button 1 time to enter the rescue mode. (If the screen shows that "Your device is corrupt", press the power button one more time to proceed). After a while, the device will enter the rescue mode screen. (
Open
Wait until the process is complete. After this step, the bootloader still notifies that the device is corrupted, but it can boot the device up/enter the android home screen. (
(Supported on the unlocked device only)
Boot the device back to fastboot mode and run the following commands:
$ fastboot snapshot-update cancel
$ fastboot -w
$ fastboot reboot
The "Your device is corrupt" notice will be gone and the device can boot up normally.
na...@gmail.com <na...@gmail.com> #17
al...@gmail.com <al...@gmail.com> #18
al...@gmail.com <al...@gmail.com> #19
an...@gmail.com <an...@gmail.com> #20
al...@gmail.com <al...@gmail.com> #21
ya...@gmail.com <ya...@gmail.com> #22
br...@gmail.com <br...@gmail.com> #23
al...@gmail.com <al...@gmail.com> #24
With the last released OTA's Beta 4.2 and Android 14 August Update the adb sideload process still getting aborted at 47%. kError1
When I try to do a factory reset:
ERROR: recovery: [libfs_mgr] Unable to enable ext4 verity on /dev/block/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing.
ko...@gmail.com <ko...@gmail.com> #25
With the last released OTA's Beta 4.2 and Android 14 August Update the adb sideload process still getting aborted at 47%. kError1
When I try to do a factory reset:
ERROR: recovery: [libfs_mgr] Unable to enable ext4 verity on /dev/block/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing.
co...@gmail.com <co...@gmail.com> #26
Same issues here.
The pixelrepair tool fails, maybe because I'm selecting the wrong carrier. I bought the phone on the Google store and I'm in France, it was not bought via a carrier. What country/carrier must I select ?
vl...@gmail.com <vl...@gmail.com> #27
al...@gmail.com <al...@gmail.com> #28
p....@gmail.com <p....@gmail.com> #29
ro...@gmail.com <ro...@gmail.com> #30
oriole-ota-ap3a.241005.015-35b1560c.zip via sideload still getting aborted at 47%. kError1
Fucking google, there will be no fix, i will go to ebay for mobo...
ju...@gmail.com <ju...@gmail.com> #31
vi...@google.com <vi...@google.com> #32
Re-
ww...@gmail.com <ww...@gmail.com> #33
bm...@gmail.com <bm...@gmail.com> #34
al...@gmail.com <al...@gmail.com> #35
These bastards at Google don't care if we get our phones back, this is an obvious case of planned obsolescence, nothing is by chance, we've already seen it at Apple and Samsung, that's the way the world is, they can fix it but they're not going to do it.
vi...@google.com <vi...@google.com> #36
Re-
ww...@gmail.com <ww...@gmail.com> #37
The issue is there since several months and no official support till date from a reputed company is not acceptable.
The cheap phones are more easy to fix than your so called flagships
go...@gmail.com <go...@gmail.com> #38
al...@gmail.com <al...@gmail.com> #39
al...@gmail.com <al...@gmail.com> #40
co...@gmail.com <co...@gmail.com> #41
co...@gmail.com <co...@gmail.com> #42
nb...@gmail.com <nb...@gmail.com> #43
ba...@gmail.com <ba...@gmail.com> #44
sh...@gmail.com <sh...@gmail.com> #45
al...@gmail.com <al...@gmail.com> #46
ka...@gmail.com <ka...@gmail.com> #47
vi...@google.com <vi...@google.com> #48
Re-
Hello, your comments were flagged for review. We understand that you’re frustrated, but please keep your language civil. If you continue to post abusive statements to the Google Issue Tracker, we will be forced to take action by removing your ability to make any comments or changes on the Google Issue Tracker.
ap...@gmail.com <ap...@gmail.com> #49
I'm also stuck in this fastboot loop. For me the right solution was to go to this page
go...@gmail.com <go...@gmail.com> #50
gk...@gmail.com <gk...@gmail.com> #51
My pixel 6 is bricked, after update.the msg I'm getting is " No valid Os Found" , I have been searching for solutions over The internet bt nothing is working, can't flash as OEM is disabled and bootloader is locked, And can't get warranty support as it was not launched in india officially. Please google fix it somehow! I can't buy another device now!!...
Description
Hi. I'm really hoping someone will be able to help me. I tried to update to the latest beta and my phone is in a really bad state right now. The thing that's most notably bad about it is that I can't even factory reset my phone.
When I try to factory reset it I cant an error:
ERROR: recovery: [libfs_mgr] Unable to enable ext4 verify on /dev/block/platform/147000000.ufs/by-name/metadata because /system/bin/tune2fs is missing
And then other various errors like
Error in /sideload/package.zip (status 1)
First I tried to sideload the update via adb sideload, no luck. Then I tried to restore a factory image, but that didn't work because I didn't unlock the device and there appears to be no way to unlock the device without booting into the OS.
Am I out of luck? In other words do I need to replace my phone?