Pixel 6 crash after memory full. Need help

[Chamblard]

Hello

My Pixel6 won’t boot, here’s what happened :

• the phone was up and I used it normally
• the memory becomes full but the phone was still up
• I experienced issues like : cannot turn off wifi, so I reboot the phone
• at startup I can read messages like “this application stops systematically” … and after 5 seconds the phone say “shutdown…” and turned off.

The good thing is :

• I can boot in recovery
• I am root.
  so I tried :
• recovery > enable adb
• adb -s "XXXX...XX" shell
• I got the shell but can’t find datas.

df -h
Filesystem      Size Used Avail Use% Mounted on
tmpfs           3.6G 1.3M  3.6G   1% /dev
tmpfs           3.6G    0  3.6G   0% /mnt
tmpfs           3.6G    0  3.6G   0% /apex
tmpfs           3.6G 4.0K  3.6G   1% /linkerconfig
tmpfs           3.6G  32K  3.6G   1% /tmp
tmpfs           3.6G    0  3.6G   0% /storage

In recovery I did :

• recovery > Advanced > Mount/umount system, but got :

ERROR : recovery: [libfs_mgr]Unable to enable ext4 verify on /dev/block/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing
Mounted /mnt/system.

• adb -s "XXXX...XX" shell

oriole:/ # df -h /mnt/system/ 
Filesystem      Size Used Avail Use% Mounted on
/dev/block/dm-0 1.2G 1.2G   0M  100% /mnt/system

• with du I tried to find something to delete to make space
  I found
  /mnt/system/system/app/eDrive/eDrive.apk
  and /mnt/system/system/app/Maps/Maps.apk
• exit

mkdir tmp_adb; cd tmp_adb/
adb pull /mnt/system/system/app/eDrive/eDrive.apk .
adb pull /mnt/system/system/app/Maps/Maps.apk .
adb shell mount -o rw,remount,rw /mnt/system

adb -s "XXXX...XX" shell

rm /mnt/system/system/app/eDrive/eDrive.apk /mnt/system/system/app/Maps/Maps.apk
df -h /mnt/system/                                                                                                         
Filesystem      Size Used Avail Use% Mounted on
/dev/block/dm-0 1.2G 1.1G   92M  94% /mnt/system

• exit
• reboot > same issue

I would like to mount my user data partition in adb to get access to my files. But can’t managed to find it.

ls /dev/block/platform/14700000.ufs/by-name/                                                                           
abl_a  bl2_b   devinfo       dtbo_a      frp     ldfw_b    modem_b         pvmfw_a  userdata         vbmeta_vendor_a
abl_b  bl31_a  dpm_a         dtbo_b      gsa_a   metadata  modem_userdata  pvmfw_b  vbmeta_a         vbmeta_vendor_b
bl1_a  bl31_b  dpm_b         efs         gsa_b   mfg_data  pbl_a           super    vbmeta_b         vendor_boot_a
bl1_b  boot_a  dram_train_a  efs_backup  klog    misc      pbl_b           tzsw_a   vbmeta_system_a  vendor_boot_b
bl2_a  boot_b  dram_train_b  fips        ldfw_a  modem_a   persist         tzsw_b   vbmeta_system_b

I try :

adb -s "XXXX...XX" shell 
mkdir /mnt/tmp
mount /dev/block/platform/14700000.ufs/by-name/userdata  /mnt/tmp/                                                     
mount: /dev/block/platform/14700000.ufs/by-name/userdata: need -t

mount -t ext4 /dev/block/platform/14700000.ufs/by-name/userdata /mnt/tmp/                                              
mount: '/dev/block/platform/14700000.ufs/by-name/userdata'->'/mnt/tmp/': Invalid argument

mount -t f2fs /dev/block/platform/14700000.ufs/by-name/userdata /mnt/tmp/                                              
mount: '/dev/block/platform/14700000.ufs/by-name/userdata'->'/mnt/tmp/': Invalid argument

Can someone know how to mount userdata ?
OR any idea to resolve the boot issue ?

Thanks for your help

[tcecyk]

@Chamblard

the memory becomes full but the phone was still up

