I've updated to .253 with all the wipes last week and today I discovered I only have 16 Gb of internal memory now.
Has anybody encountered the same issue? What can cause such a problem? And how can I solve it?
I've been getting this issue but some reason, I'm not limited to 16, I'm limited to 22? I'm not sure.
Is the same information as the picture, if you check memory with a file explorer(Es file explorer for example)? On a computer what is the situation with memory?
Monipeev said:
Is the same information as the picture, if you check memory with a file explorer(Es file explorer for example)? On a computer what is the situation with memory?
Click to expand...
Click to collapse
I noticed it on a computer initially. It showed 16 Gb instead of 32 Gb.
Now it shows something even worse! Total irrelevance.
It is absolutely illogical. In file explorer? What about if restart your phone? Any differents?
No difference, reloading doesn't change anything.
I'm so puzzled.
Also getting this issue @ 16GB internal storage.
FWIW i'm using the XPower 3 debloat with the .253 kernal.
@jufofu, What will show if despite the small remaining space, continue to copy more information in the internal memory? Whether it will continue to collect more data in memory, which means just bad reporting of information on available memory ? Maybe factory reset or repair with Xperia Companion. If problem still there, then the option is service. If you decide to do this, copy your information from phone to computer before this steps.
@Poag, was the problem there on the previous firmware? Do you have any ideas about its origins?
@Monipeev, it doesn't copy files from PC when the small memory is filled.
I will try to flash it again this week. If it doesn't work properly I'll have to restore TA backup and go the the service.
To be honest, i can't remember. I just flashed .224 from Flashtool wiping everything and TWRP reports only 8GB for internal.....booting into system atm....
Would someone with a 32GB internal mind posting a df?
[edit] Ok thats given me back my 32GB internal storage, currently sat on a freshly imaged device with 10GB of 32Gb used internal.
Poag said:
To be honest, i can't remember. I just flashed .224 from Flashtool wiping everything and TWRP reports only 8GB for internal.....booting into system atm....
Would someone with a 32GB internal mind posting a df?
[edit] Ok thats given me back my 32GB internal storage, currently sat on a freshly imaged device with 10GB of 32Gb used internal.
Click to expand...
Click to collapse
How did you go about fixing this?
I have the same problem.
So this is supposedly a bug in .253? I'm glad that it can be solved by reflashing.
@MattyCurrann, you too got this problem after flashing .253?
So i
1- Downloaded the UK Customised 224 in Flashtool - XperiFirm
2- Flash this wiping everything in the 'Wipe' box.
3- Booted into Fastboot and flashed the .253+TWRP kernal listed in the XPower thread post #312
4- Booted in system and then set about resetting up the device from TitaniumBackups.
---------- Post added at 10:30 AM ---------- Previous post was at 10:23 AM ----------
MattyCurrann said:
How did you go about fixing this?
I have the same problem.
Click to expand...
Click to collapse
I dont think you have the problem. 22GB is were you are meant to be.
10GB is system 22GB is user space.
jufofu said:
So this is supposedly a bug in .253? I'm glad that it can be solved by reflashing.
@MattyCurrann, you too got this problem after flashing .253?
Click to expand...
Click to collapse
nope, NOT a bug in .253,
afaik it's been there on Lollipop as well,
existed on Lollipop firmwares, 185, 224, 253 MM firmwares
(I got it too on Z5).
It sometimes occured during flashing Firmwares via XperiFirm + Flashtool or flashing new ones via TWRP,
really weird "bug"
There is another thread regarding this bug:
http://forum.xda-developers.com/z5-compact/help/how-storage-t3398804/post67849319#post67849319
You can fix it without flashing anything - if you have TWRP recovery, just Repair /data partition in Wipe menu. If that doesn't help, try Repairing /system partition (that helped in my case).
Another cases of the same issue: http://forum.xda-developers.com/xpe...-repack-stock-kernel-dm-t3301605/post67317647
Edit: posted it without refreshing the page, basically the previous post covers it all.
flashtools sucks nowadays!
Repairing didn't help, but resizing /data works perfectly. I've got my memory back.
jufofu said:
Repairing didn't help, but resizing /data works perfectly. I've got my memory back.
Click to expand...
Click to collapse
A little "how to" would be nice.
EDIT:
As TWRP kept giving me Errror 4. I did figure out what it meant by that.
It needs manual handling (answering questions) in cli.
I went on with "adb shell" on my computer while the device was started up in TWRP/recovery mode.
There I unmounted everything, and then I ran this command from adb shell:
Code:
e2fsck -f /dev/block/mmcblk0p42
There I had to answer a bunch of questions about orphaned inodes and other corruptions. (Tookl a while to answer them all. I could have used "-y").
Once done, the fs was marked as clean, and the rezise command in TWRP worked flawlessly. Problem solved.
Strange that it had so many corruptions/orphaned inodes, considering it was a new fresh flash made just recently with flashtool.
how did you update your phone?
Related
I have my nook rooted through my memory card. When I check how much internal storage I have on it through the nook it shows only 900 mb. It shows the same when I have it hooked to my computer. I know its supposed to have 5 gigs. I havent downloaded anything so I dont know where all the 4 + gigs went. Can anyone help? Thanks.
Can anyone please help?
thegameksk said:
Can anyone please help?
Click to expand...
Click to collapse
Barnes & Noble repartitioned the newest Nook Colors. If you had done even a hint of research before starting yet another thread you would know that.....which is why no one answered you last night when you asked this question....C'mon man this isn't customer service, do a search before you post.
How bout I did research and everything that i've seen has said that 5 gigs should show not 900 mb. The nook has 8 gigs. 3 are used for the os/repair and 5 for downloading things.
Nope, you are wrong.
New models made in May or refurb units as of May are partitioned for 1 GB of space.
http://forum.xda-developers.com/showpost.php?p=13772065&postcount=4
http://forum.xda-developers.com/showthread.php?t=1083506
http://forum.xda-developers.com/showthread.php?t=1080445
http://forum.xda-developers.com/showthread.php?t=1077321
Thats bs. When I bought it I was told there were 5 gigs for storage of files from my computer. Lokks like im sending this back. Thanks. Sorry bout the tude before.
No worries...I didn't mean to jump on you either. Just gets frustrating seeing new posts with the same old questions. Makes it tough to stay on top of the most current stuff and gets a little frustrating.
YeA i had searched but everything that came back said 5 gigs. Based on my reading of the threads that were posted theres no way to reparation the nook?
thegameksk said:
YeA i had searched but everything that came back said 5 gigs. Based on my reading of the threads that were posted theres no way to reparation the nook?
Click to expand...
Click to collapse
It's being worked on by many, but as of yet has not been solved. Conventional methods have come up empty. I'm quite sure we're getting closer to a solution though.
I was doing some research and came across this:
Here's how to convert a new NC (or one where you don't care about anything in /data and /media that won't be automatically restored by B&N) with only a 1GB /media space, back to one with with 5GB media space:
Boot a rooted Android system in the external SD card slot:
Access the rooted OS command line prompt, using either ConnectBot or ADB.
Fire up "busybox fdisk /dev/block/mmcblk0"
Delete partition #8 (the /media partition).
Note the size of partition #7 (the cache partition), and delete it as well.
Delete partition #6 (the /data partition).
Recreate partition #6 (the /data partition), to the size you want (say 1GB).
Recreate partition #7 (the /cache partition), to the size noted in step #5.
Recreate partition #8 (the /media partition), to occupy the remainder of the space.
Remove the SDcard and reboot.
When the NC boots its native system, it will recreate (just like a factory reset), the contents of the resized partitions. Yes, you will have to reregister. Of course, the same process, but with a different number in step #7, can give you more app space.
This is easily scriptable as well, and I fully expect such scripts.
Do you think this could work? I dont know enough about modding to try it. lol
I have a rather urgent issue, in which a factory reset wiped my sdcard. First of all, is that normal? This is my first device with no external microsd, and my first time using TWRP. Before, I had been using various versions of Amon-Ra or CWM, and when I factory reset they never wiped the sd card. Next, whether it was normal or not, I need a way to recover my data. I had around 8 gigs in sdcard before it got wiped.
To give you more background info on what was going on, I had a rooted 4.1.2 16GB Nexus, and I decided that I wanted to try PA. I made a nandroid backup of course, and then proceeded to flash the rom. I followed the instructions on the PA thread, first doing a factory reset followed up by the actual flashing, then a wipe of cache/davlik. After I tried the rom out for a few minutes, I noticed that there weren't any redeeming features to make it worth the time-consuming switch from stock to PA, transferring all my data and setting up my settings once more.
I rebooted back into recovery and factory reset again, and then I went to restore and saw that there were no backups. Suspicious, I went to the install menu, and found my entire sdcard folder had been wiped out. What happened?
Edit: I'm currently still on the recovery, afraid to do anything in case I lose my data forever.
Was your boot loader already unlocked or did you unlock it right before you flashed the ROM?
littleemp said:
Was your boot loader already unlocked or did you unlock it right before you flashed the ROM?
Click to expand...
Click to collapse
Thanks for the reply, especially on Christmas, but I got around the issue myself. It had been unlocked for 2 months now.
I noticed that every time I booted into recovery, it would make a "0" folder and move the contents of my sdcard into that "0" folder. Then the 0 folder would go inside another 0 folder, and so on and so forth. It was a really strange issue because I was unable to restore my backup; TWRP could not find my /sdcard/TWRP/backup folder, because it did not exist! It was in sdcard/0/0/TWRP/backup. I used the built in file manager in TWRP, and moved the contents back into the proper folder. I could then restore, and now I'm feeling relieved.
However, two issues remain; the 0 folders are still there, and storage transfer speeds seem very slow.
Edit: I got rid of the 0 folders by moving my folders out of them and then deleting the 0 folders, but the size of my files seem to have been inflated. What took up 6 gigs before is now taking up 8.8gb. Lol wut? Also, when I hook it up to a computer it tells me that 12GB has been filled. So many discrepancies.
androidwkim said:
Edit: I got rid of the 0 folders by moving my folders out of them and then deleting the 0 folders, but the size of my files seem to have been inflated. What took up 6 gigs before is now taking up 8.8gb. Lol wut? Also, when I hook it up to a computer it tells me that 12GB has been filled. So many discrepancies.
Click to expand...
Click to collapse
I am having the same problem. I think everybody has that problem, because it's caused by jelly bean 4.2 and its new emulated storage.
The only way I have found to get arround it was to copy all files on the computer from the sdcard, then formating the sdcard in recouvery and moving everything back.
Only problem I am having right now is that I can't for the love of it copy my files. Stupid MTP filesystem is really buggy and extremly slow. I constantly crashes or gives me multiple erros. The one I am having at the moment is something about a parameter error.
Very annoying the stupid filesystem under 4.2.
Btw. I can't get the adb pull command to work either. When I tell it to copy system/storage/emulated/legacy (I believe thats where the sdcard is actually loccated, right?!) it doesn't copy a single file.
If anybody could help me I would be very greatfull.
xaboren said:
I am having the same problem. I think everybody has that problem, because it's caused by jelly bean 4.2 and its new emulated storage.
The only way I have found to get arround it was to copy all files on the computer from the sdcard, then formating the sdcard in recouvery and moving everything back.
Only problem I am having right now is that I can't for the love of it copy my files. Stupid MTP filesystem is really buggy and extremly slow. I constantly crashes or gives me multiple erros. The one I am having at the moment is something about a parameter error.
Very annoying the stupid filesystem under 4.2.
Btw. I can't get the adb pull command to work either. When I tell it to copy system/storage/emulated/legacy (I believe thats where the sdcard is actually loccated, right?!) it doesn't copy a single file.
If anybody could help me I would be very greatfull.
Click to expand...
Click to collapse
I had the same fear, emotion and discovery a week ago when trying a new Rom thanks multi users feature .
You may try to switch from MTP mode to MSC in system setting to increase the speed.
Take care of the different tools because as example JROMFlasher will format the SD card for better cleaning. (I had backup!)
I think I read that the Factory Reset from the settings menu WILL erase everything.
Formatting with ClockworkMod, saves your sdcard files.
I also recommend unlocking asap just for laughs. Even if you don't plan on rooting or Modding... unlocking will ensure your files won't be deleted if you decide to or something happens that requires it
Sent from my Nexus 7 using XDA Premium HD app
[Not sure this is the right section, but since it requires a bit of knowledge on adb and stuff, I thought the development area would be better]
I happened to do something, somehow, which cause my Internal Memory to completely "disappear". The only way to get it back was downgrading to GB. However signal wouldn't work. I tried everything I saw on the Internet. But most people had to take it to the customer service. I didn't want that. My mobile was still working, I knew I only needed to fix something no matter what!
I realised that when this problem occurs, if you go to About Device, you'll see that your Baseband version will be XXXX. If that's not the case, just try factory reset, wipe cache, dalvik, etc... and re-flashing stock via odin. BUT if that IS the case, follow the steps below:
DO THIS ONLY ON I9070 (GALAXY S ADVANCE) DON'T TRY IT ON I9070P SINCE I'M NOT SURE IT WILL WORK AND IT MIGHT BRICK YOUR DEVICE.
1 Download http://d-h.st/W5W
2 extract it into your SD Card
3 Run adb, since you won't be able to install terminal on your mobile. However if you've got a ROM with terminal pre-installed you can use it anyways.
4 Use this command on adb: adb shell
su
dd if=/sdcard/modemfs.img.md5 of=/dev/block/mmcblk0p2
If you have this problem on a different device and found this thread, try looking for the mmcblk0p2 for your device, extract it to your SD Card and type on adb: dd if=/sdcard/mmcblk0p2 of=/sdcard/modemfs.img.md5
Then, go to step 4
That's it, folks! If nothing happened yet, reboot your mobile and both your network and memory will be working.
Hit thanks if I've helped you anyroad
Sorry but it didn't work for me.
hey buddy, thanks for the info... in my phone i have baseband name, but i dont have system storage ... i try your metod but i couldnt fix it...
can you give me a little more information how did you do? thanks and sorry my bad english....
are u sure u have root access? try using Root Explorer, google it. there is one that is really good. I used this method on JB. It should work on GB also... if nothing like reflashing stock, wiping data, cache and dalvik cache and fixing permissions worked, thats the last hope. other than that, only customer service as far as I know :sad: try to follow the steps thoroughly. ALSO, just to make sure, put the modemfs file both on the internal memory and external sd card, since it might have been changed. MIUI for example would recognize your external sd card as ur internal memory and vice-versa
gustavray said:
are u sure u have root access? try using Root Explorer, google it. there is one that is really good. I used this method on JB. It should work on GB also... if nothing like reflashing stock, wiping data, cache and dalvik cache and fixing permissions worked, thats the last hope. other than that, only customer service as far as I know :sad: try to follow the steps thoroughly. ALSO, just to make sure, put the modemfs file both on the internal memory and external sd card, since it might have been changed. MIUI for example would recognize your external sd card as ur internal memory and vice-versa
Click to expand...
Click to collapse
Yes, i have a root access. I flash JB XXLPY, then i flash kernel to have CWM, then i wipe all data, install Chuckybean ROM and i have 0 MB internal memory. After tha i've tried your fix via adb and even wondering if i can do this via odin...
NOTHING still the same 0 MB...
jjeerry said:
Yes, i have a root access. I flash JB XXLPY, then i flash kernel to have CWM, then i wipe all data, install Chuckybean ROM and i have 0 MB internal memory. After tha i've tried your fix via adb and even wondering if i can do this via odin...
NOTHING still the same 0 MB...
Click to expand...
Click to collapse
then try reflaashing via odin the stock rom with the pit file. that can be found on section on how to downgrade to GB. make sure u use the right pit file for the 8 or 16gb version. then when flashing, make sure to check the option of Re-format
gustavray said:
then try reflaashing via odin the stock rom with the pit file. that can be found on section on how to downgrade to GB. make sure u use the right pit file for the 8 or 16gb version. then when flashing, make sure to check the option of Re-format
Click to expand...
Click to collapse
Been there, done that
I am using Hongkong version of SM-N9005, everything worked just fine earlier, but recently after I flashed stock NB3 the total amount of internal storage I could use cut down to about 28GB. Then I tried XNOTE v10 and official CM11 as well, but the internal memory kept getting smaller and smaller after every flash as I could see it when I attached my phone to my computer. I tried factory reset in the ROM and also wipes in CMW recovery, but neither seems to be working. And I found out that Storage→System memory took up a space about 6.5G.
Does anyone have an idea about this? How should I wipe correctly and get my memory back? Thanks in advance.
When flashing in cwm I usually wipe in mounts and storage first. Research which ones to wipe...as I cant remeber which ones exactly. Things like format cache...format system...format sdcard(but the internal sd card - what it is named depends on which recovery is flashed)...just remeber this will wipe alk ur internal data like game saves, game data, local pictures etcetc...but should clear the excess storage being used.
Example...if you flash CM11 it uses a seperate sub-directory as main storage...and reverting back to stock changes to normal but the CM11 directory remains...something similar to sdcard/0/ ...soooo....if you are on stock now...use a file manager and if you have a folder named '0' ypu can usually delete what's in there...but the folder itself remains unless u change write permissions or formate ur internal storage.
Sent from my SM-N9005 using XDA Premium 4 mobile app
ZH_Ray said:
I am using Hongkong version of SM-N9005, everything worked just fine earlier, but recently after I flashed stock NB3 the total amount of internal storage I could use cut down to about 28GB...
Click to expand...
Click to collapse
It is not uncommon for stock ROMs released by Samsung to come with a new partitioning scheme to make slightly more space in certain partitions. In this regard the HK N9005 was already known to have a system partition that was smaller than the EU N9005 (which resulted in some of the problems seen when the first XEO 4.4.2 leak was attempted on HK 9005).
"fastboot flash userdata userdata_64g.img"
xclub_101 said:
It is not uncommon for stock ROMs released by Samsung to come with a new partitioning scheme to make slightly more space in certain partitions. In this regard the HK N9005 was already known to have a system partition that was smaller than the EU N9005 (which resulted in some of the problems seen when the first XEO 4.4.2 leak was attempted on HK 9005).
Click to expand...
Click to collapse
Fix partition table with this:
http://www.androidheadlines.com/2014/07/android-flash-oneplus-one-stock-cyanogenmod-11s.html
I have an unlocked bootloader, but I'm not rooted. I upgraded to MM via OTA and set my SD Card to be used as internal memory. I've had some problems since:
1) The first real issue is that Evernote is giving me a database read/write error and not working. It seems that to resolve that, I'll probably need to root. So, I went to do a MM nandroid before rooting
2) When i went into TWRP (i a had flashed 2.8.7.1-clark), and tried to create a backup, I received a Failure: E: Unable to mount storage (one note: the top of my screen shows TWRP 2.8.7.0, not .1, so i double-checked that i was using the correct version from https://dl.twrp.me/clark/, and I am. The file name is 2.8.7.1, but it appears on screen as .0. Is anyone else seeing this?)
3) When i go into the Mount screen and select storage, it is showing Internal as just 2+GB free (which is correct), but 0MB for my Micro SDCard. So, it can't mount it.
4) Looking around, the fixes for this seem to be a bit severe in terms of formatting the SD Card again, etc. (ex. http://forum.xda-developers.com/showthread.php?t=2354029)
So, my questions are:
1) If anyone knows of a solution to that Evernote issue, that would be great
2) More importantly, what my options are for fixing the Backup problems
3) Specifically, with my SDCard now supposedly acting as internal memory, if i format the card per the common fixes, will that cause other unexpected problems with apps and other functions that are now using my SD Card as usable storage?
How did you set SD card as internal storage. Me: stock, no root, MM
Sent from my XT1575 using Tapatalk
I'm giving up on combined storage until twrp is fixed.
You just go into settings, storage, then click on the SD card. I'm back to lollipop at the moment, so I cant say exactly what to do next, but I think from there it should be clear. It may be an option up in the overflow menu at the top right. It will make you reformat your card as part of the process .
Thanx Chuck! Need to b.u. before formatting as internal...
I had the same issue with the SD card set as internal, couldn't make a twrp backup, so I had to reformat as storage and it works. Only bad part is now I can't move apps to SD
Is there a twrp fix in the works??
chuck-fu said:
2) When i went into TWRP (i a had flashed 2.8.7.1-clark), and tried to create a backup, I received a Failure: E: Unable to mount storage (one note: the top of my screen shows TWRP 2.8.7.0, not .1, so i double-checked that i was using the correct version from https://dl.twrp.me/clark/, and I am. The file name is 2.8.7.1, but it appears on screen as .0. Is anyone else seeing this?)
Click to expand...
Click to collapse
I don't have MM installed, so I don't know about the rest of it. But I've flashed the 2.8.7.1 IMG twice now and my TWRP still says 2.8.7.0 on the top of the screen. So either we're both making the same mistake, or TWRP didn't update their version number in the recovery.
ScaryBugThing said:
I don't have MM installed, so I don't know about the rest of it. But I've flashed the 2.8.7.1 IMG twice now and my TWRP still says 2.8.7.0 on the top of the screen. So either we're both making the same mistake, or TWRP didn't update their version number in the recovery.
Click to expand...
Click to collapse
It's a known issue that the version displayed stays on 2.8.7.0 after updating.
Sent from my Moto XPE