Database Develop

Missing Storage Space?

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!

Missing storage on 32gb Nexus 6

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.

[Q] 64gb version N6 showing only 23gb total space?

Just manually updated to 5.0.1 and my phone is showing 23gb total space. I purchased the 64gb version. Unfortunately I never thought to check this earlier, so I guess it's possible they sent me the wrong version. Box showed 64gb as well.
I feel like I read something about a user's space showing the incorrect amount after doing something. Is that possible?

I just noticed the same thing this morning! I'm running a custom rom and Kernel but that shouldn't make a difference. Please let me know if you find anything out

boynamedstacy said:
I just noticed the same thing this morning! I'm running a custom rom and Kernel but that shouldn't make a difference. Please let me know if you find anything out
Click to expand...
Click to collapse
I did a factory reset and data wipe and I'm back to normal.

Can't turn off wifi toggle

has any one been having any trouble with their wifi on their nexus 6, randomly the wifi toggle will stop working the toggle will be off and it still says "Turning Wi-Fi on..." i've booted into recovery and cleared cache and rebooted the phone and it worked the first time and it's been acting up again and this time clearing the cache isn't working does anyone else have any ideas without doing a factory reset.

humpty123 said:
has any one been having any trouble with their wifi on their nexus 6, randomly the wifi toggle will stop working the toggle will be off and it still says "Turning Wi-Fi on..." i've booted into recovery and cleared cache and rebooted the phone and it worked the first time and it's been acting up again and this time clearing the cache isn't working does anyone else have any ideas without doing a factory reset.
Click to expand...
Click to collapse
maybe try just flashing the system img, then wipe cache's again before booting. if that doesnt work, its may be time for the dreaded fdr.

I've never been into flashing system img & fdr? It's just sad because I had the same issue before also losing signal with my device. Til I got a replacement and the replacement device is starting to act up also.
Sent from my Nexus 6 using XDA

bweN diorD said:
maybe try just flashing the system img, then wipe cache's again before booting. if that doesnt work, its may be time for the dreaded fdr.
Click to expand...
Click to collapse
okay so put the phone in recovery and did cache wipe and reset it from recovery also and got everything set up again and still it shows Wi-Fi toggled off and saying turning on Wi-Fi im not sure what todo at this point.
https://goo.gl/photos/bdHB8Nw2tbH71LMj6

humpty123 said:
okay so put the phone in recovery and did cache wipe and reset it from recovery also and got everything set up again and still it shows Wi-Fi toggled off and saying turning on Wi-Fi im not sure what todo at this point.
Click to expand...
Click to collapse
my only other suggestion would be to re-flash. you could try just the system partition, but if it were me i would just go all in for full clean flash.
im sure Simms will get on me for saying so, but you can just grab wugs toolkit and be done in 20min or so.

bweN diorD said:
my only other suggestion would be to re-flash. you could try just the system partition, but if it were me i would just go all in for full clean flash.
im sure Simms will get on me for saying so, but you can just grab wugs toolkit and be done in 20min or so.
Click to expand...
Click to collapse
I've never flashed before i know from what i hear its really easy for Nexus devices. but i'm just curious what would of caused this like from my first N6 since December and it acts up now in Sept and having the replacement N6 acting up the same way.

Is it rooted with mods or completely stock? If stock, try deleting the saved wireless networks..

danarama said:
Is it rooted with mods or completely stock? If stock, try deleting the saved wireless networks..
Click to expand...
Click to collapse
100% stock I can't get access to any saved networks at all
https://goo.gl/photos/34veZPQvW3pLiB5YA

humpty123 said:
I've never flashed before i know from what i hear its really easy for Nexus devices. but i'm just curious what would of caused this like from my first N6 since December and it acts up now in Sept and having the replacement N6 acting up the same way.
Click to expand...
Click to collapse
these random issues usually come from a corrupt file, either by an update or some other means. its hard to impossible to pinpoint the cause usually.
if you never flashed before, its best to read up on it a bit first. wugs walks you through the steps, from downloading the files, and drivers, to the flashing. its not foolproof, but if you follow the lead of the script, its not hard to figure out.

