I am on a Fairphone 3 and run /e/os 1.9. # Background # I recently started to run out of disk space each time one of my apps (Signal messenger) started to create a new backup, as my free space was not large enough to accommodate a new backup file. Yesterday I turned off the phone when I saw that the "little storage left" notification came up and the backup was running, and put a brand new micro SD card in the phone that I had meant to set up since a while. After powering up the phone again, the notification for low storage was (non-surprisingly) still showing, alongside with one for the new SD card. When I opened the SD card I saw that a lot of empty folders had been creating, mirroring the ones in my internal storage. The phone also started to vibrate repeatedly and showed "No log (file) could be created" in a small popup on the bottom of the screen. I decided to ignore that and try to move some files from the internal storage to the SD card to free up some space. After a short while, the phone crashed and rebooted into recovery. # Problem # When I power up the phone, it boots into recovery, showing this screen: Recovery Version 1.9 () Active slot: a Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device. > Try again Factory data reset I can also navigate back into a recovery menu. When I select *try again*, the phone starts up as normal. I get then to unlock my SIM. However, as soon as try to unlock the normal lock screen for the first time, the phone will crash. If I just try to unlock the screen, an empty home screen will show for a moment, before my normal home screen loads (I use lawnchair as a launcher, which is not /e/os default). Then, sometimes a popup comes saying *??? launcher crashes all the time*, partially obscured by an other popup saying *Power off*. The phone will then reboot into the recovery. If I try to directly go to the settings page by swiping down and clicking the settings shortcut, that page is shown for a second or two before the phone also powers off and reboots into recovery. If I click on the "Out of storage" notification, the same thing happens. **I would really like to prevent losing my data.** # What I have tried so far # It appears like I can't do anything after unlocking my phone, as it will reboot directly. I have gone through the recovery and fastboot menus, trying to find anything that could be of help. I was able to activate ADB and browse around in the file system using

shell

, but none of my personal files where accessible and there was apparently a lot of space available on that partition. I was also able to *mount system* from an option in the recovery. Even this partition showed only 73% disk usage. It was also read-only, so I was not able to remove any files. The sdcard folder in both

/

and

/mnt/system/

was empty. The recovery also gives me the option to install an update, e.g. via adb sideload. I have not tried that, since I don't know how to do so and if it will give me access to my personal data. # What to do now? # If this would be a computer, I would use a live linux system to run

and similar tools to identify and repair the corrupted data and to free up some disk space. Is it possible to do something similar with my phone, for example using adb? Is there any way to access/recover and possibly back up my personal data?

Hello I have a Samsung s22 ultra which used to work completely fine till one UI 7 update after that I was screen recording when the mini thing which shows timer of screen recording and pause button disappeared then I couldn't find my screen recording in the gallery but I found it in my files saved as a .pending file and it also shows the video occupies around 1gb space but it's unplayable. Then I lost hope and screen recorder worked fine for a few days and then again the problem started and screen recording saved as .pending but it showed it occupied around 600mb space but it didn't play and then it happened several times btw I had enough storage my phone is 12gb ram and 512gb room variant I had more than 150gb free space also I had enough battery and everything else was working fine. Someone please help me I really need those screen recorded files. Please anyone provide a working solution about how to get that video back. It's been some days now I even restarted my phone still it didn't work also it's up to date and no malicious software is present it's not rooted or something too just everything is normal.

I'm using Samsung Galaxy S10e on Android 12. I took several screen recordings using the native function. Moved many to SD card using "Files by Google" app. Moved them separately in groups of 1-3. Some of them are playable, some are not. As pictured, the ones with blank thumbnails are unplayable. They are unplayable with both the native video player and EX File Manager. The files still show the full sizes (1+GB). With EX File Manager, I could see that they were 0 mins long in the file info. Worth noting that the SD card is 99% full now. Also, worth noting that a couple of the files wouldn't transfer due to limited space, so I had to make more space, then they transferred, and I remember at least one of the specific files that I had to reattempt is definitely playable after transfer. What can be done?

I have a Samsung Galaxy A7 Lite tablet with updated Android and a 32GB Adata SD card I bought a few months ago. I was trying to move apps from internal storage to an SD card and the tablet suddenly crashed. Now, the apps on the SD card are greyed out and not usable. I tried to move SD card files to a PC and it cannot copy one file with the **asec** extension. The error indicates it's corrupt or broken. Could that be the problem? I don't want to lose data as much as possible. How can I solve it?

