Fixed
Status Update
No update yet.
Comments
ca...@gmail.com
Thanks for finding this, fixed internally, will go out with next release (both to 1.0 and androidx).
ca...@gmail.com
Fixed released in 1.0.1
Note though that this won't be released in AndroidX (2.0) until its next release.
Note though that this won't be released in AndroidX (2.0) until its next release.
ca...@gmail.com
Eas
vi...@google.com
vi...@google.com
...
ca...@gmail.com
Eas
ku...@gmail.com
Epic game
ju...@gmail.com
GameOver
mo...@gmail.com
Comment has been deleted.
mo...@gmail.com
I have the same issue, i live in Saudi Arabia and there are no official Google repair centers here, any way i could possibly unlock the bootloader of my pixel 6 pro?
vv...@gmail.com
Hello, you need to add information that it happens when you forgot to charge your phone you will get same issue.
n....@gmail.com
I have the same problem, sadly there is nothing to do until now
an...@gmail.com
This happened to my Google Pixel 6 Pro two days ago. First I got the "corrupted" screen, and after numerous failed reboot attempts, I decided to factory reset. Now it's stuck in an endless boot loop. I contacted support and since it's out of warranty they said there's nothing they could do. They suggested I bring it into a Google Store. I did, and the tech said it would be a $578 motherboard replacement -- more than the phone is worth.
I brought up that this was an issue caused by an official software update, and that the Google Pixel support team has acknowledged the issue. They said there's nothing they can do because the issue "isn't in their system." Now I have a bricked phone days before I need it for international travel. Google sabotaged my phone with an official update and is now refusing to accept responsibility.
I brought up that this was an issue caused by an official software update, and that the Google Pixel support team has acknowledged the issue. They said there's nothing they can do because the issue "isn't in their system." Now I have a bricked phone days before I need it for international travel. Google sabotaged my phone with an official update and is now refusing to accept responsibility.
ky...@hotmail.com
Hi team, can we get an update on this issue please?
There's potentially thousands of affected customers waiting for some acknowledgement.
There's potentially thousands of affected customers waiting for some acknowledgement.
al...@gmail.com
Damn Google sons of bitches fix the mess you created with the pixel 6 series, it's not fair and I'm upset, you can be sure I'll never buy anything from you again.
jo...@gmail.com
I did not perform a factory reset! I noticed my "dynamicSpot" app icon was not loaded in properly (Purple Android Logo). I then proceeded to restart my device (Turn off and On, not with shutdown). The device turned off and attempted to turn back on but then stopped. I then tried to turn on with power button and concluded it was bricked. Google service was not useful. Thankfully I have a spare iPhone 11.
ju...@gmail.com
Nothing yet? Just add the compatibility to pixelrepair please
ro...@gmail.com
Google release August Pixel Update. And fix for pixel 6 series : "Fix for issue occasionally causing devices to be in a reboot loop after factory reset in certain conditions".
But users like us with bricked devices still cant fix it! FullOTA gives error at 47%, pixel rescue mode not working at all!
So google just like say to us all : "go to the store and buy a new one, and throw the old one in the trash".
Super solution, many thanks google!!! awfully support google
But users like us with bricked devices still cant fix it! FullOTA gives error at 47%, pixel rescue mode not working at all!
So google just like say to us all : "go to the store and buy a new one, and throw the old one in the trash".
Super solution, many thanks google!!! awfully support google
al...@gmail.com
Fucking google
dd...@gmail.com
Not knowing about this issue, I tried to Reset my Pixel 6 Pro for my daughter to use, and now it has been rendered useless. Hoping for some kind of fix.
da...@gmail.com
As of Aug 12th - I just tried using the Pixel Repair tool. I no longer get the "Your phone's current software version is newer than this repair tool has".
However it now fails at the "Erasing device data" step - Getting the "Couldn't erase device data" message.
However it now fails at the "Erasing device data" step - Getting the "Couldn't erase device data" message.
na...@gmail.com
Please give us a fastboot or sideload option that works.
Spending $250 to fix it at our own expense is not an acceptable option.
Spending $250 to fix it at our own expense is not an acceptable option.
vi...@google.com
The issue has been fixed and watch out for future releases, Thanks.
al...@gmail.com
I just tried using the Pixel Repair tool. I no longer get the "Your phone's current software version is newer than this repair tool has".
However it now fails at the "Erasing device data" step - Getting the "Couldn't erase device data" message.
FIX THIS SHIT GOOGLE
However it now fails at the "Erasing device data" step - Getting the "Couldn't erase device data" message.
FIX THIS SHIT GOOGLE
da...@gmail.com
Comment has been deleted.
da...@gmail.com
"The issue has been fixed and watch out for future releases, Thanks."
But what exactly is the fix?!
ro...@gmail.com
Where is that fix? Status changed to fixed but we still here((
al...@gmail.com
Don't lie anymore, you don't have any solution, you are giving the matter a long time so that what you did cools down, no method works, the phone does not respond to anything that is possible to try, neither adb commands nor the pixel repair website, the reality is that they finished us off and now that, not all of us live in countries with official Google support where we can go, the biggest shit of the Google century has been this, shame on them, they don't have quality control to review an update before If it happens like this, users will avoid this damn bad time they are putting us through, it is their moral obligation to provide us with a real solution, no more LIES.
al...@gmail.com
What do I do now with my broken phone, I eat it?
al...@gmail.com
Damn it, release a solution to this shit, I don't have another phone, this situation is not easy damn Google, 2 months have already passed and they don't give a shit about this problem, damn it now.
al...@gmail.com
FUCKERRRRSSSSS
al...@gmail.com
There is no way to revive, for God's sake, damn Google, what did you do, what an overwhelming situation, it's not fair to the user, it's not even in the beta and anyway, I'm screwed, this has no solution and they won't give you the one they have. Because everything is money and bureaucracy, now I have a nice paperweight while Google scratches its ass without doing anything.
ju...@gmail.com
So... where's the fix?
na...@gmail.com
Is there a way we can test the fix? Any details on what the actual issue was and what is the proposed fix for devices that are already in the bad state?
Can you confirm that the fix can be done by users and we no longer have to take it in to a repair center ( which is very expensive?)
Can you confirm that the fix can be done by users and we no longer have to take it in to a repair center ( which is very expensive?)
na...@gmail.com
Since this issue is marked as fixed, I tried adb sideloading the latest OTA - raven-ota-ap2a.240805.005.f1-486d5763.zip
The sideload also fails with the missing tune2fs error
Seems to be failing here -
Please reopen, as this issue is not fixed.
ju...@gmail.com
Google team, I really miss using my Pixel 6 Pro, PLEASE, have mercy of us, release some fix, an magic OTA, an web tool, a factory image that bypass the OEM lock. Please, help us to use our smartphones again. It's dificult to find any information about it. Most of us that are here at this portal have some ADB and fastboot knowledge, so please, release something that fix this issue... Please help.
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Please help. pixel 6 oriole
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.
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.
al...@gmail.com
Give us an answer damn bastards you fucking update brick my phone
he...@gmail.com
WTF GOOGLE DO SOMETHING!
ch...@gmail.com
I really hope Google fixes this for the people who's phone is already bricked.They gotta do something for you or else face a class action suit like with the nexus 6p remember that? Personally thanks to people posting and my own vigilance I did not get stuck with this. They say its fixed but Im about to get the 9 and trade in the 6. Im thinking if I unlock the bootloader before I factory reset Then just relock it is probably the best way. This way if it does happen at least my bootloader will be unlocked and I can use the android repair tool.Good luck to all my fellow pixel fans I hope Google does the right thing for you all.
ro...@gmail.com
People says that September patch via sideload aslo not help(((
Some one try sideload new - QPR Beta 1.1 (AP41.240726.010) Android 15 ???
Google where is fix? WTF?
Some one try sideload new - QPR Beta 1.1 (AP41.240726.010) Android 15 ???
Google where is fix? WTF?
ju...@gmail.com
Just tried all lasts releases, Android 14 and Android 15 ota and factory (my bootloader is locked but I`m trying every possibility)
Sideload
Flash
PixelRepair
PixelFlasher
adb sideload process still getting aborted at 47%. kError1
Sideload
Flash
PixelRepair
PixelFlasher
adb sideload process still getting aborted at 47%. kError1
ju...@gmail.com
Please release an image or a tool that fix this...
vl...@gmail.com
It's been a long time, Google is silent. FOR WHAT?
al...@gmail.com
google i hate you
al...@gmail.com
HAVE MERCY OF US GOOGLE
p....@gmail.com
Contacted google support - the "fix" is to send the device back to a repair centre for the modest amount of £385, as the device is obviously out of warranty!!!!
So basically, according to Google, I need to pay £385 (which, by the way, is over double the resale value of the device) to fix a problem created by Google in the first place????
So basically, according to Google, I need to pay £385 (which, by the way, is over double the resale value of the device) to fix a problem created by Google in the first place????
ab...@gmail.com
Es increible que casi 3 meses despues del problema Google solo este rascandose el culo, SACA UNA MALDITA SOLUCION YA!
am...@mobileup.ch
Comment has been deleted.
am...@mobileup.ch
I FOUND A FIX!!! GO TO RECOVERY MODE AND MAKE A DATA WIPE THEN YOU CAN RESTART THE PHONE AND IT WORKS
al...@gmail.com
HA HA HA HA HA HA HA HA HA HA
vu...@gmail.com
I HAVE NOT RESOLVED THIS ERROR. PRETTY SAD
al...@gmail.com
GOOGLE DAMN YOU ARE SONS OF A BITCH, THEY BREAK USERS' PHONES AND NOW THEY DO NOT GIVE A SOLUTION, IT IS MY LAST DAMN GOOGLE PHONE THAT I BUY, I PREFER TO GIVE MYSELF A FIRE THAN TO BUY AGAIN ONE AGAIN, YOU FUCKING SONS OF BITCHES.
ro...@gmail.com
Today android 15 release. i will try ota via sideload soon)
ro...@gmail.com
Android 15!!! WHERE FIX GOOGLE???
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...
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...
al...@gmail.com
android 15 not fix this, fuck you google, fucking scammers
al...@gmail.com
We have already been forgotten by Google, what happened to us is not fair, unfortunately I do not have money to buy another phone, I saved for many months to be able to buy this one and it did not last even 1 hour with it.
na...@gmail.com
Yes - this is very disappointing coming from Google - they don't stand behind their products. I am personally never buying any Pixel ever again and recommending the same to my friends and family. Hopefully a class action lawsuit can be filed for this issue soon.
ju...@gmail.com
Please fix this....
al...@gmail.com
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, what a coincidence it was only the pixel 6 series.
al...@gmail.com
I have the same issue and I hope there is a class action suit that we can join. Google remotely bricked our phones and now expects us to purchase an upgrade when there is nothing mechanical wrong with our handsets. Instead, the negligence of their QA team has resulted in thousands of us losing the ability to use our own phones after an upgrade they pushed. Gross misconduct; I will absolutely support a class action suit.
al...@gmail.com
Listen to me Google instead of threatening or trying to censor the affected users, they should be honest for once and give a solution to the disaster they caused to the users, not to You have provided a real solution to this problem. In fact, you are blatantly trying to make money off a problem created by you. This is not fair and we will see you in court.
al...@gmail.com
Every time I see my damn pixel 6 collecting dust in a drawer it makes me angry, it was a fine working phone until Google intentionally blocked it, this shit isn't fair dammit.
al...@gmail.com
On top of this, there is a damn comment moderator trying to threaten anyone who commented on something they don't like, but there is no civilized way to look at this problem calmly, this is not fair.For a user who has been loyal to Google and its devices, I am so angry at this outrage and lack of resolution.
al...@gmail.com
Give a damn solution that everyone knows they have and can do, do the right thing damn
al...@gmail.com
God Damm it do something motherfucker
ni...@gmail.com
Planned Obsolescence - is the concept of policies planning or designing a product with an artificially limited useful life or a purposely frail design, so that it becomes obsolete after a certain predetermined period of time upon which it decrementally functions or suddenly ceases to function.
Will wait for gpt to put you in grave.
Will wait for gpt to put you in grave.
al...@gmail.com
😥
al...@gmail.com
Comment has been deleted.
al...@gmail.com
No matter what you say, you are not going to solve this problem. I give up Google, you won, I will never comment here again.
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
Fucking scammers i hate google with all my heart no solution for us
al...@gmail.com
fuck
al...@gmail.com
Fix it dammit
al...@gmail.com
this is the most scammer company in the world, the broken the pixel 6 han then not provide a solution, im super angry fucking bastards
al...@gmail.com
Christian without any solution, so sad the life, everything for money
al...@gmail.com
30 of december and nothing, google is the worst diabolical company of all universes, fuck you google
al...@gmail.com
2025 without my phone
al...@gmail.com
This shit its not fixed why you said its fixed
al...@gmail.com
This shit its not fixed why you said its fixed
vi...@google.com
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.
ac...@gmail.com
Cant you speak me in french I dont understand because my english is not good, ILook one message you send me and I never send a worst message to ggogle and I had a Pixel 9 not 6 I dont know wy you received the worst message. Just explain me how I cant result this problem.
Obtenir Outlook pour Android<https://aka.ms/AAb9ysg >
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Monday, January 6, 2025 5:11:31 AM
To: b-system+-1756083234@google.com <b-system+-1756083234@google.com>
Cc: acouturier66@gmail.com <acouturier66@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
https://issuetracker.google.com/issues/350285633
Changed
vi...@google.com addedhttps://issuetracker.google.com/issues/350285633#comment119 >:
Re-https://issuetracker.google.com/issues/350285633#comment118 >, https://issuetracker.google.com/issues/350285633#comment115 >, https://issuetracker.google.com/issues/350285633#comment113 >, https://issuetracker.google.com/issues/350285633#comment110 >.
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.
_______________________________
Reference Info: 350285633 An Unexpected Aftermath of a Factory Reset
component: Android Public Tracker > Framework<https://issuetracker.google.com/components/192705 >
status: Fixed
reporter: ca...@gmail.com
assignee: vi...@google.com
cc: ca...@gmail.com, vi...@google.com
type: Bug
access level: Default access
priority: P2
severity: S2
blocked by: 350510248<https://issuetracker.google.com/issues/350510248 >, 349287459<https://issuetracker.google.com/issues/349287459 >
duplicate: 360421335<https://issuetracker.google.com/issues/360421335 >
hotlist: [AOSP] assigned<https://issuetracker.google.com/hotlists/468531 >
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system.
You're receiving this email because you are subscribed to updates on Google IssueTrackerhttps://issuetracker.google.com/issues/350285633 > where you have the roles: starred
Unsubscribe from this issue.<https://issuetracker.google.com/issues/350285633?unsubscribe=true >
Obtenir Outlook pour Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Monday, January 6, 2025 5:11:31 AM
To: b-system+-1756083234@google.com <b-system+-1756083234@google.com>
Cc: acouturier66@gmail.com <acouturier66@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
vi...@google.com added
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.
_______________________________
Reference Info: 350285633 An Unexpected Aftermath of a Factory Reset
component: Android Public Tracker > Framework<
status: Fixed
reporter: ca...@gmail.com
assignee: vi...@google.com
cc: ca...@gmail.com, vi...@google.com
type: Bug
access level: Default access
priority: P2
severity: S2
blocked by: 350510248<
duplicate: 360421335<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system.
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
al...@gmail.com
fuck you
vi...@google.com Restricted+
Restricted+
al...@gmail.com
Comment has been deleted.
al...@gmail.com
Comment has been deleted.
al...@gmail.com
Comment has been deleted.
al...@gmail.com
Comment has been deleted.
al...@gmail.com
Comment has been deleted.
al...@gmail.com
Comment has been deleted.
al...@gmail.com
Issue was solved after july update, but 3300 users who had factory reset their devices entered this limbo without any solution, glad you could do it without issues
al...@gmail.com
fix the phone please common why this things happen
al...@gmail.com
nothing
al...@gmail.com
NOT FIX YET GOOGLE?????
al...@gmail.com
TOTALLY IGNORED, GOOGLE HAS A GOOD DEAL
al...@gmail.com
Injustice
ac...@gmail.com
Vous m:envoyer depuis un an des messages pour un probleme avec un google
pixel 6a. Je n:ai jamais envoyer de messages pour me plaindre de quoi que
ce sois . Quelqu'un semble se servir de mon adresse gmail pour vous
harceler et j:ai un pixel 9 . Comment est ce possible de se servir de mon
adresse et comment puis-je faire vetifier si mon adresse a ete volé?
Le lun. 6 janv. 2025, 06 h 40, Alain Couturier <acouturier66@gmail.com> a
écrit :
pixel 6a. Je n:ai jamais envoyer de messages pour me plaindre de quoi que
ce sois . Quelqu'un semble se servir de mon adresse gmail pour vous
harceler et j:ai un pixel 9 . Comment est ce possible de se servir de mon
adresse et comment puis-je faire vetifier si mon adresse a ete volé?
Le lun. 6 janv. 2025, 06 h 40, Alain Couturier <acouturier66@gmail.com> a
écrit :
gk...@gmail.com
Where is the fix google? My device showing " no valid Os Found" I'm unable to flash it as OEM and bootloader is locked, it's in bootloop , can't get recovery mode or rescue mode!.. please provide us a damn solution
ve...@gmail.com
Why you dont add oem unlocking to Pixel Repair tool? Maybe to unlocking it after sign in, or something? OTA sideload is failed, because patritions in RAW after that error. And pixel repair is literally OTA Sideload...
mo...@gmail.com
My pixel watch 2 has the same issue and it's only 1 year old - spent $349.99 and the warranty just expired! I have a $349 brick now!!
Description
A treacherous, fatal error may be responsible for the unexpected behavior that occurs after a factory reset.
After a short survey from a countable quantity of forums from different subreddits, it has been concluded that this is not a manufacturer-specific defect of UFS chips (Chips manufactured from SK Hynix, Kioxia, Micron and et cetera exhibited the same scenario) and may be a software-side defect. In addition, reports are from the Pixel 6 lineup (A-Series, Vanilla, Pro).
The issue may stem from a message containing, "tune2fs is missing".
Factory Reset aftermath includes, leaving the device untouched—data is not deleted nor formatted—and in some cases, inescapable bootloops to recovery.
You can find more details of the aftermath here:
Its effects may be detrimental to the workflow and life expectancy of the said devices.
Impacted audience consists of both non-beta testers and beta testing users (
There were attempts of remediation such as:
- Using
-
- Attempt of ADB sideloading, returned a non-zero value. (Which almost indicates something is wrong in the process of sideloading an official package.)
and many more...
Some user reports of the erroneous process happening:
-
-
-
-
-
-
(Incomplete list.)
More details:
Waiting for your response/feedback,
Pixel Users
* Are you an Android developer?" (Y/N)
- I am not an Android Developer.
* Which Android Developer Preview build are you using? See Settings > About phone > Build number (for example AP31.240119.016).
- I am not currently in a beta build. Right now, I am in a public, official build: 14 (AP2A.240605.024)
* What device are you using? (for example, Android Emulator, GSI, Pixel 7)
- Pixel 6 (Vanilla) but is also reproducible throughout the Pixel 6 lineup.
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
- Conduct a factory reset through settings.
* What was the expected result?
- Successful and secure data wipe.
* What was the actual result?
- Untouched and populated data partition. In some cases, an inescapable recovery boot.
I can provide a recovery log prior to mounting the system partition only, as factory resetting my primary device may lead to a potentially unrecoverable situation. At this time of writing, I am not able to provide logs. But rest assured I will try and upload recovery logs related to this problem.