Galaxy Tab 10.1 shows only 13gb instead of 32gb - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hey Guys,
I have read all over the internet for a possible solution and have not been able to find one. I will list the things i have tried:
I own a Galaxy Tab 10.1 3G.
a) Return to stock 4.0.4 and factory reset.
b) Flash .pit file.
c) Return to stock 3.2 and factory reset.
d) Flash stock recovery and reset.
I have used df to see the partitions table, the data partition is 13gb and the sdcard partition is 13gb again. so i am guessing the culprit is the data partition. please help me get my partitions.
Regards,
Kalpak.

---

bump. no one?

---

I am surprised no one else is facing a similar issue. Can anyone please help me? I am running stock 3.2 right now. My sdcard partition is 16gb and my data partition is 16gb again so please help me regain my space back.

---

kalpak2021 said:
Hey Guys,
I have read all over the internet for a possible solution and have not been able to find one. I will list the things i have tried:
I own a Galaxy Tab 10.1 3G.
a) Return to stock 4.0.4 and factory reset.
b) Flash .pit file.
c) Return to stock 3.2 and factory reset.
d) Flash stock recovery and reset.
I have used df to see the partitions table, the data partition is 13gb and the sdcard partition is 13gb again. so i am guessing the culprit is the data partition. please help me get my partitions.
Regards,
Kalpak.
Click to expand...
Click to collapse
You need to verify that the PIT file is for the 32 Gb, then install it using ODIN with the "Re-Partition" checkbox checked.
You can see the size of the partitions using fdisk - what df does is to tell you the size of the filesystem on that partition; if something went wrong and formatted only 16Gb of your data partition even though it's got 32Gb allocated, then you'll need to re-create that filesystem.
The most likely cause is that you installed a 16Gb PIT file.
You can find a PIT file editor here: http://forum.xda-developers.com/showthread.php?t=1916936

---

k1mu said:
You need to verify that the PIT file is for the 32 Gb, then install it using ODIN with the "Re-Partition" checkbox checked.
You can see the size of the partitions using fdisk - what df does is to tell you the size of the filesystem on that partition; if something went wrong and formatted only 16Gb of your data partition even though it's got 32Gb allocated, then you'll need to re-create that filesystem.
The most likely cause is that you installed a 16Gb PIT file.
You can find a PIT file editor here: http://forum.xda-developers.com/showthread.php?t=1916936
Click to expand...
Click to collapse
Thanks for your reply. But i tried using fdisk and pit magic (could not understand anything) without much help. fdisk -l shows nothing.
and i did an fdisk /dev/block/mmblk* -l and i'm quoting the results.
Code:
Disk /dev/block/mmcblk0: 15.7 GB, 15756951552 bytes
4 heads, 16 sectors/track, 480864 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p1: 12 MB, 12582912 bytes
4 heads, 16 sectors/track, 384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p1 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p10: 314 MB, 314572800 bytes
4 heads, 16 sectors/track, 9600 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p2: 5 MB, 5242880 bytes
4 heads, 16 sectors/track, 160 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p2 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p3: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p4: 606 MB, 606076928 bytes
4 heads, 16 sectors/track, 18496 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p5: 469 MB, 469762048 bytes
4 heads, 16 sectors/track, 14336 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p6: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p7: 12 MB, 12582912 bytes
4 heads, 16 sectors/track, 384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p8: 14.3 GB, 14305198080 bytes
4 heads, 16 sectors/track, 436560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p9: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p9 doesn't contain a valid partition table
also, i am attaching the .pit file i used to flash.

---

kalpak2021 said:
Thanks for your reply. But i tried using fdisk and pit magic (could not understand anything) without much help. fdisk -l shows nothing.
and i did an fdisk /dev/block/mmblk* -l and i'm quoting the results.
Code:
Disk /dev/block/mmcblk0: 15.7 GB, 15756951552 bytes
Disk /dev/block/mmcblk0p1: 12 MB, 12582912 bytes
Disk /dev/block/mmcblk0p10: 314 MB, 314572800 bytes
Disk /dev/block/mmcblk0p2: 5 MB, 5242880 bytes
Disk /dev/block/mmcblk0p3: 8 MB, 8388608 bytes
Disk /dev/block/mmcblk0p4: 606 MB, 606076928 bytes
Disk /dev/block/mmcblk0p5: 469 MB, 469762048 bytes
Disk /dev/block/mmcblk0p6: 2 MB, 2097152 bytes
Disk /dev/block/mmcblk0p7: 12 MB, 12582912 bytes
Disk /dev/block/mmcblk0p8: 14.3 GB, 14305198080 bytes
Disk /dev/block/mmcblk0p9: 8 MB, 8388608 bytes
Click to expand...
Click to collapse
OK, so you've got a /dev/block/mmcblk0 with 15.7 GB. That's apparently the cause of your problem.
Your attached PIT file looks very strange to me, which probably means that I don't understand what PIT Magic is saying. The partition sizes in that file are all too small.
You'll need to find yourself a good .PIT file.
Does anyone know if there's some way of extracting the PIT from a working device?