bweN diorD said:
these random issues usually come from a corrupt file, either by an update or some other means. its hard to impossible to pinpoint the cause usually.
if you never flashed before, its best to read up on it a bit first. wugs walks you through the steps, from downloading the files, and drivers, to the flashing. its not foolproof, but if you follow the lead of the script, its not hard to figure out.
Click to expand...
Click to collapse
well i have before but that was so long ago and that was for my MyTouch and HTC Sensation but that was years ago. Now I know things are easier but I've never really been into flashing and the only reason I did back then was for updates and different version of Sense UI but since I've been using Nexus Devices I didn't have a need or desire to actually flash. Pretty much I'm a NOOB! :laugh:
but I don't see why wouldn't a factory reset fix it. even if it was temp.

humpty123 said:
well i have before but that was so long ago and that was for my MyTouch and HTC Sensation but that was years ago. Now I know things are easier but I've never really been into flashing and the only reason I did back then was for updates and different version of Sense UI but since I've been using Nexus Devices I didn't have a need or desire to actually flash. Pretty much I'm a NOOB! :laugh:
but I don't see why wouldn't a factory reset fix it. even if it was temp.
Click to expand...
Click to collapse
a factory reset only deletes data, it does not restore any of the file system to its original state.

bweN diorD said:
a factory reset only deletes data, it does not restore any of the file system to its original state.
Click to expand...
Click to collapse
oh... so when I called Motorola they told me to wipe cache how did that help the first time ?

humpty123 said:
oh... so when I called Motorola they told me to wipe cache how did that help the first time ?
Click to expand...
Click to collapse
clearing the cache is always a good idea, i think i suggested that earlier.
i dont know how to explain well what cache is exactly, its not part of the file system, its more like temp data storage i believe.

bweN diorD said:
clearing the cache is always a good idea, i think i suggested that earlier.
i dont know how to explain well what cache is exactly, its not part of the file system, its more like temp data storage i believe.
Click to expand...
Click to collapse
yeah i tried that a few times today and it did nothing... i'm about to give up since i don't have a PC anymore i use a Chromebook

humpty123 said:
yeah i tried that a few times today and it did nothing... i'm about to give up since i don't have a PC anymore i use a Chromebook
Click to expand...
Click to collapse
def of cache from google
"In cell phones and networks, a cache usually refers to a memory storage area in the phone or network that stores copies of information that is likely to be needed in the near future, so it can be accessed faster."
i dont know how to flash with a chrome book, if possible. sorry

bweN diorD said:
def of cache from google
"In cell phones and networks, a cache usually refers to a memory storage area in the phone or network that stores copies of information that is likely to be needed in the near future, so it can be accessed faster."
i dont know how to flash with a chrome book, if possible. sorry
Click to expand...
Click to collapse
all i know it happened a day after i got the last update from T-Mobile. i should them back and tell them i'm having the same issues with my phone have them replace it for me again.

humpty123 said:
all i know it happened a day after i got the last update from T-Mobile. i should them back and tell them i'm having the same issues with my phone have them replace it for me again.
Click to expand...
Click to collapse
thats pretty consistent with what i said earlier. these type of issues frequently arise after updates. files dont update exactly right and something gets corrupted.

bweN diorD said:
thats pretty consistent with what i said earlier. these type of issues frequently arise after updates. files dont update exactly right and something gets corrupted.
Click to expand...
Click to collapse
i decided to call T-Moblie and talk to them they told me to take it to a store and get it dianogsed and they will call to get it replaced since it is the 64GB and stores don't have it.... I just want the Wi-Fi to work even though i don't use it all the time but still.

FRB wont let me boot!

