Status Update
Comments
je...@gmail.com <je...@gmail.com> #3
ol...@gmail.com <ol...@gmail.com> #6
os...@gmail.com <os...@gmail.com> #7
st...@gmail.com <st...@gmail.com> #8
Same issue here with two profiles, primary can't access storage. Happened when trying to snap a photo days after the last Android or Google Play uprgrade!
Please fix urgently, thanks!
jo...@gmail.com <jo...@gmail.com> #9
sa...@gmail.com <sa...@gmail.com> #10
er...@gmail.com <er...@gmail.com> #11
hi...@gmail.com <hi...@gmail.com> #12
pa...@gmail.com <pa...@gmail.com> #13
Tried to clear the cache on recovery mode and I can't access the mount drive either
ji...@gmail.com <ji...@gmail.com> #14
dr...@gmail.com <dr...@gmail.com> #15
an...@gmail.com <an...@gmail.com> #16
ha...@gmail.com <ha...@gmail.com> #17
pr...@googlemail.com <pr...@googlemail.com> #18
Prio 1 Bug
so...@gmail.com <so...@gmail.com> #19
he...@gmail.com <he...@gmail.com> #20
se...@googlemail.com <se...@googlemail.com> #21
be...@gmail.com <be...@gmail.com> #22
yv...@gmail.com <yv...@gmail.com> #23
iv...@gmail.com <iv...@gmail.com> #24
an...@gmail.com <an...@gmail.com> #25
ms...@gmail.com <ms...@gmail.com> #26
mi...@gmail.com <mi...@gmail.com> #27
After update to officially 14f from 13
on the main profile no internal storage is not available.
The phone is not useable!
This is known by Google since offered the 14
but no fix is out unbelievable!
Never heard about that from Apple.
na...@gmail.com <na...@gmail.com> #28
ms...@gmail.com <ms...@gmail.com> #29
fr...@gmail.com <fr...@gmail.com> #30
sk...@gmail.com <sk...@gmail.com> #31
sn...@gmail.com <sn...@gmail.com> #32
Looks like. Symlink form /storage/self/primary to /storage/emulated/0 is missing.
no...@gmail.com <no...@gmail.com> #33
me...@gmail.com <me...@gmail.com> #34
aa...@gmail.com <aa...@gmail.com> #35
sa...@gmail.com <sa...@gmail.com> #36
ed...@gmail.com <ed...@gmail.com> #37
I can't take new pictures, or download attachements. My phone is pretty useless and I'm several thousands of km from home, I need access to my banking apps which I'd lose if I factory reset my phone.
lo...@gmail.com <lo...@gmail.com> #38
Downloading and updating apps has become impossible due to the failure to recognize internal storage.
Accessing and searching for files on the device is not possible.
Creating and accessing backups is not possible.
mc...@gmail.com <mc...@gmail.com> #39
me...@gmail.com <me...@gmail.com> #40
sa...@gmail.com <sa...@gmail.com> #41
ma...@gmail.com <ma...@gmail.com> #42
da...@gmail.com <da...@gmail.com> #43
Pixel 6. Updated to Android 14 a few days before the following failure.
- Couldn't take screenshots due to a storage failure.
- Rebooted.
- After unlock, the phone told me "Factory resetting, restarting" without any action.
- Pixel 6 restarted without any action.
- Was presented a boot menu telling me of some malfunction, with two choices: factory reset or starting as usual.
- Selected the start as usual.
- Phone is stuck in the "Phone is starting" step. Restarting the phone does not fix the issue.
- Note: Bluetooth connects to my paired headphones even during "Phone is starting".
- Note 2: the previous special boot menu never showed up again.
- Note 3: standard boot menu is accessible.
- Note 4: recovery mode and the mode designed to work with Chrome's repair tool are accessible.
- Note 5: the Chrome's repair tool did not find any version to fix the Android installation (installed version was "unknown" by the tool).
- Note 6: three profiles enabled.
sa...@gmail.com <sa...@gmail.com> #44
ng...@gmail.com <ng...@gmail.com> #45
Here's an extract from adb logcat (on pixel 6a) that provides some clues about the issue. A vold storage mount of user-data is failing on login.
This seems to be the underlying reason: 10-21 07:48:35.408 root 555 555 E vold : Failed to open directory /data/media/0: Structure needs cleaning
Device info:
Build: UP1A.231005.007
Build fingerprint: 'google/bluejay/bluejay:14/UP1A.231005.007/10754064:user/release-keys'
Bootloader: bluejay-1.3-10674934
Radio: g5123b-120690-230802-B-10596884
Network: T-Mobile
Module Metadata version: 341049004
Android SDK version: 34
SDK extensions: [ad_services=9, r=9, s=9, t=9, u=9]
Kernel: Linux version 5.10.157-android13-4-00001-g5c7ff5dc7aac-ab10381520 (build-user@build-host) (Android (8508608, based on r450784e) clang version 14.0.7 (https://android.googlesource.com/toolchain/llvm-project 4c603efb0cca074e9238af8b4106c30add4418f6), LLD 14.0.7) #1
SMP PREEMPT Fri Jun 23 18:30:49 UTC 2023
Command line: stack_depot_disable=on kasan.stacktrace=off kvm-arm.mode=protected cgroup_disable=pressure cgroup.memory=nokmem rcupdate.rcu_expedited=1 rcu_nocbs=0-7 clocksource=arch_sys_counter root=/dev/ram0 firmware_class.path=/vendor/firmware reserve-fimc=0xffffff90f9
fe0000 clk_ignore_unused loop.max_part=7 coherent_pool=4M no_console_suspend softlockup_panic=1 cgroup_disable=memory exynos_mfc.load_sequential=1 exynos_drm.load_sequential=1 pcie-exynos-core.load_sequential=1 g2d.load_sequential=1 disable_dma32=on dyndbg="func alloc_co
ntig_dump_pages +p" printk.devkmsg=on cma_sysfs.experimental=Y swiotlb=noforce at24.write_timeout=100 log_buf_len=1024K bootconfig console=null exynos_drm.panel_name=samsung-s6e3fc3_6a tcpci_max77759.conf_sbu=0 tcpci_max77759.mode= id_aa64mmfr1.vh=0 kvm-arm.mode=none boo
tconfig
snip from adb logcat:
10-21 07:48:35.300 1000 1637 2665 I LockSettingsService: Successfully verified lockscreen credential for user 0
10-21 07:48:35.305 1017 601 629 I keystore2: system/security/keystore2/src/authorization.rs:143 - on_lock_screen_event(r#UNLOCK, user_id=0, password.is_some()=true, unlocking_sids=None)
10-21 07:48:35.370 root 555 555 D vold : fscrypt_unlock_user_key 0 serial=0
10-21 07:48:35.371 root 555 555 D vold : Trying user CE key /data/misc/vold/user_keys/ce/0/current
10-21 07:48:35.376 root 555 555 D vold : Successfully retrieved key
10-21 07:48:35.396 root 555 555 D vold : Installed fscrypt key with ref be0c1aae1d23a74e78ff942ec88a67be to /data
10-21 07:48:35.396 root 555 555 D vold : Added fscrypt-provisioning key for be0c1aae1d23a74e78ff942ec88a67be to session keyring
10-21 07:48:35.397 root 555 555 D vold : Installed ce key for user 0
10-21 07:48:35.398 1000 1637 2665 I LockSettingsService: Unlocked CE storage for secured user 0
10-21 07:48:35.399 1000 1637 2665 D SystemServerTiming: finishUserUnlocking-0
10-21 07:48:35.400 1000 1637 2665 D ActivityManager: Started unlocking user 0
10-21 07:48:35.400 1000 1637 2665 D LockSettingsService: unlockUser started
10-21 07:48:35.400 1000 1637 2665 D ActivityManager: Unlocking user 0 progress 0
10-21 07:48:35.400 1000 1637 2665 D LockSettingsService: unlockUser progress 0
10-21 07:48:35.400 1000 1637 2665 D ActivityManager: Unlocking user 0 progress 5
10-21 07:48:35.400 1000 1637 2665 D LockSettingsService: unlockUser progress 5
10-21 07:48:35.401 1000 1637 1717 D SystemServerTiming: UM.onBeforeUnlockUser-0
10-21 07:48:35.401 1000 1637 1717 D SystemServerTiming: prepareUserData-0
10-21 07:48:35.402 root 555 555 D vold : fscrypt_prepare_user_storage for volume null, user 0, serial 0, flags 2
10-21 07:48:35.402 root 555 555 D vold : Preparing: /data/system_ce/0
10-21 07:48:35.403 root 555 555 I vold : Verified that /data/system_ce/0 has the encryption policy be0c1aae1d23a74e78ff942ec88a67be v2 modes 1/4 flags 0xa
10-21 07:48:35.403 root 555 555 D vold : Preparing: /data/vendor_ce/0
10-21 07:48:35.406 10208 2669 2694 V WindowManagerShell: Transition requested: android.os.BinderProxy@656ddb6 TransitionRequestInfo { type = TO_BACK, triggerTask = null, remoteTransition = null, displayChange = null }
10-21 07:48:35.406 1000 1637 2658 D ActivityTaskManager: Top Process State changed to PROCESS_STATE_TOP
10-21 07:48:35.407 root 555 555 I vold : Verified that /data/vendor_ce/0 has the encryption policy be0c1aae1d23a74e78ff942ec88a67be v2 modes 1/4 flags 0xa
10-21 07:48:35.407 root 555 555 D vold : Preparing: /data/media/0
10-21 07:48:35.408 root 555 555 E vold : Failed to open directory /data/media/0: Structure needs cleaning
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: android.os.ServiceSpecificException: (code 0)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.Parcel.createExceptionOrNull(Parcel.java:3071)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.Parcel.createException(Parcel.java:3041)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.Parcel.readException(Parcel.java:3024)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.Parcel.readException(Parcel.java:2966)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.IVold$Stub$Proxy.prepareUserStorage(IVold.java:2168)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at com.android.server.StorageManagerService.prepareUserStorageInternal(StorageManagerService.java:3262)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at com.android.server.StorageManagerService.prepareUserStorage(StorageManagerService.java:3253)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.storage.StorageManager.prepareUserStorage(StorageManager.java:1613)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at com.android.server.pm.UserDataPreparer.prepareUserDataLI(UserDataPreparer.java:91)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at com.android.server.pm.UserDataPreparer.prepareUserData(UserDataPreparer.java:75)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at com.android.server.pm.UserManagerService.onBeforeUnlockUser(UserManagerService.java:6239)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at com.android.server.am.UserController.lambda$finishUserUnlocking$1(UserController.java:665)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at com.android.server.am.UserController.$r8$lambda$igR-ZJDYJXDcQT5ACfj0lLfj1XE(UserController.java:0)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at com.android.server.am.UserController$$ExternalSyntheticLambda2.run(R8$$SyntheticClass:0)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.Handler.handleCallback(Handler.java:958)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.Handler.dispatchMessage(Handler.java:99)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.Looper.loopOnce(Looper.java:205)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.Looper.loop(Looper.java:294)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at android.os.HandlerThread.run(HandlerThread.java:67)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: at com.android.server.ServiceThread.run(ServiceThread.java:46)
10-21 07:48:35.409 1000 1637 1717 E StorageManagerService: ignoring error preparing storage for existing user 0; device may be insecure!
10-21 07:48:35.409 1000 1637 1717 V UserDataPreparer: Found /data/user/0 with serial number 0
10-21 07:48:35.409 1000 1637 1717 V UserDataPreparer: Found /data/system_ce/0 with serial number 0
ga...@gmail.com <ga...@gmail.com> #46
zu...@gmail.com <zu...@gmail.com> #47
er...@gmail.com <er...@gmail.com> #48
ni...@gmail.com <ni...@gmail.com> #49
@google please provide appropriate fix ASAP.
am...@gmail.com <am...@gmail.com> #50
mu...@gmail.com <mu...@gmail.com> #51
st...@gmail.com <st...@gmail.com> #52
mg...@gmail.com <mg...@gmail.com> #53
in...@gmail.com <in...@gmail.com> #54
an...@gmail.com <an...@gmail.com> #55
ma...@gmail.com <ma...@gmail.com> #56
From Vancouver, Canada
as...@gmail.com <as...@gmail.com> #57
Secondary profile shows the correct storage but of course can't access the files from primary.
dr...@gmail.com <dr...@gmail.com> #58
al...@gmail.com <al...@gmail.com> #59
je...@gmail.com <je...@gmail.com> #60
ts...@gmail.com <ts...@gmail.com> #61
The phone is useless anymore.
Lost all access to my internal storage.
What happened to my files is unknown.
Apps requiring access to internal storage (camera, music, photos, screenshots, whatsapp, Viber ) do not work.
Also updating the apps is impossible, since there is no identifiable storage.
Downloaded playlists in YouTube Music app are lost and the app does not play any songs.
Keep paying Google for YouTube Premium for no reason at all, at this point.
ra...@gmail.com <ra...@gmail.com> #62
r....@gmail.com <r....@gmail.com> #63
jo...@gmail.com <jo...@gmail.com> #64
jo...@gmail.com <jo...@gmail.com> #65
be...@gmail.com <be...@gmail.com> #66
to...@gmail.com <to...@gmail.com> #67
Get your fucking shit together and fix this colossal bug which is an absolute catastrophe.
du...@gmail.com <du...@gmail.com> #68
At this point, I would appreciate any transparency from Google.
th...@gmail.com <th...@gmail.com> #69
lu...@gmail.com <lu...@gmail.com> #70
jo...@gmail.com <jo...@gmail.com> #71
je...@gmail.com <je...@gmail.com> #72
gr...@gmail.com <gr...@gmail.com> #73
la...@gmail.com <la...@gmail.com> #74
je...@gmail.com <je...@gmail.com> #75
da...@gmail.com <da...@gmail.com> #76
A bit worried because this makes the phone unusable with all the security concerns of not being able to update any apps
zo...@gmail.com <zo...@gmail.com> #77
What's the point of making your own phones if you are not testing with them? Stability is the whole appeal, it's not like Pixel's fastest, lightest, prettiest or anything. It's meant to be worry free. So much for that.
ch...@gmail.com <ch...@gmail.com> #78
ke...@gmail.com <ke...@gmail.com> #79
My Pixel 6 pro was updated last week. Then the issue happened on October 19th. I switched back to the main profile from the secondary one, tried to open an app that requires storage but it keeps crashing. Then I remembered reading about the storage issue on some website and sure it is, the main storage is not found for main profile. Sub profiles are fine.
ch...@gmail.com <ch...@gmail.com> #80
st...@gmail.com <st...@gmail.com> #81
su...@gmail.com <su...@gmail.com> #82
sa...@gmail.com <sa...@gmail.com> #83
So I found my way to this issue.
Android14 was working fine before.
ge...@gmail.com <ge...@gmail.com> #84
as...@gmail.com <as...@gmail.com> #85
ma...@gmail.com <ma...@gmail.com> #86
The secondary profile doesn't have access to the primary Profile files, therefore data is inaccessible and cannot be backed up.
This should definitely be a P0...
sh...@gmail.com <sh...@gmail.com> #87
ra...@gmail.com <ra...@gmail.com> #88
an...@gmail.com <an...@gmail.com> #89
I have same issue on pixel 6a, 2 profiles, and after upgrade to 14, same problems as other users.
You have released breaking changes, and broken significant functionality on supported devices.
Please escalate so fix can be expedited and we can use our phones
ra...@gmail.com <ra...@gmail.com> #90
Google support staff tried to "troubleshoot" by asking me to tap on storage to clear storage space, ha. Then advised to factory reset. So i have some SMSes that have not been backed up. Staff said I could download an app to back those up. Which clearly, I can't do.
Much regret updating. pls escalate and fix soon.
we...@gmail.com <we...@gmail.com> #91
Google support is useless since they expect me to back up and factory reset, but it's not possible to back up since the local storage is not mounted.
ma...@gmail.com <ma...@gmail.com> #92
da...@gmail.com <da...@gmail.com> #93
l....@gmail.com <l....@gmail.com> #94
ca...@gmail.com <ca...@gmail.com> #95
ei...@gmail.com <ei...@gmail.com> #96
st...@gmail.com <st...@gmail.com> #97
They need to realize we can send reports because our devices can't access storage. They need to replicate the issue locally and hopefully push a patch soon.
Godspeed you wonderful computer magicians!
tw...@gmail.com <tw...@gmail.com> #98
tw...@gmail.com <tw...@gmail.com> #99
cj...@gmail.com <cj...@gmail.com> #100
mi...@gmail.com <mi...@gmail.com> #101
Please fix ASAP, this is a critical error that should not ever have happened.
sa...@gmail.com <sa...@gmail.com> #102
So we should all loose all our data because of Pixel Team's mistake. And no consequence for your team.
la...@gmail.com <la...@gmail.com> #103
jo...@gmail.com <jo...@gmail.com> #104
There may of may not have been a message about "trying something" again at this point, i do not remember.
After the reboot the phone boots to the "pixel is starting" screen, but will not go any further. I haven't activated ADB nor have I unlocked the bootloader, so I'm stuck. Have tried to sideload the original 14.0 firmware via the recovery menu with ADB over USB. The firmware gets installed allright, but the situation does not change. Have tried to sideload the last android 13 firmware as well, but, at the end of the process the bootloader complains that this is a downgrade which can't be done for security reasons.
Makes sense i guess, but, now I've lost access to some stuff that is important to me. And no, backups are not an option because unlike in the 90's where you could just simply copy over everything that is yours to touch, 30 years later we have to trust companies to keep our data for us with no real notion of what data is stored, or even where. I got a bunch of 2FA codes stuck inside there, and the app is designed not to allow copying the data out using a file transfer. For security reasons.
Anybody make any progress in getting the data partitions remounted? Also, escalate this thing. This is not some fringe bug with little fallout.
pa...@gmail.com <pa...@gmail.com> #105
mi...@gmail.com <mi...@gmail.com> #106
Can anyone please raise the priority and severity?
ar...@gmail.com <ar...@gmail.com> #107
sk...@gmail.com <sk...@gmail.com> #108
ao...@gmail.com <ao...@gmail.com> #109
da...@gmail.com <da...@gmail.com> #110
ma...@gmail.com <ma...@gmail.com> #111
ju...@gmail.com <ju...@gmail.com> #112
FUN.
yv...@gmail.com <yv...@gmail.com> #113
gu...@gmail.com <gu...@gmail.com> #114
Disappointed to hear that an official software from a manufacturer is effectively soft-bricking its users' phones.
sr...@gmail.com <sr...@gmail.com> #115
I can not access storage info (from storage app) or photos.
If I lose my photos, it will be bye bye Google phone. I have used only used google phone since Google came out with their first phone.
Mine is pixel 6
Please have a fix ASAP.
su...@gmail.com <su...@gmail.com> #116
er...@gmail.com <er...@gmail.com> #117
ja...@gmail.com <ja...@gmail.com> #118
an...@gmail.com <an...@gmail.com> #119
bo...@gmail.com <bo...@gmail.com> #120
ma...@gmail.com <ma...@gmail.com> #121
ah...@gmail.com <ah...@gmail.com> #122
The last "Google" phone I had (N5X) burned me with sudden hardware failure. I've waited many years using cheap-but-okay Moto phones before getting a Pixel. I hoped it would be a fast and reliable phone for many years more than I got out of my Motos. So far the experience with the Pixel 6a is very much like it was with the Nexus 5X - very good until it was very very bad. At least I don't have to mail it away.
My Moto G Power 2020 is slow and the battery doesn't last as long as it used to and it doesn't get security updates anymore, but golly is it reliable.
I'm still holding out hope that the storage in question is just "disconnected" and not actually wiped or missing a decryption key.
My best wishes go to the Google teammates working on this. It's no fun, I'm sure.
(One thing to note for the future is that Google Photos doesn't have to back up to the same profile as the one that you're logged in to on the phone. So if you are like me with most of your primary account's storage used by Gmail and Drive files and you have under 15GB of photos, you can migrate your photos to a secondary Google account and stretch your free storage a bit.)
ma...@gmail.com <ma...@gmail.com> #123
jo...@gmail.com <jo...@gmail.com> #124
aj...@gmail.com <aj...@gmail.com> #125
ah...@gmail.com <ah...@gmail.com> #126
go...@gmail.com <go...@gmail.com> #128
el...@gmail.com <el...@gmail.com> #129
bu...@gmail.com <bu...@gmail.com> #130
This has been known for a week at least. Instead of all these Pixel 8 announcement emails you have been sending, I would much rather have received a SINGLE one
warning me about this MAJOR issue. But admitting a phone bricking bug at the time of a new model release is terribad for business, right??? Better ignore it
and not make a single comment on it.
1. I WILL NOT factory reset, because all my data is in there, with no backups.
2. YES, NO BACKUPS. WHY? Because of your ilks disgusting, evil track record of infringements on user's data privacy. Your clouds cannot be trusted with our data.
3. I would have sped up my backup schedule had I known that my phone would break barely THREE MONTHS after purchase.
4. This was Android 14 production release, not some beta testing program.
5. Why did I buy your phone, then? We are given little choice these days. Even institutions and banks expect us to have one. Thought by going straight to the source I would
at least minimize the privacy invasion and get the best support.
Also, I refuse to install any updates from a computer via adb. What if the computer is compromised and installed something else? Why should I take responsibility for that? It's unreasonable to ask users to fix a problem that you caused. Good luck fixing the phone when it won't even boot up (stuck on "Pixel is starting" for hours, and neither "Safe mode" or "Recovery mode" will make a difference) and the user refuses to install updates via adb.
LOST ACCESS TO ALL MY HUNDREDS OF CONTACTS, PICTURES, NOTES, SO MANY THINGS ...
medical surgery procedure annotations are on that device. ain't no ... factory reset when a patient dies, you ....!
if you still have a modicum of decency (which is probably asking too much from you), you will get your ... together and fix this right ... now!
mg...@gmail.com <mg...@gmail.com> #131
wi...@gmail.com <wi...@gmail.com> #132
ae...@gmail.com <ae...@gmail.com> #133
ar...@gmail.com <ar...@gmail.com> #134
th...@gmail.com <th...@gmail.com> #135
am...@gmail.com <am...@gmail.com> #136
as...@gmail.com <as...@gmail.com> #137
It was reported over a week ago and still no acknowledgement of the issue from Google. This is absurd.
They should be sued for such negligence and non existent customer support.
ma...@gmail.com <ma...@gmail.com> #138
gi...@gmail.com <gi...@gmail.com> #139
je...@gmail.com <je...@gmail.com> #140
Without a root cause analysis, what is the guarantee that the next security update will not break the phone again?
ku...@gmail.com <ku...@gmail.com> #141
je...@gmail.com <je...@gmail.com> #142
No answer yet. I wonder why Google does not make a statement regarding this.
be...@landler.io <be...@landler.io> #143
No file access, no ability change settings, no app updates anymore...
I can't understand that Google is still pushing the update to these phones. By now, one could even argue for "malicious intent", since they know of the issue but don't act on it, hence knowingly keep bricking customer's phones.
sk...@gmail.com <sk...@gmail.com> #144
sp...@gmail.com <sp...@gmail.com> #145
19...@gmail.com <19...@gmail.com> #146
sp...@gmail.com <sp...@gmail.com> #147
vb...@gmail.com <vb...@gmail.com> #148
ab...@googlemail.com <ab...@googlemail.com> #149
2 profiles and no access to my data from profile 1.
Not very happy
[Deleted User] <[Deleted User]> #150
fl...@googlemail.com <fl...@googlemail.com> #151
ma...@gmail.com <ma...@gmail.com> #152
wj...@gmail.com <wj...@gmail.com> #153
pa...@gmail.com <pa...@gmail.com> #154
dr...@gmail.com <dr...@gmail.com> #155
I have very important data and it wont be acceptable to just offer "wipe storage/hard reset" option!!!!!!!!
ru...@gmail.com <ru...@gmail.com> #156
Main one has no access to storage. Weirdly it did not happen immediately after the update but 2 or 3 days later. (In case that info helps anyhow).
Please fix asap!
pa...@gmail.com <pa...@gmail.com> #157
fl...@googlemail.com <fl...@googlemail.com> #158
This should definitely be P1!
je...@gmail.com <je...@gmail.com> #159
Is it possible it is android 14 with multiple profiles, triggered by an updated app?!
ri...@gmail.com <ri...@gmail.com> #160
pa...@gmail.com <pa...@gmail.com> #161
kh...@gmail.com <kh...@gmail.com> #162
Tried viewing the drive in Linux could not mount. S
kh...@gmail.com <kh...@gmail.com> #163
Searched Instagram and see no mention of the bug. Hardly anything on YouTube also. So outside of the issue tracker and a few tech news headlines, not much awareness. Google doesn't care as it doesn't impact their image and many others will upgrade. So please get the word out.
Already said would be happy to pay into a GoFundme for a Dev to fix this. Think it'd be worth it as Google isn't giving this priority.
Any lawyers out there please chime in with any thoughts on compensation. It's horrendous to think that some people have not only been inconvenienced, but been financially impacted by this.
This isn't restricted to Pixel 6. Reported on other models.
jb...@gmail.com <jb...@gmail.com> #164
Add me to this list of victims fallen ill to poor code quality control. Pixel 7 pro, updated to android 14 a few days prior, multiple profiles. Did you guys add an extra -R
to a chmod
command? No luck accessing any user storage via ADB while phone is in a failed state so any user data not backed up was lost. Factory reset from recovery was the only path to a working unit.
And no, I wont buy a new unit like support is suggesting!
ni...@gmail.com <ni...@gmail.com> #165
yv...@gmail.com <yv...@gmail.com> #166
I am able to use my primary profile (with the storage issue of course). Any ideas on what I can do while it is getting booted to prevent/reduce permanent loss of data to reduce the damage before it becomes a brick?
In my opinion, the most frustrating and infuriating aspect is the lack of official guidance from Google on this matter. I believe our best course of action, given the circumstances, is to minimize interactions with the main profile. If you need to use it, consider transferring your workload to a secondary profile, which "appears" to be unaffected by this issue.
ho...@gmail.com <ho...@gmail.com> #167
tr...@gmail.com <tr...@gmail.com> #168
On my primary profile I am unable to use camera. Files app shows 0 bytes. I am also unable to connect phone to my laptop for File transfer. All of these were possible before Android 14 upgrade on October 18th 2023.
I also had Netflix video downloaded for offline viewing and it now says external storage not found with error (OF.NA.5).
pr...@googlemail.com <pr...@googlemail.com> #169
se...@gmail.com <se...@gmail.com> #170
se...@gmail.com <se...@gmail.com> #171
ms...@gmail.com <ms...@gmail.com> #172
I'm baffled that this continues to be ignored
ma...@gmail.com <ma...@gmail.com> #173
te...@gmail.com <te...@gmail.com> #174
gu...@email.cz <gu...@email.cz> #175
To mount partition manually?
na...@gmail.com <na...@gmail.com> #176
yv...@gmail.com <yv...@gmail.com> #178
Hey people, please remember to up vote this issue.
na...@gmail.com <na...@gmail.com> #179
je...@gmail.com <je...@gmail.com> #180
fr...@gmail.com <fr...@gmail.com> #181
ni...@gmail.com <ni...@gmail.com> #183
ra...@gmail.com <ra...@gmail.com> #184
And can't use the phone
All crashed
We need answer
le...@gmail.com <le...@gmail.com> #185
ja...@gmail.com <ja...@gmail.com> #186
Updated last week, restarted phone last night, since then no access to internal storage on primary profile.
After some investigating I find this is a common issue with Pixel 6 phones since A14 yet Google aren't even acknowledging it's a thing??
re...@gmail.com <re...@gmail.com> #187
ga...@gmail.com <ga...@gmail.com> #188
jo...@gmail.com <jo...@gmail.com> #189
fr...@gmail.com <fr...@gmail.com> #191
lo...@gmail.com <lo...@gmail.com> #192
ms...@gmail.com <ms...@gmail.com> #193
sc...@gmail.com <sc...@gmail.com> #194
fl...@gmail.com <fl...@gmail.com> #195
bi...@gmail.com <bi...@gmail.com> #196
bi...@gmail.com <bi...@gmail.com> #197
ge...@gmail.com <ge...@gmail.com> #198
mo...@gmail.com <mo...@gmail.com> #199
sa...@googlemail.com <sa...@googlemail.com> #200
sk...@gmail.com <sk...@gmail.com> #201
ca...@gmail.com <ca...@gmail.com> #202
da...@gmail.com <da...@gmail.com> #203
du...@gmail.com <du...@gmail.com> #204
ca...@gmail.com <ca...@gmail.com> #205
kh...@gmail.com <kh...@gmail.com> #206
de...@gmail.com <de...@gmail.com> #207
es...@gmail.com <es...@gmail.com> #208
We need decisive actions, from the company, and a plan to fix this.
There's too many people with the error for Google to not have an official response and a timeline to fix
la...@gmail.com <la...@gmail.com> #209
ch...@gmail.com <ch...@gmail.com> #210
not something like this:
restart your smartphone.........
install updates........
factory setting.......
sk...@gmail.com <sk...@gmail.com> #211
ed...@gmail.com <ed...@gmail.com> #213
sz...@googlemail.com <sz...@googlemail.com> #214
I'm guessing if anyone has a Terminal Emulator installed already before the update, You possibly manually mount the partition to retrieve data? but i'm not sure.
I've noticed mine is showing a large amount of data in "System" so i'm guessing the data has been mounted in the wrong place.
It's also possible they could use that system reserved partition for an update.
ra...@gmail.com <ra...@gmail.com> #215
da...@gmail.com <da...@gmail.com> #216
ge...@gmail.com <ge...@gmail.com> #217
js...@gmail.com <js...@gmail.com> #218
Where's your pride Google?
da...@gmail.com <da...@gmail.com> #220
ku...@gmail.com <ku...@gmail.com> #221
je...@gmail.com <je...@gmail.com> #222
I guess that everyone is experience this. I don't want to reboot again to get a full software bricked phone!
There must be a way to reproduce this issue and troubleshoot. I hope that this is only a mount issue and not deleted data issue.
Is there a way to access the data without a working OS. The pin code is used for encryption of the data?
je...@gmail.com <je...@gmail.com> #223
Is there any way this issue can be assigned at least?
There are so many people here whom I am sure are very willing to help provide debug information. We just need someone to guide us through the next steps.
Thanks,
se...@googlemail.com <se...@googlemail.com> #224
Absolutely shocked that Google has marked this as P2 and not even assigned it despite it being a reported issue for two weeks.
This will be my last ever Google phone.
ca...@gmail.com <ca...@gmail.com> #226
lo...@gmail.com <lo...@gmail.com> #227
sa...@gmail.com <sa...@gmail.com> #228
does google think we are stupid ?
sp...@gmail.com <sp...@gmail.com> #229
ir...@gmail.com <ir...@gmail.com> #230
va...@gmail.com <va...@gmail.com> #231
an...@gmail.com <an...@gmail.com> #232
sh...@gmail.com <sh...@gmail.com> #233
mo...@gmail.com <mo...@gmail.com> #234
su...@gmail.com <su...@gmail.com> #235
How this can still only be a P2, and with no official statement from Google is both inexplicable and irresponsible.
ra...@gmail.com <ra...@gmail.com> #236
jd...@gmail.com <jd...@gmail.com> #237
vi...@googlemail.com <vi...@googlemail.com> #238
ji...@gmail.com <ji...@gmail.com> #239
os...@gmail.com <os...@gmail.com> #240
an...@gmail.com <an...@gmail.com> #241
ra...@gmail.com <ra...@gmail.com> #242
xt...@gmail.com <xt...@gmail.com> #243
po...@gmail.com <po...@gmail.com> #244
bi...@gmail.com <bi...@gmail.com> #245
ga...@gmail.com <ga...@gmail.com> #246
The guys is telling me the only solution at the moment is to do a factory reset.... :-(
co...@gmail.com <co...@gmail.com> #247
ga...@gmail.com <ga...@gmail.com> #248
The Google support guy gave me some interesting information, it didn't work for me but who knows, maybe it works for for someone else: Apparently the pixel phones have a Restart Counter, when the phone is restarted 7 times consecutively it automatically switches the boot image... so, restart the phone, wait until the power button menu works and restart again, 7 times...
vd...@gmail.com <vd...@gmail.com> #249
ge...@gmail.com <ge...@gmail.com> #250
bo...@gmail.com <bo...@gmail.com> #251
Apps have read-only access to /storage/emulated/0/Android/data folder since upgrading to Android 14.
Maybe other users are also affected, but haven't noticed yet? 🤔
For me, Gmail still works, but downloading attachments does not, for example. Ringtones on my device still work, but switching to another tone (which has never been downloaded to the device) is not possible. Also DriveSync app stopped working and reports the missing write permissions for internal storage. 😞
Google, this should be a P1 issue. 😠
ra...@gmail.com <ra...@gmail.com> #252
to...@wfg-gmbh.net <to...@wfg-gmbh.net> #253
jo...@gmail.com <jo...@gmail.com> #254
Fi...@ilux.co.uk <Fi...@ilux.co.uk> #255
ch...@gmail.com <ch...@gmail.com> #256
I just do not have access to all files in primary account and can not install/update any app. It essentially brick the whole phone (while still can using app without using any storage at all).
One fun thing I find is that while file explorer of secondary account shows ~7Gb left and seem function normally, primary account shows ~2Gb left and is completely locked up.
My phone contains all important information. Maybe time to buy a non Google phone now?
sa...@gmail.com <sa...@gmail.com> #257
I would request everyone to reply to official pixel and google tweets with links to this bug tracker and
This level of taken for grantedness for customers is unacceptable.
We spend our hard earned money for a peaceful and good experience. If I wanted headaches, I would have gone with chinese phone.
du...@gmail.com <du...@gmail.com> #258
ke...@gmail.com <ke...@gmail.com> #259
"The team is working on how to fix this issue and until then users can reach out to 1:1 support for real time assistance."
So they are at least acknowledge the issue and trying to find the way to fix it.
l....@gmail.com <l....@gmail.com> #260
de...@gmail.com <de...@gmail.com> #261
jc...@gmail.com <jc...@gmail.com> #262
al...@gmail.com <al...@gmail.com> #263
ba...@gmail.com <ba...@gmail.com> #264
3l...@gmail.com <3l...@gmail.com> #265
Status "Pixel is starting..."
ch...@hcs.us.com <ch...@hcs.us.com> #266
For me I think the triggering event was trying to download a second language in live-caption in one of the secondary profiles. After that, it was borked.
fo...@gmail.com <fo...@gmail.com> #267
Yesterday night after a reboot I can't access storage.
al...@gmail.com <al...@gmail.com> #268
Google please resolve this bug ASAP! Many users are waiting
se...@gmail.com <se...@gmail.com> #269
Sa...@gmx.de <Sa...@gmx.de> #270
ab...@googlemail.com <ab...@googlemail.com> #271
ta...@gmail.com <ta...@gmail.com> #272
fr...@gmail.com <fr...@gmail.com> #273
mi...@gmail.com <mi...@gmail.com> #274
se...@gmail.com <se...@gmail.com> #275
"Thanks for contacting Google support.
I can certainly understand your point here. However, I wouldn’t be able to comment on any information shared on third party websites and Google Forums.
You can contact us anytime you need help. We'll be happy to help you.
Have a nice day."
ma...@gmail.com <ma...@gmail.com> #276
ch...@gmail.com <ch...@gmail.com> #277
mi...@gmail.com <mi...@gmail.com> #278
Google has probably reached the lowest point in its technological history. A bad reputation that will push many users who have spent a lot of money on Pixels to leave Google and return to the safer arms of Samsung. I am stunned not only by the bug, but by the absence of an official and public apology from Google to all customers and not having made this transparent and honest communication is taking the company itself out of the concept of the digital community it would like to create (discount codes are an aspirin for a seriously ill person to compare the loss of the relationship of trust with customers). And don't expect help from influencers and YouTubers, many of whom review for a fee. The even more serious issue is represented by the fact that after ten days no official date was communicated by the company for the resolution of the bug (the problem had to be addressed and made public immediately and urgently resolved after a few hours). Pixels have become a expensive roulette. Unfortunately, I'll come down here
db...@googlemail.com <db...@googlemail.com> #279
rh...@gmail.com <rh...@gmail.com> #280
gi...@googlemail.com <gi...@googlemail.com> #281
sa...@gmail.com <sa...@gmail.com> #282
mi...@gmail.com <mi...@gmail.com> #283
yv...@gmail.com <yv...@gmail.com> #284
For those affected by this, please use the following template and post it on social media, tagging both Google and the Pixel accounts. As others have mentioned, you can also reply to posts made by Google's official accounts. Tweak the template as needed:
@google please! Fix the Android 14 bug that's kidnapping our data! How are you supposed to offer seven years of updates if you're turning these phones into bricks!? This is affecting Pixel 6, 7, and likely 8! 😡
https://issuetracker.google.com/issues/305766503 #PixelGate #Android14 #Ransomware
lo...@gmail.com <lo...@gmail.com> #285
co...@andrewjuneau.com <co...@andrewjuneau.com> #287
ju...@gmail.com <ju...@gmail.com> #288
na...@gmail.com <na...@gmail.com> #289
mi...@gmail.com <mi...@gmail.com> #290
A) factory reset
B) device exchange (so basically the same from a data preserving point of view)
C) wait until an update comes (but without being able to tell me the date or even if this issue will be fixed there)
As an apology I got a voucher for GBP 25... YAY! As if I wanted to buy something from them with this horrendous quality control and support... I'm sorry for the people who work at the support centre having to listen to frustrated customers and not being able to do anything
du...@gmail.com <du...@gmail.com> #291
If you install the app to a secondary profile, then attempt to install it to the primary profile the app will then install.
ge...@gmail.com <ge...@gmail.com> #292
ra...@gmail.com <ra...@gmail.com> #293
I have an important data for urgent matters
jo...@gmail.com <jo...@gmail.com> #294
lu...@gmail.com <lu...@gmail.com> #295
ku...@gmail.com <ku...@gmail.com> #296
My Pixel is still in warranty, if that even matters to you.
du...@gmail.com <du...@gmail.com> #297
do...@gmail.com <do...@gmail.com> #298
mi...@gmail.com <mi...@gmail.com> #299
no...@gmail.com <no...@gmail.com> #300
fa...@gmail.com <fa...@gmail.com> #301
fa...@gmail.com <fa...@gmail.com> #302
qx...@gmail.com <qx...@gmail.com> #303
ke...@gmail.com <ke...@gmail.com> #304
ch...@chrispalmer.info <ch...@chrispalmer.info> #305
Not impressed. Was already on the fence about buying a Pixel 8. That ship has sailed I'll never buy a Pixel again.
I totally understand that software bugs happen, and can rarely be fully squashed before going to production. The lack of response from Google is a choice however.
ma...@gmail.com <ma...@gmail.com> #306
I contatcted google support today but they only told me "we are working on a fix". I don't find the right words to say how disappointed I am.
ch...@chrispalmer.info <ch...@chrispalmer.info> #307
ma...@gmail.com <ma...@gmail.com> #308
le...@gmail.com <le...@gmail.com> #309
co...@gmail.com <co...@gmail.com> #310
du...@cadet.ws <du...@cadet.ws> #311
From some comments and articles read, factory reset is not an option. It does not resolve the issue.
What is Google doing about this issue. Phone is practically useless except to make calls. Can't run some apps because they require an update, which will fail due to the storage issue.
Can't take pictures or access documents stored locally. No ringtones....
ch...@chrispalmer.info <ch...@chrispalmer.info> #312
Reading through reddit threads and reports above, it appears that the "Pixel is starting" loop is often (though not always) a secondary result of the broken-symlink storage issue.
For those who only have the storage issue at this point, I highly recommend backing everything you can up to Google One (you should only need the cheapest plan) on the off chance that you get caught in the starting loop and formally lose access.
I was able to turn backups on, and successfully back up my app settings, SMS/MMS, call logs, etc, despite the storage issue. Unfortunately some individual cloud backups cannot function in this current state as they require filesystem access to create the backup file (ex. Whatsapp).
Given that it's been two weeks since some users have had this issue come up, and total radio silence from Google, it's worth taking some immediate steps to protect your data while you can.
pe...@gmail.com <pe...@gmail.com> #313
ni...@gmail.com <ni...@gmail.com> #314
ab...@gmail.com <ab...@gmail.com> #315
مو معقول كل ذا الوقت
حل الموضوع اعن منت منه
ya...@gmail.com <ya...@gmail.com> #316
sh...@gmail.com <sh...@gmail.com> #317
tp...@gmail.com <tp...@gmail.com> #318
aa...@gmail.com <aa...@gmail.com> #319
Just an UPDATE here:
I submitted a bug myself and through this same platform and went nowhere. They responded me some nonsense about submitting the bug as an android user rather than a open source developers. Like wat??
Here's the ID:
I ended up doing a factory reset on my phone (pixel 6a). My recommendation is to factory reset the phone at the very moment you get this bug. The more time it passes, the more data you'll lose, specially for apps that do not work with cloud backup.
Hope this helps!
du...@gmail.com <du...@gmail.com> #320
vo...@gmail.com <vo...@gmail.com> #321
aa...@gmail.com <aa...@gmail.com> #322
ia...@gmail.com <ia...@gmail.com> #323
ia...@gmail.com <ia...@gmail.com> #324
ma...@gmail.com <ma...@gmail.com> #325
I already installed multiple different software like ultdata without success.
mi...@gmail.com <mi...@gmail.com> #326
in...@8bitphotobooth.com <in...@8bitphotobooth.com> #327
[Deleted User] <[Deleted User]> #328
la...@gmail.com <la...@gmail.com> #329
da...@gmail.com <da...@gmail.com> #330
po...@gmail.com <po...@gmail.com> #331
la...@gmail.com <la...@gmail.com> #332
va...@gmail.com <va...@gmail.com> #333
ma...@gmail.com <ma...@gmail.com> #334
Finally she told me that she will escalate the case and the team will get back to me withing 24-48 hours.
da...@gmail.com <da...@gmail.com> #335
da...@gmail.com <da...@gmail.com> #336
er...@gmail.com <er...@gmail.com> #337
jo...@gmail.com <jo...@gmail.com> #338
... i had no option to factory reset my pixel 7a.
Since the phone wouldn't boot i had to do that from the recovery menu with the powerbutton+volumedown trick. Gone are all personally relevant photos, 2FA codes, notes, who knows what. Thankfully i had written down a bunch of single-use OTP codes for most of my accounts with my employer so i wasn't locked out of online services for long.
Going by the comments on this thread, this bug appears to affect essentially all modern pixel devices. While humans are humans and errors will occur, the passive response on the part of google does convince me that these systems are unqualified for use in professional environments. Making a mental note here as a sysadmin: do not ever buy a fleet of these things, because when the proverbial poo hits the fan, instead of running for cover, google is just going to stand there smiling open-mouthed for a whole month, saying, "have you tried resetting your phone ?"
vd...@gmail.com <vd...@gmail.com> #339
Come on Google. show some respect to your customers
se...@gmail.com <se...@gmail.com> #340
I made another ticket to see if i could add it as a child to this one and possibly get it bumped up but its impossible for me to add it as a child and its p2 s2 also...
laughable how many does it take to change or at least get a response rather than sitting in the queue ignored by someone.
gb...@gmail.com <gb...@gmail.com> #341
bu...@gmail.com <bu...@gmail.com> #342
Hiding behind unpaid, unofficial collaborators with all the plausible deniability in the world (no matter how well meaning they may be).
Screw these people. WE DEMAND A PROPER FIX. NO AMOUNT OF MONEY (ok, maybe $10,000, and even that won't be enough for some folks) will compensate the TROUBLE AND DATA LOSS they seem to be trying to get away with, and which they single handedly created.
HODL THE LINE!!! KEEP THE PRESSURE UP. Stop enabling their disgusting behavior. Don't let them get away with it, or it can only get worse from here. And next time, our reply to those who allowed it, will be: you totally had it coming, you fully deserve it, you spineless prick! Even if you don't care about a factory reset. Even if you were lucky to have a recent local backup, or foolish enough to trust them with your data in "the cloud", that doesn't change these facts. Ask yourself: will I be so lucky next time? Demand accountability and responsible behavior now, and you may get it next time, too.
also:
za...@gmail.com <za...@gmail.com> #343
te...@gmail.com <te...@gmail.com> #344
ay...@gmail.com <ay...@gmail.com> #345
du...@gmail.com <du...@gmail.com> #346
Update from me:
-
I'm still experiencing the same storage access issues - factory reset isn't an option for me if there's a chance of getting my data back
-
I've learnt this ticket isn't an official place to lodge a bug... but a great place to centralise comms with others affected
-
I've opened a support case with Google... am getting the same "we'll get back to you in 24-48 hours" ... same response others are getting
-
I've tried DMing @GooglePixel_US on Twitter... they're responsive, but can't provide any more information. They did escalate my case - and I did get an email from the "Social Support team" saying:
Please be assured, our engineering team is currently working on this for further insight and there may be a fix in a future update.
It's still quite generic with no guarantees 😞
-
There is another bug logged in this system... someone beta testing a future Android release... who seems to have hit a similar storage issue when upgrading from Android 13. That issue is assigned to a Googler (who then raised it with an engineering team), and it's rated a S0 (but a P2). I've linked them to this issue - hoping that if they feel it's the same, might help escalate.
-
A while back, I owned the Nexus 6P... and after an update... got the Boot Loop Of Death. Now this 🤦🏻
ia...@gmail.com <ia...@gmail.com> #347
Removing secondary profile
Restoring primary profile from recent backup
Restart
Would this work do you think?
gg...@gmail.com <gg...@gmail.com> #348
The issue hit me last night (2023-10-26).
I upgraded my Pixel 6 to Android 14 as soon as I got the "reboot to install Android 14" alert (appx 2023-10-05).
My phone already had primary and secondary users set up, and I switched between them multiple times a day. The user switching continued to work after upgrading to Android 14: I switched between accounts multiple times a day. Last night, my battery died. I plugged it in to an Anker charger, turned on the phone (which doubles as my alarm clock), and went to bed. (I'm highlighting the Anker charger to specify the phone was connected to a charging device; it was not connected to a data device like a computer.)
This morning (2023-10-27), I went to refresh my podcasts and the app threw a "Storage problem" error ("Your external storage is not available (unmountable)." Installed apps are reacting in different ways:
- some close immediately: DiskUsage, Pikmin Bloom
- some display an error: DoggCatcher
- some have reduced functionality: cannot download videos in Netflix; cannot save files in Firefox
- some applications appear to be unaffected (perhaps not fully tested?): Disney+, Ring, Waze
When the phone is connected to a computer and "File transfer / Android Auto" is selected, the computer displays an empty folder where "internal storage" used to be.
The secondary user account is not experiencing any issues.
se...@gmail.com <se...@gmail.com> #349
others have tried removing the second profile and its only compounded the issue as some are unable to get into anything in the phone with the main account.
Some like me rebooted their device and now have had a brick for a week waiting for an update to flash to hopefully not loose all storage as they dont backup with google but make local backups.
je...@gmail.com <je...@gmail.com> #350
- upvoting gave a close to reality scope of how many people might be affected [ transparency] (Google wants 1:1 support call to keep everything internal)
- we found the scope was not limited to pixel 6 (includes 7 and maybe even pixelfold)
- we found support had a standard response (will get back to you, factory reset, replace your hardware/free under warranty and pay if not, no ETA for fix)
- that the rollout continues , despite our issue
- that there are no official acknowledgement yet of this issue to the public. Although they say they are working on it, I have not seen anyone post a response where Google has repeated the details of the problem.
Also, this place is im sure crawling with the best minds who have in depth knowledge of android and more direct lines to the people who need to know. I hope they are taking a stab at recreating the issue.
Hopefully some devs here can step up and recreate the issue and submit a more technical description to the people who need to know. I'm sure a good number of the 500+ who upvoted is willing to provide bug reports to help solve this.
ch...@chrispalmer.info <ch...@chrispalmer.info> #351
@348 My issue also appeared after an overnight dead battery. Upon reconnection to my charger and the new auto-boot, the issue began.
I wonder if this is a random coincidence or if something happens during the mount process on boot that causes this. Interesting nonetheless.
se...@gmail.com <se...@gmail.com> #352
it doesent cover everything as im sure this is someone just scraping anything they can off the internet to post with a chatbot speaking what they typed but hey its yet another source
kr...@gmail.com <kr...@gmail.com> #353
Just had this happen on my new Pixel Tablet. Stuck in a Pixel is Starting loop after it tried to factory reset after a device restart.
Join the face-palming discussion here:
qx...@gmail.com <qx...@gmail.com> #354
Unfortunately, the video was just a waste of time, advising reboot, or to do a factory reset. It then loops the same information a few times and it was published 8 days ago.
Support repeated that supervisors coming back to you in 24-48 hours line..
ia...@gmail.com <ia...@gmail.com> #355
se...@gmail.com <se...@gmail.com> #356
@354 yeah unfortunately but i wanted to post it as its at least another form of media " covering the issue"
lu...@gmail.com <lu...@gmail.com> #357
lu...@gmail.com <lu...@gmail.com> #358
ab...@gmail.com <ab...@gmail.com> #359
الى الان لم يتم فعل اي شي
صمت صمت صمت !!
انتم سيئن
st...@gmail.com <st...@gmail.com> #360
je...@gmail.com <je...@gmail.com> #361
lu...@gmail.com <lu...@gmail.com> #362
ma...@gmail.com <ma...@gmail.com> #363
gu...@email.cz <gu...@email.cz> #364
ml...@gmail.com <ml...@gmail.com> #365
sh...@wtf.sg <sh...@wtf.sg> #366
da...@gmail.com <da...@gmail.com> #367
ma...@gmail.com <ma...@gmail.com> #368
ga...@gmail.com <ga...@gmail.com> #369
I did that 2 days ago, they called me to tell me the phone is unfixable and to contact Google Support again, so I did that and they are now sending me a replacement... freaking google, tons of data lost... :-( this will at least give me some time with a replacement device while maybe someone figures out to recover the data...
je...@gmail.com <je...@gmail.com> #370
What happens when you install a 2nd profile and update to android 14 again?
el...@gmail.com <el...@gmail.com> #371
kr...@gmail.com <kr...@gmail.com> #372
ke...@gmail.com <ke...@gmail.com> #373
Unlike flashing the phone, if side loading could work then the data is preserved.
Waiting to hear from Google...
vi...@gmail.com <vi...@gmail.com> #374
ti...@gmail.com <ti...@gmail.com> #375
je...@gmail.com <je...@gmail.com> #376
jc...@gmail.com <jc...@gmail.com> #377
d....@gmail.com <d....@gmail.com> #378
pi...@gmail.com <pi...@gmail.com> #379
Google needs to fix this asap !!!
da...@ulap.co <da...@ulap.co> #380
You inspired me to also create the issue through my google work email which is linked to the device. I have raised the issue to other android users in our company and have recommended to use non google devices for our security requirements. Furthermore, it's worth noting that we are on the brink of escalating this matter to our contacts in the DOD due to the severity of the issue. The bug not only constitutes a significant denial of service but also bears a resemblance to ransomware attacks.
bi...@gmail.com <bi...@gmail.com> #381
ad...@gmail.com <ad...@gmail.com> #382
da...@ulap.co <da...@ulap.co> #383
If, on the other hand, you find an issue that requires a Factory Reset to fix, or if you can trigger the reboot remotely (e.g. via a malformed media file on a website), then it qualifies as a security issue.
https://bughunters.google.com/learn/invalid-reports/android-platform/5148417640366080/bugs-with-negligible-security-impact#triggering-a-local-temporary-denial-of-service
According to Google's own guidelines, an issue that requires a Factory Reset to resolve qualifies as a security concern. The issue at hand falls into this category and, considering its potential implications, I believe it demands prompt attention.
I want to highlight a potentially critical security vulnerability in the current production release of the Android platform, which requires a Factory Reset to address. This vulnerability is concerning due to its impact on users and the potential for malicious exploitation.
Implications:
User Impact: Requiring a Factory Reset for resolution is a significant inconvenience to users and results in data loss. This can have serious consequences, particularly for enterprise users.
Malicious Potential: While the initial observation may not suggest malicious intent, the need for a Factory Reset raises concerns about possible exploitation and malicious activities.
Request:
Given the potential severity of this vulnerability and its impact on a production release, I strongly request that the security team at Google expedite their investigation and response. Swift action is essential to address the security implications and protect Android users from potential exploitation.
We understand the importance of allowing developers time to assess and resolve issues, but in this case, prioritizing the issue due to its impact on a production release is vital.
We urgently seek a response from Google to address this security concern and protect the Android platform and its users.
Thank you for your commitment to ensuring the security and reliability of the Android platform.
br...@google.com <br...@google.com> #384
da...@gmail.com <da...@gmail.com> #385
yv...@gmail.com <yv...@gmail.com> #386
I am also experiencing this issue, and am incredibly frustrated at the lack of information from Google. I fear that I have lost/am going to lose a considerable amount of files/information due to this.
Ditto. At this point my empathy for Google is P4
.
ia...@gmail.com <ia...@gmail.com> #387
Any tech heads that can shed light on if we will have an acceptable resolution to this?
Whatever happens, Google has lost a serious amount of goodwill towards them. I barely stuck by the Pixel after losing cellular reception for almost a whole month last year from an update, this could push me away from Google phones for good.
wi...@outlook.com <wi...@outlook.com> #388
st...@googlemail.com <st...@googlemail.com> #389
fa...@gmail.com <fa...@gmail.com> #390
I am shifting back to iPhone.
ma...@googlemail.com <ma...@googlemail.com> #391
Seit heute früh kann ich keine Bilder mit der Kamera mehr machen, beim start wird mir angezeigt das der Speicher voll ist. Die Bilder die ich gestern aufgenommen habe, und wahrscheinlich noch nicht im Drive gesichert sind, kann ich in voller Auflösung öffnen, die anderen Bilder sind nur als Vorschaubilder zu sehen, total pixelig und unscharf. Auch Apps lassen sich nicht seit heute früh installieren, Update genauso. Komisch ist das ich gestern noch Apps installieren konnte. Vielleicht liegt das Problem nicht an den Telefonen sondern an irgendeinem Server von Google.
Ich werde heute Abend versuchen die restlichen Daten auf meinem Telefon zu sichern und eigentlich will ich es nicht das Telefon zurück setzen.
ro...@gmail.com <ro...@gmail.com> #392
st...@gmail.com <st...@gmail.com> #393
ab...@gmail.com <ab...@gmail.com> #394
فقط تريدون ضياع مزيد من الوقت
#393
ke...@gmail.com <ke...@gmail.com> #395
Google isa big organisation. The people at device-support are probably just reading scripts and are based abroad. It feels like their job is to close a query, rather than to solve a problem.
"br...@google.com <br...@google.com> #384" is probably someone in the Pixel development team who finaally acknowledged the problem. So, a small step forward.
la...@gmail.com <la...@gmail.com> #396
yi...@gmail.com <yi...@gmail.com> #397
I am wondering, what does it take for something to be P0?
I own a Pixel 6 and I have been a hardcore fan of Google branded phones, going back to the Nexus series.
I was thinking to replace my Pixel 6 with a Pixel 8. But why bother? Support is pretty much non existing.
This ticket is a statement that Google does not care about frustrated users or about user data.
Note: I had a Google Pixel 1 with a microphone issue. Google acknowledged it 1 year after the problem was reported.
mi...@gmail.com <mi...@gmail.com> #398
a....@gmail.com <a....@gmail.com> #399
an...@gmail.com <an...@gmail.com> #400
Today I could not take a screenshoot as pointed by others. After that the phone was buggy so I restarted and never came back
va...@gmail.com <va...@gmail.com> #401
ma...@gmail.com <ma...@gmail.com> #402
se...@gmail.com <se...@gmail.com> #403
ma...@googlemail.com <ma...@googlemail.com> #404
Anscheinend weiß Google von dem Problem seit dem 7. Oktober und nichts passiert. Man erlaubt sich von Seiten Google die zurecht gefrusteten Nutzer Rezensionen zu löschen. Tolles Unternehmen. Ich wohne leider nicht in den USA. Hoffe aber sehr, das es dort eine große Sammelklage gibt.
ro...@gmail.com <ro...@gmail.com> #405
vielen Dank, dass Sie sich mit uns in Verbindung gesetzt haben.
Wir haben diese Informationen zur weiteren Überprüfung an unser internes Team weitergeleitet. Derzeit lässt sich nicht genau abschätzen, wann zusätzliche Angaben verfügbar sein werden.
Falls Sie weitere Fragen haben, können Sie sich jederzeit wieder an uns wenden.
note that the internal team, yes the experts of Google should be^^
va...@butanescu.com <va...@butanescu.com> #406
My secondary account was buggy even on Android 13. The apps would go super slow and the gestures did not work sometimes. When I updated to Android 14 it was happening the same.
Have to confirm that, when the work profile was unpaused things were getting laggy or consistently not work completely (like double tap to wake). This is what probably saved me for now as I have the profile paused most of the time.
There is probably some bug that involves something being open in one place while some app is updated and writes in some other place unexpectedly, or it can't update or unmount something or something along these lines. Google needs to figure out what's happening, come up with a fix, and with some guidance about what to do to avoid this (can we remove the work profile or it might trigger the problem, should we allow or not allow this or that app or the OS to get updated, and so on).
po...@gmail.com <po...@gmail.com> #407
je...@gmail.com <je...@gmail.com> #408
ha...@gmail.com <ha...@gmail.com> #409
pa...@google.com <pa...@google.com>
ji...@gmail.com <ji...@gmail.com> #410
mi...@gmail.com <mi...@gmail.com> #411
mi...@gmail.com <mi...@gmail.com> #412
rr...@gmail.com <rr...@gmail.com> #413
I did lose all my local files and all my photos that weren't synced with Google photos, even though support insisted multiple times that I would not. I didn't believe them, but my phone has been dysfunctional for days now and I didn't know what else to do. Besides turn off auto updates for the future.
ke...@gmail.com <ke...@gmail.com> #414
Are you able to advise how you were able to get to a specialised unit? All I got was pointless responses trying to fob me off.
Also, how could that be in next month's update? Phones already affected won't boot and will not be able to receive OTA updates (it has to be via SDCard since Pixel doesn't have a SD slot, or ADB - but there may be problems there).
ma...@nerox.io <ma...@nerox.io> #415
Im really sad that this happened when im on holiday and i need access to my authenticator apps, which i have no backup with me of course.
mi...@gmail.com <mi...@gmail.com> #416
in developer mode I sent the report file to Google and the support team in the United States and the operator (very kind and empathetic, a rarity in all this chaos) told me that this file had been sent to the specialists (with the number of my device IMEI and with a privacy consent statement for the use of data sent with the bug report file). This entire procedure dated October 24th (after I pointed out that hundreds of other users in the forums had the same problem and that what they told me from support in Italy was not correct: factory reset and inelegant subscription request, backup and conversation settlement in 3 minutes). To my further request for a software update date, the response was: "It should be on the next month's update."
br...@gmail.com <br...@gmail.com> #417
have anyone of those ..i have a Galaxy A13..please help me i live in
colorado usa ..the other accounts are out of state I don't know I know one
of them is Japan
On Sat, Oct 28, 2023, 10:38 AM <buganizer-system@google.com> wrote:
va...@butanescu.com <va...@butanescu.com> #418
Maybe this would be a good time to remind Google that we actually need the ability to have COMPLETE backups of our devices, not to still reconfigure apps and find what we're missing for 3 weeks after a "successful" restore using any and all methods we currently have to back up our devices.
Ideally with all the main scenarios (Google Drive, self-hosted and computer-tethered) but in the end even one would be literally infinitely more than what we have now.
pj...@gmail.com <pj...@gmail.com> #419
ro...@gmail.com <ro...@gmail.com> #420
pj...@gmail.com <pj...@gmail.com> #421
ke...@gmail.com <ke...@gmail.com> #422
" I sent the report file to Google"
Thank you.
I think the device support Chat / Email support are based abroad and was probably the wrong way to do it :-(
Now it has got their attention, let's see how Google will be able to redeem itself/regain our goodwill (or not).
a....@gmail.com <a....@gmail.com> #423
[Deleted User] <[Deleted User]> #424
sa...@gmail.com <sa...@gmail.com> #425
I am able to apply updates from the secondary profile, but yes they are only limited to the Play Store Updates and the Google Play System Updates.
ma...@gravitate.energy <ma...@gravitate.energy> #426
ah...@gmail.com <ah...@gmail.com> #428
@#418
"Maybe this would be a good time to remind Google that we actually need the ability to have COMPLETE backups of our devices, not to still reconfigure apps and find what we're missing for 3 weeks after a "successful" restore using any and all methods we currently have to back up our devices.
Ideally with all the main scenarios (Google Drive, self-hosted and computer-tethered) but in the end even one would be literally infinitely more than what we have now."
I was going to ask something like this, but wordier. Besides a paid Google One account, what backup options are there that would be set-it-and-forget-it and that would allow me easily to restore my phone to its previous state? Apps, app data, desktop setup, icon placement, etc. I realize that this is complex, but I don't know the details.
If I knew for sure that I could restore my phone to its previous state - even if it was just my main account for now and the secondary accounts later - then I would have done a factory reset as soon as this issue occurred. It would have been a blip in my life.
When I ran CyanogenMod on my Nexus 4, I could use TWRP to do a full backup, brick the phone, and then restore EVERYTHING to its as-before state. This was nice, but it was a manual operation and it required rooting the phone, which itself required me to start from scratch. It required me to keep a lot of free storage on my phone and computer, but it was nothing by today's standards. My N4 only has 8GB of STORAGE (not RAM/memory, but storage for the OS, apps, photos, etc.).
If there was a way to do this type of full backup, say, each night while my phone charged and have it upload the backup image over my local wifi to local storage, I could have said darn, factory reset, and then restored to the previous-known-good image and then keep going. If my local storage fails because I'm an idiot, that's on me and I should reconsider throwing a few bucks a month Google's way for storage.
pr...@gmail.com <pr...@gmail.com> #429
And now I cannot download anything 😞.
Please fix this soon or just send affected users the new Pixel 8.
ia...@gmail.com <ia...@gmail.com> #430
I was holding out for a fix and not reset so as not to lose my data but is this even possible now??
a2...@gmail.com <a2...@gmail.com> #431
ch...@chrispalmer.info <ch...@chrispalmer.info> #432
@420 a fix is still likely possible, so I wouldn't lose hope. It seems like this comes down to a broken symlink that is preventing user 0 storage from mounting at boot.
Google could likely push a fix out via their recovery tool (something they'd undoubtedly need to do for those stuck in the "pixel is starting" loop). They could also push an update via a core component that can be updated via a secondary profile (ex. Google Play Services)
That said, even if the error is simple, the fix is likely non trivial. Hopefully the Google team is pushing extra time on this one.
gu...@email.cz <gu...@email.cz> #433
du...@gmail.com <du...@gmail.com> #434
yi...@gmail.com <yi...@gmail.com> #435
a....@gmail.com <a....@gmail.com> #436
is it possible to reapply the latest stock google firmware?, i would try it out if it might fix it?
ha...@gmail.com <ha...@gmail.com> #437
si...@gmail.com <si...@gmail.com> #438
I'm wondering if creating a 4th profile for me could work until resolution... But I'm afraid to make things worse (don't know if this can be worse... My phone seems useless at this point)
lu...@gmail.com <lu...@gmail.com> #439
For all of you out there with a soft-bricked Pixel waiting for a fix: forget it and do a Factory reset as there will be no fix for you. Google has already halted the Android 14 update (for the few lucky ones that did not yet receive it) and what they will do next, is to fix the OTA update and just restart the deployment after that. The others? The most you can expect is a Google Play voucher worth of 25 USD. Unfortunately, that's the reality.
je...@gmail.com <je...@gmail.com> #440
jo...@gmail.com <jo...@gmail.com> #441
te...@gmail.com <te...@gmail.com> #442
fa...@gmail.com <fa...@gmail.com> #443
yu...@gmail.com <yu...@gmail.com> #444
I did want to note that my primary profile has the "Shelter" app previously installed, and my work profile with Shelter is able to access the internal storage without an issue, however this is only limited to the items that were downloaded within the work profile.
je...@gmail.com <je...@gmail.com> #445
After factory resetting I wanted to see if it would happen again. After all I have nothing to lose now, I already lost all that was to be lost.
I created a second user profile WITHOUT switching to it, phone was fine for several hours of use. I switched to it, completed the initial setup, downloaded 1 app, and switched back to main profile. Suddenly my phone was behaving exactly how it had before. So I deleted the second profile and turned off multiple profiles but I was still having crazy UI issues. So I held my breath and reset my phone and it came up 100% normal. Granted I did all of this pretty quick, and I didn't have some of the issues I had the first time on the test go-around, so it may just be that I stopped the process quickly enough that deleting the second profile before rebooting was enough to save it, but it's absolutely infuriating that google hasn't responded to this issue yet.
je...@gmail.com <je...@gmail.com> #446
sh...@gmail.com <sh...@gmail.com> #447
du...@gmail.com <du...@gmail.com> #448
Checking back here every now and then... and I see this issue has been assigned and reclassified to P0
and S0
🙂
Google devs... thanks for the acknowledgement that this is being looked into.
I can't imagine the pressure you're currently working under.
jo...@gmail.com <jo...@gmail.com> #449
ry...@gmail.com <ry...@gmail.com> #450
da...@gmail.com <da...@gmail.com> #451
da...@gmail.com <da...@gmail.com> #452
ti...@gmail.com <ti...@gmail.com> #453
ch...@gmail.com <ch...@gmail.com> #454
va...@butanescu.com <va...@butanescu.com> #455
when are expected to have the fix released?
Given that it took a little over 11 days for the issue to be assigned, and there is no indication that the root cause is know, or how the fix (if any) will be released, if it'll be able to fix existing installs (and in which state they need to be in order for that to work) ... I'd say the secret to happiness is low expectations.
ma...@gmail.com <ma...@gmail.com> #456
an...@gmail.com <an...@gmail.com> #457
mi...@gmail.com <mi...@gmail.com> #458
al...@gmail.com <al...@gmail.com> #459
In my case, no app updates can be installed in primary profile --> this is a massive security problem as Chrome and many apps no longer receive security updates.
I have a Pixel 6a with two profiles and the 1st profile has no access to storage.
ce...@gmail.com <ce...@gmail.com> #460
Even though I cannot update apps in primary profile, updating apps in secondary profile via play store automatically updates the same apps in primary profile as well, for my 6A at least.
va...@butanescu.com <va...@butanescu.com> #461
In my case, no app updates can be installed in primary profile --> this is a massive security problem as Chrome and many apps no longer receive security updates.
Do not worry, THIS problem will fix itself when the device gets bricked, then it'll be fully secure.
s....@gmail.com <s....@gmail.com> #462
ma...@gmail.com <ma...@gmail.com> #463
ro...@gmail.com <ro...@gmail.com> #464
a....@gmail.com <a....@gmail.com> #465
z....@googlemail.com <z....@googlemail.com> #466
an...@gmail.com <an...@gmail.com> #467
Multiple accounts had bugs like making the phone slow or gestures not working since the Pixel 6 even on Android 13. I thought that would be fixed on the Pixel 7 Pro. Not the case. Android 14 came along and also I was facing issues.
Yesterday the worst happened and I could even enter the phone. I was amazed that this bug was reported more than a week ago and was on P2 (Has been changed to P0 finally probably thanks to media coverage)... I need my phone to work so I had to factory reset losing my personal data that cannot be recovered... This is not small bug if the only solution to use your phone is to delete all your data. Also my watch had to be reset to factory to reconnect.
As a developer I know bugs can happen but I have the feeling the Pixel phone is not taken seriously. The multiple accounts bugs have been for years and are not addressed. It seems that multiple accounts funcionality never was tested on Pixels by google, as even this is a huge bug, as I told before, another smaller bugs have been all over the place for years and were not fixed with new phones or updates.
I can not recommend Pixel phones anymore and I will have to switch to another phone brand with my next phone.
ma...@googlemail.com <ma...@googlemail.com> #468
Ich habe Mal bei Disney einen Film heruntergeladen. Das funktionierte, ich konnte diesen Offline sehen. Wahrscheinlich hat das was mit den noch übriggebliebenen 4 GB zu tun.
Ich denke alle mit der 128 GB Ausführung haben eines gemeinsam - 4 GB frei 96 Prozent sind belegt.
Ich hatte ein bisschen in den Systemdateien geblättert. Mir ist eine versteckte Systemdatei mit der Bezeichnung "Medien" aufgefallen, deren Cache über 20 GB bei mir groß ist. Es könnte vielleicht sein, das dort meine gesamten Daten versteckt sind.
Vielleicht sind das empfehlenswerte Informationen für das Google Team.
to...@gmail.com <to...@gmail.com> #469
da...@gmail.com <da...@gmail.com> #470
uz...@gmail.com <uz...@gmail.com> #471
ma...@gmail.com <ma...@gmail.com> #472
ma...@gmail.com <ma...@gmail.com> #473
ua...@gmail.com <ua...@gmail.com> #474
ir...@gmail.com <ir...@gmail.com> #475
But apart from that, for the ones with Android 14 and multiple profiles, probably a good thing in general would be not to do big stuff, app updates, offline maps updates and so on? Stay on the main profile? Stay on the profile you are now? Remove the extra profile? DON'T touch the extra profile? Don't reboot? Do reboot (in case it's something that has a chance to be triggered by X amount of uptime)?
The only somehow safe path for now looks to be to wipe every device that was touched by multiple profiles and not touch this feature again, but that's outrageous.
je...@gmail.com <je...@gmail.com> #476
After updating to Android 14, there were initially no apparent issues. A second user profile is available.
However, the following problems arose for the main user:
No access to the gallery via WhatsApp. Error message: "Storage full".
The camera app is not usable.
App updates via the PlayStore are not possible.
The swipe function (from bottom to top) is impaired, especially on a screen without the three digital buttons.
Saving is not possible.
The smartphone is barely operable; only emergency functions are available.
Backup functions are not usable, preventing access to existing data.
om...@gmail.com <om...@gmail.com> #477
Was able to use my phone today morning, post that similar issue as reported by others.
ma...@gmail.com <ma...@gmail.com> #478
je...@gmail.com <je...@gmail.com> #479
ru...@gmail.com <ru...@gmail.com> #480
ga...@gmail.com <ga...@gmail.com> #481
gr...@gmail.com <gr...@gmail.com> #482
di...@gmail.com <di...@gmail.com> #483
mo...@gmail.com <mo...@gmail.com> #484
This is completely unacceptable due to the lack of a response from Google, and it's imperative to emphasize that this affects all current Pixel users.
ah...@gmail.com <ah...@gmail.com> #485
@#429
Please fix this soon or just send affected users the new Pixel 8.
I was thinking about this comment and while I don't see Google just mailing out Pixel 8's to people, there is an option that I can see being reasonable IMO. Assuming the "fix" is to do a factory reset and start over (and not something more elaborate, but that saves your data), affected users who are subscribed to or who switch to Fi could get a Pixel 8 with the "on us" deal (pay retail but get it back in bill credits over two years). Maybe throw in a Basic (100GB) Google One subscription free or for the reduced price ($0.75/mo) for life (and just tack it on to my Fi bill).
(Comedy option: Make my Gmail go back to growing constantly over time like it did back in the day! NEVER DELETE ANOTHER EMAIL!!!)
I would consider this fair (and possibly even BETTER for Google) as 1) the P8 has a longer support period, so you're using Google services (and creating revenue-generating data for them) for a longer period of time and 2) it would allow me to run beta versions of Android on my P6a for as long as it's supported. Currently I only have the one Pixel and don't have a good reason to buy another one just to play around with buggy software in my free time (I do enough of that at work!).
ro...@gmail.com <ro...@gmail.com> #486
jo...@gmail.com <jo...@gmail.com> #487
A year ago my Samsung Galaxy 20 also got stuck in a boot loop... maybe it's time to finally try the iPhone.
at...@gmail.com <at...@gmail.com> #488
ed...@gmail.com <ed...@gmail.com> #489
This is such a bad bug. On the broken profile Gmail app can't even display images, another email app can display images, but can't download or share them
yi...@gmail.com <yi...@gmail.com> #490
The first mistake was that the issue was declared as P2 for 8 days. The second issue is that it is P0 and we still have no official statement from Google.
Let me summarize the points of frustration:
- this issue is equivalent to a ransomware
- the data is there but we can access them
- the only entity that can help is Google and the support says: replace device with a pixel 8 and enable backup to the cloud (which means Google One, a paid service)
- Asking the user to do a factory reset is unacceptable: the user owns the data
- asking the user to backup on the cloud is unacceptable, given that there is only one backup service and it is a paid service. Google removed adb backups to just force people to get Google One subscriptions
- This whole behavior is disrespectful to the users. Google invested a lot in Google Pixel 8. The way this issue was handled is just negative publicity.
ma...@nerox.io <ma...@nerox.io> #491
after like an hour i tried to reboot it, .. same
... went into fastboot again and tried to wipe it again.. giving me following output:
```
Wiping data ...
ERROR: recovery: [libfs_mgr] Unable to enable ext4 verity on /dev/block/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing
ERROR: recovery: Open failed: /metadata/ota: No such file or directory
Formatting /data...
Formatting /metadata ...
Resetting memetag message...
Wiping Titnan M....
Wiping keys...
Data wipe complete.
```
im a bit clueless on howto move on, i am glad if i could fully reset it somehow. but have it bootloader locked, can not go into developer mode / usb debug mode ...
mi...@gmail.com <mi...@gmail.com> #492
my...@gmail.com <my...@gmail.com> #493
se...@gmail.com <se...@gmail.com> #494
Loosing data is not an option, please help.
vi...@gmail.com <vi...@gmail.com> #495
Need a fix soon!
am...@gmail.com <am...@gmail.com> #496
I liked the open system, but now, I started to think about my next phone will be an iPhone...
eg...@gmail.com <eg...@gmail.com> #497
am...@gmail.com <am...@gmail.com> #498
Facing the same issue on Pixel 6. One support is playing "transfer the chat" game. At least be responsible, IT'S OUR DATA,NOT YOUR DEVELOPER'S PLAYGROUND!!!!!!
ra...@gmail.com <ra...@gmail.com> #499
Cleaning storage was stuck and now no userspace file is accessible for the main user.
Storage manager and file manager crashes upon opening any detail. Secondary profile/user works normally and I was able to clean 40GB on the phone, but the issue continues.
I can still install and remove apps, but even backups are stuck, so I can't backup to reset the phone and fix the issue.
ma...@kelhamtechnologies.co.uk <ma...@kelhamtechnologies.co.uk> #500
ca...@google.com <ca...@google.com> #501
We are aware of an issue occurring on some Pixel devices (Pixel 6 and later models) that have both received the Android 14 update and have multiple users (other than the primary user) set up. Multiple users include
Depending on the device, this issue can result in the primary user being unable to access media storage. Alternatively, the issue can reboot the device with a “Factory data reset” message. If this message is accepted, data that is not backed up can be lost, and if it is declined, the device repeatedly reboots with the “Pixel is starting” message.
We’re continuing to work on fixes for impacted devices, and have already pushed out a Google Play system update that will help prevent this issue from being triggered on additional devices. To check if a Google Play system update is available for your device, follow the instructions in this
If you’re experiencing this issue: If your impacted device is unable to access media storage, we anticipate a system update will repair the issue and restore access to media files without requiring a factory reset. If your device is stuck in a "Pixel is starting" boot loop due to this issue, we are investigating methods that may be able to recover some data. We’ll provide more information as soon as it is available.
For users who are not experiencing this issue, or have already factory reset their device, we recommend avoiding creating or logging into a secondary user on the device until the OTA update is available.
We're sorry for the inconvenience this has caused, and we appreciate your patience.
ch...@gmail.com <ch...@gmail.com> #502
Pixel 6 with 34GB of free space.
no...@gmail.com <no...@gmail.com> #503
aa...@gmail.com <aa...@gmail.com> #504
Here's the official update regarding this issue:
I recommend subscribing to the thread to get the updates in real time.
Hope it helps!
- Aaron Muniz
je...@gmail.com <je...@gmail.com> #505
ga...@gmail.com <ga...@gmail.com> #506
me...@gmail.com <me...@gmail.com> #507
ca...@gmail.com <ca...@gmail.com> #508
je...@gmail.com <je...@gmail.com> #509
If the problem is mitigated by a Google play security update, is it logical to assume that the problem is related to Google play? Or an app that was exploiting a security hole in Google play (advertently or inadvertently)?
Seems we all have to be a little more patient, but there seems to be some light here. Hoping for the best (but not holding my breath just yet).
do...@gmail.com <do...@gmail.com> #510
Given that I am already stuck in the boot screen, I was thinking to use the PRT but I can't back up anything.
ma...@gmail.com <ma...@gmail.com> #511
Secondary account was a "work only" profile, thankfully reassigning OTP keys isn't a nightmare.
Specifically got the "Pixel is starting" version of the bug.
Unfortunately since the bootloader was still locked, I didn't have as many debugging options or available logs. Since I couldn't swap active partitions for this reason, I tried re-sideloading the OTA per some random theory.
No luck there.
After their factory reset, gave it a couple days and started to create a new secondary profile. The device immediately rebooted, didn't create the new profile, but thankfully didn't nuke the phone at it's current point.
Based on
Following that logic, my guess is the multiprofile logic, which seems to securely isolate each profile from one another, has a glitch that's getting profile X to write some portions of it's encrypted data to profile Y's encrypted sectors, ultimately corrupting a filesystem/keys/encryption/etc since the IO pattern would be encrypted with a different profile's keys. I have no involvement with Google, so this is purely just tossing a random theory into the wind.
va...@butanescu.com <va...@butanescu.com> #512
As #506 says I too don't see any Play system update above the 1st of October. It's probably making its way through I guess.
Note for everyone that might be puzzled about which update we're waiting for (to PREVENT the issue, not to fix it for the people that already have trouble): it is "Google Play system update" under "System and updates". It ISN'T the regular system update and it ISN'T coming via Play Store updates.
Speaking of Play Store there are tons of Android System Update, Play Update and similarly named (of course third party) apps. There are literally two apps called "Pixel Launcher" (nothing more nothing less). I know the Play Store it's supposed to be the Wild West (and that's why we like it to some extent more than the competition) but somehow this is "too wild".
ak...@gmail.com <ak...@gmail.com> #513
Please fix ASAP! It's is making it impossible to use my phone and applications.
ug...@gmail.com <ug...@gmail.com> #515
a....@corp.nekki.ru <a....@corp.nekki.ru> #516
sk...@gmail.com <sk...@gmail.com> #517
se...@gmail.com <se...@gmail.com> #518
Sad cause I had to buy this one that way I wouldn't have to wipe my 6a and loose precious baby photos. I am happy they are finally responding, thank you.
la...@gmail.com <la...@gmail.com> #519
I'm sure it will be here eventually but just wanted to leave a page up if there is one available.
ch...@gmail.com <ch...@gmail.com> #520
al...@gmail.com <al...@gmail.com> #521
el...@gmail.com <el...@gmail.com> #522
je...@gmail.com <je...@gmail.com> #523
It is not possible to have a cell phone without being able to use it.
da...@ulap.co <da...@ulap.co> #524
Official statement from google here. They are creating mitigations for the various manifestations of the issue. Unfortunately, there is no big fix yet, but there is finally movement.
Thank you for the hard work. I'm sure it was a long weekend.
ah...@gmail.com <ah...@gmail.com> #525
@#519
See the link posted by Aaron in #504
As he says - subscribe to the thread so you get updates in real-time.
Don't worry - unlike this one, that thread is locked, so there are no "me too" posts and you'll only get updates when it's worth reading :-)
My understanding of the current situation is it's a bit like the movie Speed - just keep moving and don't make too many changes, or else...
If you're on a device that would be affected (i.e. a Pixel 6/7/a on A13 with multiple profiles) you can download a Play System update that will mean that you won't encounter this issue if you upgrade to Android 14. As someone else says, this is confusing, but Play System updates are separate from security updates and app updates. On the up-side, even very old versions of Android can still get Play System updates (like at least back to Android 11, maybe even further back?)
If you're already on Android 14, but not in a "Pixel is starting...." bootloop and just can't access the memory, don't reboot or switch profiles. In my experience, switching profiles caused the phone to become slower and slower and warm to the touch until it spontaneously rebooted on its own, so I got into the habit of just rebooting in order to switch from my secondary profiles to my primary in order to preserve battery and a little of my sanity. I had previously reached out to the Pixel social team on Twitter/X for help, who transferred me to Fi Support because that's where I got my P6a, and they suggested a factory reset.
(Aside: If your answer to all issues is to factory reset or reboot, I would be concerned about being replaced with a robot... Sure, it works most of the time, but cmon)
If you're already in the bootloop (like me), just hang tight and they might be able to save some of your data. I'm guessing this will be done with the Chrome Android update tool.
I'm anxious for this issue to be resolved. At the same time, I hope that the engineers and developers are able to take the time to solve the problem correctly. (i.e. it'd be nice if I get my phone back up and running and if profile switching finally worked smoothly...)
vi...@gmail.com <vi...@gmail.com> #526
sk...@gmail.com <sk...@gmail.com> #527
Open your device’s Settings app.
Tap Security & privacy and then Updates.
For security updates, tap Security Update.
For Google Play system updates, tap Google Play system update.
je...@gmail.com <je...@gmail.com> #528
Also, I'm sure everyone is getting paid premium overtime money, for a problem they created and sat on for a long time.Thats just a fact.
So much personal data still held hostage for me and other... And for others who were guided by support to factory reset, data gone forever.
Credits is due when the problem is fixed, but at the moment, they just need to do their jobs...
mo...@gmail.com <mo...@gmail.com> #529
gu...@gmail.com <gu...@gmail.com> #530
Won't be using your Android crap again.
be...@gmail.com <be...@gmail.com> #531
dr...@gmail.com <dr...@gmail.com> #532
eb...@google.com <eb...@google.com> #533
Hi, this is Eric from the Android engineering team. I wanted to step in to answer a few questions and give a few clarifications:
What should impacted users do?
I realize this is the most important question, but I don't have much to add to
Note that the Google Play system update, which is already available, is preventative; it doesn't help already-impacted users.
As always, you can also contact Pixel Support to talk with an agent one-on-one.
How do I tell if I've gotten the (preventative) Google Play system update?
You've gotten it if your device shows "Google Play System Update: October 1, 2023", and you've checked for updates and none is available. Unfortunately, both the old and new October updates show the same date of October 1, but checking for an update should ensure that you've gotten the new one.
Why wasn't this issue acknowledged earlier?
We've actually been working on this since October 16, and the internal issue has been P0 (highest priority) since October 19. There seem to have been several factors that contributed to the public issue not being updated. We'll be looking very closely at how the gap in communication happened and seeing how we can prevent it in the future. I appreciate everyone's persistence in reporting this issue, and the details you provided were very valuable in diagnosing this issue.
Why wasn't this issue found before release?
We'll be looking at this very closely later; currently our highest priority is to help impacted users. But there seem to have been multiple factors that contributed to this, including: the issue was not triggered by Android 14 alone, but rather by an unexpected interaction between the September Google Play system update and Android 14; the issue only occurs on devices with secondary users; and the issue happened only after the device has been used for a while, not immediately.
Why are only Pixel 6 and later device models affected?
A certain kernel change was necessary for this issue to occur, and only these devices received that change as part of the Android 14 update (and received the Android 14 update in the first place).
ke...@gmail.com <ke...@gmail.com> #534
Perhaps there is a lesson to be learnt here as if the issue was known on 16/10 and yet the update was continued to deployed via OTA until one or two days ago. Device-support did not appear to be briefed about the issue either and continued to provide silly "replies".
There is a feeling that it was only when media coverage was picked up by someone "high up" that the issue finally received the proper attention.
Finally, thank you for finally actively updating the community and working tireless for a fix. Better late than never..
me...@gmail.com <me...@gmail.com> #535
ga...@gmail.com <ga...@gmail.com> #536
That said, for devices stuck in the "Pixel is starting", recovering media files is great but unfortunately not enough, the dumb google one backups are quite incomplete and do not backup downloads or documents or data in any folder manually created, or data for many applications...
Sounds like recovering these devices to boot normally without factory reset is not possible? if so, please make an afford to not just recover media file, but all data from the device...
lu...@gmail.com <lu...@gmail.com> #537
For devices stuck in the "Pixel is starting", we are investigating a solution that should recover media files, as long as you did not accept the factory reset prompt.
It was Google support that told me there's no other way to get my phone back to normal if not a factory reset! And due to lack of communication I finally went that way! I've lost very important photos (to me) and am very saddened! How can you, Google, make up for this?
mi...@gmail.com <mi...@gmail.com> #538
a....@gmail.com <a....@gmail.com> #539
I want to recommend that you tell the support team to tell people who have this issue that the team is working on the bug currently and refer them to this issue. If I wasn't a developer and wanted to see if I had other options I would have gone with their recommendation and lost my data forever.
nh...@gmail.com <nh...@gmail.com> #540
do...@gmail.com <do...@gmail.com> #541
For those of us stuck in a boot loop, is the desired solution from Google that we will be unstuck and regain full access to our devices or is the outcome that we'll have a way to pull our media files but still have to reset the device?
Also, are there plans to compensate users for this? Many of us rely on our phone to do our jobs and don't have a second device just lying around. When we downloaded a normal version of an OS, not a beta, we expect it to work.
eb...@google.com <eb...@google.com> #542
As others commented here, when I contacted the support they told me the only options I had were a factory reset and warranty options. Which was unacceptable as first choices.
I want to recommend that you tell the support team to tell people who have this issue that the team is working on the bug currently and refer them to this issue.
I've confirmed with Support that they have the latest information, and "wait" is being given as an option too. I don't know the exact timeline of when information was conveyed to them, but we'll be taking a close look at anything that could have been done better.
For those of us stuck in a boot loop, is the desired solution from Google that we will be unstuck and regain full access to our devices or is the outcome that we'll have a way to pull our media files but still have to reset the device?
We're still looking into this.
bu...@gmail.com <bu...@gmail.com> #543
Responsibility, ever heard of that?
I got this bug on Oct 23. That is ONE WEEK, 168 hours, 604800 seconds after you first got notice of the bug. All you had to do was simply STOP the rollout, or at the very least WARN users about this potential issue. Instead, all I got was ads about how great the new Pixel 8 was. Why did you keep pushing the update one week later?
Look, for those of us caught in the boot loop, getting back "some data" ( #501 ), our "media" ( #533 ) is very disquieting.
I've got HUNDREDS of (anonymimzed) patient notes seen in the last three months, in a note taking app.
DOZENS of bookmarks and probably A HUNDRED important browser tabs open.
OVER A HUNDRED new contacts which I may need to reach out to in years to come.
Conversations in Whatsapp groups that no longer exist.
Losing that data, in these circumstances and with full knowledge on your part, is something I will never forgive. I'd be willing to pay upwards of $10k to recover it (not to you, of course). Imagine that.
As you may see, I totally expect to recover more than "some" data, and am willing to go to great lengths to get exactly that. Even if that means suing for the very first time in my life.
Sincerely hoping you are underselling your data recovery skills. Even if takes sending in our devices.
je...@gmail.com <je...@gmail.com> #544
bu...@gmail.com <bu...@gmail.com> #545
Are you telling us you knew about this since Oct 16, but nonchalantly decided to keep the poison spreading until now? What the actual ...? Responsibility, ever heard of that?
I got this bug on Oct 23. That is ONE WEEK, 168 hours, 604800 seconds after you first got notice of the bug. All you had to do was simply STOP the rollout, or at the very least WARN users about this potential issue. Instead, all I got was ads about how great the new Pixel 8 was. Why did you keep pushing the update one week later?
Look, for those of us caught in the boot loop, getting back "some data" as per
I've got HUNDREDS of (anonymimzed) patient notes seen in the last three months, in a note taking app. DOZENS of bookmarks and probably A HUNDRED important browser tabs open. OVER A HUNDRED new contacts which I may need to reach out to in years to come. Conversations in Whatsapp groups that no longer exist.
Losing that data, in these circumstances and with full knowledge on your part, is something I will never forgive. I'd be willing to pay upwards of $10k to recover it (not to you, of course). Imagine that.
As you may see, I totally expect to recover more than "some" data, and am willing to go to great lengths to get exactly that. Even if that means suing for the very first time in my life.
Sincerely hoping you are underselling your data recovery skills. Even if takes sending in our devices.
mi...@gmail.com <mi...@gmail.com> #546
You know what? I never had an issue with Huawei... It looks that I made really stupid decision to buy Google phone for safety reasons.
ch...@chrispalmer.info <ch...@chrispalmer.info> #547
Thanks Eric for the update. Hopefully nobody attacks you directly. It's not like you pushed the code yourself.
I have to agree with others that the statement that you've known about this issue since the 16th is disconcerting. It was only publicly acknowledged on the 29th.
Given there were likely preventative steps that could have been taken by users in the interim (not updating to A14, not using secondary profiles, not downloading the September play update, etc etc), the lack of communication effectively exacerbated the issue.
I very much do appreciate the update, but the amount of goodwill lost here is significant. Even a perfect fix at this point is unlikely to repair the reputational damage done.
eb...@google.com <eb...@google.com> #548
Just to clarify, the date I mentioned was just when this issue first started being investigated. This was a complex issue, and it took time for it to be investigated, including understanding its impact on different devices and determining which update had actually been responsible (considering that this issue was caused by an interaction of a Google Play system update with a regular system update, not by one update alone). I agree that communication has not been adequate, and we'll keep you updated going forwards.
br...@gmail.com <br...@gmail.com> #549
On Mon, Oct 30, 2023, 5:52 PM <buganizer-system@google.com> wrote:
du...@gmail.com <du...@gmail.com> #550
I suggested Pixel phones to various friends and family members, I've been directly responsible for several people making the switch, and now I have to apologise to those close to me who trusted my judgement when their phones no longer work.
fa...@gmail.com <fa...@gmail.com> #551
am...@gmail.com <am...@gmail.com> #552
k3...@gmail.com <k3...@gmail.com> #553
Use another profile (or guest), install the app there. Once it's fully downloaded, switch back to the main profile and install it again. This time, since it is already on your phone, it will fully install to your profile. If the app requires storage access like your camera, well, that part of the issue will still be a problem.
But at least you can install apps now.
6 pro here.
km...@gmail.com <km...@gmail.com> #554
je...@gmail.com <je...@gmail.com> #555
ab...@gmail.com <ab...@gmail.com> #556
da...@gmail.com <da...@gmail.com> #557
Same with my Pixel 6a. The gallery had no images or videos so I checked File Manager but it showed nothing then I tried to Restart it hoping it will fix this issue but after restarting it Showed Data is corrupted Factory Resetting Device and then it stuck in Pixel is Starting.... Boot Loop. So, I had to Factory Reset from Bios menu.
an...@gmail.com <an...@gmail.com> #558
ja...@gmail.com <ja...@gmail.com> #559
an...@gmail.com <an...@gmail.com> #560
But showed that either factory reset or try again,
Chosen try again option, after appearing google logo
Screen shows " Pixel is starting .... "
I can take phone call if using earphones 😄
So my question is when will my pixel sart again???
ig...@gmail.com <ig...@gmail.com> #561
ja...@gmail.com <ja...@gmail.com> #562
lo...@gmail.com <lo...@gmail.com> #563
- It affects not only pixel 6, but also 7 and above.
- According to Eric, this is caused by a google play services update interaction with andoid update
- It's not only storage access, the issue also causes a bootloop
js...@gmail.com <js...@gmail.com> #564
Issues arise when trying to open images in WhatsApp. Now no access to internal storage In time manger or for any apps.
mi...@gmail.com <mi...@gmail.com> #565
It was recommended to update to the latest version. How will this happen when the OS doesn't have storage function!?
mi...@gmail.com <mi...@gmail.com> #566
Waiting for the fix ASAP please!
sk...@gmail.com <sk...@gmail.com> #567
gr...@gmail.com <gr...@gmail.com> #568
Installed the 14 sometime last week. Two nights ago (29th), I noticed that the security pattern suddenly stopped working properly. Kept saying 'wrong' even when I used correct pattern. Restarted the phone. Now it stuck in FastBoot mode. I can't get out of it.
NOS-production: error
Device-State: error!
Boot-slot: b
Enter reason: failed to load/verify boot images
cb...@gmail.com <cb...@gmail.com> #569
in Settings > Security > Updates
On Tue, Oct 31, 2023, 9:23 AM <buganizer-system@google.com> wrote:
im...@gmail.com <im...@gmail.com> #570
ma...@gmail.com <ma...@gmail.com> #571
If a P0 issue takes them this much time to be fixed - I don't even want to ask how long it will take until they fix the battery draining and bluetooth issues with the new Pixel 8 devices.
mi...@gmail.com <mi...@gmail.com> #572
el...@gmail.com <el...@gmail.com> #573
do...@gmail.com <do...@gmail.com> #574
ro...@gmail.com <ro...@gmail.com> #575
ma...@gmail.com <ma...@gmail.com> #576
Woke up to find mine in the "Pixel Is starting" bootloop this morning.
I refuse to factory reset and lose all my data. Plz fix bruh.
la...@gmail.com <la...@gmail.com> #577
Shouldn't have traded in my Samsung .
ya...@gmail.com <ya...@gmail.com> #578
yi...@gmail.com <yi...@gmail.com> #579
Hey Eric from the Android team (
The least you can do for now is give us some daily update on the status of the fix.
je...@gmail.com <je...@gmail.com> #580
gr...@gmail.com <gr...@gmail.com> #581
I am on Vacation and can't take picture or do almost anything on my pixel 6Pro - how wonderful 🤨. This is totally unacceptable.
mi...@gmail.com <mi...@gmail.com> #582
do...@gmail.com <do...@gmail.com> #583
Frankly, I am not ok with "a discount voucher". Even if fixed eventually (and I truly hope you guys can figure this out like yesterday because every minute, hour, day makes it a bit worse), but there is true opportunity cost here, true losses for people that depend on their phone to do their work, and even simple things like logging into a bank account to pay bills is not possible which in turn can create overdraft fees and other issues.
So fix it and figure out how you'll make it up to neglected customers.
da...@gmail.com <da...@gmail.com> #584
Is there any more details to provide towards the technical reasons of the issue? There seems to have been a lot of small changes to the ways volumes are mounted and users are assigned storage. We could be leveraging the full expertise of the android community to solve a critical vulnerability for users. I consider this a win anything at all helps expedite the fix.
Based on some of the logs below, we can begin to trace the code.
Are there any talks of creating a CVE ID to track the issue for the greater community?
ch...@gmail.com <ch...@gmail.com> #586
hu...@gmail.com <hu...@gmail.com> #587
re...@gmail.com <re...@gmail.com> #588
At this point I don't think I can trust the phone again even if the issue gets resolved.
br...@gmail.com <br...@gmail.com> #589
es...@gmail.com <es...@gmail.com> #590
ad...@gmail.com <ad...@gmail.com> #591
ma...@gmail.com <ma...@gmail.com> #592
Just went to ensure the preventative Google Play patch was loaded on my Pixel 7 Pro, and it TRIGGERED THE BUG!!!
Stupid me, it was working before and I should've just left it alone.
My device had "Google Play System Update: September 1, 2023", I hit the "check for updates", which gave me a reboot button.
I hit the reboot button and it rebooted straight to recovery offering me to "Try again" or "Factory Reset".
Now I'm stuck on "Pixel is starting...".
Thanks Google! The preventative update can trigger it too!
yu...@gmail.com <yu...@gmail.com> #593
What are the conditions for the bootloop? Does anyone know?
I had created a 2nd profile on the 27th not knowing there was a bug. This caused both the main and 2nd profile to lag considerably when swiping up to get to the home screen. I was able to restart a few times, and finally the delay stopped occurring. I realized there was an issue with the storage later that night, where I found out about this bug. Ever since reading about the possibility of a bootloop, I haven't restarted since, nor have I really used any apps so it doesn't use up all the "cache/storage???" in case causes some random overflow and automatically trigger a mandatory restart that could result in the bootloop.
I can't afford to lose the pictures and videos I took from my recent month long trip that ended a few days prior to the start of this issue. It's been stressful, definitely did not sleep well the first couple of days.
bi...@gmail.com <bi...@gmail.com> #594
It'll be good, they said.
I can deal with the bad battery life, I can deal with the shit carrier support, but having my phone being bricked all of a sudden after I return to my desk? Naaah
I am beyond enraged right now. I have to leave all of my work data on the phone, because some asshat Google engineer didn't feel a need for passing QA.
Provide a fix soon.
To the community: We should organize a case. Hit Google in the money, where it hurts them. Probably the court case would be solved quicker than this bug...
sh...@wtf.sg <sh...@wtf.sg> #595
va...@gmail.com <va...@gmail.com> #597
se...@gmail.com <se...@gmail.com> #598
Factory reset is not a workaround.
If there is no workaround or fix for the phones which are struck in boot, please let us know. Waiting for this long without any update and without a phone is frustrating.
hu...@gmail.com <hu...@gmail.com> #599
1) in case there will be an update, it has to be updated via main profile, where the storage is full?
2) is there any mechanism to push critical updates despite lack of storage in the phone's main profile?
ry...@gmail.com <ry...@gmail.com> #600
bc...@gmail.com <bc...@gmail.com> #601
This lack of communication is really really astoundingly bad. iPhone is looking like a much better option than a pixel 8.
to...@gmail.com <to...@gmail.com> #602
I cannot update my APPs, launch the camera, or access internal storage on my Pixel 6 Pro now.
tc...@gmail.com <tc...@gmail.com> #603
Since I read in the article, that a security update is supposed to "prevent" the issue, I tried to install it, only to be now stuck in the said boot loop.
Did I just really lose all of my data yet again? I can't restore my banking apps that easily and require access to the phone. Please find a solution to restore access to the phone from the boot loop.
If it's not possible, at least tell us so we don't have to wait and be stuck without a phone. In this age and day to be "unreachable" is not very good. I can't even use a replacement phone, since I am using an eSim and this is also my **only** eSim device.
ma...@googlemail.com <ma...@googlemail.com> #604
Vielen Dank für die Info.
ia...@gmail.com <ia...@gmail.com> #605
This is NOT good enough. November is here now, no ETA on a fix from Google, the incompetence is astounding.
Speaks volumes for the paid YouTube shills too that none have passed any remarks on this issue, trust in the community is very low (for me anyway)
ir...@gmail.com <ir...@gmail.com> #606
I have been offered a replacement Pixel 6 from Google. Great, a new model of the phone with the same software problem.
The only safe ones for sure are the ones not receiving Android 14. "Fortunately" there are plenty of them as for example the Pixel 4a isn't receiving any updates of any kind, despite being barely 3 years old this summer. Pixel 5 is also out of software support (including security updates) as of today, but I think there's a chance you'll get (the bad) Android 14 though.
Actually this is a good question, if Pixel 5 is eligible only to whatever update that broke everything, but not to further support, what happens? Ok, maybe Pixel 5 won't be affected anyway but what if Google drags this fix so long that Pixel 6 is too out of support? If you think that's unthinkable I'll show you unfixed tickets since 2018.
la...@gmail.com <la...@gmail.com> #607
an...@gmail.com <an...@gmail.com> #608
Has anyone tried to change the active slot? fastboot set_active b or fastboot set_active a depending on the slot you're in
al...@gmail.com <al...@gmail.com> #609
sl...@gmail.com <sl...@gmail.com> #610
No access to storage
mu...@gmail.com <mu...@gmail.com> #611
gl...@gmail.com <gl...@gmail.com> #612
tr...@gmail.com <tr...@gmail.com> #613
ju...@gmail.com <ju...@gmail.com> #615
Just click on the +1 button at the top right corner and wait patiently, like the rest. It is a pain in the ass for those subscribed to the tracker that actually await news from google (good old Eric)
ia...@gmail.com <ia...@gmail.com> #616
Also, there is a Google Play update available on secondary profile also but it requires a restart...which I am reluctant to do in case of bricking device
su...@gmail.com <su...@gmail.com> #617
Well, people get a Pixel for 2 major reasons: (1) Immediate availability of the latest Android updates & (2) Camera. Other than these two, it is a pretty sub-par phone overall at that price point.
Now imagine these exact two things getting broken on a Pixel - the "latest" Android update locking the phone to a semi-brick state, and the first thing that bricked-state affects is the camera - it is now unusable because of no storage!
Last ever Pixel for me or for any one in my recommendation network after this fiasco! Google engineering (or rather the lack of it) is just not worth it.
st...@gmail.com <st...@gmail.com> #618
st...@gmail.com <st...@gmail.com> #619
yi...@gmail.com <yi...@gmail.com> #620
Dear Google reps,
Here are my arguments:
- there is a significant lack of official communication
- Google is keeping our data hostage
- All the Google support reps recommended two options: a) we should buy the new Google Pixel 8, and / or b) we should backup our data using Google One, a paid service by Google
I think these arguments will stand well in a class action.
We will call it: A class action... made for Google
du...@gmail.com <du...@gmail.com> #621
dr...@gmail.com <dr...@gmail.com> #622
fa...@gmail.com <fa...@gmail.com> #623
If I could use my warranty I would but unfortunately I bought the phone from mexico through Amazon import.
A real mess.
ia...@gmail.com <ia...@gmail.com> #624
cb...@gmail.com <cb...@gmail.com> #625
get sent to the wrong person" bug when Android was new.
On Wed, Nov 1, 2023, 5:25 PM <buganizer-system@google.com> wrote:
wa...@gmail.com <wa...@gmail.com> #626
st...@gmail.com <st...@gmail.com> #627
Hey, goodle, what's the problem or you fired all good developers?
da...@gmail.com <da...@gmail.com> #628
ve...@gmail.com <ve...@gmail.com> #629
ca...@gmail.com <ca...@gmail.com> #630
hb...@gmail.com <hb...@gmail.com> #631
Pixel 6 Pro
...and to think I was about to pull the trigger on a Pixel 8 Pro. Not likely now.
ad...@gmail.com <ad...@gmail.com> #632
ca...@gmail.com <ca...@gmail.com> #633
ro...@gmail.com <ro...@gmail.com> #634
So just to be clear, if my pixel 6 is unable to access local storage (data seems to be there since I can see how much storage is being used total, just not the breakdown), I should wait for a Google play update that will re-enable access to local storage. And this will not result in any lost data? (as long as I don't factory reset) Most of the important stuff is backed up but I have media and some other files that weren't backed up on purpose, which are now inaccessible
do...@gmail.com <do...@gmail.com> #635
But could you guys just give 2 updates a day? Is that too much to ask? Every day at noon and in the evening update on progress, is it going well, are we days away etc. I don't know how that's too much to ask from a company like Google. We feel not heard, not talked to, and that leads to a lot of anxiety over our data (and again our livelihoods since our jobs may well depend on a usable phone). So the least you guys can do is show that you're working on the problem. Show some compassion.
I don't care where the update is, just make it daily, ideally more than once, keep us in the loop, be proactive. Come on.
kw...@gmail.com <kw...@gmail.com> #636
stupid me should keeping use my iPhone.
rf...@gmail.com <rf...@gmail.com> #637
rf...@gmail.com <rf...@gmail.com> #638
presence to save ourselves.
<buganizer-system@google.com> 於 2023年11月2日 週四 上午10:35寫道:
nh...@gmail.com <nh...@gmail.com> #639
mu...@gmail.com <mu...@gmail.com> #640
-The developers have all the information that they need. Hundreds of people contacted support to send information to the developers. Including myself many went out of their way to provide additional information that includes personalized data.
-The issue was reported to Google on Oct 8 (This is the date from the major Reddit thread.) But, guess what? They either IGNORED the reports coming from people for 2 WEEKS, or they let more people suffer by not acting on it because action on it would be a confession.
Here is a comment for @Eric. You said that you became aware of this issue on Oct 16. Coincidentally, I also reported my case on Oct 16, and when I reported, there were about 100 people who upvoted the Google support thread and the Reddit thread. And yet, on Oct 17, the support said to me, "I can't comment on the third-party sites, and we did not receive any such cases where customers were unable to access files on their device or storage outage after installing updates." Here are the possibilities that I could come up with:
-Possibility 1: Your support and engineering teams are so disconnected that after hundreds of reports, your support team still does not know you are working on the issue.
-Possibility 2: Your support team is lying.
-Possibility 3: The engineering team is lying.
Regardless of what the case is, fix your support team. They are not saying anything other than "How about a factory reset" or "We are working on it."
za...@gmail.com <za...@gmail.com> #641
what is that for a company. The phone has been always Buggy and now this !!!
in...@wellnessprudential.com <in...@wellnessprudential.com> #642
re...@gmail.com <re...@gmail.com> #643
(These two have been broken since Android 13. But now it hit a new low on 14 by bricking my 6a.)
With these two combined, added with the offense to Material Design that googled called "material you", Android is now the most horrendous UI experience.
ma...@gmail.com <ma...@gmail.com> #644
I really hope it will have some serious consequences for google. I miss my windows phone.
mi...@gmail.com <mi...@gmail.com> #645
br...@gmail.com <br...@gmail.com> #646
GOOGLE YOU TUBE EVERYTHING ELSE NOT GETTING ALL MY EMAILS I DONT KNOW WHERE
THERE GOING TO MY EMAILS KEEP GETTING BLOCKED N MY APPS OR deleting my
goverment emails or my accounts can anyone help me i got like 62 or more
hacking me please i need help
On Thu, Nov 2, 2023, 4:31 AM <buganizer-system@google.com> wrote:
ma...@gmail.com <ma...@gmail.com> #647
Here is the text she sent me:
"This email is in regards to the query you have raised. I am sorry for the trouble caused to you. We have checked this case and as per update from internal teams we have two resolutions which you may try to resolve the issue.
We are set to have a software update rolled out in the November security patch which will resolve the issue.
In case you do not wish to wait for the update, please check if your data is backed up and try factory data reset."
ko...@gmail.com <ko...@gmail.com> #648
Apart from this, there's also another issue that's been happening for 2 years: when switching users, Pixel Launcher freezes and you need to force quit the Pixel Launcher in order to work again.
ko...@gmail.com <ko...@gmail.com> #649
After updating, it forces you to restart device. After rebooting the issue still persists and it's not fixed.
ko...@gmail.com <ko...@gmail.com> #650
ta...@gmail.com <ta...@gmail.com> #651
hu...@gmail.com <hu...@gmail.com> #652
ko...@gmail.com <ko...@gmail.com> #653
ko...@gmail.com <ko...@gmail.com> #654
an...@gmail.com <an...@gmail.com> #655
See
ko...@gmail.com <ko...@gmail.com> #656
dj...@gmail.com <dj...@gmail.com> #657
ko...@gmail.com <ko...@gmail.com> #658
gu...@gmail.com <gu...@gmail.com> #659
I did a reset on my Pixel tablet and until now it works since 3 days with two active profiles.
I also reset the Pixel 6 after waiting for a too long period for a fix. Right now I only work with one profile, as it is business critical.
td...@gmail.com <td...@gmail.com> #660
ms...@gmail.com <ms...@gmail.com> #661
je...@gmail.com <je...@gmail.com> #662
Even the 'official' announcement was only done as a community posting, and can't even be commented on and not referenced in the official help page of Google. It is mainly scoped to the audience who already fell in the hole. I mean, how would someone not having the issue yet know to search the community page for such an announcement?
IMO, this is the right place to upvote and express grievances, because this is a page Google cannot ignore.
It shows the numbers (at least the ones not duped by support to factory reset or buy a new phone). They already tell you officially when calling support that they don't look at third party sites like reddit at the very least, the upvotes here is a minimum head count.
In reality, all pixel phones 6 and above updating to android 14 are vulnerable to this issue. They just haven't triggered it yet.
I hope someone here can point more media and bring more attention to this tracker thread. Let's keep Google accountable.
And Google, a daily update would have been the best action, even if the update was no update. And having a preventative fix means you already figured something out, so an ETA is a realistic expectation from us.unless it was all a lie
What a sht show.
st...@gmail.com <st...@gmail.com> #663
Contacted support trying to find out if the update that is failing on my device is this supposed fix.... It's not working.
They said we see our team is working on it and will email you but I'm not confident anymore.
ma...@gmail.com <ma...@gmail.com> #665
Oh and it would be nice if you could get in touch with someone (even a damn robot) instead of scouring the internet for any kind of an answer:)
I am genuinely panicking thanks to your approach to this.
THANKS!!
ga...@gmail.com <ga...@gmail.com> #666
ia...@gmail.com <ia...@gmail.com> #667
I have been assured, if you have a replacement (I assume Pixel) device, doing a new setup (data transfer) via USB will recover ALL data to the new device. Including any secondary profiles.
I pressed the support guy on this and he told this has been tested internally and found to be working.
When I asked why this information was not available online & publicly he could of course not comment on that.
Do I trust this info? Not in the slightest. Anyone tried this yet?
va...@butanescu.com <va...@butanescu.com> #668
I have been assured, if you have a replacement (I assume Pixel) device, doing a new setup (data transfer) via USB will recover ALL data to the new device. Including any secondary profiles.
Anyone who has done this even under the best conditions with a working device and without any bug and even with only a profile can tell you this can't be true. There are a lot of apps where you need to follow their own workflow to recover from a backup, if you have configured one and it worked well (most popular example is of course WhatsApp) and many, many apps that will just have all their data wiped on the new device.
hb...@gmail.com <hb...@gmail.com> #669
hb...@gmail.com <hb...@gmail.com> #670
st...@gmail.com <st...@gmail.com> #671
m....@gmail.com <m....@gmail.com> #672
cm...@googlemail.com <cm...@googlemail.com> #673
ah...@gmail.com <ah...@gmail.com> #674
#643 I'm a user of Android's two most dangerously broken features nowadays: Multiple users and the 3-button navigation bar.
If there is any good to come from this issue discussion, it is that I know now that my phone getting warm, slow, getting terrible battery life, and spontaneously rebooting after switching between users was in fact a common complaint. I also tried to use the three button navigation on my 6a and gave up when apps didn't quite work right. I did get used to it after a while, but it was annoying to have to pick one option over the other because it was buggier and not because I actually preferred one over the other.
Here's hoping this issue marks an inflection point where Android releases actually do get better over time. You can do it Googlers! (Alphabetters???)
#639 This isn't the place for whining and threats. Contribute with information that might support the Developers
Thank you for your efforts. They are very much appreciated ;-)
As long as I'm posting, I might as well include that Fi support did recommend waiting on Engineering to get back with a fix or to do a factory reset. I don't like it, but the reality is that these are the only two options at the moment. Nevertheless, I'm waiting...very patiently.
Lastly, while I'm at it here's the link to where you can subscribe to get the official updates.
If you're looking to reduce your notification fatigue a bit, subscribe there and unsubscribe here.
ko...@gmail.com <ko...@gmail.com> #675
Have had this for two years now.
ch...@gmail.com <ch...@gmail.com> #676
[Deleted User] <[Deleted User]> #677
sp...@gmail.com <sp...@gmail.com> #678
I pay for Google one, YouTube premium and update my pixel every 2 years and before this debacle was about to pull the trigger on getting the P8. Not now I'm syncing my Google one data to my local NAS and cancelling my subscriptions and will turn to a different provider. This is simply not acceptable behaviour from a so called innovator of technology.
Time to move out the Google ecosystem for me.
mu...@gmail.com <mu...@gmail.com> #679
@667 A week ago, support claimed that the drive backup works, too. If that would solve the issue, they would immediately make that info public and brag about how they solved the problem. I think that they are just stalling people with these additional questions, processes, etc.
wa...@gmail.com <wa...@gmail.com> #680
Here's hoping they identify a way to recover the data of bootlooped devices and do so expeditiously.
ia...@gmail.com <ia...@gmail.com> #681
But that would involve giving a f*ck about your customers in the first place.
bo...@gmail.com <bo...@gmail.com> #682
mu...@gmail.com <mu...@gmail.com> #683
bo...@gmail.com <bo...@gmail.com> #684
ju...@gmail.com <ju...@gmail.com> #685
st...@gmail.com <st...@gmail.com> #686
ko...@gmail.com <ko...@gmail.com> #687
st...@gmail.com <st...@gmail.com> #688
vy...@gmail.com <vy...@gmail.com> #689
bo...@gmail.com <bo...@gmail.com> #690
yu...@gmail.com <yu...@gmail.com> #691
This was always Google's plan, to use OTA and fix it.
From their community post: "If you’re experiencing this issue: If your impacted device is unable to access media storage, we anticipate a system update will repair the issue and restore access to media files without requiring a factory reset."
It seems like a new android beta just came out today. However, no mention of it profile storage bug getting patched.
Has anyone else given this a go?
@682
Does the secondary profile still work? Or is this basically a state where the 2nd profile was never logged into, and the moment you go into it again, the storage bug occurs?
bo...@gmail.com <bo...@gmail.com> #692
Then settings - system - system upgrade
The fix is not listed in the changelog.
bo...@gmail.com <bo...@gmail.com> #693
os...@gmail.com <os...@gmail.com> #694
sa...@gmail.com <sa...@gmail.com> #696
It did start downloading, but I paused and cancelled it.
Seems like it should work!
Thanks #692!
jj...@gmail.com <jj...@gmail.com> #697
sz...@googlemail.com <sz...@googlemail.com> #698
I'll be trying that first thing in the morning to see if it works.
sa...@gmail.com <sa...@gmail.com> #699
Hopefully it will restart normally !!
Fingers crossed!
ja...@gmail.com <ja...@gmail.com> #700
can confirm the new beta program release has fixed the issue for me
sz...@googlemail.com <sz...@googlemail.com> #701
la...@gmail.com <la...@gmail.com> #702
I don't have much hope of that happening but maybe something eventually will.
sh...@wtf.sg <sh...@wtf.sg> #703
lo...@gmail.com <lo...@gmail.com> #704
vy...@gmail.com <vy...@gmail.com> #705
That might be alluding to this problem
Also saw somewhere (not verified) that the beta will be fully released in 5 days
sz...@googlemail.com <sz...@googlemail.com> #706
So you still lost all your data with the beta update?
sa...@gmail.com <sa...@gmail.com> #707
I kept my secondary profile intact with files on that profile as well..
Hopefully both profiles will still have the DATA!!!!
sh...@wtf.sg <sh...@wtf.sg> #708
sz...@googlemail.com <sz...@googlemail.com> #709
td...@gmail.com <td...@gmail.com> #710
hu...@gmail.com <hu...@gmail.com> #711
wa...@gmail.com <wa...@gmail.com> #712
"Warning: Flashing to a Beta build from a production build—or going back to a production build from a Beta build—requires a full device reset that removes all user data on the device. Make sure to back up the data from your Pixel first."
Will sideloading the beta wipe the phone just like a factory reset would?
sa...@gmail.com <sa...@gmail.com> #713
Secondary profile also worked for me !!
Settings App no longer crashes!!
sz...@googlemail.com <sz...@googlemail.com> #714
And in future I'll be backing up ALL of my phone's data to my NAS.
Always backed up the Very important photos. But not the rest.
je...@gmail.com <je...@gmail.com> #715
hb...@gmail.com <hb...@gmail.com> #716
tr...@gmail.com <tr...@gmail.com> #717
ca...@google.com <ca...@google.com> #718
Update 11/02/2023
Thanks again for your patience. Starting in the next two weeks, we’ll roll out an Android update for impacted users that will return their devices to an operable state. Unfortunately, this update may not enable data to be recovered for devices that are repeatedly rebooting.
In the meantime, we’re actively working with users 1:1 via
– This will clear your device’s storage, so we only recommend this if you have recently backed up your data. FDR can be completed even if your phone is repeatedly rebootingFactory Data Reset (FDR) .using the device’s buttons - Over The Air (OTA) Test Update – We’re currently testing the upcoming Android System update over-the-air. For devices where the primary user is unable to access media storage, this may help remedy the issue without clearing your device’s data. Complete
to receive the test update within 24 hours, which can take 1-2 hours to fully update.this form
If your device is impacted by this issue and you’d like to try these workarounds, Pixel Support is ready to assist with step-by-step instructions. We’ll provide more information as soon as it is available.
td...@gmail.com <td...@gmail.com> #719
da...@gmail.com <da...@gmail.com> #720
kr...@gmail.com <kr...@gmail.com> #721
yu...@gmail.com <yu...@gmail.com> #722
Not risking the potential for bootloop.
am...@gmail.com <am...@gmail.com> #723
wa...@gmail.com <wa...@gmail.com> #724
jm...@gmail.com <jm...@gmail.com> #725
jm...@gmail.com <jm...@gmail.com> #726
os...@gmail.com <os...@gmail.com> #727
I found the beta zip image files @
wa...@gmail.com <wa...@gmail.com> #728
On Thu, Nov 2, 2023, 7:27 PM <buganizer-system@google.com> wrote:
an...@gmail.com <an...@gmail.com> #729
cj...@gmail.com <cj...@gmail.com> #730
Many thanks to the Google team for making this update available early.
Hint - for anyone waiting for the OTA update - go in and force a system update check in Settings -> System.
po...@gmail.com <po...@gmail.com> #731
ma...@gmail.com <ma...@gmail.com> #732
:C
That's what I'm still stuck in. I filled out the form but I guess that wasnt for me. P7P here.
to...@tommon.com <to...@tommon.com> #733
"Leaving the beta program
You can opt out of the program at any time to return to the stable public version of Android. When you opt-out of the program, all user data on the device will be wiped.
During the beta program’s release cycle, there will be stable releases to the public (the official platform release followed by Quarterly Platform Releases (QPRs)). When you apply the stable release update for the version you’re beta testing, you can opt out without a data wipe for a limited time until you apply the next beta update."
So, get the beta, then get the stable (when it releases), and if you don't want to be locked into a beta without doing a factory reset, remember to opt-out, as soon as you get stable installed.
km...@gmail.com <km...@gmail.com> #734
Same as #729 and #730
After the Test OTA Update no issues (so far).
je...@gmail.com <je...@gmail.com> #735
I was able to save my family photos and videos, and all apps are finally getting updated. Camera is back online as well.
Hope your team can focus to help the boot loop folks now and save their data as well
Hopefully an RCA as well when all is done.
sh...@gmail.com <sh...@gmail.com> #736
Although I will be backing up all my data because I don't want to take any risks as the fix is in beta testing. I will be waiting for a stable public release update.
sh...@gmail.com <sh...@gmail.com> #737
gr...@gmail.com <gr...@gmail.com> #738
ju...@gmail.com <ju...@gmail.com> #739
ma...@knaup.io <ma...@knaup.io> #740
My Pixel 6 was booting but storage was inaccessible. Today I updated to the latest beta using the normal system update after the
st...@gmail.com <st...@gmail.com> #741
I´m relieved, but also puzzled by this experience, waited to upgrade to Android 14 a while, then got stung by this bug on the 18th of October.
Please publish a RCA soon, thanks!
Thanks,
Ciao,
Steve
th...@gmail.com <th...@gmail.com> #742
Thanks for the update!
I have one small intricate complication about the update that I'd like to clarify before I fill out the
I caught the file access issue at almost the same time as the first
So I now have a Google Play Update ready to install on the next restart... And I wondered how this would affect the NEW update (which I believe is an Android System Update?)...
- Would the next restart install JUST ONE update (the first one, which was the Google Play Update one) therefore NOT fixing the issue and potentially bricking my device (as it'll be restarting)?
- Or would it install both updates (as one is a GPlay Update and the other is an Android System Update) and can be done at the same time?
- Or will it only install whatever update I hit "Restart Now" on?
I'd really like this update to go through correctly and would appreciate some advice
th...@gmail.com <th...@gmail.com> #743
Mildy off topic (but I cannot post this to the Pixel Community page because of... the 3rd Google based bug I've experienced this week...)
The email: a14-storage@google.com
is sending automated UNDELIVERED emails...
Hello, We're writing to let you know that the group you tried to contact (a14-storage) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post:
Could a member of the team look into this?
am...@gmail.com <am...@gmail.com> #744
Regarding OTA Test Update: I filled out the form mentioned in #718 and received a 25MB Security update. It took 1 hr to get installed. Everything seems back to normal as of now, got access to storage. But I couldn't find the most recent 2-3 images clicked from camera, before this issue started. Anyways, I'm relieved that this sh*t show ended and I've gotten back access to my own data which was taken hostage. Eagerly awaiting the RCA Report (A real one, not a random technical story), and whether it was some kind of CVE.
Also they should provide a fix ASAP for those stuck in bootloop and apologize publicly along with compensation.
ra...@gmail.com <ra...@gmail.com> #745
I was had an storage pug's
sh...@gmail.com <sh...@gmail.com> #746
hu...@gmail.com <hu...@gmail.com> #747
to...@gmail.com <to...@gmail.com> #748
1. You recommend a factory reset only if the data was recently backed up. My device was not backed up. Are you working on a solution to back up devices that are stuck in the boot-loop?
2. The link you posted about the factory reset recommends to use the Update & Software Repair tool for the factory reset. Is it possible and recommended to do the factory reset in this way if the device is stuck in the boot-loop or should it be done by using the device's buttons?
3. The mentioned link also describes that one may be able to update the software manually to the latest version without a factory reset. On the other handy you wrote that "this update may not enable data to be recovered for devices that are repeatedly rebooting". Do you already know whether the Android update that should be rolled out in the next two weeks can be done using the Update & Software Repair tool and if it will be possible without a factory reset? May it be possible to install that update this way and to lose no data or is it already sure that also with this update all data on the device will be lost? Please give us some more information on this topic and what you know for sure and what you are working on. This helps to decide if one wants to do the factory reset soon or if it can make sense to wait for the update.
Thank you very much in advance.
qx...@gmail.com <qx...@gmail.com> #749
3. For phones in boot loop, If you go into the Recover mode, you have 2 options to apply OTA updates. One via ADB and one via SD Card (Pixel doesn't have a SD slot, so unclear whether USB would work, or a USB-C card reader could work), I believe these are the only 2 ways to apply an update without erasing all the data.
The ADB method *may* require USB debugging to be turned on *before* the phone is stuck in bootloop - so probably won't work for phones that are already in bootloop.
The SD card method maybe the only way to rescue phones that do not have ADB debugging enabled prior to the boot loop. I do not know how this works in practise and hope Google Dev can comment.
Unless the bootloader is already unlocked, unlocking that so that one can side-load Android 14 image via ADB will ERASE all data.
sz...@googlemail.com <sz...@googlemail.com> #750
I'll be sending the phone in for a separate hardware repair now (Microphone isn't working in case anyone is curious) So a factory reset needs to be done anyway.
jo...@gmail.com <jo...@gmail.com> #751
Previously, I was able to use the device fine EXCEPT for the fact that I had no storage access and couldn't install apps. I was NOT getting reboot issues, and I was NOT getting startup issues.
The OTA test update has RESTORED storage access, and I am able to update apps again. This seems like a fix WITHOUT having to wipe my device. I'll continue testing, but very encouraging so far. Thank you!
ms...@gmail.com <ms...@gmail.com> #752
How long after filling out the OTA form should I expect to see the update come through and what is the mode of delivery?
The factory data reset piece of the beta program confuses me as well ...if I opt out at the right time, then I don't have to worry about the reset? Is that true? And if so when is that perfect moment?
I apologize for what might be redundant questions. I've read up and down these comments for weeks now keeping up to date and my brain is exhausted.
to...@tommon.com <to...@tommon.com> #753
If this is too confusing, I'd just wait for an official stable patch to be pushed.
ia...@gmail.com <ia...@gmail.com> #754
Feedback from real users seems to go down the Over The Air (OTA) Test Update route, I will be doing that later today.
Google support, you suck.
ju...@gmail.com <ju...@gmail.com> #755
Remember: all of those opting in for the beta program are, in fact, becoming "beta testers" of a company that already screwed us. So... very brave people.
I'm DEFINITELY waiting two more weeks for the stable version. But then again, I'm lucky enough that my phone is not bricked...
ma...@gmail.com <ma...@gmail.com> #756
As for Google: the behavior was a complete disaster. Communication was non-existent and it took far too long to fix the error.
To me it looks like Google wants to sweep the dirt under the rug. That's why they release the fix in the form of a beta and the actual version comes in the normal November update so that it doesn't attract attention. I am happy about every news site that has shown transparency and published an article.
It shows once again how many YouTubers are paid to publish positive test reports.
Thanks to the users and the cohesion of the community. I wish everyone who is still stuck in the boat loop that they too receive a solution.
I will now copy my data away from the device and say goodbye to Google. You will never be able to repair the trust you have lost.
je...@gmail.com <je...@gmail.com> #757
Signing up to the beta program means you are legally giving Google a license and free pass to any data loss due to any bugs that come with the beta program. You will be on your own.
Just my five cents.
"How do I get help with Android beta versions?
As this is a beta program, there are no official support channels available. Post your question on the Android Beta Reddit community and a fellow community member may assist you."
Btw, after the test OTA, my phone is now overheating after a couple of minutes of normal use, FYI.
ia...@gmail.com <ia...@gmail.com> #758
yu...@gmail.com <yu...@gmail.com> #759
OTA for the Beta works without any issues. 2ndary profile is working and storage issue has not come back, even after a few restarts. I would assume the same for the regular OTA update.
ah...@gmail.com <ah...@gmail.com> #760
For those stuck in Pixel is starting... (like me) opening a case with Pixel Support as referenced in #718 on 11/2/23 is very simple, but the only answer I got back for now is that they will get back to me in a few days. Still, I got a case number and I would encourage others in this boat to put in a ticket. I'm sure it's been a long week for them, so just be cool and hopefully they will do the same.
What might be tricky is that they will ask for your IMEI. The easiest options are to look on the box or (if you're in your 20s or own an electron-scanning microscope) the SIM card tray. You may also be able to use the buttons to get the phone to fastboot and then use the barcode option to display the IMEI, but I'd be really careful about turning it on at this point without further guidance from Google.
The key here I think is to have enough internal tickets referencing the same overall issue ("phone is stuck on Pixel is starting...") to give them a concrete idea of the scope of the problem. In other words, "We have 4,723 tickets about the Pixel is starting... bootloop issue" is a lot more actionable than "a lotta/buncha/bazillion ppl on the internet are complaining about this issue". They have a lot of issues to fix and it's a lot easier to prioritize them if you have something to sort on. Numbers are sortable. How do you sort "lotta", "buncha", and "bazillion"???
ro...@gmail.com <ro...@gmail.com> #761
la...@gmail.com <la...@gmail.com> #762
j5...@gmail.com <j5...@gmail.com> #763
Google irritates me even when it comes to things like this.
(I know They say "within 24 hours").
gr...@gmail.com <gr...@gmail.com> #764
I thought maybe because my account is in USA, but I now live in Germany and are currently in Spain. But that should not really be an issue since They have serial and imei number?
la...@gmail.com <la...@gmail.com> #765
ko...@gmail.com <ko...@gmail.com> #766
ch...@gmail.com <ch...@gmail.com> #767
mg...@gmail.com <mg...@gmail.com> #768
also confirm the the boot loop issue comes 2 weeks after the upgrade to android 14. try a lot to fix. nothing work.
full documentation:
the Conclusion of this second evening:
repairpixel.with
Instead there is now the "corrupt" warning message. but the boot loop is gone.
adb sideload finally works with a different usb cable, but the
ota-build from android 14: bramble-ota-up1a.231005.007-231386fe.zip breaks at 94% with xfer 2.00x.
Android 13's ota bulid: bramble-ota-tq3a.230901.001-6d107ffa.zip breaks at around 25% with xfer 1.00x
The factory image of Android 13: bramble-tq3a.230805.001-factory-4fd0e3b4.zip breaks directly with xfer 0.00x
today i get from a "brain" user the factory image of Android 14, but he said, it will not run, because of "oem locked" state of the phone.
error messega after inital a factory reset ot the "repaired" android 14 with repairpixel.with
could somebody explain me the error logs xfer 2.00x, xfer 1.00x and xfer 0.00x
attached ist the error message of the wipe/factory reset at recoverymode
a....@gmail.com <a....@gmail.com> #769
gu...@gmail.com <gu...@gmail.com> #770
I had the development mode enable prior to the incident. Out of curiosity, I tried to sideload the Android 14 version which is already installed. adb loaded it well but I got a "completed with status 0" message. Maybe it wasn't even applied because it is the same version. The device is still showing the same boot loop.
I am now waiting to get hands on the OTA with the fix as a file to sideload it. I am willing to take the risk of losing data and try it out for all the others here, so please reach out to me, dear Google Support.
Long story short: sideloading works for me, applying the same version did not resolve the issue. Please send me the OTA file to try again.
zo...@gmail.com <zo...@gmail.com> #771
What an appalling mishandling of communication.
ge...@gmail.com <ge...@gmail.com> #772
After the update something should appear saying you got a personalized update:
ha...@gmail.com <ha...@gmail.com> #773
ga...@gmail.com <ga...@gmail.com> #774
So, as per the agent, the information they have is that the only way to recover the phone is with a factory reset (losing all data), she also asked me to try a hard restart (hold power for 30 sec) but that of course does not work, the phone goes back to "Phone is starting...". Also, the only way they have to recover the data is to backup / restore and of course as it is not possible to do a backup on this state it is only possible if there is a backup in google one from before the problem started. Which even if you have one its a super incomplete as the backup system in android SUCKS!
So it seems they do not have any way to recover the data for us with the bootloop... She also says they are yet to receive any information from the management team about compensation for this...
I'll wait a week or two before factory resetting in hopes they figure out something, a formal and clear statement from google is seriously needed here!
Also, things to learn for google developers / engender:
- Backup functionality sucks, why doesn't it backup downloads, documents, many apps, etc.? this needs a serious overhaul...
- Having Multiple Profiles is used by many, this needs to be better tested and better supported and improved to work Better as well...
pa...@gmail.com <pa...@gmail.com> #775
la...@gmail.com <la...@gmail.com> #776
Someone posted earlier about maybe applying OTA with USB-C card reader in recovery mode. Has anyone tried that or is there a copy of the update I can try it with or is it even plausible for this?
As many have mentioned Google chat support has been less than helpful, and only want to factory restore.
cb...@gmail.com <cb...@gmail.com> #777
How do you know?
On Fri, Nov 3, 2023, 2:15 PM <buganizer-system@google.com> wrote:
ma...@googlemail.com <ma...@googlemail.com> #778
Vielen Dank nochmal an alle die hier anwesend sind und dazu beigetragen haben das auch schnell etwas passiert.
Und natürlich vielen Dank auch an Google das sie uns helfen und geholfen haben, auch wenn man hier auf dem Kanal nicht viel gehört oder gelesen hat von Google.
Ich hoffe für alle die jenigen die in einer Bootschleife stecken, das hier auch lösung gefunden wird. Ich drücke euch die Daumen.
ga...@gmail.com <ga...@gmail.com> #779
va...@gmail.com <va...@gmail.com> #780
ab...@googlemail.com <ab...@googlemail.com> #781
Thanks!
cb...@gmail.com <cb...@gmail.com> #782
On Fri, Nov 3, 2023, 3:35 PM <buganizer-system@google.com> wrote:
al...@gmail.com <al...@gmail.com> #783
ia...@gmail.com <ia...@gmail.com> #784
Nice having a working phone again but I'm sure I'm not the only one that will think twice before buying another Pixel
ru...@gmail.com <ru...@gmail.com> #785
To #771
Is there a way to check that #718 is a legit Google post? Anyone can post a message here (as I'm doing now). How do I know it's not an exploit, phishing for email, IMEI and the phone serial number?
The same update is posted to the official community post about the issue:
my...@gmail.com <my...@gmail.com> #786
1) when it is stuck at "Phone is starting..." it responds to "Hey Google, shutdown". I don't know what else I could ask the assistant to do that might help e.g. "Hey Google, install the update from the Play Store"
2) when I contacted support the person tried to get me to factory reset several times, without acknowledging that Google had caused this problem, before finally saying that they would "raise it with the internal team". It took nearly an hour for which I was given a £25 discount in the store.
wo...@gmail.com <wo...@gmail.com> #787
du...@gmail.com <du...@gmail.com> #788
Not sure where/how you'd submit it. I'm sure google is actively monitoring the test fix
So far it appears to be working normally for me, no issues currently
a....@gmail.com <a....@gmail.com> #789
la...@gmail.com <la...@gmail.com> #790
zi...@gmail.com <zi...@gmail.com> #791
da...@gmail.com <da...@gmail.com> #792
a....@gmail.com <a....@gmail.com> #793
I think the main issue here isn't about the technical issues anymore. Google has a huge problem when it comes to communication.
ge...@gmail.com <ge...@gmail.com> #794
Does that mean that they probably can't fix the phones stuck in the boot loop or that there might be another update that can fix it? I am still waiting with my dead phone for a fix, so I don't have to factory reset and lose all my data.
la...@gmail.com <la...@gmail.com> #795
I would guess people that have multiple profiles are on average more technically inclined and have been fans of Pixels for a long time. I been with Pixel since the first one and had a Galaxy Nexus way before that, in the last year I've convinced two friends and two coworkers to switch. None of them have this problem but I feel foolish now.
Still love the Pixels (when they work) but this reminds me a lot of my issues with LG and their bootloops and why I had to abandon them.
Not interested in any monetary store credits or vague glimmers of hope, all I want is the phone to boot in to Android without data loss and a way to do proper backups in the future. Happy for but a bit jealous of all the people who have theirs working now.
PLEASE GIVE US CONSISTANT UPDATES HERE IN THIS FORUM OR IN OUR EMAIL
sk...@gmail.com <sk...@gmail.com> #796
co...@gmail.com <co...@gmail.com> #797
So far everyone seems to be saying it's fixed things for them and no major issues but I'm nervous to try before the stable release just cuz last time it took awhile before the bug started getting noticed...(then again that release was supposed to be 'stable' LOL)
st...@gmail.com <st...@gmail.com> #798
OTA update seems to be working so far. Pixel 6a (not boot loop).
I responded to support telling them my issue was resolved but they insist on not even reading what I send over. I get there's a script and steps to take but these reps have absolutely no ability to zoom out and understand the matter at hand.
Such a disappointing experience. Is this what we can expect from Google moving forward? What if something similar happens? We just sit in the dark for 2 weeks and once it is quietly resolved it is swept under the rug?
ma...@gmail.com <ma...@gmail.com> #799
trust me when I say I have read almost all of these previous ~800 messages here, and not found one instance that this issue happened on a non-Pixel phone! (or was I not in the correct forum?)
Well here goes, my mum's BlackBerry Keyone has been hit by this very same issue, on an Android 8.1.0. I was not trying to update the software (like the Pixels trying to update to Android 14), none was available since the last few years of course. The last thing I remember I did the night of 3 Nov to the phone was trying to update some random apps on PlayStore, though one or two might have been a non-3rd party apps (something like Google Partner Setup, Android Accessibility Suite etc). Then the next morning, mum complained she could not load received picture on WhatsApp (media auto-download turned off).
So far it did not go to boot loop yet (hopefully never) and I am hoping I can get some advice on what can I do next?
The phone has been configured with Adaptable Storage with a 64-GB microSD and that was shown as "Checking" upon booting, then as "Corrupted" after some time. As far as i remember, all camera and Bluetooth photos have been moved to this microSD and it is my biggest concern to be able to retrieve them. Others data like device settings and some other whatnots have been synced to Google (One?) backup after the internal storage locking incident.
I have visited the #718 to fill out the form but no non-Pixel device listed on the form to be able to submit it further. Apologies for the long message, just hoping that non-Pixels devices are not left out in this situation! Also, how do I have a 1-to-1 chat support with a Google rep? Do i state the email as mine or the one logged on the BlackBerry?
Thank you, regards.
ma...@gmail.com <ma...@gmail.com> #800
ah...@gmail.com <ah...@gmail.com> #801
Hi #799/#800
You are in the wrong place for support. The issue you're experiencing may look the same as what is being discussed here, but I can say pretty confidently that it is different.
You can try to reach out to BlackBerry for assistance as they are the phone manufacturer, but they will likely say that this phone is out of support. (Android 8 is very old at this point, and you should strongly consider replacing the device if/when you are able to restore the data.)
If I have to guess, the issue lies with the SD card. It is either corrupted or (hopefully) just needs to be removed and reinserted. The Adaptable Storage feature is very interesting, but it can easily go very wrong, as you've seen. Not all SD cards are made the same and they aren't necessarily made for the type of workload demanded by a phone or tablet. There's a good reason that iPhones and Pixels do not come with SD card slots (as much as I wish it wasn't the case).
You may also try reaching out to a data recovery service if the data on the SD card is that valuable. These can be very expensive services (as me how I know) but they are very impressive and very well may be able to recover some of your data.
Here's hoping Google's engineers can come through for those like me whose Pixels are stuck in the bootloop :-)
Best of luck to you!
a....@gmail.com <a....@gmail.com> #802
Thanks to everyone for raising the issue and those who worked on the bug.
Google, please improve the way you communicate with your customers.
Now, I can finally close this tab (:
ge...@gmail.com <ge...@gmail.com> #803
Pixel 6 Pro
wo...@gmail.com <wo...@gmail.com> #804
I applied the fix and noticed that I had less room than I thought I would have. So I believe that Apps that were deleted during the storage bug are still hidden away. I had to reinstall and delete them to recover my missing space.the apps we're significantly big for me to notice this bug.
uz...@gmail.com <uz...@gmail.com> #805
ko...@gmail.com <ko...@gmail.com> #806
ma...@googlemail.com <ma...@googlemail.com> #807
Der Hersteller von dem Handy von meiner Frau kann das sehr gut. Sie ist von iTunes begeistert.
ak...@gmail.com <ak...@gmail.com> #808
th...@gmail.com <th...@gmail.com> #809
sa...@gmail.com <sa...@gmail.com> #810
se...@googlemail.com <se...@googlemail.com> #811
ba...@gmail.com <ba...@gmail.com> #812
je...@gmail.com <je...@gmail.com> #813
ah...@gmail.com <ah...@gmail.com> #814
For those still stuck in a bootloop, here's the conversation I had with Pixel Support (linked in #718 above, where you can apply for the OTA update). I started the chat with something like "My Pixel 6a was affected by the Android 14 multiple profiles storage bug. It is stuck at Pixel is Starting... and I do not want to do a factory reset." This was from a few days ago. No news yet. As someone else said, it's the weekend...
I am a nobody like you, so I would encourage you to contact Pixel Support as well so that there is some strength in numbers. Just be cool, but persistent. I did my best to be cool, but I slipped a bit when I was asked to verify the IMEI :-) (Notably, she pasted the IMEI instructions very quickly, so presumably they have a shortcut for the most common types of instructions.)
IANA Android Developer/Engineer, but my guess is that any fix may be possible with adb, but Google will have us use the Android Flash Tool or something else with less margin for error (hence the OTA update was first). Maaaaybe affected devices will need to be shipped in or physically taken to a location where a tech can do the work??? Remember that "normal" people are affected here, too, and "fastboot your Pixel and sideload a zip" sounds a bit like Mad Libs to them.
I'm sure there are at least a few Android developers at Google who desperately want to get this fixed right, so we need to be patient, calm, and put our lawyers down.
(This chatlog has been sanitized for your protection and mine.)
Jackie: I understand that your device is currently stuck at "Pixel is starting" and you do not want to reset the device and get this sorted.
Looper: That's correct. I'm hoping that there is a way to get the phone to boot.
Jackie: I’m sorry you’re experiencing this problem. I’m sure we can figure this out, and I’ll work on finding a solution right away!
Jackie: Please allow me 2 - 3 minutes while I check my resources.
Jackie: Thanks for your time.
Jackie: Loopy, in this case, “If you’re not worried about losing data, such as app data, recent downloads, or media, or you have a very recent backup, you can factory data reset your device. Once you’ve done so, you can restore your data from the backup.
Jackie: However, I understand that you do not want to lose your important data. I will escalate this with my team and see if an alternative solution is available.
Jackie: Could you please confirm the device IMEI number is ending with *4242?
Looper: Where do I find that?
Jackie: You can find the IMEI in the following different places:
- Settings > About Phone > MEID > IMEI information.
- On the SIM tray.
- On the device box.
- Dial *#06# on your phone.
Looper: So options 2 or 3... one moment
Jackie: Sure, take your time.
Looper: Correct - the IMEI ends in 4242
Jackie: Thanks for confirming. May I know the carrier you're using on the phone?
Looper: Google Fi
Jackie: Noted. Let me get this checked with my specialist and get back to you.
Jackie: We may need a few days to reach out again, so thank you for your patience.
Looper: Understood - is there anything I should do in the meantime?
Jackie: No, Loopy. We will check the alternate options internally from our end and get back to you.
I've received a few emails since - presumably from a human and not a robot :-] :-] :-] - but no real positive news, so I'm assuming "no news is good news" and I'm not being strung along. I did suggest again that someone should update this thread once per day, even with "still working on it" just so we know they haven't forgotten.
to...@gmail.com <to...@gmail.com> #815
I also suggested that they publish information on this topic and if they are working on it in the IssueTracker and that they should let the engineering team know that a solution for a backup or an update without data loss is needed.
ke...@gmail.com <ke...@gmail.com> #816
mi...@gmail.com <mi...@gmail.com> #818
It restarted automatically and the attached screen was displayed when I was charging the Pixel Stand (Gen2). (see 2023-11-06 054944.png)
When I refused to initialize the data it started boot looping. (see 2023-11-06 055424.png)
I contacted Google Support and was told that there was no other option other than to initialize the data at now.
I'm looking forward to being able to use it normally without losing data.
ah...@gmail.com <ah...@gmail.com> #819
I could be wrong, but I believe there are different and separate support teams (silos) at Google. It's a massive company and nobody can know everybody. I think this particular issue is going to be best handled by Pixel Support, hence why it was mentioned specifically by the Google employee in post #718. See that post or paste this link
Previously, for an overheating+rebooting issue (interestingly, one that only occurred after switching profiles) I reached out to the "social" team on X/Twitter and was redirected to Fi Support since that's where I bought the phone. I had a feeling they wouldn't be that helpful, but I went along with it. Their only suggestion was a factory reset. It's not a good answer, but it makes sense that that's the best I can expect from that team. They support the "cellular MVNO" product which works on tons of different devices. I bet there's a lot of turnover, so the least technical answer is better than gibberish about adb and logcat that most customers won't understand. The Pixel Support team supports the Pixel devices specifically and likely has a more direct contact on the Android team.
This is all guessing and speculation, so if you know better and are allowed to, please correct me! My attempt at invoking Cunningham's Law :-)
If you've already reached out to Google Support or Fi Support or something other than Pixel Support, I would suggest that you politely close the ticket and open one with Pixel Support, or maybe try to have them transfer your ticket to Pixel Support if that's possible.
sa...@gmail.com <sa...@gmail.com> #820
dr...@gmail.com <dr...@gmail.com> #821
Question since this is a test update what should i do if a final update comes and how will i know? N what will happen to this one?
bi...@gmail.com <bi...@gmail.com> #822
Make sure to check this link for OTA packages of your device that will likely contain the fix. They appear 3-4 days before you can update via the phone (in normal circumstances).
I have used these images before for a colleages' bricked 4XL and it did not wipe the data. This being a different case, I cannot guarantee when they release the image - that the data will be safe.
ke...@gmail.com <ke...@gmail.com> #823
May I ask how did you apply the OTA files? Was it via Pixel Recovery mode and then via ADB or SDCard?
Thank you.
bi...@gmail.com <bi...@gmail.com> #824
It is mentioned in the link I sent. It is not complicated. You can likely do it via OTG/SD Card, but the steps mention ADB sideloading only. In my case, I used ADB.
ke...@gmail.com <ke...@gmail.com> #825
That was very helpful and now there is a reasonable hope of fixing the boot loop problem once the OTA image is released.
lu...@gmail.com <lu...@gmail.com> #826
For applying such a fix, would there be prerequisites such as having rooted the device or having debug mode enabled before the boot loop was encountered?
m....@gmail.com <m....@gmail.com> #828
Thank you
an...@gmail.com <an...@gmail.com> #829
So now what? I lost all my 2FA? My chat history which apparently wasn't doing its backup is gone as well?
I'm really hoping that there's a solution to the bootloop issue. This magnitude of a bug is something I had never seen before on any Android smartphone I've ever had.
da...@gmail.com <da...@gmail.com> #830
fixes/changes are included in a given OTA?
On Mon, Nov 6, 2023 at 2:27 PM <buganizer-system@google.com> wrote:
--
David
"Absolutely," Kelvin said temperately, as he zeroed in on the
answer. (James Ertner )
os...@gmail.com <os...@gmail.com> #831
It mentions "Fix for issue occasionally causing devices with multiple users enabled to show out of space or be in a reboot loop"
ah...@gmail.com <ah...@gmail.com> #832
Hello - "Loopy" from #814 here.
Here is the update I got from Pixel Support this morning about my ticket regarding the bootloop issue --
Our product team is actively looking into this and we’ll get back to you as soon as possible within 24 - 72 hours once we have an update.
It isn't much, but they aren't telling me to do a factory reset, so it sounds like they will have a solution that at least doesn't include losing our data. If you're having this problem too, put in a case with Pixel Support. I have no idea if it will help, but if you want to reference my case, the number is 6-9345000034482.
@#828 You may need to force your phone to check for an update. If you've already tried this and it still isn't working, perhaps try reapplying for the test OTA update, or just wait until it's officially released. Everything I know is based on posts in this thread, so these are all just educated guesses.
da...@gmail.com <da...@gmail.com> #833
Is there any update for the bootloop? I'm happy to guinea pig test images.
ly...@gmail.com <ly...@gmail.com> #834
It now longer shows the "Google" word and even could not get to the power-menu by pressing power button anymore.
Had to force-restart my phone by pressing Power + VOL up and right after it "shut off" press Power + VOL down and select power off from booting menu. No chance to get this Pixel 6a off else. :( No luck with this.
fr...@gmail.com <fr...@gmail.com> #835
ga...@gmail.com <ga...@gmail.com> #836
Sideloaded the OTA using ADB successfully and now is is on a different bootloop, its restart before getting to "Phone is starting..."
Startup Before: Full Google Logo -> Blue G -> "Phone is tarting..."
Startup after: Full Google Logo -> Blue G -> reboot...
did this like 3 time and not its just stuck in the Full Google Logo
No clue if my phone had debug mode enabled, I guess it did...
ba...@googlemail.com <ba...@googlemail.com> #837
This issue is open over three weeks, when do we get a solution??? I need my phone wtf. There is no trust anymore in Google Pixel Bug.
ke...@gmail.com <ke...@gmail.com> #838
ADB Stage:
Now send the package ...
Finding update package..
Verifying update package..
Update pacakge verification took 154 s (result 0)
Installing update
Step 1/2
Step 2/2
Install from ADB completed with status 0
Upon reboot back into recover - still at 231005 version.
ke...@gmail.com <ke...@gmail.com> #839
Thank you.
je...@gmail.com <je...@gmail.com> #840
er...@gmail.com <er...@gmail.com> #841
ah...@gmail.com <ah...@gmail.com> #842
@#841 That's interesting. I hadn't thought to check my router and see if it showed my Pixel, but I bet it does. It makes sense, too, that these system-level functions would still work. They probably need to be up and running before your user account can log in, which it can't do because it can't mount the user storage area.
I'm not an Android expert or developer, but I've run Linux systems for a while and Android is basically built on top of Linux, so the concepts are similar.
My understanding so far is that storage for user files becomes somehow inaccessible to the rest of the system root partition, but it isn't corrupted (unless you do a factory reset so don't do that). As long as you don't reboot, you'll see this manifest as running low on space, being unable to access files, unable to update or open apps, unable to take pictures, etc. However, you're apparently still able to download and install updates OTA (over the air) and so the fix for the issue was able to be delivered relatively easily to these folks as a system update. I haven't seen where someone says that their phone was acting funny but still able to reboot, so it's possible that they were fine as long as they kept the phone charged and didn't reboot until after they'd installed the OTA update that fixes the issue.
Those of us who rebooted or whose phones rebooted spontaneously (old profile switching bug -- ggl plz fix kthx) and then were stuck on the Pixel is Starting... screen will likely not be able to install an update OTA, cause like...you know...we can't get in to the phone. My guess is that we'll be able to install an update by connecting our phones to a computer with the Android Flash Tool, but this is pure speculation. With my Linux systems, I have occasionally needed to rescue them by booting to a "live USB", but from what I've read, the """Android BIOS""" has no understanding of USB mass storage, so booting our phones to a "rescue environment" is unlikely.
I have a case open with Pixel Support to see if I can get my P6a back up and running without a factory reset. The agent seems understanding that I don't want to factory reset, so so far so good. The best "timeline" I've gotten is an email earlier today (Nov 7 2023) that I'll hear back in 24-72 hours about an update.
tc...@gmail.com <tc...@gmail.com> #843
I was also bold and installed panther-ota-up1a.231105.003-935105ec.zip
(Pixel 7) in hopes to remedy the boot loop. Instead, it seems like the actual OTA update only happens at boot. But since the storage symlink (or whatever the original issue is) is not present correctly, the OTA update/refresh is now stuck,
Which those nifty coders would have some kind of "Rescue Mode" command for us to restore storage access manually.
So now I am stuck in a different "reboot" loop.
Be sure to turn off your phones, since mine got stuck at the google logo once and I had to hard shut it down.
Like the others have reported, bootloader still shows the old version, that is why I assume the OTA didn't fully process, yet.
us...@gmail.com <us...@gmail.com> #844
Can we expect that goole will provide some "tool" or "rescue mode" to install it to bootlooping device?
Or is this just wasting time to wait unrealistic the best solution for us?
If so, it must let many pixel users disappiont.
ah...@gmail.com <ah...@gmail.com> #845
Here is the latest update from Pixel Support on my case. It is not very confidence-inspiring :-)
"Could you please confirm if the device has received a November system update and is it updated or if the device is still stuck in the boot loop?"
My thought is that they have a zillion similar tickets and are trying to evaluate how many devices are still broken, so put in a case with Pixel Support if you're in the boot loop.
You'll be surprised to learn that my Pixel is still stuck in a boot loop. Also, I can't tell for sure (because of the boot loop), but I'm fairly certain that it has not received the November update. I await their response....
da...@gmail.com <da...@gmail.com> #846
Sigh. Still no movement on the bootloop? I managed to get the version to finally persist by repeatedly installing the OTA but I'm still stuck in the bootloop. Carefully checking the logs during the update, I can see that a few commands complain about files not existing on the device. I can type up some of the logs. If there's a better way to pull logs off of the device and save my fingers from typing up system logs, please let me know. I'd be happy to share the full logs if that's the case. If a dev would like to get in touch with me, I'd be happy to share contact info.
ke...@gmail.com <ke...@gmail.com> #847
" finally persist"
Thanks for the update and that is still a positive progress.
I guess you can screenshot the logs ( I runs into many pages unfortunately) and send them to support? It might be possible to download that via adb shell to find the file, and then adb pull?
Might be at /dev/log
My attempt terminated at "Error: Boot complete not detected."
or...@gmail.com <or...@gmail.com> #848
Sad (glad?) to hear that a patch started rolling out 2 days ago; apparently not rolling out fast enough.
Google might consider to force-apply the fix to surviving devices immediately, rather than wait for more devices to brick themselves?
(Getting frequent updates was the main reason for me to chose a Google phone, btw...)
So, is there hope for a fix in the coming days, or should I just wipe and lose all my data right now?
ca...@google.com <ca...@google.com> #849
11/7/23
We’ve started rolling out the official
- Device is unable to access media storage – Once these devices receive the official November Update, data should be fully restored. If you are experiencing this issue and you don’t want to wait for the November update, you can complete
to return your phone to a normal state.this form - Device is repeatedly rebooting – Since these devices cannot successfully boot, your device will not be able to receive the November update. You’ll first need to submit
to enable your device to reboot normally before you can receive the update. Data recovery solutions are still being investigated for devices that are repeatedly rebooting. We’ll share additional updates soon.this form
Note that if you signed up for the Android Beta program to resolve this issue and wish to exit, you can wait until the December Update to do so without wiping your data, or you can opt-out now but user data on the device will be wiped.
Thank you again for your patience as we continue to work through this issue. For any other questions or concerns, please contact
ch...@gmail.com <ch...@gmail.com> #850
This should be fixable for everyone, including the boot looping devices, with no data loss. Google just needs to make it a priority.
kh...@gmail.com <kh...@gmail.com> #851
ah...@gmail.com <ah...@gmail.com> #853
In addition to requiring the IMEI, the form in #849 requires the device serial number. It says you can find this number on the box, but I don't see it anywhere on my P6a box. Instead, I had to boot with the volume-down button pressed to get to the fastboot menu, then select Barcode with the volume buttons and press Power to select it. There you can see the IMEI, SKU, and Serial Number.
Form submitted. Fingers crossed I can get out of the boot loop.
-Loopy
ke...@gmail.com <ke...@gmail.com> #854
Thank you very much for the update.
I have pushed the panther-ota-up1a.231105.003-935105ec.zip (Pixel 7) file to the device in *BOOT LOOP* and it appeared to be successful.
Now send the package ...
Finding update package..
Verifying update package..
Update pacakge verification took 154 s (result 0)
Installing update
Step 1/2
Step 2/2
Install from ADB completed with status 0
However, upon rebooting, the device now stuck at "Google" logo and re-entering Recover mode shows the software was still at 231005 version.
The Recover log file shows the line "Err: Boot Complete Not Detected".
Could Google Pixel Dev please investigate this as well ?
#843 above appeared to face similar error.
Thank you
to...@gmail.com <to...@gmail.com> #855
or...@gmail.com <or...@gmail.com> #856
ah...@gmail.com <ah...@gmail.com> #857
@#856 You are correct. "Boot loop" is a bit of a misnomer in this case as it's not that the device actually reboots over and over. It just sort of gets stuck.
ge...@gmail.com <ge...@gmail.com> #858
ah...@gmail.com <ah...@gmail.com> #859
@#858 My assumption has been that only actual Google employees can post with an @google.com address, and
That said, if you have further evidence to the contrary, I'm happy to be corrected.
jm...@gmail.com <jm...@gmail.com> #861
bl...@gmail.com <bl...@gmail.com> #862
Now my phone is stuck
Google log (colorful) -> Google (G blue/Pinnk) things again and again.
Now sure how to solve this. Any version that worked?
bi...@gmail.com <bi...@gmail.com> #863
Can you clarify what you meant by "For devices that are in a boot loop, fill in this form so you can boot and receive the update. We're still looking at data recovery options for those same devices."
If I am understanding right, does that mean that the update people who meet the above criteria and install the update - will have their data wiped or just inaccessible until further notice?
I would strongly suggest people wait on installing their update even if they manage to boot until we get an answer to this.
Google has previously used vague language like this when talking about the Nexus 6 RMA debacle to get out of further legal trouble.
sa...@gmail.com <sa...@gmail.com> #864
ri...@gmail.com <ri...@gmail.com> #866
Thank god I didn't update you stupid mother fuckers, I do not need that sort of nightmare. Especially when I have two profiles because one of them is for work.
fr...@yotoplay.com <fr...@yotoplay.com> #867
ra...@gmail.com <ra...@gmail.com> #868
My question is, has anyone in the same situation tried switching to their secondary profile after the update? I'm honestly afraid to in case of losing data storage access again. I've backed up my phone using Google One this time round but thing is, in my country we use WhatsApp all the time and the last time I couldn't back up my WhatsApp content bc the phone says there's no data to read.
Also Google One doesn't seem to back up other files that are not photos or videos? Things in my download folder doesn't seem to be backed up. Does that mean I have to drag them to Google drive separately.... Does anyone know if there's way to just clone the phone completely without extra apps or technical tinkering?
da...@gmail.com <da...@gmail.com> #869
#868 Nope. There's no way to completely backup your device. Sure we can backup some photos and videos, maybe some extra files if you're lucky. But to completely backup the device as we can do on computers involves root. This is why I facepalm every time someone mentions a backup procedure because the current state of phones nowadays prevent us from doing exactly that.
ke...@gmail.com <ke...@gmail.com> #870
wo...@gmail.com <wo...@gmail.com> #871
Message #849 from Google might bear some hope, so I filled out the form for "Device is repeatedly rebooting", but since then nothing happened. Technically I do not understand what possibilities Google will have to contact the device being in that state. I wonder if there really will be a mobile connection? Do I have to constantly re-start the mobile to get a patch? Should I leave it displaying the message? In case one day there would be a patch applied, does it wipe the memory? Will there be a later patch that tries to restore data?
As a matter of fact, the mobile is completely useless in that state. Desperately waiting for further answers from Google!
xp...@gmail.com <xp...@gmail.com> #872
ah...@gmail.com <ah...@gmail.com> #873
The latest on my case with Pixel Support boils down to
"Is your phone still boot looping?" "Well, yeeeesss" (Of course it ls! We haven't done anything to fix it!) "OK, please wait for engineering to get back to us with a solution"
So this is progress in that they are offering the option to wait if you don't want to wipe your device. I also filled out the form for "Device is repeatedly rebooting" and have not heard anything back yet. My guess is that they have a fix to get it out of the boot loop so that you can install the November update that fixes the issue, but they don't have a fix YET for regaining access to user data.
pe...@gmail.com <pe...@gmail.com> #874
If this is indeed the root cause, I'd imagine that a repair without wiping might be possible (but perhaps not with means accessible to "normal" users).
I can confirm that sideloading the November OTA seems to work, as described in #837. Going back to the October OTA works as well.
Now, I can't find evidence that the November OTA actually triggers the fsck that seems to repair the data partition according to Mishaal Rahman's post. And doing it manually is impossible on locked devices. But IIUC, Google should be in the position to provide a signed "repair" OTA for sideloading that would force an fsck; afterwards, downgrading to the November OTA would bring the device to a sane state. This two-step manual sideload procedure is probably not scalable as a solution for Average Joe, but so is fixing a bootloop anyway.
However, there's a couple question marks:
(1) Is that really the root cause?
(2) If so, is the fsck really a cure?
(3) If so, is Google willing/planning to create and distribute an OTA within a reasonable timeframe?
Joining in the chime of everybody who is seriously disappointed by Google's communication here. Bugs can happen, but not communicating openly is a no-go. Sharing some technical background would be highly appreciated, if only so that we can get an educated guess whether it's worth to wait or not.
ke...@gmail.com <ke...@gmail.com> #875
Thanks for the update.
Interesting comment re Nov OTA via sideloading. My experience (and a few other above) seemed to suggest thtat sideloading Nov OTA cause the phone to halt a the "Google" logo. The log shows
"Err: Boot Complete not received." (Pixel 7)
You are also right to say Google should produce a sideloading file that repairs/fsck and restore the phone, so that "normal" Nov OTA can be received. I guess it will have to be a menu of solutions depending on one's circumstances.
Also, I continue to have silly scripted conversation with device-support...
oi...@gmail.com <oi...@gmail.com> #876
My pixel 7 is also stuck on "initializing..." screen after A14 update. Yes, I have 2 users profiles. I've been in touch with google support for a week now and they don't seem to know if we will be able to recover the local data.
Definitely going back to Samsung after this.
A cia as big as google cannot launch an unfinished/untested product that make people's data hostage like this and go free from trouble.
wi...@gmail.com <wi...@gmail.com> #877
wi...@gmail.com <wi...@gmail.com> #878
Description:
Device: Pixel 7 Pro
OEM Unlocking: enabled
Bootloader: unlocked
(UP1A.231005) stuck in Phone is starting...
(UP1A.231105) loop in Google G
Steps to reproduce:
- P7P in Phone is starting...
- reboot bootloader
- connect "Android Flash Tool"
Link - then selected (UP1A.231105) and unchecked all Checkbox
- install build
- bootloop
Link
I just need to keep primary user profile data, Could Google give us a Custom Recovery to delete secondary user profile?
fastboot boot twrp.img
Please No! Factory data reset solutions
da...@gmail.com <da...@gmail.com> #879
You said sideloading the Nov OTA worked for you, what model phone do you
have?
On Thu, Nov 9, 2023 at 9:07 AM <buganizer-system@google.com> wrote:
--
David
"Absolutely," Kelvin said temperately, as he zeroed in on the
answer. (James Ertner )
pe...@gmail.com <pe...@gmail.com> #880
zi...@gmail.com <zi...@gmail.com> #881
da...@gmail.com <da...@gmail.com> #882
3 in a row) to get the version to persist.
On Thu, Nov 9, 2023, 2:35 PM <buganizer-system@google.com> wrote:
en...@gmail.com <en...@gmail.com> #883
en...@gmail.com <en...@gmail.com> #884
It worked! i am able to see my files, they are intact, at least at a cursory glance.
i think i have read it somewhere above the nov updates is coming out, or has already come out. If you can wait, wait, else can try this link.
jm...@gmail.com <jm...@gmail.com> #885
tr...@gmail.com <tr...@gmail.com> #886
Were you having the "boot loop" issue when you applied it or just the locked storage?
na...@gmail.com <na...@gmail.com> #887
After the fix from google, i didn't recovered data in my secured folder.
Someone had the problem ?
ca...@google.com <ca...@google.com> #888
Update 11/10/23
The
For impacted devices unable to access media storage: The November system update should fully restore data to devices that are unable to access media storage. If you have not yet received the update, you can go to Settings > System > System Update to trigger the update immediately.
For impacted devices that are repeatedly rebooting: Today, we are publishing a specialized solution via Pixel Repair Tool to recover partial data for devices that are repeatedly rebooting. This process offers the same solution as the form submission we detailed in earlier updates. This specialized solution will also enable devices that have been stuck in the repeat reboot state to receive the official November system update.
If you’d like to try the process on your own, please visit one of the following links to the Pixel Repair Tool based on your carrier, where you can find on-screen instructions:
- For AT&T (Pixel 6, 6 Pro, 6a), all Japanese carriers (Pixel 7, 7 Pro, 7a, Fold), click
.here - For all other devices/carriers, click
.here
If you previously submitted the form to receive this November Update, you will hear from our Pixel Support team via the provided email address as early as Monday, November 13th to walk you through the data recovery process. This process is the same as the specialized solution detailed above. The form is now closed, so please reach out to Pixel Support with any additional questions.
Thank you again for your patience as we continue to work through this issue. For any other questions or concerns, please contact
lu...@gmail.com <lu...@gmail.com> #889
When you mention partial data recovery (for the boot loop devices), what does that mean exactly? What kind of data could be lost? My main focus is recovering photo's that were taken, app data not so much.
zi...@gmail.com <zi...@gmail.com> #890
be...@gmail.com <be...@gmail.com> #891
be...@gmail.com <be...@gmail.com> #892
er...@gmail.com <er...@gmail.com> #893
zi...@gmail.com <zi...@gmail.com> #894
ma...@gmail.com <ma...@gmail.com> #895
zi...@gmail.com <zi...@gmail.com> #896
ca...@google.com <ca...@google.com> #897
After you take the update with the tool, you will need to reboot your phone multiple times to allow it to back up the data. You will also need to login to all your apps again.
ad...@gmail.com <ad...@gmail.com> #898
My phone has been fixed as google sent me a update by filling the form which is linked in the Forbes Article mentioned below. But I have that now this form is not working.
Forbes Article:
Google Article:
Device is unable to access media storage / Device is repeatedly rebooting form:
pe...@gmail.com <pe...@gmail.com> #899
I can feel #897. Why don't you publish explanations of what problem and present fix are? Why don't you announce which data is potentially irrevocably lost, and which data is still existing on the device?
("We don't know for sure yet" is an acceptable answer! It means we're kept up to date. "We know data xy is kept, but we don't know whether we can find ways to make it accessible againt" is acceptable as well. And so is "We don't see chances for recovering data z." Not disclosing anything is unacceptable.)
People that only care about photos might be pleased if you can tell them that this data can be recovered with your patch with reasonably likelihood.
Folks that only care about app data like access codes, TOTP etc. would *not* become seriously displeased after waiting for weeks for a fix, to find out that it's half baked for their use case - so if you know that app data won't be recovered, please say so.
More careful or more audacious people will know their chances.
os...@gmail.com <os...@gmail.com> #900
"BootLoop-Recovery-Incremental is not the carrier for your device's current software. Change the carrier below"
Anyone else getting this?
da...@gmail.com <da...@gmail.com> #901
Well that sucks. I should have bit the bullet 3 weeks ago and factory reset. I'll probably exchange this fold at this point.
ma...@gmail.com <ma...@gmail.com> #902
pe...@gmail.com <pe...@gmail.com> #903
On the plus side: the secondary profile seems to be 100% intact, including chat messages, settings, apparently even app caches.
sa...@gmail.com <sa...@gmail.com> #904
ga...@gmail.com <ga...@gmail.com> #905
pe...@gmail.com <pe...@gmail.com> #906
Pixel 6 Pro (raven), the device where I previously reported that also adb sideload of the November update and going back to October "worked" flawlessly.
kh...@gmail.com <kh...@gmail.com> #907
mo...@gmail.com <mo...@gmail.com> #908
ga...@gmail.com <ga...@gmail.com> #909
- If using the Repair Tool only gives you the option Reset and Update (DO NOT D THIS, IT WILL WIPE YOUR DATA), it is because you are using the wrong link, the google guy shared two links, once I used the right one I was able to just update without resetting...
- If like me, you are one of those who attempted sideloading the Nov update using adb and are stuck in the full Google logo, I am not sure if this solution still works in that state, yesterday I was able to go back to the "Phone is starting..." bootloop by sideloading the Oct OTA instead.
kr...@gmail.com <kr...@gmail.com> #910
"Unable to connect the device."
ch...@gmail.com <ch...@gmail.com> #911
us...@gmail.com <us...@gmail.com> #912
Thanks for this repaire tool, I could salvage my photos and videos from pixel 7 pro.
As several comments mentioned, all application data, SMSs, telephone history have been deleted.
And even there is buckup on Google drive, there is no way to restore them in to pixel. (why?)
So, I finally decided to do "factory reset" and restore backups from Google Drive.
I'm dissatisfied for slip out this issue to users and duration until we get the countermeasures.
However this solution could cover minimum line of my expectaion against this trouble.
So, I would appreciate engineers who charged this trouble earnestly.
ra...@gmail.com <ra...@gmail.com> #913
gb...@gmail.com <gb...@gmail.com> #914
po...@gmail.com <po...@gmail.com> #915
Also, If anyone is having issues trying to get the tool to run on Windows, make sure you have the Google driver installed. If you go into rescue mode and plug the phone in and it isn't showing up under Serial Devices in Device manager, you'll need to manually install the Google driver and reboot for it to work.
ge...@gmail.com <ge...@gmail.com> #916
Very disappointed.
to...@gmail.com <to...@gmail.com> #917
Was rebooting several times helpful to restore more data?
Is the November update being installed by the update and repair toool or do we have to install this after booting?
sv...@gmail.com <sv...@gmail.com> #918
Adding to the questions of others:
- Will there be a more in-depth attempt to recover data? As others, I have TOTP and other data saved for applications that is not synced and could not have been back up.
- If you do apply this fix, is the data for the apps irrecoverably lost or only for those apps you choose to set up again?
- If you apply this fix, is the eSIM deleted if you had one installed?
- Is there a .zip of the fix for sideloading? It would be interesting to see the code behind the fix.
- Will you be providing some sort of compensation for the stress and financial losses people have had throughout this whole debacle?
If you think not answering questions is the better strategy for action (to save face/PR reasons etc), I hope you've seen from the near thousand comments here that this is not the case.
zi...@gmail.com <zi...@gmail.com> #919
letting the system to do the security update and restarting, it started
working again allowing me to restore my gym diary and WhatsApp messages
using Google Drive.
On Sat, 11 Nov 2023, 08:43 , <buganizer-system@google.com> wrote:
ly...@gmail.com <ly...@gmail.com> #920
Now booting again but like the others, all App-data gone, only photos etc.
You can see many files if connected to PC under "android" folder path but can't copy them. This is maybe the old App Data but not readable. Other profiles like other said all app-data available.
to...@gmail.com <to...@gmail.com> #921
sa...@gmail.com <sa...@gmail.com> #922
support confirmed that the last solution (for bootloop) posted is not recommanded if you do not want to loose your data
1:55:07 AM ME: Hello, I have my pixel 6 in bootloop since Android 14 update
1:55:29 AM ME: These is a new update to unlock device since todayhttps://support.google.com/pixelphone/thread/241474288/issues-accessing-storage-after-updating-to-android-14?hl=en
1:56:39 AM Lisa: I understand that you're contacting us regarding the bootloop issue you're experiencing with your device.
1:57:15 AM ME: yes. If i follow this tool :https://pixelrepair.withgoogle.com/carrier_selection/others/BootLoop-Recovery-Incremental Do i loose my data ?
1:57:22 AM Lisa: I will certainly look into this for you.
1:58:43 AM Lisa: Yes, Seph. You will loose the data.
1:58:49 AM ME: It is instructed to backup data, however the whole point of not data factory the phone is to not loose the data
1:58:50 AM ME: Update and Software Repair.png
2:00:13 AM Lisa: I can certainly understand how important the data is for you.
2:00:54 AM Lisa: However, you will lose the data if you perform this step.
2:01:14 AM ME: so, there is still no solution to restore my data ?
2:03:10 AM Lisa: I have to check this with our higher support
team and we need your consent.
2:03:21 AM Lisa: For a limited period of time necessary to resolve your customer support issue, you agree to allow Google customer support to access data about and associated with your Google product and account, which may include product information such as IMEI, Serial Number, country in which your product was purchased, account history and limited historical usage data.
2:03:26 AM Lisa: The data accessed will be used to improve your customer service experience, to troubleshoot issues with this product, promotion history and for fraud prevention. Google will handle this data as described in Google’s privacy policy.
2:03:33 AM Lisa:https://policies.google.com/privacy?hl=en-US
2:03:36 AM Lisa: Do we have your consent?
2:04:06 AM ME: I consent
2:04:23 AM Lisa: Thank you for the consent.
2:05:17 AM Lisa: Would it be okay if I get back to you once I've an answer or would you like me to get back to you within every few minutes?
2:05:46 AM ME: I can wait for an answer.
2:06:12 AM ME: should i stay connected ?
2:06:52 AM Lisa: It might take 5-10 minutes to get back to you.
2:06:58 AM ME: okay
2:07:15 AM Lisa: Please stay connected.
2:11:24 AM ME: I will be back in 5min.
2:11:32 AM Lisa: Sure.
2:15:15 AM Lisa: Thank you for staying connected.
2:15:46 AM ME: i'm back
2:16:12 AM Lisa: I understand that you do not want to lose your important data. I will escalate this with my team and see if an alternative solution is available. We may need a few days to reach out again, so thank you for your patience.
ki...@gmail.com <ki...@gmail.com> #923
@ Bruce
Not a chance I can accept that Nov 10 update as a solution. I'll wait until you figure out a way to restore full access to my primary profile's app data.
Three weeks plus into this mess, and having lost access to basic services for just as long (banking, work chats, contacts, etc.), I hope you can get your act together real quick now.
ar...@gmail.com <ar...@gmail.com> #924
I couldn't care less about getting back my few photos or having to log back into apps, but my call and text messaging history were critical for me for work. First thing I checked after patching and booting the phone back up successfully were my messages and was relieved to see they were all present, and then before my eyes they began to be deleted and in 15 seconds everything was gone with no way to cancel it >:[ So the patch process itself didn't/doesn't clear that data, it was a post-patch step that the phone executes.
Shame they didn't make it optional. "It is recommended that you reset your messaging history after this patch, do you wish to do so (yes/no)?" seems like a few lines of code that should be simple to implement ...
gb...@gmail.com <gb...@gmail.com> #925
ki...@gmail.com <ki...@gmail.com> #926
Dear (
I'm terribly sorry for your and anyone else affected by this botched bootloop solution's loss. I wouldn't ever dare blaming you for trusting their suggested solution.
Disclaimer: I'm in no way affiliated with google other than as a customer/owner of a Pixel 6a phone. Take any and all of my recommendations as such.
I sincerely hope you still have a chance to recover the data. Sometimes, once the decrypted storage can be accessed, the deleted data can be undeleted with special tools. I would recommend you to turn off your phone and avoid using it, as once data is marked as deleted by the system, it feels free to overwrite it with new data (even just automatically generated system logs), making any potential recovery much harder, if at all possible.
To anyone facing this bootloop issue and who holds their app data dear, I concur with (
May we get a real solution soon. In my case, I wouldn't mind sending in my phone to tech support. Anything to get my app data back. So long as recovery guarantees are given (or at the very least, the phone is returned in the same state with the locked data). Just can't afford losing it.
ki...@gmail.com <ki...@gmail.com> #927
Last message was obviously directed at (
s....@gmail.com <s....@gmail.com> #928
my case: Google Pixel 6 Android 14 (UP1A.231005.007)
my phone was in "Pixel launching" stuck mode since 10/25/2023
i downloaded novemberS image (UP1A.231105.003) from
after the phone stuck in Google logo
11/11/2023 after announcing at
update downloaded, but not installed
I used browsers developer tools and got direct link of novembers update zip-file (here is
more details in link
i downloaded and manualy pushed it via "adb sideload".
had the same result (update doesn't applied) phone stuck in Google Logo screen
I downloaded again the image UP1A.231005.007 and pushed it in via adb sideload
now phone returned to "Pixel launching" stuck mode
again. I pushed november update (25MB zip file)
update applied and at last phone full launched
BUT all apps setting was reseted.
fortunately all files (photos, videos) were stiil available
Moreover, another update appeared with a size of 3.97 MB, after installing it (approximately about an hour wait) and rebooting the phone, when I checked for updates again, I received a message that updates
were temporarily suspended (I guess it's due to the update for those phones which impacted the issue)
loaded into fastboot mode discovered that the boot slot changed to B, before it was a A slot. (I guess it's due to the update also)
i couldn't change boot slot to an A using fastboot utility.
the needed features in developers option menu were enabled
i had to copy all files and do factory reset, but do not launch after
enter to recovery mode and push november image (UP1A.231105.003) via "adb sideload"
and then usually starting configuring phone
also checked "fastboot getvar all" command, now all slots are bootabled, before only slot B was bootabled
(bootloader) slot-count:2
(bootloader) slot-fastboot-ok:a:yes
(bootloader) slot-fastboot-ok:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-retry-count:b:2
(bootloader) slot-successful:a:yes
(bootloader) slot-successful:b:yes
(bootloader) slot-suffixes:_a,_b
(bootloader) slot-unbootable:a:no
(bootloader) slot-unbootable:b:no
And now while checking updates i recieved a message than the system is up to date
wo...@gmail.com <wo...@gmail.com> #929
wo...@gmail.com <wo...@gmail.com> #930
After that I performed an offered 'Security Update' of 4,31 MB. Here is the result that could help you in your decision:
- Good: All photos, eSIMs and the 2. profile is well preserved
- Bad: no contacts, no SMS, no history, all vanished. All apps are available, but without data. The screen is blank. It will take many hours to set up all the apps
- Catastrophic: My Signal App folder disappeared with all the chats and backups. I do not want data recovery apps rooting my phone, do not want to worsen the situation
Any tool that can 'officially' deep dive into the file system for signal-year-month-day-time.backup files?
di...@gmail.com <di...@gmail.com> #931
And I'm going to preach and reach everyone around me.
How can you mess up this bad.
Eat dung and sleep forever.
gb...@gmail.com <gb...@gmail.com> #932
s....@gmail.com <s....@gmail.com> #933
I didn't have any other files
considering that photos and video files are in place and other files must be in place
in my case, there was a complete reset of all applications (whatsapp chat, call log, and so on)
pu...@gmail.com <pu...@gmail.com> #934
Hi All
Issue Resolved: Pixel 6a Storage Access Post-Android 14 Update
Quick Fix:
Detailed Solution
- Initial Problem: Post-update, downloading WhatsApp images failed, leading to a persistent "Phone is starting" screen after a restart.
- First Attempt: Used "adb sideload" with the November update, but the phone got stuck at the "Google" logo.
- Second Attempt: "adb sideload" with the October update reverted the issue back to the "Phone is starting" screen.
- Successful Resolution: Instead of continuing with "adb sideload," I followed the specific instructions for my device using the Chrome repair tool. This link can be found under "For all other devices/carriers, click here." in the
.Google Support Guide - Outcome: Post-repair, I regained access to my phone's storage. However, all app data was lost, though files, photos, and videos in internal storage remained intact.
Note: This process worked for my Pixel 6a. Steps might vary slightly for other models or carrier-specific devices.
- The screen which was displayed while updating through Chrome repair tool is attached to this message
ro...@gmail.com <ro...@gmail.com> #935
Phone booted and I let it do an additional security update.
While all my previous apps were installed, they lost *all* data. Every single one started as if newly installed. Lost all messages, TOTP tokens.
The only thing that could be recovered was photos.
pe...@gmail.com <pe...@gmail.com> #936
1.) Can Google confirm that the issue is reliably fixed; i.e., there are no known issues anymore when setting up phones with two accounts?
2.) For fairly obvious reasons, I tried to bite the bullet and set up Google Backup for the secondary user (different Google account). But the option for backup for this user is grayed out. Anyone else experiencing the same?
no...@gmail.com <no...@gmail.com> #937
Nasty data-corrupting bugs in a flagship product can happen(they shouldn't, especially at Google, but they do)i am not particularly mad about that.
What is absolutely reprehensible and beyond the pale is how you handled the incident response for this giant fiasco.Not a single comprehensive post-mortem published yet, not a single technical advisory CLEARLY AND CONCISELY detailing WHICH DATA WOULD BE LOST FOR GOOD EVEN WHEN USING THE REPAIR TOOL.
You can't say "partial data recovery" and hand wave the whole thing away.
Extremely disappointed in both the timeline and outcome for the resolution of this.
Plus be extremely careful when using the repair tool as it too prompted me for a factory reset instead of pushing the correct update every time i selected a country other than the US or tried my actual carrier(YMMV).
Still holding out hope against hope something can be done to recover the totality of the data for affected devices but it's looking grim.
ar...@gmail.com <ar...@gmail.com> #938
Yes, I concluded the same thing and just switched my Pixel off without doing anything else - luckily I still had a previous phone sitting in a drawer that I can use in the meantime, otherwise I'd probably just cut my losses and reset the Pixel. But I figure I'll wait a week or so and see whether Google releases any follow-up patches to recover more lost data. Wish I could say I was hopeful ...
da...@gmail.com <da...@gmail.com> #939
Like many on this thread I am very frustrated with the level of communication from Google about this issue.
It has been very frustrating working around not having a functioning phone in the hopes of a non-destructive recovery option. If that was not ever gong to be an option I would have liked to have known that, wiped my phone and moved on.
ge...@gmail.com <ge...@gmail.com> #940
tr...@gmail.com <tr...@gmail.com> #941
At this point, I just care about pulling the 8gigs worth of messages and call logs; why should we have to wipe our devices to get that data from our backups?!
I'm hoping Google releases an option to download this data with a separate tool or something, as that just seems backwards...
You don't have to wipe a computer to recover a file, why should anyone have to wipe their phone to do the same?
tc...@gmail.com <tc...@gmail.com> #942
Can't really wait another week for no solution to pop up. App data is now all gone thanks to the patch for the boot loop, but better than nothing. I will have to re-setup everything again.
Sadly, the support was of no help either. The last two times I tried talking to them they basically just either wanted to reset my data or exchange my phone. Not helpful, Google Support.
Well, I think the next phone will be a FairPhone or something... Too bad the Linux Phone never succeeded in the world. I am out of here. Good luck to those still stuck in the boot loop issue.
ge...@gmail.com <ge...@gmail.com> #943
gu...@gmail.com <gu...@gmail.com> #944
Thanks to
App data etc. are lost and the phone behaves weird (e.g., lost Google account, could not sign in for the photo backup). I could connect with my (Windows) PC and copy all photos incl. raw dng files. Looks like downloads and some other documents are still intact, too. Althought it is visible, I did not access the secondary profile.
After transfering the files I could access, I followed the Google Play system updates and restarted. Still, I can not fix the account issues to start the photo backup. Now, I accessed the secondary profile and everything is there (of course, the secondary is the trash profile). I will probably factory reset the phone in the next days to ensure that everything is there.
(I spare you any detailed comment on the quality of the support I got via calls or e-mail. It matches what other people posted here.)
yi...@gmail.com <yi...@gmail.com> #945
Leaving this here for anyone who may want to upvote it:
sv...@gmail.com <sv...@gmail.com> #946
This is due to how partitions are set up. Usually, there is a different partition in Android for the /Android folder, where most user app data is kept. My guess to why they have trouble recovering that partition is that it was somehow corrupted by the F2FS bug (an older F2FS version partition, different partition structure not compatible with F2FS options or something else entirely). Still, this tells me that one simple temporary patch would be downsizing the main data partition, creating a new /Android one and having Android run from that with the intention of later figuring out how to recover the older /Android partition. That way no data is lost and users can use their phones somewhat while waiting for a fix.
Its depressing to have to repeat the others, but... This all boils down to Google's very bad/nonexistent communication with end users.
ga...@gmail.com <ga...@gmail.com> #947
I have to say, as bad as this bug was, Google made it 1000 times wirst by no communicating properly, their short and far between updates have been super ambiguous and not clear enough, horrible job communicating... They should have a person dedicated to answer questions here and help people out...
mo...@gmail.com <mo...@gmail.com> #948
sv...@gmail.com <sv...@gmail.com> #949
No, this is speculation as I have mentioned. I have tried to take a look at the code Google put in, but there are some changes in the Product and Boot partitions that cannot be looked at (obfuscation for the boot.img for sure). All the other .img are identical to the October OTA after diff-ing them. Maybe someone more skilled at looking through raw output would have more luck. What can be seen though, just via the junctions links in boot.img compared to the older one - is one more ext4 mounting point. I can't say for what it would be used though.
no...@gmail.com <no...@gmail.com> #950
The only datat that was "partially" recovered was my app list. I have no data in any of them, my home screen is gone, my app data is gone except from a few Google apps. Unacceptable.
ra...@gmail.com <ra...@gmail.com> #951
ag...@gmail.com <ag...@gmail.com> #952
to...@gmail.com <to...@gmail.com> #953
gb...@gmail.com <gb...@gmail.com> #954
do...@gmail.com <do...@gmail.com> #955
- Files seem to be in tact and available for transfer
- Apps: Present
- App data: Gone
- Any personalized data: Contacts, messages, call logs, etc: Gone
- For whatever reason my device was extremely buggy, e.g., it could not connect to the internet (wifi or cellular), many settings wouldn't open or only function very slowly
- Secondary profile is fully functional incl. apps, app data, personal data
So this is really only a download your data and reset the device kind of solution.
ah...@gmail.com <ah...@gmail.com> #956
I have a Pixel 6a that was experiencing the bootloop. I submitted the get-outta-da-bootloop form and applied the fix noted in #888 on Friday November 10 to get out of the bootloop and then applied the November update via OTA (like a normal security update).
As others have noted, I can see files (pictures, downloads, etc.) on a PC and I can see my apps on my primary profile, but my primary profile appears to have lost all app data and require re-logins, etc. My secondary profiles look perfectly fine.
This is where I stopped fiddling with it and turned off the phone to await further instruction.
I already had a case open with Pixel Support and heard back from them on Saturday November 11, earlier than expected, but they were just going to get back to me in 24-72 hours. I sent an update about getting out of the bootloop and applying the November update, etc. The reply was similarly boilerplate.
Now I've just received an email that sounds very promising.
Hi Loopy,
My name is George and I’m part of the Google Pixel support team. Thanks for submitting the form to address the Android 14 multi-user storage issue.
I saw that you indicated that you were experiencing the bootloop symptom and wanted to reach out to offer a potential solution for your issue. We have a new solution that we’ve tested and can help you recover the data. The process would involve downloading a special update through the Repair with Google tool and performing a data backup. We’ll walk you through the steps required to do this on the call. To use this solution, you’ll have to have the following handy: A Stable Internet Connection A computer running Mac, Chrome OS, Windows, or Linux A USB-C to USC-C cable or an USB-C to USB-A cable The affected device that you want to repair, charged Can we schedule some time for us to go through this? Please respond to this email with your availability, and we can set up some time.
Best time for callback (Including timezone)
Thanks! George The Google Support Team
So, if you submitted the form about the bootloop and/or have a case already open, they should get back to you eventually and there should be an option to recover data if you haven't already taken the nuclear option.
My fingers and toes are crossed.
to...@gmail.com <to...@gmail.com> #957
ah...@gmail.com <ah...@gmail.com> #958
As I'm re-reading the email I got from "George" (name changed) at Google Device Support, I suspect the plan is just to get me out of the bootloop (already done), and then backup and restore my primary profile. I do not know if this will include restoring my primary profile's app data, but we shall see.
ATB.
-Loopy
ge...@gmail.com <ge...@gmail.com> #959
ah...@gmail.com <ah...@gmail.com> #960
@959: I am imagining that this call will be a lot of me saying "yep, done that" and that they are catching up with people who filled out the form to get out of the bootloop.
The part about doing a backup makes me wonder if I'll be backing up the files I CAN see, then (hopefully??) restoring my app data, and then restoring those files on top. This is all speculation. As I've said before, I am not an Android developer or engineer. I just want to get back to scrolling mindlessly through my feeds, ignoring spam calls, and occasionally doing productive work.
I tried to ask about restoring app data when confirming a time for a call, but I got no further answer. It was just "thanks for confirming a time for a call".
FWIW, I do think the Google engineers who have been trying to resolve this issue have been doing their best under the circumstances. I don't blame them for not wanting to follow this thread. (If a Google employee is reading this, blink twice to tell us you're OK!)
to...@gmail.com <to...@gmail.com> #961
ar...@gmail.com <ar...@gmail.com> #962
The "solution" they're talking about is the same fix they made available on the Repair with Google site a few days ago - the one which wipes out your primary user profile's data.
I emailed with the Google Support team member a couple of times after explaining I'd already followed that solution a couple of days ago, and that:
- the fix DID get me out of the "Phone is starting" loop which was good; and
- it cleared my data which was disappointing
I then specifically asked "Are you able to please advise whether there's any way I may be able to recover my messages and other data, or was the patch from Repair with Google the extent of the fix planned for customers affected by this issue?"
Their response was that they were glad the phone issue was "resolved", which immediately told me there was no plans to do anything more than just get the hardware booting. The remainer of the response indicated that they "currently do not have a dedicated team that assists the restoration of the storage data" and that I could "troubleshoot this issue" by going to the Google Help page and following the instructions on backing up or restoring data on a Pixel phone or visiting the Help forums.
So my takeaways are:
- That Google's primary interest is only getting phones to a working state again.
- That there is probably no plan to assist users any further with recovering anything they have lost (despite this loss being caused by Google in the first place).
- That they are covering themselves in this from a customer service perspective (and probably also a legal one) by taking the stance that they had previously already provided mechanisms to perform some degree of backup of devices, and that these shall be the same mechanisms used to reinstate the data. The implication being that if customers had chosen NOT to use these then that's on them and there is no further recourse.
- That the wording of their email about the fix is misleading - possibly intentially so, who knows? They state the fix process "would involve downloading a special update through the Repair with Google tool and performing a data backup". However the order of those two things in the sentence should be the other way around because they're actually meaning that the "get my phone back like it was before" process involves having made a data backup PRIOR to the phone getting borked.
With enough public outcry I guess it's possibly that Google might do more to assist affected customers ... if there's even an ability to do so from a technical viewpoint. But to do so would admit more liability than they probably wish to bear, so I wouldn't hold out much hope.
Personally I'm just going to back up everything I can from my second profile, factory reset the phone, and make peace that their code screw-up cost me my data. And I'll start paying more attention to phones from other manufacturers ready for when I have to replace this Pixel.
Good luck to all in finding your own path forward.
ah...@gmail.com <ah...@gmail.com> #963
@962 (I'm the one who posted #956)
Thank you for this preview. This is more or less what I am expecting to come of this call.
If you keep low expectations, you are less likely to be disappointed.
gb...@gmail.com <gb...@gmail.com> #964
an...@gmail.com <an...@gmail.com> #965
Does anyone know if the WhatsApp backup counts as AppData that the current fix would delete, or if it counts as regular storage that would be saved.
da...@gmail.com <da...@gmail.com> #966
What is the official response from Google with this issue? Is it now closed that the fix is rolled out? Is there going to be an RCA report? Any steps the team is taking so this doesn't happen again?
ve...@gmail.com <ve...@gmail.com> #967
I had the planned call with Google today and I'm going to bullet point the info I got, so it doesn't get long and confusing:
- A lot of the people they have contacted so far have refused to apply the "Repair portal" fix for their boot loop due to the risk of losing Application Information
- Google is working on a new way to recover App Data for the phones who boot loop
- Even if you apply the "Repair portal" fix, they may later on recover SOME app data on SOME phones (A post prior mentioned a mysterious second partition, so that might be connected)
- They are not planning on offering any compensation, but said "We will increase the support efforts going forward for all countries" (Although that might mean only for supported ones again)
- They somewhat admitted Google doesn't have a comprehensive backup solution, even for Google One subscribers.
- If you do apply the fix, data afterwards should be safe against this bug, provided you install the November update. There is no need to factory reset. (Take that as you will)
Also, they are calling from the Philippines, which at least for me, incurred a good amount of roaming charge for the half hour I talked to them. Keep that in mind and maybe ask them to call locally if possible so you avoid this.
ke...@gmail.com <ke...@gmail.com> #968
But I do not get an information about this, after 'restoring' the phone via the 'repair' tool.
Does anybody know, if I can get access to this backup?
ki...@gmail.com <ki...@gmail.com> #969
Well, that's too bad for them, because I'm not going to give up. I need my primary profile's app data, and won't have a no for an answer.
Are we understood? I don't care what it costs you. You can burn millions for all I care. I-WANT-MY-DATA-BACK.
ONE MONTH without a phone (and counting). I've got pending payments, lost contacts, hundreds of bookmarks I check on a semi daily basis. And I AM having to apologize EVERY DAY for YOUR mess. Get real! The very least you could do is provide proper frequent updates and communication. What you are doing, the way you are behaving, hiding behind misleading, sanitized, legal a-ok responses, giving us the runaround for days upon days, is disgusting. You are disgusting.
I could sympathize with people actually pouring themselves out full time to get us a proper fix, if such a person exists. But then again, they are working for google, the same company doing this to us. So...
And by the way, I too did contact Pixel support and fill out that bootloop form. The last THREE consecutive emails I've been told that an engineer would push an update on my phone (yeah, my bootlooping phone, as I keep reminding them). Still not once have I been contacted by one such engineer (or someone on their behalf). That's the level of CARE we are getting from a company making millions a day. It's ridiculous. They couldn't give less of a hoot, they know it, and they know we know it.
ke...@gmail.com <ke...@gmail.com> #970
But they say, they can do nothing, although I am a Google One member. The backup is usesless.
ar...@gmail.com <ar...@gmail.com> #971
- Interesting that they indicated to you that they were working on a way to recover data ... they didn't indicate this to me when I asked it directly. Perhaps it's a very new development in the last few hours, or maybe the technicians just aren't all consistently updated as to the company's plans? Or maybe they were just telling you want they thought you wanted to hear so they could wrap the call up :/ With so few communications from Google as to their official progress on things, it's anybody's guess.
- The "mysterious second partition" mentioned in
- Those additional charges that people may incur for an international phone call for support is just adding insult to injury for affected customers. Google really are making one mis-step after another with how they're handling this.
to...@gmail.com <to...@gmail.com> #972
jo...@gmail.com <jo...@gmail.com> #973
se...@gmail.com <se...@gmail.com> #974
ah...@gmail.com <ah...@gmail.com> #975
@974 The fix you will apply will restore your phone so that it can boot and your pictures and downloads are there, but your home screen on your primary profile will be as it was "out of the box". Your secondary profiles will be fine.
I would avoid it if you can for now.
The call I had scheduled was cancelled as I'd already run the Pixel Repair Tool to get out of the bootloop. My question about restoring my primary profile's app data got me sent back to support to make a new case.
-Loopy
se...@gmail.com <se...@gmail.com> #976
but i went to my files and waited and data started to populate i was able to copy all my photos and videos locally stored off the phone.
Didn't get back any of the contacts i lost but i had a .vcf backup i had done recently on my pc and as for 2fa i had other devices setup.
So i was able to log into 2fa on anything without much fuss auth app asked me to login again so i cant confirm if that would be there if i wasn't logged in somewhere else,
but i keep backup keys and have a drive to act as a ghetto ubikey my main concern was photos of my newborn and i was able to get those so i feel like i can breath again.
Still had to buy another phone in the process which sucks i wish google would do a compensation for those of us financially impacted as i had to reset up all my work stuff from scratch which was a pain but in the end im just happy to have the photos back.
ma...@gmail.com <ma...@gmail.com> #977
sa...@gmail.com <sa...@gmail.com> #978
gb...@gmail.com <gb...@gmail.com> #979
ge...@gmail.com <ge...@gmail.com> #980
Even if Google just announces that there won't be any additional fix (which would be terrible), so we can move on.
se...@gmail.com <se...@gmail.com> #981
ki...@gmail.com <ki...@gmail.com> #982
Update on my case (
I've finally been contacted to schedule a phone call with "the specialists" during which I'm supposed to be walked through the patch install procedure.
I've been crystal clear on the fact that I can't risk losing my primary profile's internal app data like phone contacts, browser session and bookmarks..., and will only go ahead once an official, 100% guaranteed confirmation by google is provided that such data will be recovered.
I'll keep you posted.
ah...@gmail.com <ah...@gmail.com> #983
@982
Good luck, but I think you're going to end up like the rest of us, or you will end up with a phone that is still bootlooping. They are likely going to take a week or so to have individual calls with each person who filled out the form to get out of the bootloop, and they are going to want to use the same procedure over and over to remove as much variability as possible between the affected devices.
If we're lucky, a new procedure will be developed later, but right now they are focused on getting through the backlog of bootlooping devices.
ki...@gmail.com <ki...@gmail.com> #984
Considering the limited number of "lucky" phones available to test these patches on, it might be a good idea to get a physical unit from one of us and clone/dump it so they can keep testing to their heart's content without risking our valuable data in the process.
Despite the privacy issues this approach entails, I'd be willing to part with mine so long as they promise to return it untouched (until or unless they manage to fix it fully).
I'll make sure to bring this up in my next conversation with them. Or feel free to contact me.
However, I will not simply take some "low-level" tech reps's word for it. Been shafted way too many times (in general, not google). But the fact I’ve been suggested, in a bootloop issue ticket, and three consecutive times (after explaining the issue in each of them), to "check for updates" to get the patch installed goes to show how absolutely insane one would need to be to trust anything they say. It would need to be someone higher-up taking responsibility for my phone and its present data's sake.
I get it, they're often incentive driven (sales, "resolved" tickets goals, ...), and they're often instructed what to do or say. But that's no excuse to give misleading information, lie through their teeth, ignore you, or give you the runaround. The problem is there’s no real accountability whatsoever (despite what the name “representative” suggests). They are used as cheap liability shields (“they broke the company’s communications policy” might be the company’s lame excuse), venting sinks, and delaying/pacifying instruments to minimize the risk of angry customer going legal.
I’m not saying that’s the case with google’s support. I’m just saying that from past experience, I’m not eager to find out.
Given how bad this case is, as many others said, the least they could do is up their communications to a decent level (frequency, accuracy, etc.).
sa...@gmail.com <sa...@gmail.com> #985
jo...@gmail.com <jo...@gmail.com> #986
to...@tommon.com <to...@tommon.com> #987
...and, of course, even after the notice tells you it will not wipe your data, it wipes your data. Awesome. /s
to...@gmail.com <to...@gmail.com> #988
ki...@gmail.com <ki...@gmail.com> #989
(
st...@gmail.com <st...@gmail.com> #990
Does anyone who received a fix have any persistent issues?
I can't seem to get Android Auto to work anymore (I haven't tried too hard but never had issues before).
I have also been getting loss of service intermittently (little exclamation point next to an empty service meter symbol).
Sorry to those still experiencing serious issues, I hope Google is able to figure things out for everyone.
cb...@piggyrat.net <cb...@piggyrat.net> #991
My phone went to the boot loop at this time or on day 5.
My other phone was reset as i was not able to wait for Google to come up with a solution.
This is the 2nd lost of data I had with Google - the first was with the webview debacle. Quality of Andoid seems to be dropping fast.
From what I am reading and experience with Google Support - factory reset seems to be the only option.
mc...@gmail.com <mc...@gmail.com> #992
Lucky for me this is not my main phone and when it went into bootloop, I chatted with support and they offered factory reset, but I decided to wait because I can. When the form was posted I registered, Support finally called on Tuesday but unfortunately they are just following a script, any deviation from the script they have no idea what to do and say will schedule a call back after they check with engineering.
I was stuck at "unable to connect the device" and it turned out the problem was as simple as I wasn't "in" rescue mode, and the support person was stunt and didn't know what to do, didn't even thought of asking any questions, but just put me on hold to "check with his people".
I figure out what's wrong after the call and got pass the connection issue, but then was stuck again.
The page offers "Factory Reset Recommended". And no, I was not gonna do that after waited for weeks for the fix.
Waited for another day, no support feedback, then decided to do some research on my own, and found out that #888 was referring to a different URL than the one I used! As soon as I corrected the URL, the right one -->
The update was actually quite fast, relatively, it's not like it was applying entire Android 14 update but probably patching what got corrupted that cause the phone to boot loop.
When it's done, my Pixel7 is working again!
I would not be surprise that this is as far as this recovery can go, there were certainly some data corruption which was why the phone was stuck at boot, and the default profile which the phone always start up with, was probably corrupted as well which explains why the fix did not (could not) recover the primary user's setup, but the 2rd profile (in my case, 3rd and 4th also) are all fully intact.
Good thing I did not do a factory reset, now, just need to figure out why Android File Transfer never works, and how do I back up my photos so I can do a clean factory reset.
ge...@gmail.com <ge...@gmail.com> #993
lu...@gmail.com <lu...@gmail.com> #994
Did I understand that correct? You have installed the patch, but nonetheless your phone went once again into bootloop? I am very worried to enable a second profile on mine, even if I do need it for work. Anyone one else tried? Mine is a Pixel 7 btw. Thanks.
to...@gmail.com <to...@gmail.com> #995
Can someone who already used the tool to get out of the bootloop please share her or his experience regarding the "media"-folder?
ki...@gmail.com <ki...@gmail.com> #996
I have thought about this long and deep.
First I was mad at the reps.
Now, I'm not so sure. They are often third world hires, and we should ask ourselves if they have a choice. Do they get to jump to a different, honest job, and still live within the average standards of their country? Or is it do or die for them?
If the anwer is no, then how can we blame them for chosing to screw us, over themselves in those dire circumstances? If the answer is yes, then, odds are they are collaborators and deserve to be blamed.
Regardless, they are being used as tools, shields by the corporate overlord. It's beyond belief that a company making millions upon millions in profits treats us like this, or even refuses to hire people able to provide a quality support service. Is asking for regular, accurate, trustworthy updates too much? I think not.
I get that the developers are busy working on a fix. Personally I would be content with some broad strokes overview: Why it happened. What's so difficult about getting access to the primary profile's app data. What they are doing to overcome this. There's no need to go from radio silence to high detail explanations. A bit of transparency would go a long way.
mc...@gmail.com <mc...@gmail.com> #997
Replying to #995
>
> Can someone who already used the tool to get out of the bootloop please share her or his experience regarding the "media"-folder?
>
Unfortunately I don't use WhatsApp on this phone although the app is installed, the dir hierarchy Android > media > com.whatsapp > WhatsApp exists but were empty (not in use). I do not have the "Databases" dir.
to...@gmail.com <to...@gmail.com> #998
Maybe someone else can share experience with this Android > media directory or especially Whatsapp-databases that had been stored on the phone?
or...@gmail.com <or...@gmail.com> #999
I finally ran the software update on my bootlooping 6a on my own. As many before me, I could recover my pictures, videos and audio notes - and not much else. Pictures inside the "secret folder" are indeed gone too. All apps are in fresh install state.
The Android File Transfer app on my Mac can't connect to the phone. So the data transfer which would take 10 minutes through USB-C became a backup action of a couple of hours. Once this is done, I will try to backup my secondary profile too. Then install all available OTA updates and finally factory reset the phone and start installing my apps.
Pictures were the most important thing to me, so at least that part is covered.
I wish there was a post-mortem analysis made available. This way I could understand what happened and would learn something along the way about how Android works on a lower level.
Most important lesson: despite the difficulty, try to back up everything regularly yourself.
Description