Hello, i’m switching from FP3 to FP6, because have not enough space.
Some parts are backuped. But not all. Suddenly the fairphone 3 startet. Few second after unlock the phone the bliss and microg die and the phone shutdown. I think some memory issues.
I’m not able to connect to phone. I want to backup some files. But adb is only possible in recovery mode.
Wipe cache does in recovery not exist. Is there an idea how can i rescue some data?
Hello @TheAkki, Welcome to the /e/ users forum.
.
you should be able to boot into TWRP without installing it
fastboot boot twrp-3.7.0_9-0-FP3.img
“internal storage” is encrypted so not readable out of running the android system,
but you should be able wipe cache
and also to access to /data partition.
Infortunally:
fastboot boot twrp-3.7.0_9-0-FP3.img
Sending ‘boot.img’ (31512 KB) OKAY [ 0.852s]
Booting FAILED (remote: ‘unlock device to use this command’)
fastboot: error: Command failed
fastboot flashing unlock will erase my data. So it’s not possible for me. Or understand i the error wrong?
1 Like
i personnally never experienced re-locking, so also not re-unlocking …
as i understand it, it is expected to wipe / erase the “/data” partition, but not format it, so i believe the “internal storage” stay untouched.
BUT documentation says you will loose your data…
so, better is to wait for confirmation from someone who is accustomed with those operations
why i never lock my bootloader, to keep flexibility…
“To prevent […], unlocking the bootloader will also delete all personal data on your phone” is shown on display when i insert this command.
OK. I will wait for answer from you.
The encryption looks file and folder based is this right? So i can guess depends on size the content? I’m not sure. Can somebody ack this?
I guess you know that when a Fairphone starts to give an overfull message an urgent intervention is required as the phone will fail soon after as certain headroom is required at start up.
To be honest I am not sure if this was ever fixed with a locked bootloader. A search of threads from 
Search - too full recover data fairphone might give some clues.
1 Like
a bootloader locked FP3 (official image) can make space via adb shell from the recovery. Community images can use twrp to have easier access though.
Look at the group ownership of the file and take out a video. This thread is imo most instructive.
2 Likes
I had delete “random” two big files on /data/media/0/ and /data/app/
Now it’s booting again.
Thank you. Thread is solved.
2 Likes
on what partition / folder ?
This topic was automatically closed after 60 days. New replies are no longer allowed.