25
Any way to pull a local file from an Android 12 device stuck in Recovery before factory reset? (Unlocked bootloader) - Reddthat (reddthat.com)
submitted 3 hours ago* by to c/android@lemmy.world
7 comments fedilink hide all child comments
 

My Tecno Spark 10 Pro (MediaTek Helio G88, Android 12) bootlooped after a banking app froze. Now it boots straight into stock recovery with the message that Android cannot be loaded and data may be corrupt. The bootloader is unlocked. I hooked it up to an Android tablet via OTG with Bugjaeger. The device uses A/B partitioning and was running on slot b. I switched it to slot a via fastboot, but slot a gives the exact same recovery loop, so the issue is clearly a corrupted userdata partition failing to mount during early init. All I need is my local KeePass database file from internal storage. I know modern Android uses File-Based Encryption with keys sealed in the TEE, but since my bootloader is unlocked, is there any known way via fastboot, MTK tools, or custom boot images to extract or decrypt that single file before I wipe the device? Or is it completely unrecoverable once the filesystem fails to mount?

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 2 hours ago* (last edited 2 hours ago) (2 children)
  • are you rooted?/do you get adb while booting? (few years ago on a custom rom's debug build, but i was able to connect via adb and read logcat and solve the issue it was having while stuck in bootloop and before it auto enters recovery)
  • i see you have custom recovery now. can you boot a custom recovery (maybe temporarily via fastboot)?

it should be possible to recover given that you have full unrestricted access to the device and even know the lockscreen password..

seems like it's possible with twrp. btw, i've bootlooped my phone before after using twrp to wipe dalvik cache on a recent encrypted phone (it created an unencrypted dir on userdata iirc, removing the offending directory solved it), so beware and don't do anything that doesn't seem necessary!

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 1 hour ago (1 child)

    I don't have root and I don't have custom recovery :)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 1 hour ago*

    maybe try booting this or this TWRP temporarily without flashing using fastboot (fastboot boot recovery_filename.img)

    (kinda unlikely to be able to directly mount data though, there's one on 4PDA too dated Apr 2024 but it specifically says it doesn't support mounting data)

    are you able to obtain the installed version of the firmware or extract stock boot image from device? (if the TWRP above booted, you probably can)

    in that case, we may be able to enable adb during boot phase by changing some props on the boot image's initrd, and try logcat'ing to get android properly booting again.

  • permalink
  • fedilink
  • source
  • parent