FORUMS

Sunday Debate: How Can We Get a No-Compromise Phone?

Join us in a fun Sunday Debate on Compromises. Come with your opinions and … more

PSA: You Can Optimize Your Note 4’s Recents Menu & RAM

The Note 4 never had the fastest Recents Menu, and despite its 3GB of RAM, … more

XDA Picks: Best Apps of the Week (July 25 – Aug 1)

Apps are at the front and center of any smartphone experience, and with over a … more

Voices Of XDA: Orbiting The Earth With Android

Editor’s note: This week’s feature has been written by forum … more

Storage

111 posts
Thanks Meter: 2
 
By calibachrome, Senior Member on 3rd July 2014, 08:12 AM
Post Reply Subscribe to Thread Email Thread
I have a T-Mobile galaxy s5 stock rooted. I'm having an issue with internal storage. It says I have 5.5g in misc files being used. This was the case before when I had a nandroid backup on there. However I moved it yet the space is still being used although the file is no longer on there. Trying to figure out how I can resolve this and get my storage back.
 
 
3rd July 2014, 09:28 PM |#2  
fffft's Avatar
Senior Member
Thanks Meter: 669
 
More
Quote:
Originally Posted by calibachrome

I have a T-Mobile galaxy s5 stock rooted. I'm having an issue with internal storage. It says I have 5.5g in misc files being used. This was the case before when I had a nandroid backup on there. However I moved it yet the space is still being used although the file is no longer on there. Trying to figure out how I can resolve this and get my storage back.


Well if you moved a Nandoid or other large files and the apparent free space didn't change.. I'd suspect that you copied rather than moved the files. Use a file explorer to confirm whether the Nandroid files are still there or not.

Alternately have a look at the directories that have the largest files and re /move them as appropriate.
You can use various terminal commands to locate the largest files, e.g.

Code:
su
du -a /var | sort -n -r | head -n 10
Code:
su
for i in G M K; do du -aH | grep [0-9]$i | sort -nr -k 1; done | head -n 11
If you still have a mystery, then I suppose file system corruption is possible. Perhaps the easiest way to resolve that would be restoring a known good, full Nandroid backup.


.
The Following 2 Users Say Thank You to fffft For This Useful Post: [ View ]
Silentrath
6th July 2014, 05:46 PM |#3  
Guest
Thanks Meter: 0
 
More
.

Sent from my SM-G900T using XDA Premium 4 mobile app
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes