Closed k-arabadzhiev closed 1 week ago
This is actually new - previously this would either not give the reason for the error, or sometimes even crash the app. This is supposed to happen when one of the files or sub-folders inside your folder have a name that is illegal on Windows.
If other files are transferred without issues, then this error is correct. Whenever you select files that have illegal chars in their name, a message will pop up in the top right corner specifying where these names are illegal.
@Alex4SSB That's a cool and useful feature, but I can't even find such file, could we get an absolute path in the error?
Also what happens when an error of these is encountered? Does the file transfer stop or it will keep transfering other compatible files? What if multiple files are illegal?
This error is reported by ADB, and that's all the information it gives in this case. Regarding the completion of the operation - usually, the files before that one got transferred. I see now that I should change the Validate button to enable validation of failed operations for cases like this, to get a list of files that are missing or corrupt.
Have you tried searching for a file with that string in the name? Sadly, the app does not support searching yet (just filtering, in the current folder). If you're unable to find the file using the app, you can use the terminal to access ADB directly:
adb shell find /sdcard/ -iname "*httpscdn.liftoff-*"
I'll try to search like that on Monday when I'm back at home (no PC at the moment), thanks!
I'm not even sure I need this Android folder backed up, but I managed to solve the general problem (backing up the rest of phone's data) by transferring with your app wirelessly, then with MTP and just skip duplicates. Saved a ton of time for sure, because my phone has faster wi-fi (866 Mbps) than usb (480Mbps) port and mtp hasn't been very reliable from past experiences.
Glad to hear that.
This folder does have things you might want to backup, for example /sdcard/Android/media/com.whatsapp/WhatsApp/Media
Is there a way around this error?![image](https://github.com/user-attachments/assets/7fe0476f-56ee-4f7d-ae16-8f6cb01328a2)