Database Users

[Q] System partition

Hello everyone! Yesterday, I tried to flash the new ICS CM9 and I did it. It is laggy and I can t install GAPPS.Then i saw that my system partition is 160 mb instead of 215 (recommended).
So, how can I change my system partition from 160 to 215 ? (I tried some TPT Gen2 tutorials, but nothing).
Thanks!

stanangel said:
Hello everyone! Yesterday, I tried to flash the new ICS CM9 and I did it. It is laggy and I can t install GAPPS.Then i saw that my system partition is 160 mb instead of 215 (recommended).
So, how can I change my system partition from 160 to 215 ? (I tried some TPT Gen2 tutorials, but nothing).
Thanks!
Click to expand...
Click to collapse
ok first go to market and download tpt helper.
then choose make your own tpt fill chache as 20 mb system(dont make it less it is recommended to use 20 mb on ics) as 210 mb(or as per ur choice but not less) and rest will be system.then click ok.
it will download the tpt and edit it accordingly.then check it it should have from the app there should be 10/12 matches.
then reboot.
press menu+power+vol up then green text fill flash and tpt will start on its own.
if there is a error at 99% down worry wait and then it will be success.
u r done.
just remember to have a rom on your sd.
there will be other options like choosing splash screen, recovery etc choose accordingly in the app.
u can even use your nandroids.
remember to delete image folder from sd after flash to prevent flashes by mistakes.
u r done enjoy

thanks saaransh9 i also want this info, voted up

sorry, but my number of matches is 1/1 .It is all right?

stanangel said:
sorry, but my number of matches is 1/1 .It is all right?
Click to expand...
Click to collapse
When u set your partitions does it says finished if yes then it should be ok.

Or just TPT with the 220mb system partition version, reinstall your rom and you're done

Rastaman2302 said:
Or just TPT with the 220mb system partition version, reinstall your rom and you're done
Click to expand...
Click to collapse
yes u can do that but the stock has 20 or 30 mb oem space which is a waste instead i get 210 mb system 210 data and 20 mb cache when i made my own tpt

How to check system partition???
Sent from my Blade using xda premium

rohitzz said:
How to check system partition???
Sent from my Blade using xda premium
Click to expand...
Click to collapse
You can use this.

Hi to all, I am new at all this android stuff, so I hope you won't laught, but I have few questions.
1.Is there a way to change size of partitions without flashing new rom?
2.How big the partitions should be (System, Data, Cache) ?
According to "Blade Checker" I have European ZTE Blade 512MB, Gen2 phone, also it said that I have to use image.bin style TPTs.
Curent partitions are:
System 220MB
Data 160MB
Cache 37MB
It is running CM 7.1 stable mod and Clockwork Mod Recovery 5.0.2.0
Thanks in advance, and I am sorry if I posted at a wrong place.

ZeChe said:
Hi to all, I am new at all this android stuff, so I hope you won't laught, but I have few questions.
1.Is there a way to change size of partitions without flashing new rom?
2.How big the partitions should be (System, Data, Cache) ?
According to "Blade Checker" I have European ZTE Blade 512MB, Gen2 phone, also it said that I have to use image.bin style TPTs.
Curent partitions are:
System 220MB
Data 160MB
Cache 37MB
It is running CM 7.1 stable mod and Clockwork Mod Recovery 5.0.2.0
Thanks in advance, and I am sorry if I posted at a wrong place.
Click to expand...
Click to collapse
1. No,you cannot.
2.Your partition size is more than enough for any new ROM's. Minimum System partition size varies accordings to different ROM's. Minimum data is according to your needs for app storage. Minimum cache is 20mb,but keep in mind you can't download anything from market/play over 20mb. So cache decides your temporary market storage.
Sent from my ZTE Blade using XDA app

I have only 20-25Mb left on data partition, that's what bugs me.
Was thinking maybe to increase Data prtition or maybe install 4GB class 10 sd card I have and try to make EXT partition on it, 2GB I have now seems a bit slow for that.
Would one of thos things help?
Thanks.

ZeChe said:
I have only 20-25Mb left on data partition, that's what bugs me.
Was thinking maybe to increase Data prtition or maybe install 4GB class 10 sd card I have and try to make EXT partition on it, 2GB I have now seems a bit slow for that.
Would one of thos things help?
Thanks.
Click to expand...
Click to collapse
You better get a 4 or 8 Gig card. Class 4 should do actually.
You've tried A2SD right?
Sent from my ZTE Blade using XDA app

karthiknr said:
You better get a 4 or 8 Gig card. Class 4 should do actually.
You've tried A2SD right?
Sent from my ZTE Blade using XDA app
Click to expand...
Click to collapse
No, actually I didn't tried A2SD, I think, I am using App 2 SD, free version, but I assume that's not the same, also I think that my card has only one partition.
As I said, am new to all of this.
Sorry for bothering you and I really appreciate the help.
Thanks, again.

