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
Related
I just tried a ROM for the first time on my Nexus 7 (though I've used a lot on my past phones) and holy ****, coming from a non-Nexus device, I wasn't expect this, it wiped out my internal storage partition (/sdcard) as well as my data partition.
Losing the international storage partition is really painful, as that's where all my clockworkmod backups were.
Does this happen every time a ROM is flashed on a Nexus 7? (In case it makes a difference, this is the ROM I flashed.) Does this happen every time an update to a ROM is flashed?
For future reference, is there any way to try ROMs and flash updates without wiping out my whole internal storage?
Do you have a 3G?
Sent from my Nexus 7 using xda app-developers app
over the air system updates shouldn't delete any data but as far as I know flashing a different rom will wipe everything. With a phone the data is stored on a separate physical device such as a microsd card but with the nexus 7 its all held on the internal memory. You could use an otg cable and thumb drive as external storage for backup purposes.
dparrothead1 said:
Do you have a 3G?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I have a 3G.
corumuk said:
over the air system updates shouldn't delete any data but as far as I know flashing a different rom will wipe everything. With a phone the data is stored on a separate physical device such as a microsd card but with the nexus 7 its all held on the internal memory. You could use an otg cable and thumb drive as external storage for backup purposes.
Click to expand...
Click to collapse
So what do people normally do when an update to a ROM comes out? Do they fully backup everything and then do an advanced restore in CWM to get back their data? Or are most people starting fresh on every ROM update?
corumuk said:
over the air system updates shouldn't delete any data but as far as I know flashing a different rom will wipe everything. With a phone the data is stored on a separate physical device such as a microsd card but with the nexus 7 its all held on the internal memory. You could use an otg cable and thumb drive as external storage for backup purposes.
Click to expand...
Click to collapse
What?
A rom shouldn't wipe the Emmc (internal sdcard), coming from Samsung phones that all have 16gb of internal storage plus a slot for an external card, i have never had it wipe my storage. Either internal or external.
I have also flashed a few roms on the Nexus and the ONLY thing that wiped my storage was unlocking the bootloader.
Looks to me like you were answered in the ROM Thread that you referenced.
http://forum.xda-developers.com/showthread.php?p=35322271
Sent from my Nexus 7 using xda app-developers app
Based on my experience with the original Droid, flashing a new rom usually calls for wiping system, cache, data, boot, and dalvik. Internal memory data is deleted, but external microsd storage is not cleared. The N7 only has internal memory, and that is cleared when doing the wipes prior to installing a new rom. You should copy pictures, video, documents, downloads, music, saved texts, etc. to a pc or OTG storage along with the backups before the new rom.
Wiping system and data in recovery does not touch /sdcard. sdcard should remain intact unless flashing a factory image.
regalpimpin said:
Wiping system and data in recovery does not touch /sdcard. sdcard should remain intact unless flashing a factory image.
Click to expand...
Click to collapse
This.
If you want to be completely and absolutely sure it will not delete anything, open the zip go to:
META-INF/com/Google/android and open up the updater-script file in a text editor, look through and you will see every command that is given in the flash.
You will most likely only see it format the /system partition. Which is why you manually have to do a factory reset in recovery, which formats
/data (where your user apps and preferences are stored, as well as the dalvik cache is)
/cache
And the android secure file which is in fact located on the Emmc, but that is the only file on that partition it touches.
Thanks all, turns out the line that killed me was in the instructions for the ROM I flashed, the flash instruction was:
fastboot -w flash system system.img
Click to expand...
Click to collapse
That -w flag is what wiped my internal storage.
manekineko said:
Thanks all, turns out the line that killed me was in the instructions for the ROM I flashed, the flash instruction was:
That -w flag is what wiped my internal storage.
Click to expand...
Click to collapse
So what did you do with that ?
manekineko said:
Thanks all, turns out the line that killed me was in the instructions for the ROM I flashed, the flash instruction was:
That -w flag is what wiped my internal storage.
Click to expand...
Click to collapse
@manekineko @studacris Can you please elaborate, what do you mean by that ? I am intending to flash a different ROM on a different device.I extracted the firmware zip and checked every file but couldn't find "wipe (-w) in fastboot with system.img".
Thank you
hello. i upgraded to 4.3 MJ8 firmware yesterday. although my internal storage should be empty as you can see from the attached 2 pictures i only have 1GB left. not sure what system data is (shown in attachment diskusage) but its taking lots of space, although its shown in green.
attachment storage shows a big grey bar for empty space but below shows only 0.88 GB free space.
i have uninstalled all the bloatware with TB so i dont think its that.
also i wiped all data before flashing the MJ8 FW. Any advise on what is wrong and how i can regain some space back? thanks.:good:
forgot to add that i have flashed 3 files. PDA, modem and CSC. the MJ8 files were located in this thread but OP has removed them .
http://forum.xda-developers.com/showthread.php?t=2317105
Solved my issue. Its was 2 cwm backups stored deep in the root folder in the internal memory. Moved the bacup all is well now.
resitm said:
Solved my issue. Its was 2 cwm backups stored deep in the root folder in the internal memory. Moved the bacup all is well now.
Click to expand...
Click to collapse
Can you share the locations ... actually i got the same issue currently showing only 1.98 GB frees space even after hard wiping , flashing with pit ..really appreciate it
amanjits said:
Can you share the locations ... actually i got the same issue currently showing only 1.98 GB frees space even after hard wiping , flashing with pit ..really appreciate it
Click to expand...
Click to collapse
With a root browser go to root folder=>data=>media=>clockwork
resitm said:
With a root browser go to root folder=>data=>media=>clockwork
Click to expand...
Click to collapse
Or maybe easier boot to recovery=>backup restore=>delete. Im using philz touch cwm this option is available
On my I337 (rooted with SAFESTRAP 3.71), my STOCK ROM DATA partition is 9970MB with CACHE PARTITION AT 2046MB. I'm not sure how these were set (loaded a base 4.3 with ODIN), but when trying to load HYPERDRIVE in ROM-SLOT, TWRP shows only 12MB free! Nothing is on my device (like music, big files, etc), because I use the 32G external memory. My question is this (based on all I read), is it possible the STOCK ROM size might be reduced if I do a FACTORY/DATA/CACHE RESET and reinstall my backup from TWRP? Not sure what is consuming space and if you can't repartition it without losing the root...I'm not sure which way to proceed being I got this far. Any help regarding this would be greatly appreciated.
PS: the storage indication from within system shows: system 6.26G, used space 1.18G, cache 66MB, misc file 353MB, avail space 8.15G
beachbacon said:
On my I337 (rooted with SAFESTRAP 3.71), my STOCK ROM DATA partition is 9970MB with CACHE PARTITION AT 2046MB. I'm not sure how these were set (loaded a base 4.3 with ODIN), but when trying to load HYPERDRIVE in ROM-SLOT, TWRP shows only 12MB free! Nothing is on my device (like music, big files, etc), because I use the 32G external memory. My question is this (based on all I read), is it possible the STOCK ROM size might be reduced if I do a FACTORY/DATA/CACHE RESET and reinstall my backup from TWRP? Not sure what is consuming space and if you can't repartition it without losing the root...I'm not sure which way to proceed being I got this far. Any help regarding this would be greatly appreciated.
PS: the storage indication from within system shows: system 6.26G, used space 1.18G, cache 66MB, misc file 353MB, avail space 8.15G
Click to expand...
Click to collapse
The stock slot will never be reduced as it's the basic internal storage. Safestrap doesn't partition the internal storage, it makes image files where it holds all the slots on the internal storage. The 12mb thing is a glitch and i don't remember how to fix it if possible.
No space for adding custom ROM (S4, i337)
DeadlySin9 said:
The stock slot will never be reduced as it's the basic internal storage. Safestrap doesn't partition the internal storage, it makes image files where it holds all the slots on the internal storage. The 12mb thing is a glitch and i don't remember how to fix it if possible.
Click to expand...
Click to collapse
Well, you guys would know. If there is a lead or something you can think of regarding the "glitch"...it would be greatly appreciated. Just asking, is it possible the STOCK ROM size/usage might be reduced if I do a FACTORY/DATA/CACHE RESET and reinstall my backup from TWRP? If so, which ones (ie. just Cache, Data, or Dalvik) so that I stay rooted and can restore my backup? Thanks in advanced.
beachbacon said:
Well, you guys would know. If there is a lead or something you can think of regarding the "glitch"...it would be greatly appreciated. Just asking, is it possible the STOCK ROM size/usage might be reduced if I do a FACTORY/DATA/CACHE RESET and reinstall my backup from TWRP? If so, which ones (ie. just Cache, Data, or Dalvik) so that I stay rooted and can restore my backup? Thanks in advanced.
Click to expand...
Click to collapse
The size of the stock slot doesn't change, and shouldn't. Even if you restore a ROM slot to the stock slot, it will use the full space of the phone.
Only 12mb free for rom-slot1
DeadlySin9 said:
The size of the stock slot doesn't change, and shouldn't. Even if you restore a ROM slot to the stock slot, it will use the full space of the phone.
Click to expand...
Click to collapse
So perhaps I'm not asking the right question??? What would limit the ability to create/activate ROM SLOT1, if what you say (the STOCK SLOT) has no effect on the space available? Could it be a ghost remnant from MF3? Seems the question has been asked with no resolution?
I m new to this genre of rooting and installing ROMs so u might find the descriptive part of my problem a bit absurd and amusing to pro's out here - so please bare with me. Thanks.
I have Custom Flash software (Philz Touch 6.26.6) installed on my Samsung Galaxy S5 SM-900I. I installed " PopWiz_Telstra_v5.1_FINAL_G928FUVU2DOH6_G928FTMB2DOH6_TMB " from the community to get the S6 outlook + A few Note5 apps .
1. I used Wipe Data/Factory Reset, and then selected Clean to install A new ROM
2. I m not sure if that completely wiped data off my phone except the Custom Flash software or not
3. Thinking of the above , i installed PopWiz_Telstra_v5.1_FINAL version and proceeded .
4. I checked the storage and it shows 7.4Gb
5. Somewhere i am not doing things correctly as i have a 16Gb variant and 7.5Gb is used up in system files
Can anyone tell me how can i wipe data completely except my Flash Software , and make maximum use of my Internal Memory because as far as i know , at max system files should be of 4Gb , even that should leave me with 12Gb appx .
Please help me fix this guys
Anyone for this?
Flash TWRP recovery instead of Phillz
There is no issue it's normal , the system take too much place and you have about 9gb free. You can flash stock and check , its almost the same thing
Sent from my SM-T116 using XDA Free mobile app
delete - got ROM names confused
*Detection* said:
I'm running PopWiz, and it shows 4.85GB used / 11.84GB
And that's after installing a load of apps, and having stuff saved like videos and images etc
Click to expand...
Click to collapse
You running popwiz ? oooh come in MP i need youuu
Sent from my SM-G900F using XDA Free mobile app
u have stuff stored in your sdcard from before instaling your new rom, go into custom format option and format sdcard if you have nothing important on your phone that worth keeping.format sdcard not sdcard1
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?