First of all, I *cannot* lose my data. But for obvious privacy and security reasons I *don't* keep Google Sync enabled.
I have a rooted, but stock 5.1.1 T-Mobile Note4. Custom recovery (honestly don't recall if it's TWRP or CWM, I don't use it often). At one point I turned the phone off (actual *off*, not screen lock), but now when I try to turn it on, it refuses to allow it and says "Custom binary blocked by FRP". Same problem when I try to boot into recovery, too. I can only boot into download mode, but attempting to flash the stock 5.1.1 firmware or the stock recovery just simply fails. It just won't allow it.
If I boot into download mode, connect it to my computer via USB, and do "adb devices", no devices show up.
Need help!!!! I need my phone and my data!!!!

jfviwerbnv said:
First of all, I *cannot* lose my data. But for obvious privacy and security reasons I *don't* keep Google Sync enabled.
I have a rooted, but stock 5.1.1 T-Mobile Note4. Custom recovery (honestly don't recall if it's TWRP or CWM, I don't use it often). At one point I turned the phone off (actual *off*, not screen lock), but now when I try to turn it on, it refuses to allow it and says "Custom binary blocked by FRP". Same problem when I try to boot into recovery, too. I can only boot into download mode, but attempting to flash the stock 5.1.1 firmware or the stock recovery just simply fails. It just won't allow it.
If I boot into download mode, connect it to my computer via USB, and do "adb devices", no devices show up.
Need help!!!! I need my phone and my data!!!!
Click to expand...
Click to collapse
It's a real pain in the butt.... I just went through this 10 minutes ago. The problem: "Custom binary blocked by FRP" - or, FRP lock.
The answer is: get the phone into download mode and use ODIN to flash the stock DOK2 tar image.
It works. Not elegant, but I don't think there is any way round this. No way to use ADB that I can figure, but ODIN will work.
Once you get back up and running, make sure to go into settings and enable developer options. When you get there, allow USB debugging and click on the "bootloader unlock" option. That will keep FRP from screwing you up again.
If you need a more detailed explanation, let me know- but that's the skeleton of the fix. Once you get running again you can set up the phone the way you want it.
Cheers! (argh)
Steven.RN
Get the Odin file here: https://www.androidfilehost.com/?fid=24269982087008345 (N910T3UVU1DOK2_N910T3TMB1DOK2_TMB.zip)
Unzip the file and it will end in ....tar.md5 Just knock off the .md5 so that it simply ends up as .... .tar, and use "AP" placeholder in Odin.
PS: way important.... the above TAR is for the N910T3 - if you have the N910T, There's a different ODIN file, easy to find.

steven.rn said:
The answer is: get the phone into download mode and use ODIN to flash the stock DOK2 tar image.
[...]
PS: way important.... the above TAR is for the N910T3 - if you have the N910T, There's a different ODIN file, easy to find.
Click to expand...
Click to collapse
That's what I did when I tried to flash the stock rom before, ODIN tried for a few seconds and then bailed out with a failure.
However, I had no idea there was such a thing as a N910T3, or that there were two T-Mobile models of Note4. The rom I tried to flash before was for N910T (the only T-Mobile Note4 I knew existed). Sure enough, I popped out my battery, looked at the specs, and my device is a N910T3. Downloading that rom now. Fingers crossed it will work this time.
That *might* also explain a mystery glitch I had been experiencing, but had resolved to just live with: About 10-20% of the time the device would load an image (in any app, system or third party, from gallery or downloaded by the app..didn't seem to matter), random parts of the image would be corrupted - usually obscured by green lines (note, this is NOT the camera issue other people have experiences, but the results look very similar). One of the first things I did when I got the phone was root it (one of the reasons I went to T-Mobile, b/c Verizon's Note4's apparently can't be rooted). But if the root I installed was for N910T and not my N910T3 then maybe that might explain those glitches...or so I hope.

jfviwerbnv said:
That's what I did when I tried to flash the stock rom before, ODIN tried for a few seconds and then bailed out with a failure.
However, I had no idea there was such a thing as a N910T3, or that there were two T-Mobile models of Note4. The rom I tried to flash before was for N910T (the only T-Mobile Note4 I knew existed). Sure enough, I popped out my battery, looked at the specs, and my device is a N910T3. Downloading that rom now. Fingers crossed it will work this time.
That *might* also explain a mystery glitch I had been experiencing, but had resolved to just live with: About 10-20% of the time the device would load an image (in any app, system or third party, from gallery or downloaded by the app..didn't seem to matter), random parts of the image would be corrupted - usually obscured by green lines (note, this is NOT the camera issue other people have experiences, but the results look very similar). One of the first things I did when I got the phone was root it (one of the reasons I went to T-Mobile, b/c Verizon's Note4's apparently can't be rooted). But if the root I installed was for N910T and not my N910T3 then maybe that might explain those glitches...or so I hope.
Click to expand...
Click to collapse
Yup.... make sure you get the right flavor of ROM or stock files. I think some devs might have roms that work with either version. But that's the first thing to check, if it's compatible.
Once I reflashed my wifey's phone, I ODIN'ed in the stock twrp recovery TAR file, then got into the recovery and flashed supersu 2.64 in a zip. Rooted, working fine, done (YaY)
BTW, once you flash SU in recovery, when you go to reboot, TWRP will say "hey, do you wanna root with SU?" DONT DO IT- just let it go to boot up. It will be there.
Let me know how things turn out; I don't think you'll have any surprises. It took me about an hour and a half to make sure I had the right solution fer shurrrre, so I think I saved you some time.
You always this lucky? :highfive:
Cheers,
Steven.RN
PS on an odd note, I dumped all my Verizon phones (5 lines) because I couldn't root my Verizon Note 4. Got rid of the VZW Note 4 for a T-mobile Note 4. Looks like we both went the same way! Verizon lost years and years of my business over this

steven.rn said:
Yup.... make sure you get the right flavor of ROM or stock files.
Click to expand...
Click to collapse
Yep, that turned out to be the problem. Device is a N910T3, I had the stock 5.1.1 rom for the N910T, that's why flashing with ODIN was being blocked. Grabbed the stock 5.1.1 rom for the correct variant, N910T3, and ODIN and the phone were both happy. No factory reset or warranty repair necessary!
Thanks soooo much for the tip!
Unfortunately that image-loading glitch is still there even though I haven't re-rooted yet (now that I think about it, it's maybe more like 5%, and some images don't seem to be vulnerable. maybe it's like a weird bad build of libjpeg or something, I dunno) Well, that's a mystery for another time.
BTW, once you flash SU in recovery, when you go to reboot, TWRP will say "hey, do you wanna root with SU?" DONT DO IT- just let it go to boot up. It will be there.
Click to expand...
Click to collapse
Thanks, I'll keep that in mind. (Don't remember offhand what exactly I did there before.)
You always this lucky? :highfive:
Click to expand...
Click to collapse
Nah, I'm just one stubborn SOB, and once in a while it actually pays off
PS on an odd note, I dumped all my Verizon phones (5 lines) because I couldn't root my Verizon Note 4. Got rid of the VZW Note 4 for a T-mobile Note 4. Looks like we both went the same way! Verizon lost years and years of my business over this
Click to expand...
Click to collapse
Yea. There were actually several reasons I jumped Verizon -> T-Mobile, but that was one of them. Little over two years ago when I got an S3, all the lockouts from Samsung/Google/Verizon were so heavy it wound up bricking within the first couple weeks (complications trying to downgrade an OTA update I didn't want - long story). Anyway, trying to get a proper working replacement took them several tries (one replacement was DOA, another wasn't even a Samsung at all, let alone the right model) and just trying to even communicate with them at all was like having a roundtable with a cage of chimps. (just one example, I couldn't convince them there really were different models of any phone, like the S3, between different carriers, dev versions etc. Nevermind that I'm a career programmer, I couldn't possibly know what I'm talking about ) Plus Verizon's so much more expensive, and T-Mobile just strikes me as a vastly more level-headed pro-consumer company overall. And with the new Band 12 (the reason I got Note4 instead of Note3, oddly enough), their network's been every bit as good as Verizon's for me anywhere I've taken it.

Flashing DOK2 firmware via Odin will wipe internal memory.

ShrekOpher said:
Flashing DOK2 firmware via Odin will wipe internal memory.
Click to expand...
Click to collapse
Doing that didn't wipe internal memory for me (Odin 3.10.6). It did unroot my phone and I'm sure it probably reset my recovery image back to stock (didn't actually try booting into recovery again yet), but all my data was still 100% intact. And not just the data on the "external" SD but also all user data on the internal storage. (It never wiped user data for me on my old S3 or Nexus S either, but maybe the wiping after flashing is just a newer thing?)
Maybe it only wipes internal memory if you're flashing a different version of android? I was simply flashing 5.1.1 overtop rooted 5.1.1.