ZeChe said:
No, actually I didn't tried A2SD, I think, I am using App 2 SD, free version, but I assume that's not the same, also I think that my card has only one partition.
As I said, am new to all of this.
Sorry for bothering you and I really appreciate the help.
Thanks, again.
Click to expand...
Click to collapse
A2SD gives u lots of space. I have a 4 gig SD card with a 1 gig partition and I've 300 apps installed
Here's how u do it
-backup ur SD card
-boot into recovery
-select advanced
-partition SD card
-select size. recommended 1gb
-select swap size as 0. Select 32 if u use it for gaming
-reboot
-install s2e
-check all four boxes
-reboot
-start installing apps
(Tested with gingerbread roms)

ZeChe said:
Hi to all, I am new at all this android stuff, so I hope you won't laught, but I have few questions.
1.Is there a way to change size of partitions without flashing new rom?
2.How big the partitions should be (System, Data, Cache) ?
According to "Blade Checker" I have European ZTE Blade 512MB, Gen2 phone, also it said that I have to use image.bin style TPTs.
Curent partitions are:
System 220MB
Data 160MB
Cache 37MB
It is running CM 7.1 stable mod and Clockwork Mod Recovery 5.0.2.0
Thanks in advance, and I am sorry if I posted at a wrong place.
Click to expand...
Click to collapse
If you changed your partition sizes, your rom and all your data would be wiped. If you made a backup before, you could restore it afterwards as long as it could fit in the new sizes (eg. if your rom took up 160MB in system just now, and you changed system to 170MB then it would fit so you could restore it, same for other partitions).
Size for the partitions depends on what rom you are wanting to install. Some like Swedish Snow can fit in 128MB system, others like the ICS ones need ~180MB or bigger.
As your current layout is big enough for any rom out now, you'd be better making an ext partition on your phone and using that. S2E from Google Play works well with CM7 and lets you move most, if not everything, on the data partition to the ext partition. Its usually best just to move apps, but it means you can have loads of space. You can choose the size of ext partition depending on how big your sdcard is and how much space you need.
karthiknr said:
2.Your partition size is more than enough for any new ROM's. Minimum System partition size varies accordings to different ROM's. Minimum data is according to your needs for app storage. Minimum cache is 20mb,but keep in mind you can't download anything from market/play over 20mb. So cache decides your temporary market storage.
Sent from my ZTE Blade using XDA app
Click to expand...
Click to collapse
2MB is the minimum for cache. You can redirect the market downloads to data/ext partition/somewhere else, so you can download any app you like. Most roms do this automatically if your cache partition is small. By making it bigger than 2MB, you are either wasting the extra space if its still small enough to be redirected, or you are restricting the size of apps you can download if its too big to be redirected.

Amphoras said:
If you changed your partition sizes, your rom and all your data would be wiped. If you made a backup before, you could restore it afterwards as long as it could fit in the new sizes (eg. if your rom took up 160MB in system just now, and you changed system to 170MB then it would fit so you could restore it, same for other partitions).
Size for the partitions depends on what rom you are wanting to install. Some like Swedish Snow can fit in 128MB system, others like the ICS ones need ~180MB or bigger.
As your current layout is big enough for any rom out now, you'd be better making an ext partition on your phone and using that. S2E from Google Play works well with CM7 and lets you move most, if not everything, on the data partition to the ext partition. Its usually best just to move apps, but it means you can have loads of space. You can choose the size of ext partition depending on how big your sdcard is and how much space you need.
2MB is the minimum for cache. You can redirect the market downloads to data/ext partition/somewhere else, so you can download any app you like. Most roms do this automatically if your cache partition is small. By making it bigger than 2MB, you are either wasting the extra space if its still small enough to be redirected, or you are restricting the size of apps you can download if its too big to be redirected.
Click to expand...
Click to collapse
I stated 20mb as minimum because Tilal recommended 20mb for ColdFusion and I would rather change partition sizes once than doing it repeatedly.
Sent from my ZTE Blade using XDA app

Well, I did few things.
I did what QuantumFoam suggested, partitioned my old 2GB card that was already in phone, created EXt partition of 512MB, to try if it work. I'we made backup on PC, but when I rebooted few of apps I had on sd desapeared, also all my music, pictures, wallpapers and other stuff.
Question I have now is should I copy all the things from PC back to SD and where.
Thanks all of you guys for helping me and having so much patience with me.

karthiknr said:
I stated 20mb as minimum because Tilal recommended 20mb for ColdFusion and I would rather change partition sizes once than doing it repeatedly.
Sent from my ZTE Blade using XDA app
Click to expand...
Click to collapse
That's because ColdFusion didn't have the redirect script added yet. If you add that, then 2MB is fine for it as well.
ZeChe said:
Well, I did few things.
I did what QuantumFoam suggested, partitioned my old 2GB card that was already in phone, created EXt partition of 512MB, to try if it work. I'we made backup on PC, but when I rebooted few of apps I had on sd desapeared, also all my music, pictures, wallpapers and other stuff.
Question I have now is should I copy all the things from PC back to SD and where.
Thanks all of you guys for helping me and having so much patience with me.
Click to expand...
Click to collapse
I think creating the ext partition formats the whole card. If you plug your phone into your pc and turn on usb storage, you should see it appear with ~1.5GB space. You can copy all the stuff back onto there and it should work again. You might have to reinstall the apps that were moved to the sdcard, don't know if just copying them back will work.

Amphoras said:
I think creating the ext partition formats the whole card. If you plug your phone into your pc and turn on usb storage, you should see it appear with ~1.5GB space. You can copy all the stuff back onto there and it should work again. You might have to reinstall the apps that were moved to the sdcard, don't know if just copying them back will work.
Click to expand...
Click to collapse
I did that, reinstalled few apps and it works, thx.
Have one more question, if you all don't mind
I know that these questions sound stupid, but as I said, I'm new to all of this and have a strong will to learn.
Is it possible to switch this card with bigger one I have, without flashing ROM again?
If it is, I would apritiate If someone could point me to some guide, because I presume it is not easy task and I think I bothered you enought already.
If it isn't possible, can I then format new card on my PC,copy ROM on it, partition it from CM recovery and then install ROM and all of the apps?
Thx again

[SOLVED] Nexus 7 32GB down to 6GB internal memory

I didn't want to trouble anyone, but I really couldn't find any thread on the same topic as this one.
Also, I don't have ten posts, so I can't post direct links. I'll have to post them in plain text.
I'm a generally disk-space conservative person.
When Android version 4.2.2 was released, I tried updating but without any luck (update failed).
So a couple of days later, I factory reset my Nexus 7, then I truly wiped it and proceeded to flash 4.2.2 and root the device.
No custom ROM:s.
Yesterday, I randomly checked my storage information, just to find that 4 gigabytes out of max 6 gigabytes storage was used.
See puu.sh/2fe9V for an image.
I'm a newcomer to both xda and Android and I followed several tutorials whilst doing this. One of them led to me bricking my device.
I wish I could, but I was only able to track up one of the ones I followed;
blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc (this is the one that was successful).
I'm guessing that I may possibly have accidentally created some other partion or something similar.
I would really appreciate some help in this (to me) confusing topic.

Re: [Q] Nexus 7 32GB down to 6GB internal memory
Sounds like you flashed an 8 gig image. Where did you get the image?
Sent from my Nexus 7 using xda app-developers app

rmm200 said:
Sounds like you flashed an 8 gig image. Where did you get the image?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you. That definitely sounds like a possibility.
I got mine from developers.google.com/android/nexus/images#nakasijdq39
(Sorry again for plain text links)