---

Heimdall can download PIT files from devices from Download mode
Sent from my GT-P7510

---

dave106 said:
Heimdall can download PIT files from devices from Download mode
Sent from my GT-P7510
Click to expand...
Click to collapse
i would like to apologize for such a delayed reply. i am trying to extract the pit file using heimdall but i am getting a "Failed to initialize protocol" error.
Any help would be appreciated.

---

Some Progress
Some progress guys. Here's a report.
I have been trying for over three hours to get the .pit extracted from the tab and after three tiresome hours (and a little backache), i have successfully extracted the .pit from the tab. So here it goes, first i tried to run the heimdall 1.3.1 on a windows 8 machine, wasted around half an hour and then figured there's something wrong with this version. The next thing i did was looked for a build of 1.4RC1 for windows, could not find. So i downloaded Ubuntu 12.10, ran it in virtualbox. Now, another daunting task was to get rid of unity 3d and install Gnome 3 cuz Unity was sluggish as ****.. Next thing, i download a prebuild version which refuses to work so i build my own heimdall from this link and voila, it worked. Phew!
Now, enough of stories. Here is the print-pit output.
Code:
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "SEC DEV"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Entry Count: 17
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 0
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SMD
Flash Filename: emmc.img
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 6
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BCT
Flash Filename: bct.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PT
Flash Filename:
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EBT
Flash Filename: bootloader.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EB2
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 8
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GP1
Flash Filename: fusetrigger.bin
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 24
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 10
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SOS
Flash Filename: recovery.img
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: LNX
Flash Filename: boot.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 1156
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APP
Flash Filename: system.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 896
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CAC
Flash Filename: cache.img
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MSC
Flash Filename:
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 24
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MDM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 27285
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UDA
Flash Filename: data.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename:
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HID
Flash Filename: hidden.img
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GPT
Flash Filename:
FOTA Filename:
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
I am also attaching the generated .pit file. I am attaching the generated heimdall too in case anyone needs it. Cheers. :good:

---

BUMP, anyone?

---

Hi! did you found solution?
i have similar problem. my system partiotn is 19gb and tablet was 32gb ...now i have 2gb free
cant find what to do ....how to repait it

---

mxmone said:
Hi! did you found solution?
i have similar problem. my system partiotn is 19gb and tablet was 32gb ...now i have 2gb free
cant find what to do ....how to repait it
Click to expand...
Click to collapse
no mate. i haven't found any solution yet. i am planning to take it to service center as a last resort.

---

Hi! i revert back to previous nandroid backup and all back to normal ( i mean size of system partiotion ) ...as i can see problem is this rom..it have pid file or something like this for 16gb version and not for 32gb.
so just restore you nandroid backup ....

---

mxmone said:
Hi! i revert back to previous nandroid backup and all back to normal ( i mean size of system partiotion ) ...as i can see problem is this rom..it have pid file or something like this for 16gb version and not for 32gb.
so just restore you nandroid backup ....
Click to expand...
Click to collapse
the sad thing is i dont have one. any other suggestion mate?

---

you always can try to install different roms or just try to download from samsung stock image and flash it
try to look for 32gb roms .
http://www.sammobile.com/firmwares/#osa ( stock samsung roms)

---

kalpak2021 said:
Hey Guys,
I have read all over the internet for a possible solution and have not been able to find one. I will list the things i have tried:
I own a Galaxy Tab 10.1 3G.
a) Return to stock 4.0.4 and factory reset.
b) Flash .pit file.
c) Return to stock 3.2 and factory reset.
d) Flash stock recovery and reset.
I have used df to see the partitions table, the data partition is 13gb and the sdcard partition is 13gb again. so i am guessing the culprit is the data partition. please help me get my partitions.
Regards,
Kalpak.
Click to expand...
Click to collapse
Or you had repartion in the wrong way. Try Reset again.

---

I have tried multiple roms.. I have tried flashing pit too. The only hope was to extract the pit using Heimdall and flash it via odin or heimdall itself. Tried both but I get a red colored message on my screen which I'm guessing is due to a locked boatloader. So I will have to go to the service center itself.