FORUMS

Is the LG G4’s Camera Really DSLR-worthy?

After months of anticipation, the LG G4 was finally unveiled today, showing off an … more

SuperSU Beta Updates With Minor Fix For Galaxy S6

ChainFire’s root permissions app SuperSU has updated to v.2.49 to fix audits on … more

LG G4 Day Event Coverage: Specs, Features, Design & More!

LG has been teasing us with a countdown for a while now, and today it reached … more

Xposed Modules to Modify Email – XDA Xposed Tuesday

Even though we have Dropbox and other ways to share files, people still want … more
Post Reply Subscribe to Thread Email Thread

Storage

3rd July 2014, 08:12 AM |#1  
calibachrome's Avatar
OP Senior Member
Jacksonville, FL
Thanks Meter: 2
 
More
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: 652
 
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