FP4 device sometimes boot loops and always has no audio

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

Hi, I had fairphone 4 with the stock OS, I wanted to switch to /e/OS, using the web installer but after unlocking the bootloader, I got hit with the google account prompt, so I looked it up on google how to remove it, and I did fastboot erase persist , said it would remove FRP, but I think that erased something important instead, after it led to a boot loop, so I tried to continue installing /e/OS through fastboot instead, which worked, but sometimes still boot looped, and even if it successfully booted, there’d be no audio and no outgoing calls. Am I screwed now? Or is there a dump I need to flash to the persist partition to fix this, I looked at the errors in logcat, which are:

03-03 19:46:45.087 650 16522 W sscrpcd : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:892: Warning: apps_std_fopen_with_env failed with 0x2 for /mnt/vendor/persist/sensors/registry/registry (No such file or directory)
03-03 19:46:45.087 650 16522 E sscrpcd : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:1246::Error: 201: 0 == (nOpenErr = apps_std_fopen_with_env(ADSP_LIBRARY_PATH, ";", name, "r", &ps))
03-03 19:46:45.087 650 16522 E sscrpcd : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:1265:Error 0x201: apps_std_stat: failed to stat /mnt/vendor/persist/sensors/registry/registry, file open returned 0x2 (No such file or directo
ry)
03-03 19:46:45.109 650 16522 W sscrpcd : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:892: Warning: apps_std_fopen_with_env failed with 0x2 for /mnt/vendor/persist/sensors/registry/registry (No such file or directory)
03-03 19:46:45.109 650 16522 E sscrpcd : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:1246::Error: 201: 0 == (nOpenErr = apps_std_fopen_with_env(ADSP_LIBRARY_PATH, ";", name, "r", &ps))
03-03 19:46:45.109 650 16522 E sscrpcd : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:1265:Error 0x201: apps_std_stat: failed to stat /mnt/vendor/persist/sensors/registry/registry, file open returned 0x2 (No such file or directo
ry)
03-03 19:46:45.116 1384 1384 I adsprpcd: vendor/qcom/proprietary/adsprpc/src/rpcmem_android.c:159: rpcmem_init_internal: opened ION device fd 4, configured heap IDs: system (0x2000000), contig (0x400000), secure (0x200), secure flags
(0x80080000)
03-03 19:46:45.116 1384 1384 I adsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:3092: fastrpc_apps_user_init done with default domain:0 and &fastrpc_trace:0x731b164fa0
03-03 19:46:45.117 1384 1384 I adsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1345: remote_handle_open: Successfully opened handle 0x0 for '":;./\createstaticpd:audiopd on domain 0
03-03 19:46:45.118 1384 1384 E adsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2875: Error 0x4e: apps_dev_init failed for domain 0, errno Operation not permitted
03-03 19:46:45.118 1384 1384 E adsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2973: Error 0x4e: open_dev (-1) failed for domain 0 (errno Operation not permitted)
03-03 19:46:45.120 1384 1384 E adsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1348: Error 0x4e: remote_handle_open failed for adsp_default_listener (errno Success)
03-03 19:46:45.121 1384 1384 I adsprpcd: vendor/qcom/proprietary/adsprpc/src/rpcmem_android.c:192: rpcmem_deinit_internal: closed ION fd 4
03-03 19:46:45.121 1384 1384 I adsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:3024: fastrpc_apps_user_deinit done

I assume it may have led to the system remaking the persist partition but empty and not completely valid.

I hope to get this fixed ASAP, because it is my only phone right now and I have to rely on my computer for now. Even flashing the fairphone OS will always end up in a boot loop and only recovery is accessible.

you remove the FRP by removing the device properly from the Google Account it was associated with.

As to the persist partition, you should be able to obtain the partition from FPOS factory images. And reflash to it individually (through fastboot)

I checked and persist partitions are not included in the factory images, I think I need a dump from someone

if the persist partition is an a/b partition (it should), you could check if both slots got erased (probably), but if not, you can get the healthy partition via dd within twrp or a recovery and flash back.

Unfortunately the persist partition is not a/b, but what do you exactly mean by healthy partition? I haven’t backed it up beforehand. I have tried flashing the factory OS and the boot logo changes to factory, still boot loops.

healthy would’ve only made sense if it’s a/b. But yeah I see with my FP3 it too is a single partition. Maybe worth to ask in the fairphone forums for a persist partition donation

Yea thanks, I’ll see what the fairphone forums will say, I think they may be more helpful.

While not very recent and is written for Xiaomi [Guide] About repairing/fixing the persist partition | XDA Forums may be worth following carefully the initial steps to see if persistbak exists ??

Hi, I’ve checked but I see this instead of a persistbak:
lrwxrwxrwx 1 root root 15 1970-01-01 11:22:02.863999998 +0000 oempersist → /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-01-01 11:22:02.843999998 +0000 persist → /dev/block/sda3

oempersist could be a backup of persist? They don’t have the same size though, so I don’t think it would work if I flashed the oempersist to persist.

My low level experience of persist is where it intersects with EFS which I had cause to backup years ago to ensure preservation of IMEI. I cannot really help other than searching where I also found Fix Persist, resolve IMEI=0, Volte, 4G, Explanation, Requirements | XDA Forums. I found no Fairphone links.

I am guessing you may well know more of the subject than me but … regarding diff in sizes with oempersist, I wonder how one would read persist maybe the regular persist contains extra “device or even user specific” data (if your original link thought that a Google password would be here) ??

I guess also a requirement to learn to read persist in case a donated one can be used. If asking for a donation can you define how a user here might extract one in a useful format?

For someone to donate me their persist partition from FP4, they can boot into TWRP, then access the adb shell from the pc, and dd if=/dev/block/by-name/persist of=/sdcard/persist then they could do adb pull /sdcard/persist and upload the persist dump file to me.

Perhaps; the answer to this would depend on “how is persist populated?” Will it repopulate from oem with some command or even on reboot / Factory reset?


dd if=/dev/block/by-name/persist of=/sdcard/persist.img

might make the file safer to transmit ??

However when I do boot /e/OS, the persist partition does get recreated and boots ok, but with no sensors and audio. Probably because it wasn’t made fully and important files couldn’t be remade.

I checked what could be inside oempersist, but there’s nothing really interesting besides an empty folder.

I believe the persist partition could be unique per device and doesn’t repopulate properly, I’ll just see if I can even attempt to get a working donation or just ship the phone for a repair and pay.

Those are two things that the oem variant could potentially contain ?? … but are you saying that there is only an empty folder?

Yes, this is whats made in the persist partition, which is partially made and lacks some folders like sensors:

persist partition:

