Last night i did the deencrypt mod, cf auto root, and flashed twrp. I have only 23 gb available(at least 2gb missing) and Im confused out the box I swear i had near 26. I know that twrp and root dont take up that much space. Is the userdata.img taking up that much storage? I already reset to factory to see if that would clear anything. Is anyone else having this issue?
Can't offer any suggestions, but wanted to confirm that even after removing encryption I still have 26GB available.
After resetting back to factory default, does it still show up as only 23GB?
nerdgenius said:
Last night i did the deencrypt mod, cf auto root, and flashed twrp. I have only 23 gb available(at least 2gb missing) and Im confused out the box I swear i had near 26. I know that twrp and root dont take up that much space. Is the userdata.img taking up that much storage? I already reset to factory to see if that would clear anything. Is anyone else having this issue?
Click to expand...
Click to collapse
if you bought your phone from at&t, its probably the crap in the oem partition
It is a at&t phone but I deleted all the crap out the oem partition. Even the at&t still has 25 gigs with apps installed.
Did you make a backup prior to dencrypting? Might explain it...?
No I haven't. I will just reflash the stock image and try again.
This happened to me yesterday. I have the 64gb version and after trying to decrypt I was down to 23gb. I flashed the firmware, and then relocked the bootloader, and my space was back. Fair warning after relocking your boot up time will take forever.
This happened to me yesterday night too. I have the N6 64gb and after:
- unlock bootloader
- decrypt
- cf root
I was down to 23gb. What I should do now?? I don't care about data but what I have to do, will I lose root acces and decrytion??
Any Tutorial? I'm not that smart ;]
Happened on the Nexus 5 sometimes. Here's an article of how to fix that phone. Maybe the steps are similar.
http://www.droidviews.com/your-32gb-nexus-5-now-shows-only-16gb-here-is-how-to-fix-it/
Ok but do you think I can use a Tool Kit 1.9.9 ?
porn does take up a lot of space even if you have it in a zip folder labeled "Disney movies"
dligon said:
porn does take up a lot of space even if you have it in a zip folder labeled "Disney movies"
Click to expand...
Click to collapse
u know from experience..
I didn't decrypt my phone, but after flashing a stock image I did only have about 23 gb of space showing on my 64 gb phone. I had to do a factory reset to restore the missing space. Note this is a reset from the phone's settings menu (Settings > Backup & Reset > Factory data reset). It takes a while, and obviously deletes all the data on the phone.
Yep, Factory reset from settings - This way solve my problem, :good:
Do a factory reset. That will solve your problem.
My total space is 25.98gb on the 32gb model my phone is decrypted and rooted. I got it from US Cellular. No problems here besides apps like Facebook taking up several hindered megabytes....
Nexus 6
Just use fast boot to format user cache and see if that works. This happened to me 3-4 tens gene restoring my phone and its an easy fix. There is no need to relock your BL. There is also another OP I made a whole ago when this happened it me which could have answered your question much faster.
Related
My 64GB Nexus is now saying it has 23gb of total storage and 21gb available. I had to reflash the stock ROM after a failed twrp flash. Is there anyway to fix this? I have already tried reflashing and wiping the phone 2 times but the storage decreases each time.
Use a factory image and start over.
ericsignals said:
Use a factory image and start over.
Click to expand...
Click to collapse
I've already done that twice
Pilz said:
I've already done that twice
Click to expand...
Click to collapse
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.
jhax01 said:
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.
Click to expand...
Click to collapse
I can try to redownload the SDK, but my question is what does the SDK have to do with losing space on my phone?
I don't pretend to know what the cause is behind it but when the 5.0 factory images were released, people who flashed it with an older version of fastboot were losing storage on the Nexus 5.
Sent from my Nexus 5 using Tapatalk
I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.
Pilz said:
I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.
Click to expand...
Click to collapse
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?
the.emilio said:
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?
Click to expand...
Click to collapse
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.
Pilz said:
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.
Click to expand...
Click to collapse
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.
the.emilio said:
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.
Click to expand...
Click to collapse
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.
Pilz said:
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.
Click to expand...
Click to collapse
Figured. I will keep trying. Thanks!
---------- Post added at 11:56 PM ---------- Previous post was at 11:08 PM ----------
After about 10 attempts it turns out all i had to do was fastboot format cache then fastboot format userdata. Reboot and boom restored to normal. LMAO! Wasted 4 hours tonight just for that. Live and learn!
Just do a factory reset in recovery WITHOUT reflashing and the problem is taken care of.
Seems a like a bug in the factory images that can cause of wrong partition sizes.
Worked on my N9 (which I already sent back to Google due to excessive lightbleed lol)
I had the same issue after trying to root the phone showed 23 GB.
I was able to get back to 53 GB after wipine cache and formatting user data, but that still seems like I'm missing something . I did not check how much storage was available before I started.
Can any one tell me what the storage numbers should be on like on a stock device with nothing installed please?
I remember hearing about this same issue with the Nexus 5. Don't recall the cause though. Sorry folks I know this post is useless I'm just excited to be getting my Nexus 6 so I perusing the forums.
Hey everyone,
I'm having a storage issue with my Nexus 6. My available space is showing up as 32GB even though I have 64GB of real space. When I was on full stock, it showed up correctly, but after I flashed the no-encrypt boot.img in Android Development, Its showing up as 32 GB instead of 64.
Help appreciated!
You're going to have to do a factory reset from the backup & reset menu. Back up anything you want to keep since it will wipe EVERYTHING on your device. That's the only thing that worked for me when I had the issue with my N5 and that's what is suggested in the toolkit
Hero_Guy said:
You're going to have to do a factory reset from the backup & reset menu. Back up anything you want to keep since it will wipe EVERYTHING on your device. That's the only thing that worked for me when I had the issue with my N5 and that's what is suggested in the toolkit
Click to expand...
Click to collapse
Quick question, I have the exact same thing happening with my Nexus 6P - will this same fix work for me?
Hero_Guy said:
You're going to have to do a factory reset from the backup & reset menu. Back up anything you want to keep since it will wipe EVERYTHING on your device. That's the only thing that worked for me when I had the issue with my N5 and that's what is suggested in the toolkit
Click to expand...
Click to collapse
Yeah well, that is why toolkits are worse then paying attention and learning things
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
No need to factory reset, you can fix through TWRP
JNCHD said:
Hey everyone,
I'm having a storage issue with my Nexus 6. My available space is showing up as 32GB even though I have 64GB of real space. When I was on full stock, it showed up correctly, but after I flashed the no-encrypt boot.img in Android Development, Its showing up as 32 GB instead of 64.
Help appreciated!
Click to expand...
Click to collapse
Did you resolve this using the TWRP method? I can't get it to work and I'm at my wits end.
mrdannyaitch said:
Did you resolve this using the TWRP method? I can't get it to work and I'm at my wits end.
Click to expand...
Click to collapse
What did you do and what part didn't work?
quick glance at TWRP makes me think all you need to do is go Wipe>advanced wipe>select data>repair or change file system>RESIZE. it seems like this should do it but having a 32gb n6 I can't test that. doesn't wipe anything so it could be worth a shot
Apologies, am typing from my phone and can't worm out how to link to another thread but there's also a thread where someone else has a 64gb showing 25gb which there are more details on.
Essentially I've flashed the December factory image using fastboot, using various methods:
All stages per the Q&A sticky, including flashing userdata and then using the TWRP method. Also all stages but replacing fastboot flash userdata with fastboot format userdata as I'm aware that the userdata.IMG is not intended for the 64gb.
Trying the TWRP method to resize always ends up with the same result, the red message saying my phone is unstable (or similar, I've seen other threads with the correct message, again apologies but am on my phone).
I've tried locking and relocking OEM lock to see if that helps or not, but nothing does.
My initial request for help on the other thread is because I got a replacement phone under insurance and didn't check if it was 32gb or 64gb and then noticed I only have 25, with the bootloader saying its a 32gb phone. I've asked but have had no answer yet whether the bootloader would change, is would it always actually know its a 64gb even if internal memory only shows it as a 32gb?
Believe it or not, I called Motorola and even with the IMEI and serial number, they could not tell me what my phone was!
Hi everbody, I have a rooted phone which I wanted to unroot to be able to install the 5.1.1 update. But when I unrooted the phone without even doing a factory reset or cleaning the cache or all of those wiping the phone procedures, the phone got totally wiped and also the memory got completely wiped with all folders and whatever gone. Pictures are backed up to Google Drive and numbers are in Google Contacts but there are some folders and backed up apps that I wanted to have.
Is there any way this can be restored? I'm guessing there is not, but I still wanted to put the question out there if anybody knows a way?
Sia_ said:
Hi everbody, I have a rooted phone which I wanted to unroot to be able to install the 5.1.1 update. But when I unrooted the phone without even doing a factory reset or cleaning the cache or all of those wiping the phone procedures, the phone got totally wiped and also the memory got completely wiped with all folders and whatever gone. Pictures are backed up to Google Drive and numbers are in Google Contacts but there are some folders and backed up apps that I wanted to have.
Is there any way this can be restored? I'm guessing there is not, but I still wanted to put the question out there if anybody knows a way?
Click to expand...
Click to collapse
Always back up before starting. They are gone. Lesson learned.
Sia_ said:
Hi everbody, I have a rooted phone which I wanted to unroot to be able to install the 5.1.1 update. But when I unrooted the phone without even doing a factory reset or cleaning the cache or all of those wiping the phone procedures, the phone got totally wiped and also the memory got completely wiped with all folders and whatever gone. Pictures are backed up to Google Drive and numbers are in Google Contacts but there are some folders and backed up apps that I wanted to have.
Is there any way this can be restored? I'm guessing there is not, but I still wanted to put the question out there if anybody knows a way?
Click to expand...
Click to collapse
1) Not sure why your device got wiped...
2) Only way to restore is if you had a backup stored off line...
3) There is no reason to "unroot" if you intend to fastboot flash the factory image.
4) Using the "unroot" feature is NOT sufficient if you want to flash the OTA update. It still leaves a few modified files around, and the updater script will not install the OTA. You will need to fastboot flash the factory system.img. If you are going to do that, then just fastboot flash 5.1.1 and be done with it.
cam30era said:
1) Not sure why your device got wiped...
2) Only way to restore is if you had a backup stored off line...
3) There is no reason to "unroot" if you intend to fastboot flash the factory image.
4) Using the "unroot" feature is NOT sufficient if you want to flash the OTA update. It still leaves a few modified files around, and the updated will not install the OTA. You will need to fastboot flash the factory system.img. If you are going to do that, then just fastboot flash 5.1.1 and be done with it.
Click to expand...
Click to collapse
it will wipe your storage when you fastboot lock your bootloader
simms22 said:
it will wipe your storage when you fastboot lock your bootloader
Click to expand...
Click to collapse
Right. OP didn't say he relocked (and hopefully he didn't).
cam30era said:
Right. OP didn't say he relocked (and hopefully he didn't).
Click to expand...
Click to collapse
lol, i assumed he did, as thats what i would consider part od "unrooting". if he did, then thats why its wiped. if he didnt, then im clueless :angel:
simms22 said:
lol, i assumed he did, as thats what i would consider part od "unrooting". if he did, then thats why its wiped. if he didnt, then im clueless :angel:
Click to expand...
Click to collapse
We are definitely in the same camp on that.
simms22 said:
lol, i assumed he did, as thats what i would consider part od "unrooting". if he did, then thats why its wiped. if he didnt, then im clueless :angel:
Click to expand...
Click to collapse
Op what "method" or steps did you take to "un-root"?
Manually, or some toolkit? Did you re-lock your bootloader, or check or forget to un-check some sort of reset my phone to factory settings setting?
Help guys....
I rooted my T-Mobile HTC m7 the other day and soft bricked my phone, followed xda forum posts to recover and flash a new rom, but now my storage nomally 32gb shows at least 8 gbs used already, and on my pc shows that i only have 25gb! Definately noob mistake, somewhere in installing xposed and getting the soft brick, I still cant figure out how to rid that darn partition! Anyways thanks.
trujillogabe said:
Help guys....
I rooted my T-Mobile HTC m7 the other day and soft bricked my phone, followed xda forum posts to recover and flash a new rom, but now my storage nomally 32gb shows at least 8 gbs used already, and on my pc shows that i only have 25gb! Definately noob mistake, somewhere in installing xposed and getting the soft brick, I still cant figure out how to rid that darn partition! Anyways thanks.
Click to expand...
Click to collapse
The /system partition (the OS) and other firmware partitions (i.e /hboot, /boot, /recovery, /radio, /pg1(2)fs, /misc, /modem, etc etc... ) are taking about 8gb of space on your 32Gb emmc which will give the /data partition (the memory left for the user) about 25gb of space.
If you find a way to get more than 25gb, you'll be deleting some crucial partitions and your phone will not boot, so its not really advised
For your softbirck problem, did you tried to flash the xposed-uninstaller zip to disable Xposed? If your problem was caused by Xposed, disabling it with this zip should fix your problem, first thing you want to try before flashing something else. In the worst case you'll have to reflash your rom (stock or custom).
http://www.htc.com/us/smartphones/htc-one-m7/#/
see note 1
Just noticed something odd:
My S10+ reports only 32gb of internal storage capacity.
When I plug it into my PC it shows even less, something like 17,2gb of total available space.
The external sd card seems unaffected.
I thought there were only 128/512gb variants?
I bought it used and now I think this might've been a scam.
It's a legit S10+ alright.
Is there some strange partitioning I'm not aware of?
check this out, he shows a fake s10+: https://www.youtube.com/watch?v=J11I4u2X_1o
almaalma74 said:
check this out, he shows a fake s10+: https://www.youtube.com/watch?v=J11I4u2X_1o
Click to expand...
Click to collapse
Now I'm relieved that mine doesn't look anything close to the fake one haha.
Mine even has the pre installed screen protector still on.
hoeni said:
Now I'm relieved that mine doesn't look anything close to the fake one haha.
Mine even has the pre installed screen protector still on.
Click to expand...
Click to collapse
There have been some people over in the Samsung community saying their S10+ phones are reporting incorrect internal memory. I don't have an answer but if your phone is legit then maybe it's just a glitch that will be fixed in a future update. There's always the dreaded and sometimes useless clearing internal cache then system reset.
I'm currently trying to get TWRP and magisk running and I've been flashing with odin non stop.
After another flash the memory seems to have been corrected, showing all 128gb of available space.
I'm relieved to no end haha.
Similar thing happened to me after I rooted my S10 plus.
There are two resons in my case:
1- I did not install the latest usb driver.
2- I didn't wipe after installing the multidisabler file.
So just follow the procedures exactly and there will be no troubles.
In my case, my phone is 128GB and after I rooted it, it was reduced to 32GB. I was shocked and in doubt.
I had to check the phone receipt to make sure it is 128 and not 32.
Did u recently just flashed your phone with odin?
Player04 said:
Did u recently just flashed your phone with odin?
Click to expand...
Click to collapse
99% sure that he did, and when he did, im also betting that he didnt perform a factory reset after doing so. Common problem with Samsung devices over the years. When you flash in Odin, its always a good idea to factory reset afterwards which will allow the firmware to look for the actual size of internal storage. Its happened to me on both of my S3's, my S4, all 4 of the S5's ive owned/worked on, S7 flat and Edge etc etc. Never happened on my S9 yet, but ive only flashed the U1 firmware once on it and it was fine. Ive never messed much with S6s or S8s, but im 99% sure its the same deal there too
Youdoofus said:
99% sure that he did, and when he did, im also betting that he didnt perform a factory reset after doing so. Common problem with Samsung devices over the years. When you flash in Odin, its always a good idea to factory reset afterwards which will allow the firmware to look for the actual size of internal storage. Its happened to me on both of my S3's, my S4, all 4 of the S5's ive owned/worked on, S7 flat and Edge etc etc. Never happened on my S9 yet, but ive only flashed the U1 firmware once on it and it was fine. Ive never messed much with S6s or S8s, but im 99% sure its the same deal there too
Click to expand...
Click to collapse
I flashed BL, AP, CP and CSC with odin.
Went back to twrp and installed the multidisabler.
when do i have to wipe?
directly after installing the multidisabler? just a factory reset or wiping everything?
after that installing the ROM/MOD whatever...?
Something similar happened to me recently. After restoring the backup, I suddenly saw that I only had 32GB. I did a TWRP -dalvik cleanup, cache and date but it didn't help. Only cleaning the format data (not only wipe, choose specifically "Format data" and write "yes". Only then did I get back 128GB.