memory as in “disk space”? in any case, you’d need to free up space in userdata, not system

@Chamblard

Invalid argument

in an older thread I speculate “… the invalid arg error is originating from fs [recovery-] kernel module / mount-option incompatibility”, see How to mount encrypted /data partition in recovery mode? - #51 by tcecyk

Can you try suppling some of the mount options (oriole → raviole → gs101) of userdatas

fstab entry

(it’s f2fs)

mnt_flags / options:

noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt,atgc,checkpoint_merge

fs_mgr_flags:

latemount,wait,check,quota,formattable,sysfs_path=/dev/sys/block/bootdevice,checkpoint=fs,reservedsize=128M,fileencryption=@fileencryption@,metadata_encryption=@metadata_encryption@,keydirectory=/metadata/vold/metadata_encryption,fscompress,readahead_size_kb=128

[Chamblard]

Hello @tcecyk thank you for your help

• the thread : How to mount encrypted /data partition in recovery mode? - #51 by tcecyk helps me but does not solve the problem.
  My issue is the exact same problem :

  memory to 100% - now, upon phone start, MicroG and system services immediately crash, shutting down the phone.

• I can’t managed to find twrp for my phone : no Pixel6 here twrp.me/Devices/Google

• I tried many many mount options (thanks for the link) but I don’t know how to deal with mnt_flags or fs_mgr_flags en the -o
  The option line is very long ! ! !

Work in progress

[tcecyk]

pixels seems special in terms of recovery.
as for the mount, I’d try to start with mnt_flags only.

mount -v -t f2fs -o noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt,atgc,checkpoint_merge /dev/block/bootdevice/by-name/userdata /mnt/tmp/

[Chamblard]

I’ll try this week-end

[tcecyk]

did you have any results?

[Chamblard]

Hello @tcecyk
I’m sorry for only responding now
I had planned to respond sooner, of course, but between the holidays and the start of the school year, I couldn’t find the time.
Here’s what happened:

• My phone had the same problem as described in this post: How to mount encrypted /data partition in recovery mode? - #123 by rabon

  Signal messenger backup and incoming WhatsApp videos clogged memory to 100% - now, upon phone start, MicroG and system services immediately crash, shutting down the phone.

• A friend lent me a phone for several weeks.
• I searched several times for a solution to mount this /data partition. I ran tests, tried with another Pixel (7a), read the Android documentation, but I couldn’t mount this partition.
• Then a miracle happened: I turned on my phone and it worked. It was no longer blocked.
  I don’t know how or why, but it worked.
  I immediately deleted unnecessary data to free up space, and now it’s working normally again!

The only explanation I can think of would be the following (but this is just an idea on my part that has not been proven in any way):
During startup, certain actions are performed by the system, such as deleting obsolete system data. So with the passage of time (about three weeks), some data became too old (e.g., logs) and the system deleted it at startup, making enough free space to function.

I wanted to do more tests, but I haven’t found the time yet. For me, the question remains:

• How do I mount the /data partition from adb shell on a Pixel6 Android 13?
  But above all:
• Could my phone crash again due to a space issue?

In fact, I thought it was going to happen again, because I had another space issue:
My system wasn’t saving my actions, such as the messages I was writing.
Instead of restarting, I thought to check the available space, and it was 100% full.
I immediately deleted some data, even though it wasn’t easy because the apps were crashing.
I realized that the mistake I shouldn’t make was to restart the phone, because I could end up in the same situation:
Don’t restart the phone if it bugs, but check the available space and free up some if necessary.

Thank you very much for your help, which has allowed me to better understand certain things.
I hope to have time to figure out how to mount this /data partition.
Thanks again.

[aibd]

@Chamblard

Could my phone crash again due to a space issue?

Some headroom is required. There is usually a “full storage” warning after which I understand that proprietary Google will actually delete things. /e/OS will not delete stuff at this warning. Other users have reported “fails at next boot” idk but, as you observe, the warning it should be acted upon without delay.

Thanks for the detailed reply. I recommend a self imposed limit of 85% on internal storage. (If it grows a bit before one makes the next check no harm should come.)