Zsded said:
...
So a couple of days later, I factory reset my Nexus 7, then I truly wiped it and proceeded to flash 4.2.2 and root the device.
No custom ROM:s.
...
Yesterday, I randomly checked my storage information, just to find that 4 gigabytes out of max 6 gigabytes storage was used.
See puu.sh/2fe9V for an image.
I'm guessing that I may possibly have accidentally created some other partion or something similar.
Click to expand...
Click to collapse
rmm200 said:
Sounds like you flashed an 8 gig image. Where did you get the image?
Click to expand...
Click to collapse
Could be, but then the Google factory images do not discriminate between 8/16/32, and in this case the OP used a factory image.
@Zsded
I had this happen to me the other night (in the middle of doing something else). The long & boring story follows, but let's begin with a solution: The partitioning data did not get changed, but mysteriously the /data filesystem got created with with only about 6-7 GB of capacity. Re-creating the /data filesystem using the "Format data" operation in TWRP will create an ext4 filesystem of 29 GB or so.
You need to backup everything worth saving and re-create the /data filesystem. This can be accomplished (for instance) using the "Format data" operation in TWRP. But - again - this destroys everything in /data including everything in /sdcard. (Note it does not touch /system or /cache though - so your bare ROM is still there)
What you might want to do is the following:
1) back up everything in /sdcard that you want to save
2) make a full Nandroid backup of your current ROM
3) get copies of the TWRP Nandroid backup off the device (on to the PC)
4) perform the "format data" operation in TWRP (iirc it is in the Wipe sub-menu)
5) copy your Nandroid backup back to the tablet***
6) restore the Nandroid backup (or just the data partition if you prefer)
7) Boot into the ROM and copy the saved contents of /sdcard back onto your device from your PC
*** This is a mouthful. On a fresh /data filesystem, TWRP (v2.4.1.0, anyway) wants to find its backup folders at
/data/media/TWRP/BACKUPS/<device-id>/*
But if you use MTP with the OS to copy the nandroid backup files, you will only have access to /data/media/0/* (the "sdcard" mount point) using MTP So, you might need to copy the files and then using a root shell or the custom recovery, get a copy of your TWRP folder into /data/media/ e.g. with TWRP recovery booted:
Code:
adb shell cp -R /data/media/0/TWRP/ /data/media/
OK, now for the long and boring story.
I had something identical happen to me the other night - I have a 32G N7, and it ended up showing only 6.5 GB total in /data. Because of the sequence of events involved, I don't know the exact cause, but using TWRP to re-create the /data filesystem as explained above solved the problem.
First, some background so you will know why I don't know the cause (get a beverage, this is going to be a long post):
The other night, I decided to capture Nandroid backups of every N7 factory ROM from JZO54K through JDQ39 (4.1.2 - 4.2 - 4.2.1 - 4.2.2). My plan was to do a factory install of JZ054K (4.1.2) and then apply each of the OTAs in sequence. So, I backed everything up (including using a certain busybox version of "tar" to backup about 2.5 Gigs of stuff from the /sdcard mount point), and completely wiped the device and did a fastboot install of 4.1.2 (JZO54K) nakasi (WiFi N7) factory ROM.
The ony thing that I did not do in the initial step was flash the bootloader - I left the 4.18 bootloader in place (initially). I did not follow the factory install script; instead I used the following sequence:
Code:
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format system
fastboot format userdata
fastboot format cache
fastboot flash system system.img
fastboot flash userdata userdata.img
The above installed the JZO54K factory ROM - but with the newer 4.18 bootloader still in place.
For each of the OTA package installs & nandroid backups, I would "soft-boot" TWRP (thus leaving the factory recovery still flashed on the tablet), e.g.:
Code:
C:\foo> fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
C:\foo> adb push 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip /cache/update.zip
C:\foo> adb shell sha1sum /cache/update.zip
C:\foo> adb shell
# cd /cache/recovery
# echo '--update_package=/cache/update.zip' > command
# exit
C:\foo> adb reboot recovery
... (OTA runs, device reboots into OS, perform shutdown, boot to bootloader) ...
C:\foo> fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
... take a Nandroid backup (including recovery partition!)...
Now, as it turned out, before any of this had taken place I had noticed filesystem corruption in my /system partition. Because I was making Nandroid backups for reference/archival purposes, after each OTA install, just prior to making the nandroid backup (with TWRP soft-booted as shown above), I did a filesystem check on system and data:
Code:
adb shell e2fsck -f -n /dev/block/mmcblk0p3
adb shell e2fsck -f -n /dev/block/mmcblk0p9
(for Wifi/nakasi/grouper devices, mmcblk0p3 is /system and mmcblk0p9 is /data).
The reason I mention this is that I was focused on making sure that there were no filesystem errors (there were none). Had I been paying attention, I might have noticed that something was wrong with the allocation size. But, read on...
When I finally got finished (3 OTAs and 3 Nandroid backups) I decided to restore the contents of my 2.5 Gb tarball. Nothing should been in /data except for a couple (TWRP) Nandroid backups. So, I start restoring the tarball... and after a good long wait ... tar exits due to lack of space. WTF?
Well, /data and /sdcard were mounted (in TWRP), so I did a
Code:
adb shell df -k /data
and it showed a little over 4.5 GB used ... in a 6.5 GB partition - WTF?
Now, because I wasn't watching carefully, I can't be sure what caused the small filesystem in a big partition, but here's my theory:
Because the OTAs are designed to leave /data and /data/media/* alone (more or less), that means that the /data filesystem was only created once: it would not have been destroyed & re-created by the successive application of the 3 OTA bundles that took me from JZ054K -> JOP40C -> JOP40D -> JDQ39.
To me, that says that one of the two following initial operations was the culprit:
Code:
fastboot erase userdata
fastboot format userdata
OR
Code:
fastboot flash userdata userdata.img
What is rather shocking about this is because of the way that I did things, I had the newest bootloader on the device when I did this - v4.18. I wouldn't have been surprised if an older bootloader had a bug that got fixed... but it surprises me that the very newest bootloader seems to be implicated.
But anyway - to recap - your partition data has not been altered. AFAIK, nobody (but Asus/Google) knows how to do that as it probably requires talking to the device in APX mode. Somehow, whatever recreated your filesystem in /dev/block/platform/sdhci-tegra.3/by-name/UDA ( userdata ) mysteriously created a filesystem substantially smaller than the physical partition size.
My suspicion is that it is a bug in the bootloader.
good luck

Actually all you had to do is do a factory reset in the recovery, and reboot. BAM - all your actual storage is back

Fatal1ty_18_RUS said:
Actually all you had to do is do a factory reset in the recovery, and reboot. BAM - all your actual storage is back
Click to expand...
Click to collapse
Factory Reset in the recovery does not recreate the ext4 filesystem, it only does deep removal (rm -rf) excluding /data/media. That won't solve the problem of having a tiny filesystem in a huge partition; same filesystem - same max capacity.

bftb0 said:
Factory Reset in the recovery does not recreate the ext4 filesystem, it only does deep removal (rm -rf) excluding /data/media. That won't solve the problem of having a tiny filesystem in a huge partition; same filesystem - same max capacity.
Click to expand...
Click to collapse
Strange. After I flashed the stock 4.2.1 after playing with some custom ROMs - I, too, had only 6GB available, but then I did either factory reset/wipe data or something else - and BOOM everything was fixed

bftb0 said:
Could be, but then the Google factory images...
Click to expand...
Click to collapse
Snipped to save people's screen space.
Thanks a lot! This solved my problem and I'm now back to 27 gigabytes (which should be somewhere around the promised 32 gebibytes).
I truly appreciate it. I would do more than just to thank your post, but I'm kinda out of ideas (and money).
And of course I'd like to thank everyone else for the help.
This thread can be regarded as closed.

@Fatal1ty_18_RUS
There have been a couple of other reports about "6 Gigs in a 32 GB device". I just dismissed them as folks not being aware of how much space they were using (e.g. Nandroid backups) - until it happened to me.
Enough strangeness seems to be present to make me nervous for folks that don't have a lot of *nix experience to sort things out when they get mucked up.
The other thing I didn't mention in my story was that restoring a tar file into the /sdcard mount point using a root shell in TWRP (v2.4.1.0) was sufficient to massively corrupt the ext4 filesystem on /data every time I did that (based on looking at the output of "e2fsck -f -n" in TWRP). After cleaning things up (ugh - recreating userdata ext4 from scratch means shuttling everything back onto the tablet again) I booted into the (stock) OS, and restored the same tar file into /sdcard as an unprivileged user - and no problems. No clue how/why that would happen, as tar files contain no inode information; but it suggests that there is some strangeness in the way that that emulated /sdcard mount works when a root user writes things... at least in the TWRP version of things. Very bizarre indeed.
Suffice it to say the whole exercise blew away a massive chunk of my time, even though I'm comfortable with this kind of stuff (I have used *nix systems for 30+ years). I can only imagine how folks with less experience feel when they get into a jam.
---------- Post added at 12:01 PM ---------- Previous post was at 12:00 PM ----------
Zsded said:
Snipped to save people's screen space.
Thanks a lot! This solved my problem and I'm now back to 27 gigabytes (which should be somewhere around the promised 32 gebibytes).
I truly appreciate it. I would do more than just to thank your post, but I'm kinda out of ideas (and money).
And of course I'd like to thank everyone else for the help.
This thread can be regarded as closed.
Click to expand...
Click to collapse
Cool!
Change your thread title to include the token "[SOLVED]" - maybe it can help others.
bftb0

bftb0 said:
Cool!
Change your thread title to include the token "[SOLVED]" - maybe it can help others.
bftb0
Click to expand...
Click to collapse
Good idea and thanks for your help!

is there any alterations in ghrese steps for CWM users? I too am having this problem after installing a stock image friom the same sources as posted above, but i used onw of the nexus 7 toolkits to help asist me with this.
Thabnks, i am leaving for a trip tomorrow, so i was sorta shpcked to see 6 gb of storage on my device.

GH0 said:
is there any alterations in ghrese steps for CWM users? I too am having this problem after installing a stock image friom the same sources as posted above, but i used onw of the nexus 7 toolkits to help asist me with this.
Thabnks, i am leaving for a trip tomorrow, so i was sorta shpcked to see 6 gb of storage on my device.
Click to expand...
Click to collapse
Well, given that you need to rebuild the filesystem in the userdata partition, you may not have enough time to work on this tonight, as it means getting everything worth saving backed up to a PC, and then transferring it all back after /data is rebuilt (back to the size that it should be). At that point you can either boot the "factory reset" OS to push your backups back to the tablet, or push them with adb & the recovery running so you can restore the backup before the first time you boot.
You saw how long the TWRP post was; can't say I want to do the same thing for a CWM version. Nor do I know even the first thing about any "toolkit" or what their operational hazards are.
But basically, the bottom line is re-building the /data ext4 filesystem from scratch. Even though TWRP has "mke2fs" & "tune2fs" utilities in it's ramdisk, it appears that they use a custom-built "make_ext4fs" utility for rebuilding ext4 filesystems. CWM probably has something similar - maybe a "format data" menu pick/button or something that sounds like that.
If you think you have enough time for this, you could perform the format using fastboot, as in:
Code:
fastboot format userdata
bearing in mind that this wipes EVERYTHING in /data including the psuedo-SD card (just as will any other procedure which rebuilds /data). So, if you make a Nandroid backup before starting this process, make SURE you've got your backups in a safe place off of the tablet before the format occurs.
Not having an external SD card on the N7 sure makes everything like this a pain in the a**, especially when it's potentially 20+ Gigs of stuff to move around.
good luck

So... I currently did this:
erasing 'userdata'...
OKAY [ 9.107s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 30080499712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7343872
Block groups: 225
Reserved block group size: 1024
Created filesystem with 11/1836000 inodes and 159268/7343872 blocks
sending 'userdata' (139157 KB)...
writing 'userdata'...
OKAY [ 30.145s]
finished. total time: 39.254s
Click to expand...
Click to collapse
I had to pull my CWM backup (however, doing a format data/cache using CWM didn't fix it). Eventually, the fastboot command fixed it. However, now when I try to transfer files over MTP/USB, it fails on the Internal Storage. So I am not sure why it is complaining. It doesn't give me an error, it just says the device has stopped responding, even though it is still listed and I have folders that are accessbile.
I guess I will just have to use adb push

EXT4
bftb0 said:
Factory Reset in the recovery does not recreate the ext4 filesystem, it only does deep removal (rm -rf) excluding /data/media. That won't solve the problem of having a tiny filesystem in a huge partition; same filesystem - same max capacity.
Click to expand...
Click to collapse
So where can u find the ext4 file to delete? I did this once, it was a while agao but i need to find it

fixed on my nexus 7 but not sure what happened
thanks to you guys I solved my problem, same thing after installing a stock image from google i got 8gb of storage instead of 32. I did format data on CWM and than i got all of the storage back...i was really worried of not finding a way to solve this a big thanks to you guys.
In case u have the same problem you need to do format data on CWM and NOT wipe data/factory reset.
-----------------------------------------------------------------------------------UPDATE---------------------------------------------------------------------------------​
The same problem happened again, i was not worried I did everything i did the first time but for some reason this time nothing got fixed...so after trying many things i asked myself "well what happen if I do not flash in my device the stock userdata after i erased them with the command >>fastboot erase userdata<< ?"
I tried and apparently it solved the problem i had all of my GB back. A little bit scare because during the boot in while i was on the image of the nexus logo (the X with four colors) it went back to the google screen (that one that appears when you turn on your device) but than it kept going normally. I did this two times first flashing in the stock stuff of the 4.1.2 of android and than with the 4.3 version (stock images downloaded from google)
Here the list of commands I used:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash boot (I flashed the boot image of android 4.3)
fastboot flash system (I flashed the system image of android 4.3)
For the 4.1.2 I did the same except that i flashed in the userdata image of the 4.1.2 version I turned on the device to check the space on the settings and than i came back and used >>fastboot erase userdata<< and than turned on the device to check if there were some issues but it worked and the storage was back at full size.
I ask to someone a little bit more skilled than me to explain better what happened, and what I really did, because I'm really not sure about this I mean why not flashing the userdata image that came with the full pack from google is not creating problems and flashing it makes my device loose space? I would like to understand more about this.

Thanks bftb0 for this excellent working solution.
My Nexus 7 recently wouldn't boot (bootloop after a power off for no good reason...) and I used the Nexus Root Toolkit in force mode to put 4.4 on (I was on some older version to keep Stickmount working as it didn't work straight off the bat with new Androids). I had to use force because my bootloader is 4.18 I think and the update procedure via the Root Toolkit threw an error about bootloader version. 4.4 appeared to go on fine with force. I have no idea how to update the bootloader. Just playing with GPS apps today and putting maps on and found out I couldn't do it due to lack of space. Found the box for my Nexus 7 as I wasn't 100% what size I had but thought it was a 32G... Your solution worked fine. I didn't have to move the TWRP backups, just copied them over MTP and TWRP found them.

Hello.
This is my 1st post here. Well I have the same probelm. Just bought nexus 7 32GB and 6GB is missing...

Desperion9 said:
Hello.
This is my 1st post here. Well I have the same probelm. Just bought nexus 7 32GB and 6GB is missing...
Click to expand...
Click to collapse
Does it say something like 27GB total? It's not at 32GB total because it needs room for the OS and everything.

NiteFang said:
Does it say something like 27GB total? It's not at 32GB total because it needs room for the OS and everything.
Click to expand...
Click to collapse
Also manufacturers advertise memory in base10 the decimal system so 1MB =1,000,000 bytes but computers don't work like that they operate in base2 the binary system so 1MB is actually 1,048,576 bytes. This is the brainchild of marketing gurus who think people can't understand binary.
On average for every GB advertised in base10 you get on average 70 mb less
Sent from my C5303 using xda app-developers app

Sorry for the slight necro
The same thing happened to me: coming from a custom rom and installing Nexus 7 4.4.4 factory image my 16gb device only showed 6.58gb total.
So i locked the bootloader (using WUG's) and unlocked it again. Result: it now shows 27.58Gb TOTAL SPACE LOL... I tried doing the data wipe in TWRP and i'm all out of ideas...
Anyone?

[Q] Questions regarding the two NST rooted with the same process

I rooted two nooks, and made tar backups of their partitions (I also got the dd image just in case). Out of curiosity, and with the goal of keeping minimal backup and increasing the partition for side-loaded contents to maximum, I tried to compare the contents of each partition. Since I followed the same process for rooting (Touch-Formatter v2, 1.2.1 update, NookManager, NTGAppsAttack - but before booting the Nook I got the backup), I guessed quite a lot of them are the same, and found some interesting results.
1. Boot partition is nearly the same except uRamdisk. I inspected the contents of the two uRamdisk files using bootutil by Renate, and they are identical.
-> Why are they different, and can one replace the other?
2. As we all know, rom partitions are different, but it looks only a few of them can meaningfully affect the operation. Anyway, it's small and I decided to leave them untouched and keep two separate copies.
-> What is the BCB file by the way? It just has zeroes inside. Is it automatically created if not there?
-> Some files in the devconf directory seem to be modified during the normal process or firmware update, notably BootCnt (four zero bytes), Bq275020Dffs (12 in the rombackup.zip, 13 after 1.2.1 update). What are these? Any idea?
3. The factory partition, I want to bust it (empty it up and resize it to the minimum), and let me know if I'm on a dangerous path. The idea is that I don't need rombackup.zip because I can revive the rom partition with my own tar backup if something bad happens, and it's out of date anyway after 1.2.1 update (some files in the rom partition are modified). Also, with Touch-Formatter and CWM, I wouldn't need the factory.zip file.
-> What are the files in the "touch" directory? One of my nook has them, but the other doesn't. Looking at the data inside they must be related to the display or touch screen. Maybe byproduct of calibration?
-> Can I use 1.2.1 update file with CWM instead of using Touch-Formatter, bringing it to a new fresh 1.2.1 Nook? According to this post, it seems possible.
4. The system partitions are identical, as expected. but with CWM recovery, we wouldn't need a backup of it, right?
5. The cache partition is way too big. I know the firmware update uses this space (when I resized it to something like 64MB, 1.2.1 update didn't work. I needed to increase it to something like 128MB to make it work). However, for normal operation, we surely don't need it that big.
-> How small can it be? I know it depends on individual's usage patterns... but in my case, I mostly use Nook for reading side-loaded contents. I've gone down to 32MB, but I guess that's still big.
-> Do we really need the cache partition? Can we just symlink it to somewhere in the data partition?

Out of curiosity, I just deleted BCB and BootCnt in the rom partition, and rebooted. First it said "Install Failed", a screen I have never seen before on Nook. So I looked into the rom partition and found that BCB file is recreated, but not BootCnt. On the subsequent boot, it said "Installing Rom", and then quickly rebooted. Now it's back to work. So, I guess these two files are essential for normal operation. Again, this time I deleted all files in the factory partition and also deleted BootCnt. Now, it tries to do the "Installing Rom" thing, but fell back to "Install Failed" screen. I opened up the rom partition again and I saw only BCB and BootCnt files, and none else. Nook surely formatted the rom partition first before trying to recreate it.
So I wonderfully bricked my Nook, and thought this is a good time to test if the rom partition backup works. I mounted the rom partition, untarred the backup, and rebooted. There we go, the Bronte Sisters are back. So the conclusion is that
1. When the BCB file's missing, it's simply recreated after a failed boot.
2. When the BootCnt file's missing, Nook thinks the rom partition is corrupted and tries to recreate it using rombackup.zip in the factory partition. I think this may have some side effects because firmware updates only change the files in the rom partition, leaving rombackup.zip untouched. So you will go back to the old rom partition after the built-in rom recovery.
3. The best rom recovery, I think, is using your manual backup of the rom partition. And maybe updating the rombackup.zip with a new one too?

BootCnt is a 32 bit little-endian count of the number of failed boots.
Once it hits eight your Nook will boot into the recovery image uRecImg, uRecRam.
You could also echo about anything to that file to make it arithmetically greater than 8.
Code:
echo 000 > /rom/devconf/BootCnt
That is 0x0a303030 > 8
Normally this is a B&N thing that asks you about factory restore.
If you replaced those two files it could be Clockwork Mod Recovery.

Data Partition size incorrect

Hello all,
After wiping my N7 and reinstalling stock 4.3 on my 16GB Wifi N7, I noticed that my storage is only 6.02GB total. Where did my other ~8GB go? I'm tried multiple times now to fully wipe and reinstall stock (even going back to 4.2.1 stock as well).
Any help would be very much appreciated.

Resolved!!
Found my issue:
I was using the excellent toolkit by WugFresh (v1.7.5) to push my stock images, and I had been forcing it push due to a previous error I had. This was causing my incorrect partition sizes. After pushing stock once, I unchecked the force option and pushed again. This time, the partitions came up proper.
When in panic, when in doubt: run in circles; scream and shout!

The simpliest solution is: in recovery do a wipe data/cache

Your tablet size is 8Gb ?
ROM = 512Mb
/dev directory (DON'T DELETE ! !!!!) = 1Gb
Other sys directory = 512Mb
It's normal, try to flash a stock ROM, download firmware package from Google Nexus Factory Image page (http://developers.google.com site), extract archive, connect tablet on fastboot to PC and launch "flash-all.bat"

Been there...
bigsee said:
The simpliest solution is: in recovery do a wipe data/cache
Click to expand...
Click to collapse
I did try that, and all it did was wipe the (then) ~6GB partition, but it didn't reset the size. Good thought, though.

Galaxy_Ace_Love said:
Your tablet size is 8Gb ?
ROM = 512Mb
/dev directory (DON'T DELETE ! !!!!) = 1Gb
Other sys directory = 512Mb
It's normal, try to flash a stock ROM, download firmware package from Google Nexus Factory Image page (http://developers.google.com site), extract archive, connect tablet on fastboot to PC and launch "flash-all.bat"
Click to expand...
Click to collapse
I wish I remembered to take a screenshot at the time. I've fixed the issue now, but I was definitely a wee bit panicked when I initially saw the storage size. I did try to go back to stock, but that's when I saw the storage "loss".

Any android ROM will boootloop or restart after initialization

I tried almost any ROM known to work from user's feedbacks in the XDA forums, but I couldn't get any android ROM to work on my HD2.
I have installed magldr 1.13, installed radio 2.15.50.14 (BTW, my HD2 is NOT t-mobile), installed CWM recovery*, put some android ROMs on the microSD (2GB card) and then installed android ROMs from the Android recovery.
The installation process goes fine, no warnings, no errors. After installation comes trouble, either of the next will happen:
- the phone will go in bootloop forever
- the phone will freeze on the bootscreen (freeze like the animation is still going but after hours nothing happens)
- the phone will go in soft-reboot loop. With this I mean it goes on on the boot animation, almost finishes doing whatever it was doing, and then a black screen and the boot animation will just start over and keep doing so forever.
- android will boot and do the applications installation thing (where it says "Installing apps... 10/30" or so) and when it has finished it will just reboot. On reboot it will do again the applications installation thing, and then reboot once more, and do so forever.
*I tried many recoveries: 3.0.2.4; 4.0.1.5; 5.0.2.6; 5.0.2.7; they all work fine on their own, it's just the android ROMs will go crazy. Tried different partition sizes, including 500MB system and 100MB cache, nothing changes.
I followed guides that I found on this forum, which seem to work just fine for others.
Can you help me with this? Please, my WP7 ROM is working for most things but gives me some huge troubles and lacks many apps that I need...
EDIT
Answers to obvious questions you might ask me:
Are you trying to dual-boot WP and Android? >> NO
Have you wiped before installing? >> YES, tried wiping dalvik as well
Are you using wrong ROMs? >> NO, just ROMs from NAND development section
Have you tried with GB ROMs? >> YES, same thing as with ICS/JB ROMs.
Are you trying to install ROMs with HCT Sense? >> tried one, didn't work. all others are without HTC Sense

A few things come to mind; you might have a too small data partition (i.e. gave too much to /system) or perhaps repartitioning didn't take- it's a little harder to check with magldr than cLK. If you have adb installed (or TWRP) you could boot to recovery and check with adb shell df (or df).
Have you tried with NativeSD? Repartition the sdcard in recovery (give it 1GB ext4), this will wipe the sdcard and install it as NativeSD, this would rule out any problems with the NAND (size or otherwise).

Can you give me some more info about sizing the data partition? From recovery I can only wipe the partition but it gives me no choice on how much space to give it. Also, if it helps with the issue, I tried with many system partition sizes, including the "standard" 150, 250 and 450 MB.
No, I don't have adb installed on my PC. I haven't tried to install as nativeSD yet, mainly because the card is very slow (class 2 if I remember well). I'll try though, maybe it works...

T3STY said:
Can you give me some more info about sizing the data partition? From recovery I can only wipe the partition but it gives me no choice on how much space to give it. Also, if it helps with the issue, I tried with many system partition sizes, including the "standard" 150, 250 and 450 MB.
No, I don't have adb installed on my PC. I haven't tried to install as nativeSD yet, mainly because the card is very slow (class 2 if I remember well). I'll try though, maybe it works...
Click to expand...
Click to collapse
If I recall NAND resizing is done when flashing CWM by reading a flash.cfg file, I'm thinking perhaps that the data partition (which houses dalvik) is full leading to the stall. Try installing a ROM as NativeSD (Even if your sd is slow it should at least boot) - that'll check if the issue is with something else (radio, HSPL etc.), you could try booting an SD TWRP and running df in terminal emulator (after trying to boot), to see the partition sizes and how full they are.
If you install adb - no need to install the whole sdk, you should be able to see what's causing the bootloop.

Found the issue after a dozen of trial-and-fail. Yes, the issue was that the data partition was too small (actually, it didn't exist at all).
So here's the deal. the flash.cfg file did not contain anything specific to the "data" partition. I guess it simply can't be managed from flash.cfg or for other reasons it wasn't included as an option. Unfortunately, it seems like all the guides/tutorials I have read (here on XDA, but even elsewhere) simply lack any mention about this. So for any future user having the same issue as me, the solution follows. For guide writers, if you wish you may copy-paste this to your guide. BTW, this is magldr 1.13 specific, I have no idea how cLK works.
After flashing CWM recovery, boot your phone to magldr > AD recovery. From CWM menu choose Advanced > parition sdcard. You will be asked for:
Ext size >> this is the data partition that will be used for your system
Absolute minimum size: 512MB. You'll be able to install most ROMs and boot them properly, but on first app install you might fill the whole partition
Recommended minimum size: 1024MB. You'll be able to install a handful of apps, but it's still pretty small. I have filled it with just 20 apps or so...
WARNING: don't give this partition the full sdcard or you won't have any more space for the "sdcard" partition where all your storage goes (photos, music, settings, and anything).
swap size >> a swap partition can be used to augment (read: improve efficiency, not quantity) your RAM
Any cached processes (background applications) may sit in swap when inactive. A swap partition will NOT increase your RAM to 32GB if you own such microSD card, active processes are still executed in your physical available RAM. Instead it may leave more free RAM available to active processes instead of keeping it filled with inactive applications. Please note that I strongly recommend NOT to create such partition on slow microSD cards (I'd recommend a class 6 microSD minimum). It's perfectly fine to run with no swap partition (choose 0MB size).
There you are. Now, all the ROMs that can be installed with [email protected] and [email protected] (data on sdcard) will use the newly created Ext partition.
I hope this will come useful to more people than just me
p.s. thanks for help HypoTurtle