I am amazed at how little free space I have remaining on my 32GB N5. It shows 26.8GB total space, and I realize some is used for overhead.
Running stock rom and really not that many additional apps, and no pictures, movies, or music on the phone, I am at around 8GB free space remaining.
The phone’s storage tab reports:
Total Space: 26.08 GB
Available: 8.00 GB
Apps: 1.69 GB
Pictures & Videos: 1.19MB
Audio: 304KB
Downloads: 1.8MB
Cached Data: 44.09MB
Misc: 2.96GB
When I look in Misc, 2.43GB of the 2.96 is TWRP nandroid backups, 538MB is TI Backups, the rest is insignificant. Adding up all of what is shows as used totals about 3GB. Add the 8GB available, you have 11GB. So what happened to the other 15GB?
I have installed a utility to help me analyze space usage, and it shows the biggest space user is TWRP, with 2.4GB in backups. Those are important to have and I don’t begrudge the space, but man, this is supposed to be a 32GB phone.
One problem with disk space analyzers is that they tend to look for large files, but you can have 10,000 small files that will occupy more total space than a few large ones.
Those of you who are running relatively stock, how much free storage space do you have on your 32GB Nexus 5?
michaelnel said:
I am amazed at how little free space I have remaining on my 32GB N5. It shows 26.8GB total space, and I realize some is used for overhead.
Running stock rom and really not that many additional apps, and no pictures, movies, or music on the phone, I am at around 8GB free space remaining.
The phone’s storage tab reports:
Total Space: 26.08 GB
Available: 8.00 GB
Apps: 1.69 GB
Pictures & Videos: 1.19MB
Audio: 304KB
Downloads: 1.8MB
Cached Data: 44.09MB
Misc: 2.96GB
When I look in Misc, 2.43GB of the 2.96 is TWRP nandroid backups, 538MB is TI Backups, the rest is insignificant. Adding up all of what is shows as used totals about 3GB. Add the 8GB available, you have 11GB. So what happened to the other 15GB?
I have installed a utility to help me analyze space usage, and it shows the biggest space user is TWRP, with 2.4GB in backups. Those are important to have and I don’t begrudge the space, but man, this is supposed to be a 32GB phone.
One problem with disk space analyzers is that they tend to look for large files, but you can have 10,000 small files that will occupy more total space than a few large ones.
Those of you who are running relatively stock, how much free storage space do you have on your 32GB Nexus 5?
Click to expand...
Click to collapse
No problems with storage here. I'm on stock with custom kernel, 1 nandroid backup. I have about 16.5GBs left, where about 8GB is my music and the other 2-3 are my apps and the nandroid backups.
Here's mine... 32GB rooted running stock rom..
Thanks. I thought this was abnormal. Not sure how to go about finding that 15GB.
When I went to 4.4.2 I loaded 4.4 fresh and the side loaded 4.4.2.. Not saying you should do that.. But it will reset all the space on the phone
Sent from my Nexus 5 using xda app-developers app
Thanks for the help, folks. I whacked it all the way back to stock, and installed the factory 4.4.2 image, then unlocked, installed twrp and supersu, and I am back in business with tons of free space. I have all my apps installed and now it shows over 23GB available.
I still have no idea where that 15GB went, but I figured whacking it was easier than troubleshooting it.
michaelnel said:
Thanks for the help, folks. I whacked it all the way back to stock, and installed the factory 4.4.2 image, then unlocked, installed twrp and supersu, and I am back in business with tons of free space. I have all my apps installed and now it shows over 23GB available.
I still have no idea where that 15GB went, but I figured whacking it was easier than troubleshooting it.
Click to expand...
Click to collapse
The "missing space" in the mass storage window is all the stuff on the /mnt/shell/emulated/ folder, outside of the /0/ (sdcard) directory.
For example, Nandroid Backups are stored there normally (at least CWM stores them on /mnt/shell/emulated/clockworkmod/ so they don't get wiped with the data on /0/). If you got your backups inside the /0/ folder you're in danger...
Check with the "diskUsage" app, on the root section, "mnt/shell/emulated" and you'll see what do you have there using your space (/obb/ is a symlink to /0/Android/obb/ and isn't using any space there really),
RusherDude said:
The "missing space" in the mass storage window is all the stuff on the /mnt/shell/emulated/ folder, outside of the /0/ (sdcard) directory.
For example, Nandroid Backups are stored there normally (at least CWM stores them on /mnt/shell/emulated/clockworkmod/ so they don't get wiped with the data on /0/). If you got your backups inside the /0/ folder you're in danger...
Check with the "diskUsage" app, on the root section, "mnt/shell/emulated" and you'll see what do you have there using your space (/obb/ is a symlink to /0/Android/obb/ and isn't using any space there really),
Click to expand...
Click to collapse
Thanks much. That diskUsage app is very cool, much better than the one I paid for.
nandroid backup create a new file each time you back up, so if you back up alot, you will found that the back up size is huge, just delete some old dated back up and keep the lastest one is ok
Sent from my Nexus 5 using XDA Premium 4 mobile app
RusherDude said:
For example, Nandroid Backups are stored there normally (at least CWM stores them on /mnt/shell/emulated/clockworkmod/ so they don't get wiped with the data on /0/). If you got your backups inside the /0/ folder you're in danger...
Click to expand...
Click to collapse
Where as this is the common lost space issue, its not so they don't get wiped. Its just easier to leave them there than detect if you're on a /0 device and dynamically set it. Twrp and philz do though.
Custom recoveries don't wipe /0 anyway - they run rm -Rf with an exclusion on 0.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Where as this is the common lost space issue, its not so they don't get wiped. Its just easier to leave them there than detect if you're on a /0 device and dynamically set it. Twrp and philz do though.
Custom recoveries don't wipe /0 anyway - they run rm -Rf with an exclusion on 0.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Are you saying that CWM and so started saving backups out of "/sdcard" (now /0/), and now when you wipe on them they wipe everything (including their backups that are outside of /0/) but /0/?
It has no sense. They'd have failed big time if so...
RusherDude said:
Are you saying that CWM and so started saving backups out of "/sdcard" (now /0/), and now when you wipe on them they wipe everything (including their backups that are outside of /0/) but /0/?
It has no sense. They'd have failed big time if so...
Click to expand...
Click to collapse
No.
I'm saying in the CWM source code for FUSE devices, /sdcard is mounted to /data/media - which was fine until android 4.2 which brought multi-user support. So even though other recoveries have moved with the times and updated their mount point to be /data/media/0, CWM simply didn't bother changing. It's not because they're "protecting from wipe" (in fact CWM doesn't wipe /sdcard anyway, only stock recovery does that), it's just they never updated it. That's why the backups are "outside" of /sdcard. No other reason.
Having backups outside of /sdcard has it's downfalls too. You cannot easily copy data from /sdcard to computer. Or copy a backup back to the device that can be restored.
rootSU said:
No.
I'm saying in the CWM source code for FUSE devices, /sdcard is mounted to /data/media - which was fine until android 4.2 which brought multi-user support. So even though other recoveries have moved with the times and updated their mount point to be /data/media/0, CWM simply didn't bother changing. It's not because they're "protecting from wipe" (in fact CWM doesn't wipe /sdcard anyway, only stock recovery does that), it's just they never updated it. That's why the backups are "outside" of /sdcard. No other reason.
Click to expand...
Click to collapse
Then okay, they didn't even bother to update, but as a result, the backups folder is outside the /0/ media mount point, and so, any application that wipes the real /sdcard mount point (/0) like the stock recovery as you say, won't wipe them.
Thanks for the explanation tho. I don't understand why they didn't even move a finger, but as a result the backups are more protected if you keep changing stuff and you like cleaning /sdcard (real /0 ) without touching the outside /mnt/shell/emulated folder (which contains vital data like said backups or the copy of the EFS folder usually).
rootSU said:
Having backups outside of /sdcard has it's downfalls too. You cannot easily copy data from /sdcard to computer. Or copy a backup back to the device that can be restored.
Click to expand...
Click to collapse
You can recover/push them easilly with adb tho.
RusherDude said:
Then okay, they didn't even bother to update, but as a result, the backups folder is outside the /0/ media mount point, and so, any application that wipes the real /sdcard mount point (/0) like the stock recovery as you say, won't wipe them.
Thanks for the explanation tho. I don't understand why they didn't even move a finger, but as a result the backups are more protected if you keep changing stuff and you like cleaning /sdcard (real /0 ) without touching the outside /mnt/shell/emulated folder (which contains vital data like said backups or the copy of the EFS folder usually).
You can recover/push them easilly with adb tho.
Click to expand...
Click to collapse
adb just isn't as convenient. But yes they are more protected but not by design. But also it has a problem in that your storage menu doesn't show true breakdown of space being used.
rootSU said:
adb just isn't as convenient. But yes they are more protected but not by design. But also it has a problem in that your storage menu doesn't show true breakdown of space being used.
Click to expand...
Click to collapse
Yeah.. but that drawback is minor. I would opt for a simple solution: Some root variation of the used space. Either:
a) A mod that makes the storage option to include all the stuff on /data/media/ including everything outside /0 .
b) Using another program that shows the real usage.
I don't really think that nandroid backups are "user data" per se, since this is as vital as the system itself for the user. Its logical to have it protected somehow :fingers-crossed:.
Its protected by the user not being an idiot. If they are an idiot, losing their backup is karma
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Related
Hi all,
I am trying to figure out whats taking all the space on my internal sd card. I switched to twrp recovery and deleted all clockworkmod related things, but it still says theres only 1 gb of free space left. I know for sure I could not possibly have used that much space. I store no music, very little photos.
I have tried using pc programs to visualize the space usage but none of them have been able to read the sd card, only the drives on the computer (spacesniffer for example).
Multiple apps installed (SDcard manager, Slim file manager) state i have 1 gb free space left, while another app (Storage Analyser) says I have 9gb free space.
Anyone have a program that will allow me to see whats taking up my space?
Thank you very much!
How many CWM backups did you have? When using CWM, after deleting your CWM backups did also you select the option to free up the space? How many TWRP backups do you now have?
Do you have any games installed? Have you checked file sizes or tried deleting leftover files under /sdcard/android? A lot of app data resides in the following three file paths:
/sdcard/android
/sdcard/data
/sdcard/Download
SlimSnoopOS said:
How many CWM backups did you have? When using CWM, after deleting your CWM backups did also you select the option to free up the space? How many TWRP backups do you now have?
Do you have any games installed? Have you checked file sizes or tried deleting leftover files under /sdcard/android? A lot of app data resides in the following three file paths:
/sdcard/android
/sdcard/data
/sdcard/Download
Click to expand...
Click to collapse
I had a few cwm backups. When using the "free up space" option in cwm about a week ago, it was such a small amount it said it would free up. I only have 1 twrp backup right now. I deleted all the CWM blob files and the file folder.
I'll take a look at the three file paths and come back. Thanks for your help
EDIT: nothing in /sdcard/data, sdcard/download is minimal, and sdcard/android is fairly minimal too
amotamatapia said:
I had a few cwm backups. When using the "free up space" option in cwm about a week ago, it was such a small amount it said it would free up. I only have 1 twrp backup right now. I deleted all the CWM blob files and the file folder.
I'll take a look at the three file paths and come back. Thanks for your help
EDIT: nothing in /sdcard/data, sdcard/download is minimal, and sdcard/android is fairly minimal too
Click to expand...
Click to collapse
No problem. Roughly 5 GB of data are set aside for the system, so as a reference:
-the 16 Gb GSIII would have at most 11.5 GB of free data
-the 32 GB GSIII would have at most 27.5 GB of free data
SlimSnoopOS said:
No problem. Roughly 5 GB of data are set aside for the system, so as a reference:
-the 16 Gb GSIII would have at most 11.5 GB of free data
-the 32 GB GSIII would have at most 27.5 GB of free data
Click to expand...
Click to collapse
Yeah, the weird thing though is that about a month ago i ran into the same issue of running out of space. and found that the CWM blob files were taking up about 5gb. And i had thought this was the same issue again, so I flashed TWRP and deleted the CWM files, but they arent the ones taking up the space this time
That's weird but like I said those are the main directories where app data resides on /sdcard. Which GSIII do you have 16GB or 32GB?
SlimSnoopOS said:
That's weird but like I said those are the main directories where app data resides on /sdcard. Which GSIII do you have 16GB or 32GB?
Click to expand...
Click to collapse
I have the 16gb version. I thought for sure I used "spacesniffer" last time to view the files on my sd card, which gave me a visual on whats taking up space. But I just cannot pinpoint it this time since no program ive downloaded views the internal sd card
Your best bet may be to copy over all your important files to a pc, nandroid to your external sd, then Wipe data or Factory reset in TWRP (the one that warns that it will format /sdcard. With those folders on your pc, you should be able to see their files sizes then do the math once it's back onto your phone. Maybe even do a screenshot of all the /sdcard folders first then do the above steps. You may be able to see which folder that is missing is the culprit once you put the folders back onto your phone.
Sent from my SCH-I535 using xda app-developers app
So, I'm trying to understand how and why the file system acts the way it does.
Example. I have
/sdcard
and this has a bunch of stuff under it
then i have
/sdcard/0
this has some of the same stuff under it as /sdcard, but is a different file system
Why can I not just have a simple file system that I can understand! I seem to have issues with space because sometimes wiping the phone does not wipe the /sdcard/0 so I am working out of /sdcard/0 as opposed to the base of /sdcard
Any help? I am an idiot so explain like I'm 5, if possible.
Thanks in advance.
n0xide said:
So, I'm trying to understand how and why the file system acts the way it does.
Example. I have
/sdcard
and this has a bunch of stuff under it
then i have
/sdcard/0
this has some of the same stuff under it as /sdcard, but is a different file system
Why can I not just have a simple file system that I can understand! I seem to have issues with space because sometimes wiping the phone does not wipe the /sdcard/0 so I am working out of /sdcard/0 as opposed to the base of /sdcard
Any help? I am an idiot so explain like I'm 5, if possible.
Thanks in advance.
Click to expand...
Click to collapse
5 year old explanation.
4.3 and above Android systems implement a multi user file setup similar to what Windows and OSx uses. The 0 folder is your account, your significant other could be 1, your dog could be 2, this keeps going depending how many users are registered to the device. It's actual intent is to use multi user on a tablet interface, not a phone, but because jellybean is used on both phones and tablets the file structure is the same.
Normally you don't have to worry about much of this, but if you came from 4.1 jellybean then multiuser wasn't implemented yet. This would double up your data in both places.
To me it sounds like you're OK, it's going to show double files because it's essentially reading the exact same folder, the format isn't going to understand what you're trying to do because it doesn't really know where to look for your data files. Basically, leave your 0 folder alone because that's where your data is supposed to be stored.
Was that 5 year old enough?
Edit: if you format your internal SD card in your recovery, then you'll erase the doubled data, and your folder structure will be repopulated under the 0 folder system. If you're running out of internal storage that's what you should do. Then clean flash the rom of your choice following the format.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
5 year old explanation.
4.3 and above Android systems implement a multi user file setup similar to what Windows and OSx uses. The 0 folder is your account, your significant other could be 1, your dog could be 2, this keeps going depending how many users are registered to the device. It's actual intent is to use multi user on a tablet interface, not a phone, but because jellybean is used on both phones and tablets the file structure is the same.
Normally you don't have to worry about much of this, but if you came from 4.1 jellybean then multiuser wasn't implemented yet. This would double up your data in both places.
To me it sounds like you're OK, it's going to show double files because it's essentially reading the exact same folder, the format isn't going to understand what you're trying to do because it doesn't really know where to look for your data files. Basically, leave your 0 folder alone because that's where your data is supposed to be stored.
Was that 5 year old enough?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yeah! That's a pretty solid explanation! I couldn't seem to find anywhere that broke it down that way.
So let me ask one more 5 year old question.
I seem to have TONS of space used up on my SD card, that I cannot free up.
I have a 16Gig GSIII, when I attach my phone to windows, I have 7gb free of 12gb. I just wiped system, cache, and dalvik, and have a clean version of Beanstalk 4.4.2.
How am I using 5gb when the OS itself is only, ~199Mb.
Is there anyway to have a completely clean install? Even when I soft bricked, and then revived w/odin and an old kernal, I don't think it was totally clean.
n0xide said:
Yeah! That's a pretty solid explanation! I couldn't seem to find anywhere that broke it down that way.
So let me ask one more 5 year old question.
I seem to have TONS of space used up on my SD card, that I cannot free up.
I have a 16Gig GSIII, when I attach my phone to windows, I have 7gb free of 12gb. I just wiped system, cache, and dalvik, and have a clean version of Beanstalk 4.4.2.
How am I using 5gb when the OS itself is only, ~199Mb.
Is there anyway to have a completely clean install? Even when I soft bricked, and then revived w/odin and an old kernal, I don't think it was totally clean.
Click to expand...
Click to collapse
Yup! I just told you in my post edit, left that out by accident.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Yup! I just told you in my post edit, left that out by accident.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks again! Great answers, and just the info I need!
So, to format it in CWM. I would go to
Mounts and Storage
format /data
or
format /data and /data/media (/sdcard)
i assume I don't touch
format /cache or format /system
and.. last thing I promise, how do I make sure I keep a copy of gaaps and a rom on the sdcard, if I format it?
n0xide said:
Thanks again! Great answers, and just the info I need!
So, to format it in CWM. I would go to
Mounts and Storage
format /data
or
format /data and /data/media (/sdcard)
i assume I don't touch
format /cache or format /system
and.. last thing I promise, how do I make sure I keep a copy of gaaps and a rom on the sdcard, if I format it?
Click to expand...
Click to collapse
You can't keep anything on the SD card after formatting, it'll be completely wiped clean, but you should do the second option. Also you should always format system when you clean flash a rom anyway.
I'd use an external SD card to flash the rom from. Alternatively, you could sideload the rom (if you know how). I don't know how.
Sent from my SCH-I535 using Tapatalk 2
I've searched and searched but can't figure out why my SD card keeps filling with this "system data" that disk scan says. The only way I've figured out how to clear it is factory reset and formatting the internal SD. Sadly it comes back over time. Ideas?
Kawirider1228 said:
I've searched and searched but can't figure out why my SD card keeps filling with this "system data" that disk scan says. The only way I've figured out how to clear it is factory reset and formatting the internal SD. Sadly it comes back over time. Ideas?
Click to expand...
Click to collapse
What are the contents of /sdcard (internal storage) in terms of folders? Do you save CWM/TWRP backups to internal storage?
SlimSnoopOS said:
What are the contents of /sdcard (internal storage) in terms of folders? Do you save CWM/TWRP backups to internal storage?
Click to expand...
Click to collapse
That's why I posted the screenshot. You can see that CWM is in the top folder, small amount.
Kawirider1228 said:
That's why I posted the screenshot. You can see that CWM is in the top folder, small amount.
Click to expand...
Click to collapse
I honestly don't get this SS. I always use a file browser and seeing things in a list or folder makes it easier to decipher for me. Seeing it like how you have it displayed is confusing to me.
That said, the two places data typically resides are /data/media OR /sdcard when using a file browser. I see /0 on there as well, if you use JB 4.3+ then you'll want to check /data/media for any files that were redistributed there and also "reveal hidden folders" to see if anything is hidden away there. From experience, CWM/TWRP backups tend to take up the most space if you have numerous backups and so do pics, vids, and music as well.
Sent from my SCH-I535 using Tapatalk 4
I just finished installing the latest ROM (YOG4PAS1N0) from here:
[ROM][YOG4PAS1N0] Cyanogen OS 12.1 [Rooted][TWRP flashable][NEW OTA]
http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-t3186593/page10
and it works amazing!!! No issues so far...while I was doing it I decided to use TWRP 2.8.6.0 to do a back up. I know that the following is a very "old school" way of backing my data but what I used to do is just save all the files in the exact same way my OPO is shown via the windows file system, and so I used to cut and copy .....place in a folder and done.... I have every single picture I have EVER taken since I owned a camera phone in 2007 but thats besides the point,,,I backup up my data via TWRP and I noticed that it created a 10GB partition. I am ok with it cause I keep a pretty clean phone...I have 10 apps at most and some pictures and videos.
I was wondering in the interest of recuperating that 10GB is there a way to unpartition it? my back up is 2.67 GB large and as you guessed it, I saved it on my PC....so I could do with out it on my phone. BY the way I didn't do a system or data wipe when I installed the ROM...flash and dalvik and cache wipe....I figured if I screwed up, I could do a FULL FORMAT and copy paste the files I wanted. But the update worked flawlessly ..except for the 10GB "missing"....
This is not an emergency, I can live without the 10GB I was just curious.........I have 54GB out of which I am only using 9GB...plenty left
Thanks for any help and for taking the time and reading this...
I did search for the answer but most users have other partition issues such as not loading or not finding it....I also google TWRP partitions and I got a lot of "how to use it" stuff...but nothing on how to "un partition"
seco007 said:
I just finished installing the latest ROM (YOG4PAS1N0) from here:
[ROM][YOG4PAS1N0] Cyanogen OS 12.1 [Rooted][TWRP flashable][NEW OTA]
http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-t3186593/page10
and it works amazing!!! No issues so far...while I was doing it I decided to use TWRP 2.8.6.0 to do a back up. I know that the following is a very "old school" way of backing my data but what I used to do is just save all the files in the exact same way my OPO is shown via the windows file system, and so I used to cut and copy .....place in a folder and done.... I have every single picture I have EVER taken since I owned a camera phone in 2007 but thats besides the point,,,I backup up my data via TWRP and I noticed that it created a 10GB partition. I am ok with it cause I keep a pretty clean phone...I have 10 apps at most and some pictures and videos.
I was wondering in the interest of recuperating that 10GB is there a way to unpartition it? my back up is 2.67 GB large and as you guessed it, I saved it on my PC....so I could do with out it on my phone. BY the way I didn't do a system or data wipe when I installed the ROM...flash and dalvik and cache wipe....I figured if I screwed up, I could do a FULL FORMAT and copy paste the files I wanted. But the update worked flawlessly ..except for the 10GB "missing"....
This is not an emergency, I can live without the 10GB I was just curious.........I have 54GB out of which I am only using 9GB...plenty left
Thanks for any help and for taking the time and reading this...
I did search for the answer but most users have other partition issues such as not loading or not finding it....I also google TWRP partitions and I got a lot of "how to use it" stuff...but nothing on how to "un partition"
Click to expand...
Click to collapse
What do you mean when you say it created a 10gb partition? TWRP doesn't create a partition when it makes a backup so I'm confused as to what you mean by that.
seco007 said:
I just finished installing the latest ROM (YOG4PAS1N0) from here:
[ROM][YOG4PAS1N0] Cyanogen OS 12.1 [Rooted][TWRP flashable][NEW OTA]
http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-t3186593/page10
and it works amazing!!! No issues so far...while I was doing it I decided to use TWRP 2.8.6.0 to do a back up. I know that the following is a very "old school" way of backing my data but what I used to do is just save all the files in the exact same way my OPO is shown via the windows file system, and so I used to cut and copy .....place in a folder and done.... I have every single picture I have EVER taken since I owned a camera phone in 2007 but thats besides the point,,,I backup up my data via TWRP and I noticed that it created a 10GB partition. I am ok with it cause I keep a pretty clean phone...I have 10 apps at most and some pictures and videos.
I was wondering in the interest of recuperating that 10GB is there a way to unpartition it? my back up is 2.67 GB large and as you guessed it, I saved it on my PC....so I could do with out it on my phone. BY the way I didn't do a system or data wipe when I installed the ROM...flash and dalvik and cache wipe....I figured if I screwed up, I could do a FULL FORMAT and copy paste the files I wanted. But the update worked flawlessly ..except for the 10GB "missing"....
This is not an emergency, I can live without the 10GB I was just curious.........I have 54GB out of which I am only using 9GB...plenty left
Thanks for any help and for taking the time and reading this...
I did search for the answer but most users have other partition issues such as not loading or not finding it....I also google TWRP partitions and I got a lot of "how to use it" stuff...but nothing on how to "un partition"
Click to expand...
Click to collapse
There is no 10GB partition. When a device says that there is 64 GB of storage, a bit of it is lost in formatting. It does not mean that when you plug in your phone you will get 64GB of storage. Additionally, there are several partitions, including data and system that are not visible to the user without root (or in recovery). These partitions also take up space on your phone (adding up to around 10GB of lost space), and are not visible when you plug in your phone. This is why your phone only shows 54 out of 64GB in the storage menu in settings, mine does as well. If you did have a 10GB partition on your phone, your phone would show 44GB when plugged in. I believe you can make the system partitions smaller, but its not recommended. This is simply off my memory so if I misunderstood the question or said anything wrong please be welcome to correct me.
f41lbl0g said:
There is no 10GB partition. When a device says that there is 64 GB of storage, a bit of it is lost in formatting. It does not mean that when you plug in your phone you will get 64GB of storage. Additionally, there are several partitions, including data and system that are not visible to the user without root (or in recovery). These partitions also take up space on your phone (adding up to around 10GB of lost space), and are not visible when you plug in your phone. This is why your phone only shows 54 out of 64GB in the storage menu in settings, mine does as well. If you did have a 10GB partition on your phone, your phone would show 44GB when plugged in. I believe you can make the system partitions smaller, but its not recommended. This is simply off my memory so if I misunderstood the question or said anything wrong please be welcome to correct me.
Click to expand...
Click to collapse
I figured it was a 10GB partition because I was 10GB short (64GB out of the box vs 54GB) what I have, even though I now that OS and apps take up space. So what is the actual partition size that is created when TWRP creates a back up? The size of said back up? ....my mistake...
your explanation cleared it up. If I remove the back up from my phone will I recover that HDD space? or is it already saved for future back ups?
seco007 said:
I figured it was a 10GB partition because I was 10GB short (64GB out of the box vs 54GB) what I have, even though I now that OS and apps take up space. So what is the actual partition size that is created when TWRP creates a back up? The size of said back up? ....my mistake...
your explanation cleared it up. If I remove the back up from my phone will I recover that HDD space? or is it already saved for future back ups?
Click to expand...
Click to collapse
Your backups are created on the visible portion of the data partition, in a folder called TWRP. No partition is created during a backup. You will not gain more than the available space on your phone by deleting the backup.
seco007 said:
I figured it was a 10GB partition because I was 10GB short (64GB out of the box vs 54GB) what I have, even though I now that OS and apps take up space. So what is the actual partition size that is created when TWRP creates a back up? The size of said back up? ....my mistake...
your explanation cleared it up. If I remove the back up from my phone will I recover that HDD space? or is it already saved for future back ups?
Click to expand...
Click to collapse
TWRP doesn't create a partition, it simply creates a folder in your internal storage to place your backups in. That folder will only ever be the size of your backup(s). The moment you delete/move a backup you have that space free again, they're just like any other file that consumes space on a drive (it only consumes space while it's actually there).
f41lbl0g said:
Your backups are created on the visible portion of the data partition, in a folder called TWRP. No partition is created during a backup. You will not gain more than the available space on your phone by deleting the backup.
Click to expand...
Click to collapse
ok So it works like any other file / folder...erase and you have the HDD space again....Thanks for clearing that up
I'm trying different apps that claim they securely erase files and/or securely wipe free space on your phone. None seems to work on my phone so far with little exception from Secure Eraser (it sometimes results in unlisting erased photos in DiskDigger). I wonder if it is just with my phone (rooted). Does anyone had had the same problem and eventually succeeded?
I'm aware phone NAND memory is not SSD and does not have TRIM instructions, thus file shredding might be impossible to achieve but why free space wiping does not work, either? When saying an app does not work I mean the deleted files weighing 3MB each (JPEG pictures) are fully or partly recoverable using DiskDigger root scan of /data partition (the original pictures, not only their thumbnails hidden somewhere on /data partition). I tested each app's file shredding and free space wiping functionality only to find no alleged function works.
Apps I tried:
Andro Shredder
https://play.google.com/store/apps/details?id=com.apparillos.android.androshredder
iShredder 6 Standard
https://play.google.com/store/apps/details?id=com.projectstar.ishredder.android.standard
SDelete File Shredder
https://play.google.com/store/apps/details?id=com.vb2labs.android.sdelete
Shreddit Data Eraser
https://play.google.com/store/apps/details?id=com.palmtronix.shreddit.v1
Secure Eraser (free space wipe only app)
https://play.google.com/store/apps/details?id=com.aiuspaktyn.secureeraser
Secure Wipe (free space wipe only app)
https://play.google.com/store/apps/details?id=com.pinellascodeworks.securewipe
My phone's configuration:
Custom bootloader TWRP,
LineageOS 14.1 (Android 7.1.2),
Rooted (for apps and adb),
Internal storage fully encrypted (customized with third-party app),
/data partition is formatted using F2FS file system,
stock camera app (destination: Internal storage),
all erasers are granted storage permission,
DiskDigger is granted root access and performs root scan
DonKichot said:
I'm trying different apps that claim they securely erase files and/or securely wipe free space on your phone. None seems to work on my phone so far with little exception from Secure Eraser (it sometimes results in unlisting erased photos in DiskDigger). I wonder if it is just with my phone (rooted). Does anyone had had the same problem and eventually succeeded?
I'm aware phone NAND memory is not SSD and does not have TRIM instructions, thus file shredding might be impossible to achieve but why free space wiping does not work, either? When saying an app does not work I mean the deleted files weighing 3MB each (JPEG pictures) are fully or partly recoverable using DiskDigger root scan of /data partition (the original pictures, not only their thumbnails hidden somewhere on /data partition). I tested each app's file shredding and free space wiping functionality only to find no alleged function works.
Apps I tried:
Andro Shredder
https://play.google.com/store/apps/details?id=com.apparillos.android.androshredder
iShredder 6 Standard
https://play.google.com/store/apps/details?id=com.projectstar.ishredder.android.standard
SDelete File Shredder
https://play.google.com/store/apps/details?id=com.vb2labs.android.sdelete
Shreddit Data Eraser
https://play.google.com/store/apps/details?id=com.palmtronix.shreddit.v1
Secure Eraser (free space wipe only app)
https://play.google.com/store/apps/details?id=com.aiuspaktyn.secureeraser
Secure Wipe (free space wipe only app)
https://play.google.com/store/apps/details?id=com.pinellascodeworks.securewipe
My phone's configuration:
Custom bootloader TWRP,
LineageOS 14.1 (Android 7.1.2),
Rooted (for apps and adb),
Internal storage fully encrypted (customized with third-party app),
/data partition is formatted using F2FS file system,
stock camera app (destination: Internal storage),
all erasers are granted storage permission,
DiskDigger is granted root access and performs root scan
Click to expand...
Click to collapse
Because deleted data is not actually deleted, it is only "marked" to be overwritten the next time the device needs to write/save data, in the meantime, the data is still "there", it's just being ignored by the system. The only way to really do what you're looking for is to actually format the whole partition(which wipes everything in that partition), you can't just format the "free" space at the "end" of the partition/drive.
Android doesn't work the same as PC, you seem to be trying to treat your android device the same as you would your PC. There is not that much similarity between them, they are pretty much their own different worlds.
But, you're in luck because there is this
https://android.gadgethacks.com/how-to/delete-files-android-so-they-cant-ever-be-recovered-0169550/
It kinda does what you're looking for but in a different manner.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Because deleted data is not actually deleted, it is only "marked" to be overwritten the next time the device needs to write/save data, in the meantime, the data is still "there", it's just being ignored by the system.
Click to expand...
Click to collapse
I get it but this is why Secure Eraser (brought by an xda dev Giuseppe Romano - https://labs.xda-developers.com/store/app/com.aiuspaktyn.secureeraser) works in a proper way writing dummy data to the partitions so all the free space on the physical internal card is being overwritten. It means Android gives you a warning you're running out of free space, stops the app and you have to click on the app again so it can proceed up to 100% of internal memory's free space. Still, it works only sometimes - the later you use it after deletion the smaller chance of success you get. I guess it's worth **** cause wiping is actually being done on /data's free space which doesn't mean you wipe all internal memory card's free space (let's call it a PC hard drive). There is still free space located on other physical partitions (Boot, Cache, Recovery, System, Vendor).
Fu*k it - I may have just answered myself. Where is an Android app for a rooted device doing wiping free space properly (wiping the whole internal card's free space), Anyone? A solution related to TWRP, adb command, perhaps? We need a decent [email protected] Kill Disk for Android, guys - nothing works at the moment.
DonKichot said:
I get it but this is why Secure Eraser (brought by an xda dev Giuseppe Romano - https://labs.xda-developers.com/store/app/com.aiuspaktyn.secureeraser) works in a proper way writing dummy data to the partitions so all the free space on the physical internal card is being overwritten. It means Android gives you a warning you're running out of free space, stops the app and you have to click on the app again so it can proceed up to 100% of internal memory's free space. Still, it works only sometimes - the later you use it after deletion the smaller chance of success you get. I guess it's worth **** cause wiping is actually being done on /data's free space which doesn't mean you wipe all internal memory card's free space (let's call it a PC hard drive). There is still free space located on other physical partitions (Boot, Cache, Recovery, System, Vendor).
Fu*k it - I may have just answered myself. Where is an Android app for a rooted device doing wiping free space properly (wiping the whole internal card's free space), Anyone? A solution related to TWRP, adb command, perhaps? We need a decent [email protected] Kill Disk for Android, guys - nothing works at the moment.
Click to expand...
Click to collapse
The thing that makes it tough to have a good tool to do this on android is the way android is partitioned and how permissions and read/write works in android, along with certain proprietary motivated hardware/software blocks implemented by manufacturers and carriers.
Sent from my LGL84VL using Tapatalk
Reviews on play store confirm that secure eraser isn't working. Disk digger still finds files. Don't trust it.
willpower102 said:
Reviews on play store confirm that secure eraser isn't working. Disk digger still finds files. Don't trust it.
Click to expand...
Click to collapse
The app was bought by Mobile Safe Apps, they probably destroyed it. You can still get the apk from the xda dev Giuseppe Romano - https://labs.xda-developers.com/store/app/com.aiuspaktyn.secureeraser. Thanks DonKichot.