Hello! I recently faced an issue trying to upload big file to Android tablet. It doesn’t detect with MTP so I tried to push it via ADB. But I get this error:

$ adb push myfile /sdcard
adb: error: 65544-byte write failed: Success

How can I fix it? Why is this happening? Storage space is enough:

EDIT: I want to use it for app devlopment, so I need ADB or quick MTP for app installing.

  • burgersc12
    link
    fedilink
    English
    11 day ago

    I’d check the cable. Might be a POS that only works for the bare minimum of tasks.

  • @[email protected]
    link
    fedilink
    English
    43 days ago

    Is /sdcard really the correct path? Maybe try /storage/emulated/0? That’s the internal storage

    • @user_naaOP
      link
      English
      13 days ago

      Same error. Plus /sdcard is just symlink to /storage/emulated/0/

      • @[email protected]
        link
        fedilink
        English
        13 days ago

        Yeah but sometimes stuff like this works even if it seems to make no sense. If both of your devices are on the same wifi, maybe you can just use something to transfer it using that like KDE Connect. If you don’t want to install anything, you could even try using SSH.

        • @user_naaOP
          link
          English
          13 days ago

          It will be very inconvenient to transfer app via KDE Connect on every Android Studio build

          • @[email protected]
            link
            fedilink
            English
            23 days ago

            Android studio has it’s own way to install, just enable wireless debug in devs settings (tap 7 times the build number in software info) and connect it to android studio. That’s how I do it and just click the “play” button and studio does everything automatically

            • @user_naaOP
              link
              English
              13 days ago

              Yes, but it crashes with “connection reset” if app is big enough.

              • @[email protected]
                link
                fedilink
                English
                11 day ago

                That’s really weird. Have you tried if it’s something as simple as the cable? You could also try using wireless adb if you can’t get it to work over the cable at all. I also always use wireless adb, it still allows Android Studio (or in my case VS Code) to automatically install it on your device but I find it a lot easier anyways because it just connects automatically and you don’t have to plug anything in first.

  • @Sabin10
    link
    English
    33 days ago

    A little old skool maybe but why not try ftp?

    • @[email protected]
      link
      fedilink
      English
      23 days ago

      Would be my go-to as well. I’m using x-plore file manager on my phone to start an ftp server, and then push files via filezilla from my computer. Easy, and compatible with every OS out there.

    • @user_naaOP
      link
      English
      1
      edit-2
      3 days ago

      It works, but my Wi-Fi is very slow

      • @[email protected]
        link
        fedilink
        English
        1
        edit-2
        3 days ago

        It’ll be quicker than MTP because it’s actually reliably consistent, unlike MTP.

        Since MTP is an unreliable hack, I’ve found using a “slow” wireless connection to work better.

    • @user_naaOP
      link
      English
      13 days ago

      Yes, didn’t help

      • @[email protected]
        link
        fedilink
        English
        13 days ago

        Would you mind sharing some details? computer OS name and version, your adb version and if you installed systemwide or if you compiled/downloaded out of your repos

        • @user_naaOP
          link
          English
          13 days ago

          Fedora 41 with latest adb from repos

          • @[email protected]
            link
            fedilink
            English
            13 days ago

            You didn’t mention it so I asume that you can open a shell, did you tried creating a file in the destiny? Also SELinux may be the problem, try temporary disable it, if works, enable it and create an exception. Other thing; since adb daemon runs on 127.0.0.1:5073/TCP check if you have any localhost firewall rules, but this doesn’t make sense if you can open a shell. Last things, download the lastest SDK, you don’t need to install it, just call adb with the full path.

            • @user_naaOP
              link
              English
              1
              edit-2
              3 days ago

              ADB and Android Studio works perfectly with any other Android phone, so I think it is likely not PC issue. Small files and apps can also be pushhed/installed

    • @user_naaOP
      link
      English
      1
      edit-2
      3 days ago

      Yes, I can even shell into it or pull/push small files

      • @[email protected]
        link
        fedilink
        English
        13 days ago

        How old is this phone? My guess is corruption at hardware level.

        If you can shell into it and have dd or something, try to write a simple file to e.g dd if=/dev/zero of=/sdcard/testfile bs=1MB count=200 If that fails when directly on the device, you can rule out network issues.

        You can also try downloading a file from the web that’s about the size of your file or serving your file on the local WLAN with python3 -m http.server and accessing it on your phone. Just to see what happens.

        Anti Commercial-AI license

        • @user_naaOP
          link
          English
          13 days ago

          I can’t do it until I formatted data. After it file can be downloaded from net, but adb still fails.

          • @[email protected]
            link
            fedilink
            English
            1
            edit-2
            2 days ago

            Shooting from the hip here, but it sounds like the storage chip may be dying. I have a 128GB Pixel 1XL that crashes if I use more than ~20GB of space.