I have a BQ-7082G ARMOR Android 7 device, with a SD card formatted as internal storage. One day it run out of battery, shut down, and afterwards it reported the SD card is corrupt and refuses to mount it. My only options offered by the device is to reformat it (external/internal storage), something I just won't do because there is some important data on it. Complicating matters I can't easily at least make a backup of the card because I lack a suitable reader to connect to my PC. Side note is I just don't understand how did it get damaged at all? There was no activity for like half a day and the only purpose the device fulfilled back then was to play music. Unfortunately, I got the stupid idea to take some photos with it the day before this happened and I'd like to get them all. Other than that there was no anything else I would lose my sleep over, although getting back everything would be nice. How can I figure out what happened to the card so that hopefully I could fix just that somehow and have the device recognize the SD card properly?

I want to replace the kernel inside twrp 12.1 recovery with my kernel that I built. Now with only unpacking and repacking the recovery image I end up with an image of different size The recovery image size is 128M

root@localhost:~/mkbootimg# ls -alth recovery.img

-rw-r--r--. 1 root root 128M Jul 15 12:40 recovery.img

The tool I'm using is google mkbootimg mkbootimg -h

usage: unpack_bootimg.py [-h] --boot_img BOOT_IMG [--out OUT] [--format {info,mkbootimg}] [-0]

Unpacks boot, recovery or vendor_boot image.

options:
  -h, --help            show this help message and exit
  --boot_img BOOT_IMG   path to the boot, recovery or vendor_boot image
  --out OUT             output directory of the unpacked images
  --format {info,mkbootimg}
                        text output format (default: info)
  -0, --null            output null-terminated argument strings

Output format:

  * info

    Pretty-printed info-rich text format suitable for human inspection.

  * mkbootimg

    Output shell-escaped (quoted) argument strings that can be used to
    reconstruct the boot image. For example:

    $ unpack_bootimg --boot_img vendor_boot.img --out out --format=mkbootimg |
        tee mkbootimg_args
    $ sh -c "mkbootimg $(cat mkbootimg_args) --vendor_boot repacked.img"

    vendor_boot.img and repacked.img would be equivalent.

    If the -0 option is specified, output unescaped null-terminated argument
    strings that are suitable to be parsed by a shell script (xargs -0 format):

    $ unpack_bootimg --boot_img vendor_boot.img --out out --format=mkbootimg \
        -0 | tee mkbootimg_args
    $ declare -a MKBOOTIMG_ARGS=()
    $ while IFS= read -r -d '' ARG; do
        MKBOOTIMG_ARGS+=("${ARG}")
      done 

Running the commands the tools suggests

root@localhost:~/mkbootimg# ./unpack_bootimg.py --boot_img recovery.img  --out out --format=mkbootimg |     tee mkbootimg_args
--header_version 2 --os_version 16.1.0 --os_patch_level 2127-12 --kernel out/kernel --ramdisk out/ramdisk --recovery_dtbo out/recovery_dtbo --dtb out/dtb --pagesize 0x00001000 --base 0x00000000 --kernel_offset 0x00008000 --ramdisk_offset 0x01000000 --second_offset 0x00000000 --tags_offset 0x00000100 --dtb_offset 0x0000000001f00000 --board '' --cmdline 'console=ttyMSM0,115200n8 earlycon=msm_geni_serial,0xa90000 androidboot.hardware=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 service_locator.enable=1 androidboot.usbcontroller=a600000.dwc3 swiotlb=2048 cgroup.memory=nokmem,nosocket reboot=panic_warm buildvariant=eng'
root@localhost:~/mkbootimg# nano mkbootimg_args
root@localhost:~/mkbootimg# sh -c "./mkbootimg.py  $(cat mkbootimg_args) -o  repacked.img"                root@localhost:~/mkbootimg# ls -alth repacked.img
-rw-r--r--. 1 root root 67M Jul 15 22:20 repacked.img
root@localhost:~/mkbootimg#

I had to modify mkbootimg_args and change --header_version to 3 because the tool didn't like it but you can see the repacked.img is 67M where the original recovery.img is 128M Flashing the repacked image to recovery partition I end up with destroyed boot/recovery screen