***I tried searching for an existing thread but couldn't find one so if there is one that somehow didn't see please redirect me.
After updating to 7.1.1 using the image file from google (w/full factory reset and i'm not rooted either is that's important) my storage is showing that the System is using 92.3GB of my 128GB. How is that even possible!?
Anyone else run into this?
Crazypinoy9 said:
***I tried searching for an existing thread but couldn't find one so if there is one that somehow didn't see please redirect me.
After updating to 7.1.1 using the image file from google (w/full factory reset and i'm not rooted either is that's important) my storage is showing that the System is using 92.3GB of my 128GB. How is that even possible!?
Anyone else run into this?
Click to expand...
Click to collapse
Wipe your cache In storage and delete heavy apps
boxguy1 said:
Wipe your cache In storage and delete heavy apps
Click to expand...
Click to collapse
I appreciate the reply but I don't think you're fully understanding my issue that I've stated. The issue is that the System itself is showing as taking up 92.3GB of storage. Plus, wiping my cache would be a fraction of that amount and would be negligible.
Like I stated already, this is specifically the System being populated and is only happening after updating to 7.1.1 with a completely fresh install. All i did was install my apps afterwards....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My apps are taking up exactly 5.37GB of storage. Here's a storage analysis from ES File Explorer of my app usage:
Crazypinoy9 said:
I appreciate the reply but I don't think you're fully understanding my issue that I've stated. The issue is that the System itself is showing as taking up 92.3GB of storage. Plus, wiping my cache would be a fraction of that amount and would be negligible.
Like I stated already, this is specifically the System being populated and is only happening after updating to 7.1.1 with a completely fresh install. All i did was install my apps afterwards....

My apps are taking up exactly 5.37GB of storage. Here's a storage analysis from ES File Explorer of my app usage:
My apps are taking up exactly 5.37GB of storage. Here's a storage analysis from ES File Explorer of my app usage:

Click to expand...
Click to collapse
Have you tried wiping everything in TWRP and formating then going. Back to stock with NRT toolkit
boxguy1 said:
Have you tried wiping everything in TWRP and formating then going. Back to stock with NRT toolkit
Click to expand...
Click to collapse
For now I'm saving that as my next step if I can't get any other suggestions today.
***side note, I'm currently doing a full nandroid backup (including apps/data) and it's telling me that it's backing up 8.47GB
Do you have a ton of nandroid backups? That's a ton of space.
Sent from my Pixel XL using XDA-Developers mobile app
bigmatt503 said:
Do you have a ton of nandroid backups? That's a ton of space.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope. Like I said, this is showing up after a fresh install of 7.1.1. I was just doing a nandroid backup preparing to do a full format.
I ended up doing a full wipe, still shows up as 92.31 GB of system storage usage. Then I just got done doing another fresh install of 7.1.1 from a brand new image download from Google. Still the same. After doing another full wipe after doing another fresh install it's still showing the same. I've done full wipes using the TWRP and I've tried a full wipe using the stock reset function with the stock recovery. No go...
Nothing seems to work...
Crazypinoy9 said:
. . .Then I just got done doing another fresh install of 7.1.1 from a brand new image download from Google. . .
Click to expand...
Click to collapse
Does this mean you flashed a factory image? If not, read up on this thread;
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page524
Do not use a toolkit. Learn to do it manually first. Use fastboot and manually flash all of the factory image files. If the problem persists after a factory image flash, you could contact Google or Huawei and report the issue and see if they will replace it for you.
Have had this happen to me in the past. You will need to wipe your storage and start with a clean flash with whichever, ROM or factory image.
Sent from my Nexus 6P using Tapatalk
Before that you could root your device to get full access to the file system to find where's your space is going. Also a simple df -H in android terminal will tell you the real remaining space on /data without even rooting. If there's an inconstancy raise a google problem report.
When you said "full factory reset" you mean you used the flash-all.bat from factory image?
Enviado desde mi Nexus 7 mediante Tapatalk
HI all, to answer some of your questions:
1. Yes, i manually flash all images, not through a rootkit
2. Yes, I used flash-all.bat
3. Yes, I am rooted and have checked to make sure of the exact amount of storage the entire system is actually using.
a. found out that the system itself was occupying just over 3GB
b. while doing a full nandroid backup (including data) it stated that it was backing up roughly 8-9GB
Here's the very weird part of this that I stumbled on last night. I ran the whole process again from formatting (including storage) and manually flashing images. Once it was done I ran through the google setup process with a "fresh" install (vs restoring from cloud backup). Upon checking the system storage usage it was perfectly normal. 4GB out of 128GB. Here's the twist. I proceeded to do a factory reset, and through the initial google setup process, this time I used a restore from my google cloud backup. After the process was completed, and setup was done. The system storage was showing 92.31GB of usage. ?????????
In order to test out what was happening I pulled out my Huawei P9 and formatted it, did initial google setup including restoring from the same account backup. When it was done I checked the system storage and whaddya know...it's normal at around 4GB. Just for ****z and gigglez I tried the same on my older S6 Edge. Same thing. System Storage usage was normal after using the restore function from the cloud backup.
Why would my backup through Google cause that? and why would it only affect my Nexus 6P?
Crazypinoy9 said:
For now I'm saving that as my next step if I can't get any other suggestions today.
***side note, I'm currently doing a full nandroid backup (including apps/data) and it's telling me that it's backing up 8.47GB
Click to expand...
Click to collapse
Okay good luck
Crazypinoy9 said:
3. Yes, I am rooted and have checked to make sure of the exact amount of storage the entire system is actually using.
a. found out that the system itself was occupying just over 3GB
Click to expand...
Click to collapse
So df -H /data reports the same usage?
/system is by design like 3GB (and nearly full) so the "system" in settings must also account for other things than /system. Only /data has that amount of data.
Once you've confirmed that /data is indeed so much used, download an app like Disk Usage to spot what's eating your space?
I think your issue is flashing the userdata partition.
Instead of doing the flash-all.bat, manually flash each file separately.
Skip flashing the userdata portion - only format userdata - and then when all are done, format cache and reboot.
Related
Can any one shed some light on what system data is on my N4s storage?
I assumed it was the os but that's partitioned and I then have the 5.8gb that's available...
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using xda app-developers app
Most likely the OS.
Sent from my Nexus 4 using Tapatalk 2
The OS takes up part of the 8gb to leave me with 5.8 though.. Anyone else?
Sent from my Nexus 4 using xda app-developers app
adaimespechip said:
The OS takes up part of the 8gb to leave me with 5.8 though.. Anyone else?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Are you using CWM and if you do, what version are you using?
When I just got the phone, I had the same problem as you after I install a buggy version of CWM. Basically CWM made a backup to some folder that there's no way for you, CWM, or the system to tell where the heck it is.
I got rid of that by restoring my phone to stock then started using TWRP (try it, you'll like it)
Edit: Also, look at /data instead of /sdcard
/sdcard is an emulated folder, /data is more accurate since it's where stuffs are actually stored.
thats HUGE for system data. i only have 270MB used for it
Yeah I did but that was so long ago.. It could be that I guess. You suggest erasing the whole thing and restoring my apps?
Sent from my Nexus 4 using xda app-developers app
Well, I got that back in CWM 6.0.1.6, which is like a month a go. A life time for the Nexus 4. There is a way to trace these folders using ADB, but I wiped my entire phone before I read the post so I don't know if the method works.
What I did was wiping everything (including system) then restore to stock. It was a little bit overdone, I guess restore to stock would do the trick. Just remember to back up /sdcard to your computer.
Edit: I was so annoyed by that wasted 1.7MB that I basically nuked the phone lol
bassmadrigal said:
If you are rooted and have adb set up on your computer, you can find out what folders are using the most space by using the commands below, then change into that directory and run the command again.
Code:
adb
su
cd /
du -hd 1
--find the largest folder and change directory (cd) into it - if you find you no longer want to continue in the folder you are in, you can cd .. to get to the previous folder or cd / to get back to the root of the filesystem--
Code:
cd large_folder
du -hd 1
rinse
repeat
????
profit
This will allow you to find what folders are using the most space and can eventually lead you to any large files and can then let you find out if you can delete them or if you need to keep them.
Click to expand...
Click to collapse
What application are you using to get that information?
Sent from my Nexus 4 using Tapatalk 2
netsyd said:
What application are you using to get that information?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
DiskUsage 3.4
Sent from my Galaxy Nexus using xda premium
mariosraptor said:
DiskUsage 3.4
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
What he said - one of my must have apps..
Sent from my Nexus 4 using xda app-developers app
KyraOfFire said:
Well, I got that back in CWM 6.0.1.6, which is like a month a go. A life time for the Nexus 4. There is a way to trace these folders using ADB, but I wiped my entire phone before I read the post so I don't know if the method works.
What I did was wiping everything (including system) then restore to stock. It was a little bit overdone, I guess restore to stock would do the trick. Just remember to back up /sdcard to your computer.
Edit: I was so annoyed by that wasted 1.7MB that I basically nuked the phone lol
Click to expand...
Click to collapse
Thanks! Will try when I'm back home!
Sent from my Nexus 4 using xda app-developers app
Okay no luck - Have totally reset the device and still have 1900mb of system data showing....
EDIT: Fixed - Flashed new CWM recovery and it WAS a backup i'd taken weeks ago.. deleted it and now have 200mb system data.
adaimespechip said:
Okay no luck - Have totally reset the device and still have 1900mb of system data showing....
EDIT: Fixed - Flashed new CWM recovery and it WAS a backup i'd taken weeks ago.. deleted it and now have 200mb system data.
Click to expand...
Click to collapse
So is it safe to assume that the space is from backups? I posted my situation here
There didn't seem to be a clear answer here so :
System data is the space taken up by files outside of the special sdcard directory.
Android is treating the emulated SD card as being 8Gb/16Gb (- the hidden partitions) and not taking into account space taken up by files outside of the special directories.
In the Settings > Storage screen you will also notice that the free space and used space do not add up, this difference is the 'system data'.
Apps from Google and those with root access commonly write to directories outside of the sdcard.
Google Music is particularly guilty of taking up space without reporting it properly, from the Settings > Apps menu you can see how much space the music application is taking up, and clear it if desired.
Backups are also likely to be eating a large amount of that space, from CWM or TWRP or another source.
These are outside of the sdcard to prevent you from accidentally deleting them.
They can normally be move/removed from within the application that made them, or with a root file manager.
You probably want to keep some working backups, I generally store them on a cloud service or external disk with only the latest on the phone.
You will not get the 'system data' down to 0 as some space is for actual system files, you should be able to get it below 500Mb easily, or just be happy once you know where the space has gone.
I hope that helped.
My Stock Rom N7 is stuck in a bootloop for the 2nd time.
Background:
This is the 2nd time my device has become stuck in a bootloop. First time detailed here: http://forum.xda-developers.com/showthread.php?t=2088035
After the first crash detailed above, I thought that I had rooted my device with a one-click method presented here: http://www.wugfresh.com/nrt/
But after using my 'supposedly rooted' N7 for a while I discovered that several of the rootcheckers available on the Play Store all reported that I didn't have root access. So now I'm not sure if it was rooted properly.
Details about the 2nd crash: A few months ago (yes, I was so disgusted that I just put the N7 back in it's box and have actively ignored it for about 2 months) I was using my N7, which at the time was my 'daily driver' for internet access / email / etc, and I suddenly started getting error messages saying that programs had crashed. One after another after another. Like an idiot I forced a power-off by holding the power button down. That's the last time it booted. FWIW, I am not into pirating or warez. I got burned about 12 years ago on my PC and swore it off. So I didn't have any software installed from rogue websites. All of the apps either came from the Play Store of the Amazon Android Store. I might have had one or two utilities that I got here on XDA but maybe not.
Where I am today: I can boot into the bootloader which is unlocked. The only way I can power the device off is to get into the bootloader and select 'Power off'... Otherwise it will just display the animated X forever.
If I try to go into recovery mode I am present with Clockwork Mod 6.0.1.0
In anycase, here is what I am asking for help with today...
I had progressed pretty far in several games (temple run 2, Real Racing 3 and a few others) and would like to try to retrieve my gaming save files before wiping the device. And yes, I know that RR3 NOW backs saves up to the cloud. My N7 crashed about a week before that feature was released... 8 > (
I know that ADB has a method to copy data off of a device via the command ADB GET PULL. I don't know what directories the data that I want is stored in and ideally would like to grab ALL the data off of the tablet except the OS (Android). I don't know who the partitions are laid out or if ADB GET PULL allows a wildcard to grab all directories? And lastly, given my impaired root state, I don't even know if I can access the partitions where the gaming save files are stored.
To be clear, I was signed into Google so all my other stuff was backed up. Just wanting my gaming save files.
Can anyone provide any tips/points or advice?
NOTE: I'm not above paying someone locally to help me if I could find such a person in the Denver area. I'm not sure if anyone will relate to this, but this has totally turned me off on mobile gaming. The first time my N7 crashed I was deep into several other games and lost all of those save files. It sucks. And I know that Google is moving in the right direction with the newly announced Play Games APIs, but each game developer has to implement it. But I yearn the transparent saving of my data like already happens with the native Google apps.
Many thanks!
Doug
boot into Clockwork mod.
connect to computer
adb pull /data
that will pull everything from your /data partition where your CWM(nandroid) backups, game data, installed apps, everything is stored
root access is only applicable to the booted OS and you automatically have root access in ADB in custom recovery....so it doesnt matter what state your OS was in when you are in recovery.
Pirateghost said:
boot into Clockwork mod.
connect to computer
adb pull /data
that will pull everything from your /data partition where your CWM(nandroid) backups, game data, installed apps, everything is stored
root access is only applicable to the booted OS and you automatically have root access in ADB in custom recovery....so it doesnt matter what state your OS was in when you are in recovery.
Click to expand...
Click to collapse
Ok, so will I then see different directories where my save data lived for the different apps (games)?
Thanks!
The ADB PULL failed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like it couldn't create a file on my PC that likely had a name that was too long for windows or had some character in the name that Windows didn't like ?...?
I don't care about Chrome anyway... need to exclude the chrome directory from the PULL...
If some files fail its normal. They are typically files in use that are locked. You should still be able to get the rest in the folder
Sent from my Galaxy Nexus
It's easier to use Titanium Backup for per-app backups if you can get into the system. Otherwise I would do a backup (I use TWRP so I can unpack the backups if needed), and it's easier to pull a single compressed file than it is multiples. (plus the backup of that type gives you an easy way to restore from recovery).
kbeezie said:
It's easier to use Titanium Backup for per-app backups if you can get into the system. Otherwise I would do a backup (I use TWRP so I can unpack the backups if needed), and it's easier to pull a single compressed file than it is multiples. (plus the backup of that type gives you an easy way to restore from recovery).
Click to expand...
Click to collapse
If by getting into the system you mean booting my N7, no I cannot. The intent of this thread as outlined in the op is to get help because the N7 was stuck in a bootloop...
Sent from my Nexus 7 using xda app-developers app
OldDogEyes said:
If by getting into the system you mean booting my N7, no I cannot. The intent of this thread as outlined in the op is to get help because the N7 was stuck in a bootloop...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
But you don't need to wipe everything if all you are going to do is wipe system, cache and dalvik-cache (and only those three) and re flash the same rom over it without adding anything like custom kernel. The /data will be intact and if it's the same rom it'll just boot up like normally.
Sent from my Nexus 4 using XDA Premium HD app
---------- Post added at 12:25 PM ---------- Previous post was at 12:24 PM ----------
kbeezie said:
But you don't need to wipe everything if all you are going to do is wipe system, cache and dalvik-cache (and only those three) and re flash the same rom over it without adding anything like custom kernel. The /data will be intact and if it's the same rom it'll just boot up like normally.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Ps: if stock I personally would just use fastboot to flash the stock system.img which won't wipe data either.
Sent from my Nexus 4 using XDA Premium HD app
---------- Post added at 12:28 PM ---------- Previous post was at 12:25 PM ----------
Also use a custom recovery next time, it helps a bit and twrp can even install superSu and su for you if it detects an unrooted system before you reboot out of recovery. Twrp can also be easily flashed from fastboot.
Sent from my Nexus 4 using XDA Premium HD app
Screenshots: https://m.imgur.com/a/MKU2J
I had 13/16GB available on my Nexus 5. And now I have 18/32GB available on my 6P. What kind of bull**** is this? My storage doubles and I only get 5GB more?
What is system data? Why can't I see it (it shows up nowhere, I just have less space available without actually seeing what's using up that space) and how do I delete it?
Corndude said:
Screenshots: https://m.imgur.com/a/MKU2J
I had 13/16GB available on my Nexus 5. And now I have 18/32GB available on my 6P. What kind of bull**** is this? My storage doubles and I only get 5GB more?
What is system data? Why can't I see it (it shows up nowhere, I just have less space available without actually seeing what's using up that space) and how do I delete it?
Click to expand...
Click to collapse
Have you got es file explorer
I have 25/32GB.
Corndude said:
Screenshots: https://m.imgur.com/a/MKU2J
I had 13/16GB available on my Nexus 5. And now I have 18/32GB available on my 6P. What kind of bull**** is this? My storage doubles and I only get 5GB more?
What is system data? Why can't I see it (it shows up nowhere, I just have less space available without actually seeing what's using up that space) and how do I delete it?
Click to expand...
Click to collapse
Edit: it was a ****up, twrp saved backups to a weird folger, they were the cause.
-X5- said:
I have 25/32GB.
Click to expand...
Click to collapse
same here. 25/32
Corndude said:
Edit: it was a ****up, twrp saved backups to a weird folger, they were the cause.
Click to expand...
Click to collapse
Can you share which folder TWRP was backing up to? I think this happened to me as well and I can't seem to find the folder...
I'm having a similar problem, my 128gb Nexus is showing 22/24gb used. Any idea where that extra 100gb went?!?
Demonyc said:
I'm having a similar problem, my 128gb Nexus is showing 22/24gb used. Any idea where that extra 100gb went?!?
Click to expand...
Click to collapse
Did you flash the userdata.img with fastboot at some point?
Ummmmmm why does it say of 111? Anyone else losing 17GB!? Wtf.
The" other"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is my music but jee
Sent from my Nexus 6P using Tapatalk
Heisenberg said:
Did you flash the userdata.img with fastboot at some point?
Click to expand...
Click to collapse
I think I did, when I was setting up for root at the very beginning. I'm assuming that may be my problem..? :crying: What do you suggest?
Demonyc said:
I think I did, when I was setting up for root at the very beginning. I'm assuming that may be my problem..? :crying: What do you suggest?
Click to expand...
Click to collapse
That's definitely your problem. Flashing the userdata.img allocates 32GB of storage, regardless of the original capacity of the device. As you can see this is problematic for the 64GB and 128GB models. You need to back up everything from your internal storage to your PC, and make backups of your apps with Titanium Backup and transfer that too. Boot into the bootloader, connect your phone, and issue this fastboot command:
Code:
fastboot format userdata
This is going to wipe all user data from your phone; apps, settings, photos, music, everything will be gone. So when you boot up you'll have to set the phone up again, and transfer your photos, music, and Titanium app backup back to your phone. Unfortunately this is the only way to get the right storage capacity back again. Out of interest, where did you read that you need to flash the userdata.img?
PS. You might find my guide helpful in future.
Heisenberg said:
That's definitely your problem...
Click to expand...
Click to collapse
Thank you SOOO much, Heisenberg! I actually was following your guide, but pretty sure I misread something there the first time, because my result was a softbrick at first. Sorry to take your time, and thank you for your kind (quick!) and clear response to my noob mistake. (Thanks also added)
It's people like you who make xda what it is. :highfive:
Demonyc said:
Thank you SOOO much, Heisenberg! I actually was following your guide, but pretty sure I misread something there the first time, because my result was a softbrick at first. Sorry to take your time, and thank you for your kind (quick!) and clear response to my noob mistake. (Thanks also added)
It's people like you who make xda what it is. :highfive:
Click to expand...
Click to collapse
No problems, I'm glad to help. If you have any questions in future don't be afraid to ask in my thread.
ccb1208 said:
Can you share which folder TWRP was backing up to? I think this happened to me as well and I can't seem to find the folder...
Click to expand...
Click to collapse
Sorry I only saw this now. It was in /data somewhere. Not in data/media, but in data/TWRP I believe. Definitely check /data and it's subdirs.
Corndude said:
Sorry I only saw this now. It was in /data somewhere. Not in data/media, but in data/TWRP I believe. Definitely check /data and it's subdirs.
Click to expand...
Click to collapse
Why would it be in data/media?? Data/TWRP makes perfect sense to me! All apps make folders in de data/appname path...
J_Dutch said:
Why would it be in data/media?? Data/TWRP makes perfect sense to me! All apps make folders in de data/appname path...
Click to expand...
Click to collapse
Everything is in /data/media. The usual directory for twrp backups is /data/media/twrp/whatever.
Corndude said:
Everything is in /data/media. The usual directory for twrp backups is /data/media/twrp/whatever.
Click to expand...
Click to collapse
Nope, not true.
/Sdcard/twrp or
/storage/emulated/0/twrp
Tot should use ES file explorer for example, TWRP folder is just were all the other app folders are.
I know this an old thread but I"m having storage issues as well. I'm rooted and running Pure Nexus. My phone is an 64GB version and ES File says I'm using 89% of it. I downloaded all my pics and videos and music only accounts for 5GB.
@Heisenberg, in preperation to format user data, there a folder showing called estrongs and its 32GB!! If i simply copy all my folders over then restore them all, won't it just eat up all my storage again?
I've had rooted and rom'd phones since the HTC Incredible and I've never come close to hitting my storage limit. I did follow your guide to root the 6P and I skipped the decryption step because as the guide says, if you're using a version of TWRP newer than 2.8.7.1 you don't have to, so I didn't.
Heisenberg said:
That's definitely your problem. Flashing the userdata.img allocates 32GB of storage, regardless of the original capacity of the device. As you can see this is problematic for the 64GB and 128GB models. You need to back up everything from your internal storage to your PC, and make backups of your apps with Titanium Backup and transfer that too. Boot into the bootloader, connect your phone, and issue this fastboot command:
Code:
fastboot format userdata
This is going to wipe all user data from your phone; apps, settings, photos, music, everything will be gone. So when you boot up you'll have to set the phone up again, and transfer your photos, music, and Titanium app backup back to your phone. Unfortunately this is the only way to get the right storage capacity back again. Out of interest, where did you read that you need to flash the userdata.img?
PS. You might find my guide helpful in future.
Click to expand...
Click to collapse
Heisenberg said:
No problems, I'm glad to help. If you have any questions in future don't be afraid to ask in my thread.
Click to expand...
Click to collapse
Formating data in TWRP should do the same thing, right?
warri said:
Formating data in TWRP should do the same thing, right?
Click to expand...
Click to collapse
Yes.
My device used to show 128gb of internal storage - with 111gb usable. But after I flashed to Android N Preview 4 with a modified boot.IMG for a decrypted storage so I could have TWRP working. It showed I only had 24.1gb usable. I already tried a factory reset, and flashing back to 6.0.1 (mtc19v), PureNexus, and other ROMs. I'm wondering how I can fix this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit/////////
My issue has been fixed by formatting userdata via fast boot and I'm now decrypted on Android N beta preview 4 rooted with working twrp!
Special thanks to
@SlimSnoopOS
@Sass86oh
For helping me fix it :angel:
TnT_ said:
My device used to show 128gb of internal storage - with 111gb usable. But after I flashed to Android N Preview 4 with a modified boot.IMG for a decrypted storage so I could have TWRP working. It showed I only had 24.1gb usable. I already tried a factory reset, and flashing back to 6.0.1 (mtc19v), PureNexus, and other ROMs. I'm wondering how I can fix this?
Click to expand...
Click to collapse
Looks like you flashed the userdata.img. Type this in fastboot: fastboot format userdata
This will wipe everything from your phone. It will resize back to 128 GB.
Sent from my Nexus 5X using Tapatalk
Trying this right now, will edit this with results.
// edit 1
Windows update blocked me, hopefully its not windows 10
You most likely flashed the "Userdata.img" thats included in stock Android firmaware archives. Unless you have a 32GB device, the userdata IMG does not account for storage over 32GB and if you flash it on the 64 or 128GB version, it will partiton the internal storage and only allow for you to access 32GB. I made that same mistake myself when I first got my phone. The userdata img is meant to zap the internal storage and delete all userdata on the device. Instead, just use the command "fastboot format userdata"... It will perform the same function without any loss to your overall storage space. From now on, when you flash the stock firmware make sure you steer clear of that file and instead use the command. MAKE SURE YOU BACK UP ALL OF YOUR PERSONAL FILES FIRST!! That command wipes every partition on the device!! So make sure you've saved whatever you cant afford to lose before using it. Formatting the user data is not always required when flashing roms on your device. Actually its hardly ever a requirement. Usually its used when you want to bring your phone back to the factory settings. The built in SD partition on most Android devices is isolated space. This allows you keep all of your importatnt files safe in the event that your system partition becomes corrourpt forcing you to reflash your old rom or a new one. If you need any help at all please feel free to send me a message. Hope this helps!
TnT_ said:
Trying this right now, will edit this with results.
// edit 1
Windows update blocked me, hopefully its not windows 10
Click to expand...
Click to collapse
You do know that will wipe the phone but will work I've had that lol
jaythenut said:
You do know that will wipe the phone but will work I've had that lol
Click to expand...
Click to collapse
Yes, I was and am aware.
TnT_ said:
Yes, I was and am aware.
Click to expand...
Click to collapse
Were you able to restore your storage?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Were you able to restore your storage?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I backed up all my files to my PC before I did the process in the first place - 36.8gb. Using BitTorrent sync. I was able to restore using that, therefore there was no loss.
I'm on an s5 neo, rooted but using the same software it came with.
I decided to try a factory reset, as I had done a few things I can't undo, like removing mtp application, with a root app remover whose restore function doesn't work on this device.
I was also thinking, that instead of personalizing everything, and downloading everything, and then debloating, I thought I'd start fresh and then debloat first.
Thank *god*I had gotten brave enough to download and install twrp and make a backup, that back up is where I am coming to you from now.
I used the twrp recommended wipe for the reset, not custom wipe. Worked fine. Powered back on. All looked well until I came across a screen that said "just a sec..." For an extremely long time, like 10 minutes...
Why wouldn't it fully turn on, any ideas? As of now I can't factory reset ever again.... :/ and I'd like to be able to.
I hasn't disabled anything crazy and could reboot normally before I tried the wipe. I just don't get what went wrong?
Any help is greatly appreciated.
I cant even start off with a new rom I don't think, they're all made for the 903m or 903f versions of this phone, and I'm on the international 903w. I'm guessing some thing significant is different or else it would just be called the 903.
Sent from my SM-G903W using XDA-Developers mobile app
what did you wipe in the custom wipe?
also this http://forum.xda-developers.com/galaxy-s5/general/rom-somewhat-incomplete-edition-v0-1-t3295464
I want to say it wiped data cache and dalvik cache
Sent from my SM-G903W using XDA-Developers mobile app
Pawprints1986 said:
I want to say it wiped data cache and dalvik cache
Click to expand...
Click to collapse
Well, with a bootloop you can go to recovery and recipe, then wipe data then go to advanced options in twrp and delete the Android folder in both internal and external and that should fix the issue
Recipe? I should proof read this stuff before I post it. It should have said reset, not recipe
Like, as in deleting the "system" folder, should I have wiped that too?
Or would that totally erase this current android version? And I'd be even more stuck?
Sent from my SM-G903W using XDA-Developers mobile app
Pawprints1986 said:
Like, as in deleting the "system" folder, should I have wiped that too?
Or would that totally erase this current android version? And I'd be even more stuck?
Click to expand...
Click to collapse
No, go to advanced options, file manager, then to either storage, touch the Android folder, hit the check mark in the lower right, select delete, swipe to confirm. Do this with both storages. It's not the system folder and doesn't contain anything that isn't rebuilt upon boot. But it does contain stuff from your previous install that is known to cause bootloops when going from an Android version to another. Nothing to worry about when you delete those folders. It's been the source of tons of bootloops for me
So, the android folder, in my case, I think I've only got the one internal storage path. I'd have to double check but I'm pretty sure. I have technically for some reason a bunch of storages called "USB drive". But I think they're all empty. And I think sd card and emulated lead to the same place. Its a weird setup lol
I just took a screen shot of it, I'll add it in here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G903W using XDA-Developers mobile app
Pawprints1986 said:
So, the android folder, in my case, I think I've only got the one internal storage path. I'd have to double check but I'm pretty sure. I have technically for some reason a bunch of storages called "USB drive". But I think they're all empty. And I think sd card and emulated lead to the same place. Its a weird setup lol
I just took a screen shot of it, I'll add it in here
Click to expand...
Click to collapse
Don't do it from within the system. Do it from within twrp
Here, I made a little video. I'm a 100% amateur videographer, so go easy on me lol