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?

  • hexagonwin@lemmy.todayEnglish
    2·
    13 hours ago

    do you have the stock firmware of this device (the version installed on the phone)?

    if you don’t, at least please share the build version or whatever info shows on the stock recovery, fastboot/bootloader menu (if it exists), etc

    • lipen@reddthat.comOPEnglish
      1·
      12 hours ago

      Here is the exact build information from my stock recovery screen:

      Device: TECNO Spark 10 Pro (TECNO/KI7-GL/TECNO-KI7) Android version: 12 (SP1A.210812.016) Build number: 230703V2369 Build tag: user/release-keys

      I don’t have the stock firmware package or scatter file on hand right now, but this is the exact build that is currently installed.

      • hexagonwin@lemmy.todayEnglish
        3·
        11 hours ago

        try downloading this boot.img file, and booting it with fastboot boot tecno_ki7_boot.img. let me know if it tries to boot android (shows booting animation), fails, and goes to recovery just like now.

        it’s from this firmware file. (most firmwares for your phone on the net is android 13, this is 12)

        (if this works, my idea is to unpack the boot.img, change persist.sys.usb.config and ro.adb.secure on default.prop to gain adb during boot. then we can use logcat to fix the issue and make android boot)

          • hexagonwin@lemmy.todayEnglish
            2·
            7 hours ago

            you mean it

            • tries to boot android, fails and goes to recovery?
            • or it doesn’t even show the boot animation and just hangs on fastboot? or reboots immediately?

            i’ll need details to help…