You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made a tiny bit mistake, I extracted a zip that originally Japanese encoding on Termux with zip (default, has not extra option). It creat a directory contains seve files. This directory cannot be deleted by File Manager.
The directory is located under ~/storage/shared/Something/Other/
What should I do?!
Attempts (these are done by Termux):
Move/rename into something else: rm * tmp returns No such file or directory
Remove its parents which it located: rm -rf Other returns Directory not empty
As no solution to be found, factory reset is planned on next week.
Dirty Solution
This does not require factory reset, at cost an installed app under Android/media to be sacrificed.
Get adb ready and run adb shell. The parent directory of corrupted file can be moved to specifics directories:
/sdcard (this is identical to /storage/emulated/0, I have no idea)
/sdcard/Android/media (unlike /sdcard/Android/data, the numbers of Apps that using this directory is not many: mine WhatsApp and Telegram, I have no idea)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I made a tiny bit mistake, I extracted a zip that originally Japanese encoding on Termux with
zip
(default, has not extra option). It creat a directory contains seve files. This directory cannot be deleted by File Manager.The directory is located under
~/storage/shared/Something/Other/
What should I do?!
Attempts (these are done by Termux):
rm * tmp
returnsNo such file or directory
rm -rf Other
returnsDirectory not empty
abd shell
and remove files by its inodePotentially duplicate: #3228
Information from
termux-info
.Factory reset
As no solution to be found, factory reset is planned on next week.
Dirty Solution
This does not require factory reset, at cost an installed app under
Android/media
to be sacrificed.adb
ready and runadb shell
. The parent directory of corrupted file can be moved to specifics directories:/sdcard
(this is identical to/storage/emulated/0
, I have no idea)/sdcard/Android/media
(unlike/sdcard/Android/data
, the numbers of Apps that using this directory is not many: mineWhatsApp
andTelegram
, I have no idea)/sdcard/Android/media/com.whatsapp/WhatsApp
/sdcard/Android/data
and/sdcard/Android/obb
, doesn't workWhatsApp
, be sure all of its data is remotely backed up.This is less time consuming than factory reset. Fell free to this topic here.
Beta Was this translation helpful? Give feedback.
All reactions