Date Time Attr Size Compressed Name
------------------- ----- ------------ ------------ ------------------------
2026-03-04 20:27:51 D.... lost+found
2026-03-04 20:33:06 D.... data
1970-01-01 02:32:09 D.... t2m_param
2026-03-04 20:32:02 D.... time
1970-01-01 02:32:15 D.... secnvm
1970-01-01 02:32:15 D.... iar_db
1970-01-01 02:32:15 D.... display
1970-01-01 02:32:15 D.... vpp
1970-01-01 02:32:16 D.... hvdcp_opti
1970-01-01 02:32:15 D.... rfs
1970-01-01 02:32:15 D.... hlos_rfs
1970-01-01 02:32:14 D.... data/pfm
2026-03-04 20:32:04 D.... data/f3-kdcO7vtq3DPXQWveXFSLY--rOiMGsotFIfOjqlTI_Alt
2026-03-04 20:33:06 D.... data/persist
1970-01-01 02:32:15 D.... data/pfm/licenses
1970-01-01 02:32:15 ..... 61440 65536 data/pfm/licenses/store_0
1970-01-01 02:32:15 ..... 61440 65536 data/pfm/licenses/store_1
1970-01-01 02:32:15 ..... 61440 65536 data/pfm/licenses/store_2
1970-01-01 02:32:15 ..... 61440 65536 data/pfm/licenses/store_3
1970-01-01 02:32:15 ..... 61440 65536 data/pfm/licenses/store_4
2026-02-11 16:36:32 ..... 8 8192 time/ats_15
2026-02-11 16:36:32 ..... 8 8192 time/ats_16
2026-02-11 16:36:32 ..... 8 8192 time/ats_12
2026-02-11 16:36:32 ..... 8 8192 time/ats_13
2026-03-04 20:32:02 ..... 8 8192 time/ats_2
2026-03-04 20:32:02 ..... 8 8192 time/ats_1
2026-03-05 00:36:38 ..... 200 8192 hvdcp_opti/soh_info.txt
1970-01-01 02:32:15 D.... rfs/shared
1970-01-01 02:32:15 D.... rfs/msm
1970-01-01 02:32:15 D.... rfs/mdm
1970-01-01 02:32:15 D.... rfs/apq
1970-01-01 02:32:15 ..... 15 8192 rfs/shared/server_info.txt
2026-02-11 16:36:11 D.... rfs/msm/mpss
1970-01-01 02:32:15 D.... rfs/msm/adsp
1970-01-01 02:32:15 D.... rfs/msm/slpi
1970-01-01 02:32:15 D.... rfs/msm/cdsp
1970-01-01 02:32:15 D.... rfs/msm/wpss
1970-01-01 00:01:46 ..... 5 8192 rfs/msm/mpss/server_check.txt
1970-01-01 02:32:15 D.... rfs/mdm/mpss
1970-01-01 02:32:15 D.... rfs/mdm/adsp
1970-01-01 02:32:15 D.... rfs/mdm/slpi
1970-01-01 02:32:15 D.... rfs/mdm/tn
1970-01-01 02:32:15 D.... rfs/mdm/cdsp
1970-01-01 02:32:15 D.... rfs/mdm/wpss
1970-01-01 02:32:15 D.... rfs/apq/gnss
1970-01-01 02:32:15 D.... hlos_rfs/shared
2026-03-04 20:32:04 ..... 8192 12288 data/f3-kdcO7vtq3DPXQWveXFSLY--rOiMGsotFIfOjqlTI_Alt/LYbKI1svITWlV2BqGZvt
2026-03-04 20:32:04 ..... 1588 8192 data/f3-kdcO7vtq3DPXQWveXFSLY--rOiMGsotFIfOjqlTI_Alt/f3-kdcO7vtq3DPXQWveXFSLY--rOiMGsotFIfOjqlTI_Alt
2026-03-04 20:32:04 ..... 1588 8192 data/f3-kdcO7vtq3DPXQWveXFSLY--rOiMGsotFIfOjqlTI_Alt/f3-kdcO7vtq3DPXQWveXFSLY--rOiMGsotFIfOjqlTI_Alt.bak
2026-03-04 20:32:04 ..... 4096 8192 data/f3-kdcO7vtq3DPXQWveXFSLY--rOiMGsotFIfOjqlTI_Alt/LYbKI1svITWlV2BqGZvt.bak
2026-03-04 20:32:04 ..... 8192 12288 data/f3-kdcO7vtq3DPXQWveXFSLY--rOiMGsotFIfOjqlTI_Alt/4peJ3AqBsLUCJu6La8UX
2026-03-04 20:32:04 ..... 4096 8192 data/f3-kdcO7vtq3DPXQWveXFSLY--rOiMGsotFIfOjqlTI_Alt/4peJ3AqBsLUCJu6La8UX.bak
2026-03-04 20:33:06 D.... data/persist/data
2026-03-04 20:48:53 D.... data/persist/data/fpdata
2026-03-04 20:48:53 ..... 8 8192 data/persist/data/fpdata/ifaa_fplist
2026-03-04 20:27:51 ..... 4194304 4194304 [SYS]/Journal
------------------- ----- ------------ ------------ ------------------------
2026-03-05 00:36:38 4529532 4661248 22 files, 34 folders

oempersist:

Date Time Attr Size Compressed Name
------------------- ----- ------------ ------------ ------------------------
1970-01-01 00:00:06 D.... lost+found
1970-01-01 00:00:07 D.... qns
1970-01-01 00:00:06 ..... 16777216 16777216 [SYS]/Journal
------------------- ----- ------------ ------------ ------------------------
1970-01-01 00:00:07 16777216 16777216 1 files, 2 folders