I have read that the KF has 8GB of storage. I see two partitions.... one of them is 1GB in size and the other is 5GB
Can someone explain to me how the 8GB is divided up on the KF?
Thanks
If I understand it correctly, it has two partitions. The 1GB and a 7GB that hosts the system software and where the SD-Card section is. The 5GB you see is what's free after the system software and your stored files.
Sent from my Kindle Fire using Tapatalk
If you look at Setup -> Device you will see what the memory allocation is and what is is basically for...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The top section is Application storage and is aprox 1GB. This is where your applications are loaded along with some other data.
The top section is Internal Storage and is what you see when you plug in the device as a USB drive as the SDcard. It is less than 6GB.
It is possible to move applications in a round about way from the Application Memory to the Internal Storage segment.
Dekan54 said:
I have read that the KF has 8GB of storage. I see two partitions.... one of them is 1GB in size and the other is 5GB
Can someone explain to me how the 8GB is divided up on the KF?
Thanks
Click to expand...
Click to collapse
The 1 gb partition is for your apps, etc....the rest is for reading material. It's my understanding there are utilities to repartition. Not sure if you have to root to do that however. This is where the nook tablet and KF differ the most IMO.
Also remember, there is a difference between actual memory and usable memory. Yes, it's 8 gig but that is not a full 8 gig of usable memory (which is why you only see about 6 gig.
For example, my 8 gig flash drive only has a little over 7 gig of usable memory.
Xandralia said:
Also remember, there is a difference between actual memory and usable memory. Yes, it's 8 gig but that is not a full 8 gig of usable memory (which is why you only see about 6 gig.
For example, my 8 gig flash drive only has a little over 7 gig of usable memory.
Click to expand...
Click to collapse
It's not because of "actual memory" and "usable memory" It's because manufactures represent hard drive space using a different reference.
Here's an example for a 1 TB hard drive:
Manufacturers describe the size of their drive in multiples of 1000
1,000 GB = 1,000 * 1,000,000,000 bytes = 1,000,000,000,000 bytes.
Now let's see how many KiB that is. 1 KiB = 1,024 bytes,
so 1,0000,000,000,000 bytes = 976,562 KiB.
So how many MiB is that? 1 MiB = 1,024 KiB.
So 976,562 KiB = 953 GiB.
Operating systems measure hard drive space in GiB, even though they call it "GB".
Thank you to all that answered....
Are some Fires different?
My fire shows 2.13 GB of 5.37 GB available. No matter how I calcluate that, it is still well under 7GB for content storage. Can someone explain? Thanks.
crackedshel said:
My fire shows 2.13 GB of 5.37 GB available. No matter how I calcluate that, it is still well under 7GB for content storage. Can someone explain? Thanks.
Click to expand...
Click to collapse
C:\Programme\Android\Kindle Fire Utility\tools>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
Code:
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734296576B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Calculating size using GB still falls short of 8GB. It actually has 7376MiB of storage. And of those 7376MiB, 1134MiB is for apps/data in the data partition, and 5131MiB is for other media in the sdcard partition. Android sits on a 512MiB partition leaving 599MiB for recovery, diagnostics, bootloader, etc.
Would be nice if there was a small drive we could plug into the port to add a little more.
lmntone said:
Code:
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734296576B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Calculating size using GB still falls short of 8GB. It actually has 7376MiB of storage. And of those 7376MiB, 1134MiB is for apps/data in the data partition, and 5131MiB is for other media in the sdcard partition. Android sits on a 512MiB partition leaving 599MiB for recovery, diagnostics, bootloader, etc.
Click to expand...
Click to collapse
+ any drive and any operating system uses some of the storage space for the filesystem format info, the partition tables, the file tables and so on. So it doesn't matter if the it's 8GB or 8GiB you will never have the full 8 of it unless you leave it an unformated unusable drive. The bigger the drive the bigger the amount of it that has to reserved for the format info by the system.
I've always been confused by the partitioning since I got it as well
Granite Gargoyle said:
Would be nice if there was a small drive we could plug into the port to add a little more.
Click to expand...
Click to collapse
It's been said that the Kingston Wi-Drive will have android support soon, so that would give ya a portable hard drive you could hook up to with wifi to carry around with ya.
Starfire70 said:
It's been said that the Kingston Wi-Drive will have android support soon, so that would give ya a portable hard drive you could hook up to with wifi to carry around with ya.
Click to expand...
Click to collapse
From what I've read on other Fire forums, it already does. It sends out its own wifi signal. Cost $49 for 16gb; around $90 for 32gb.
Partition sizes given in decimal kB and MB are inaccurate.
Sizes and offsets given by parted are not exact because they are given in decimal kB and MB, rather than in binary KiB and MiB, while partitioning is done in the binary units. You can see the exact numbers from the following:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
I have no idea what '179' means, but the sizes are all in 1-KiB (i.e., 1024-byte) blocks, and all the numbers are integral multiples or integral fractions of 1024, so that the partition sizes are, except for those too small, all in integral numbers of MiB.
Related
Hi
Here is my copy of Partition Table
It's Samsung Galaxy Nexus (GSM) and its Bootloader PRIMEKL01
(parted) print
print
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
hope to be useful to whoever stuck
cheers
Thank you. I've updated additional info here:
[Info] List of Samsung Galaxy Nexus GT-I9250 devices and partitions
ytwytw said:
Hi
Here is my copy of Partition Table
It's Samsung Galaxy Nexus (GSM) and its Bootloader PRIMEKL01
(parted) print
print
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
hope to be useful to whoever stuck
cheers
Click to expand...
Click to collapse
How did you get this information?
as the title said, here i will post partition table of our ancora
Code:
Number Start (sector) End (sector) Size Code Name
1 1 212991 104.0 MiB 0700 Microsoft basic data
2 212992 213991 500.0 KiB 8300 Linux filesystem
3 213992 221183 3.5 MiB 8300 Linux filesystem
5 229376 239615 5.0 MiB 8300 Linux filesystem
6 245760 285759 19.5 MiB 8300 Linux filesystem
7 286720 292863 3.0 MiB 8300 Linux filesystem
8 294912 306175 5.5 MiB 8300 Linux filesystem
9 311296 324271 6.3 MiB 8300 Linux filesystem
10 327680 333823 3.0 MiB 8300 Linux filesystem
11 335872 342015 3.0 MiB 8300 Linux filesystem
12 344064 360447 8.0 MiB 8300 Linux filesystem
13 360448 375807 7.5 MiB 8300 Linux filesystem
14 376832 387071 5.0 MiB 8300 Linux filesystem
15 393216 1488895 535.0 MiB 8300 Linux filesystem
16 1490944 1613823 60.0 MiB 8300 Linux filesystem
17 1613824 3887103 1.1 GiB 8300 Linux filesystem
18 3891200 3993599 50.0 MiB 8300 Linux filesystem
19 3997696 3998695 500.0 KiB 8300 Linux filesystem
20 4005888 4013079 3.5 MiB 8300 Linux filesystem
21 4014080 4024319 5.0 MiB 8300 Linux filesystem
22 4030464 4070463 19.5 MiB 8300 Linux filesystem
23 4071424 4081663 5.0 MiB 8300 Linux filesystem
24 4087808 4101807 6.8 MiB 8300 Linux filesystem
25 4104192 4114431 5.0 MiB 8300 Linux filesystem
26 4120576 4130815 5.0 MiB 8300 Linux filesystem
27 4136960 4147199 5.0 MiB 8300 Linux filesystem
28 4153344 7733247 1.7 GiB 8300 Linux filesystem
well, my question regarding this data are
1. why i don't get the name of each partition ?
2. as we know, kernel block memory is mmcblk0p13, the block size is 7.5MB, is this available size only for the kernel or this size included kernel+ramdisk?
3. we got so many partition, any idea of having a hidden partition that is vacant or useable to mount other things?
thanks
i hope pep would see this post and help me
Sent from my GT-I8150
hadidjapri said:
i hope pep would see this post and help me
Sent from my GT-I8150
Click to expand...
Click to collapse
You're making me ashamed
I'll look for my notes tomorrow. Of those partitions, IIRC we (that is, me & friends in this forum) successfully identified:
* bootloader partition
* 2 (two) baseband partitions
* ROM partition
* recovery partition
As to the others... they *are* still mysterious...
-- xda app / Pristine NoMod CM9b4 / CastagnaIT kernel / GT-I8150 --
pepoluan said:
You're making me ashamed
I'll look for my notes tomorrow. Of those partitions, IIRC we (that is, me & friends in this forum) successfully identified:
* bootloader partition
* 2 (two) baseband partitions
* ROM partition
* recovery partition
As to the others... they *are* still mysterious...
-- xda app / Pristine NoMod CM9b4 / CastagnaIT kernel / GT-I8150 --
Click to expand...
Click to collapse
i got efs from arco
another question, kernel got 7.5mb space,.is this only for the kernel or kernel+ramdisk?
Sent from my GT-I8150
hadidjapri said:
another question, kernel got 7.5mb space,.is this only for the kernel or kernel+ramdisk?
Click to expand...
Click to collapse
kernel+ramdisk, and boot is 5.5mb actually. Recovery is 7.5mb.
This is the information I've gathered about the partitions.
Code:
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 61440 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 51200 mmcblk0p18 //preload
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1787904 mmcblk0p28 //internal sdcard
arco68 said:
kernel+ramdisk, and boot is 5.5mb actually. Recovery is 7.5mb.
This is the information I've gathered about the partitions.
Code:
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 61440 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 51200 mmcblk0p18 //preload
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1787904 mmcblk0p28 //internal sdcard
Click to expand...
Click to collapse
hmm what does mmcblk10-26 store sir?
Sent from my GT-I8150
You mean 19-26? No idea. Probably not used for anything. You can dd them and see if they contain something, or is just filled with zeros.
arco68 said:
You mean 19-26? No idea. Probably not used for anything. You can dd them and see if they contain something, or is just filled with zeros.
Click to expand...
Click to collapse
I once dd-ed p22, it has similar strings to p6.
A kind of backup baseband?
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
My notes from analyzing dumps and tables inside loaders (apparently the partition type IDs are listed in many of these tables):
Code:
N Size (s) Size (MiB) Size (MB) B T
1 212991 104.000 MiB 106.496 MB 0c ? (hashes)
2 1000 0.488 MiB 0.500 MB *4d DBL [/boot/qcsbl_cfg] {dbl.mbn}
3 7192 3.512 MiB 3.596 MB 46 OSBL [/boot/oemsbl, /boot/osbl] {osbl.mbn}
4 2 0.001 MiB 0.001 MB 05 (extended)
5 10240 5.000 MiB 5.120 MB 47 HBOOT [/boot/appsbl] {EMMCBOOT.MBN}
6 40000 19.531 MiB 20.000 MB 49 AMSS [/boot/modem] {amss.mbn}
7 6144 3.000 MiB 3.072 MB 58 ? (empty - 00)
8 11264 5.500 MiB 5.632 MB 48 Android boot [/boot/apps]
9 12976 6.336 MiB 6.488 MB 50 ADSP [/boot/adsp] {adsp.mbn}
10 6144 3.000 MiB 3.072 MB 4a ? (random) [/boot/modem_fs1]
11 6144 3.000 MiB 3.072 MB 4b ? (random) [/boot/modem_fs2]
12 16384 8.000 MiB 8.192 MB 90 Android /persist (ext4)
13 15360 7.500 MiB 7.680 MB 91 Android recovery
14 10240 5.000 MiB 5.120 MB 92 ? (region ID) {emmcparam.bin}
15 1095680 535.000 MiB 547.840 MB 93 Android /system (ext4)
16 122880 60.000 MiB 61.440 MB 94 Android /cache (ext4)
17 2273280 1110.000 MiB 1136.640 MB 95 Android /data (ext4)
18 102400 50.000 MiB 51.200 MB 96 Android /preload (ext4)
19 1000 0.488 MiB 0.500 MB 97 ? (empty - 00)
20 7192 3.512 MiB 3.596 MB 98 ? (empty - 00) [/boot/osbl_bkp?]
21 10240 5.000 MiB 5.120 MB 99 HBOOT backup [/boot/appsbl_bkp]
22 40000 19.531 MiB 20.000 MB 9a AMSS backup [/boot/modem_bkp]
23 10240 5.000 MiB 5.120 MB 9b ? (empty - 00) [/boot/apps_bkp]
24 14000 6.836 MiB 7.000 MB 9c Android (boot image?) [/boot/adsp_bkp?]
25 10240 5.000 MiB 5.120 MB 9d ? (empty - 00)
26 10240 5.000 MiB 5.120 MB 9e ? (empty - 00)
27 10240 5.000 MiB 5.120 MB 9f Android /efs (ext2)
28 3575808 1746.000 MiB 1787.904 MB a0 Android /sdcard (FAT16)
Partitions: 7639521 3730.235 MiB 3819.760 MB
Holes: 89631 43.765 MiB 44.816 MB
Total sectors: 7729152 3774.000 MiB 3864.576 MB
Apparently some partitions were intended to store backup copies of bootloaders, AMSS, ADSP and the Android boot image; however, there are some mismatches between tables in OSBL and APPSBL, as well as apparently wrong partition sizes — e.g., the OSBL table lists the partition type 0x9b as /boot/apps_bkp, but this partition (mmcblk0p23) is too small to contain the actual boot.img, and the boot image backup is actually stored in mmcblk0p24, which was intended for ADSP backup.
sigprof said:
My notes from analyzing dumps and tables inside loaders (apparently the partition type IDs are listed in many of these tables):
Code:
N Size (s) Size (MiB) Size (MB) B T
1 212991 104.000 MiB 106.496 MB 0c ? (hashes)
2 1000 0.488 MiB 0.500 MB *4d DBL [/boot/qcsbl_cfg] {dbl.mbn}
3 7192 3.512 MiB 3.596 MB 46 OSBL [/boot/oemsbl, /boot/osbl] {osbl.mbn}
4 2 0.001 MiB 0.001 MB 05 (extended)
5 10240 5.000 MiB 5.120 MB 47 HBOOT [/boot/appsbl] {EMMCBOOT.MBN}
6 40000 19.531 MiB 20.000 MB 49 AMSS [/boot/modem] {amss.mbn}
7 6144 3.000 MiB 3.072 MB 58 ? (empty - 00)
8 11264 5.500 MiB 5.632 MB 48 Android boot [/boot/apps]
9 12976 6.336 MiB 6.488 MB 50 ADSP [/boot/adsp] {adsp.mbn}
10 6144 3.000 MiB 3.072 MB 4a ? (random) [/boot/modem_fs1]
11 6144 3.000 MiB 3.072 MB 4b ? (random) [/boot/modem_fs2]
12 16384 8.000 MiB 8.192 MB 90 Android /persist (ext4)
13 15360 7.500 MiB 7.680 MB 91 Android recovery
14 10240 5.000 MiB 5.120 MB 92 ? (region ID) {emmcparam.bin}
15 1095680 535.000 MiB 547.840 MB 93 Android /system (ext4)
16 122880 60.000 MiB 61.440 MB 94 Android /cache (ext4)
17 2273280 1110.000 MiB 1136.640 MB 95 Android /data (ext4)
18 102400 50.000 MiB 51.200 MB 96 Android /preload (ext4)
19 1000 0.488 MiB 0.500 MB 97 ? (empty - 00)
20 7192 3.512 MiB 3.596 MB 98 ? (empty - 00) [/boot/osbl_bkp?]
21 10240 5.000 MiB 5.120 MB 99 HBOOT backup [/boot/appsbl_bkp]
22 40000 19.531 MiB 20.000 MB 9a AMSS backup [/boot/modem_bkp]
23 10240 5.000 MiB 5.120 MB 9b ? (empty - 00) [/boot/apps_bkp]
24 14000 6.836 MiB 7.000 MB 9c Android (boot image?) [/boot/adsp_bkp?]
25 10240 5.000 MiB 5.120 MB 9d ? (empty - 00)
26 10240 5.000 MiB 5.120 MB 9e ? (empty - 00)
27 10240 5.000 MiB 5.120 MB 9f Android /efs (ext2)
28 3575808 1746.000 MiB 1787.904 MB a0 Android /sdcard (FAT16)
Partitions: 7639521 3730.235 MiB 3819.760 MB
Holes: 89631 43.765 MiB 44.816 MB
Total sectors: 7729152 3774.000 MiB 3864.576 MB
Apparently some partitions were intended to store backup copies of bootloaders, AMSS, ADSP and the Android boot image; however, there are some mismatches between tables in OSBL and APPSBL, as well as apparently wrong partition sizes — e.g., the OSBL table lists the partition type 0x9b as /boot/apps_bkp, but this partition (mmcblk0p23) is too small to contain the actual boot.img, and the boot image backup is actually stored in mmcblk0p24, which was intended for ADSP backup.
Click to expand...
Click to collapse
is it possible partition number 19-26 are intended to be backup partition?
Sent from my GT-I8150
Could phone operator lock code be stored in one of the (normally unmounted) partitions?
Sent from my GT-I8150 using xda app-developers app
I used "parted /dev/block/mmcblk0" to make my /data partition larger and my /sdcard partition smaller. I also swapped the internal and external SD card mount points, but that works as expected.
Well, repartitioning "worked" in that the partition table and "/proc/partitions" show them as their new sizes and "dd if=/dev/block/mmcblk0p10" of=/dev/null" writes the correct amount of data and doesn't stall.
The problem is that the OS shows and uses the old filesystem size for /data and 0.00b for the /sdcard (that's not where it is, but you know what I mean).
It's not just because the wrong info is being displayed, but is still the correct size, I can't write more than 2GB of data to /data.
-- Visual Aids --
Code:
(parted) print
Model: MMC MAG4FA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 369MB 315MB ext4 CACHE
8 369MB 386MB 16.8MB MODEM
9 386MB 923MB 537MB ext4 FACTORYFS
[B]10 923MB 15.4GB 14.5GB ext4 DATAFS[/B]
11 15.4GB 15.8GB 327MB fat32 UMS msftres
----
Code:
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 1280 mmcblk0p2
179 3 1280 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 307200 mmcblk0p7
259 0 16384 mmcblk0p8
259 1 524288 mmcblk0p9
[B]259 2 14163968 mmcblk0p10[/B]
259 3 319488 mmcblk0p11
179 16 512 mmcblk0boot1
179 8 512 mmcblk0boot0
253 0 31166976 cyasblkdevblk0
253 1 31165952 cyasblkdevblk0p1
----
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
----
----
----
Nobody?
Device Name: Xiaome Redmi 1s
Redmi 1S partition table
Fdisk
Code:
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
256 heads, 63 sectors/track, 946 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 266306 2147483647+ ee EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
phys=(1023, 255, 63) logical=(266305, 4, 4)
Parted
Code:
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
p
Model: MMC M8G1GC (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 2097kB 2080kB sbl1
2 2097kB 4177kB 2080kB sbl1bak
3 4177kB 5225kB 1049kB rpm
4 5225kB 6274kB 1049kB rpmbak
5 6274kB 7323kB 1049kB tz
6 7323kB 8371kB 1049kB tzbak
7 8371kB 8379kB 8192B ssd
8 8379kB 9428kB 1049kB sdi
9 9428kB 10.5MB 1049kB DDR
10 10.5MB 14.7MB 4194kB aboot
11 14.7MB 18.9MB 4194kB abootbak
12 18.9MB 24.1MB 5243kB bk1
13 24.1MB 28.3MB 4194kB misc
14 28.3MB 36.7MB 8389kB logo
15 36.7MB 67.1MB 30.4MB bk2
16 67.1MB 68.7MB 1573kB modemst1
17 68.7MB 70.2MB 1573kB modemst2
18 70.2MB 70.3MB 1024B fsc
19 70.3MB 134MB 64.0MB bk3
20 134MB 136MB 1573kB fsg
21 136MB 168MB 32.0MB bk4
22 168MB 201MB 33.6MB bk5
23 201MB 268MB 67.1MB fat16 modem
24 268MB 285MB 16.8MB boot
25 285MB 302MB 16.8MB recovery
26 302MB 336MB 33.6MB ext4 persist
27 336MB 1174MB 839MB ext4 system
28 1174MB 1577MB 403MB ext4 cache
29 1577MB 7818MB 6241MB ext4 userdata
(parted)
gdisk
Code:
gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk /dev/block/mmcblk0: 15269888 sectors, 7.3 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 32 entries
First usable sector is 34, last usable sector is 15269854
Partitions will be aligned on 2-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 34 4095 2.0 MiB FFFF sbl1
2 4096 8157 2.0 MiB 0700 sbl1bak
3 8158 10205 1024.0 KiB FFFF rpm
4 10206 12253 1024.0 KiB 0700 rpmbak
5 12254 14301 1024.0 KiB FFFF tz
6 14302 16349 1024.0 KiB 0700 tzbak
7 16350 16365 8.0 KiB FFFF ssd
8 16366 18413 1024.0 KiB FFFF sdi
9 18414 20461 1024.0 KiB FFFF DDR
10 20462 28653 4.0 MiB FFFF aboot
11 28654 36845 4.0 MiB 0700 abootbak
12 36846 47085 5.0 MiB 8300 bk1
13 47086 55277 4.0 MiB FFFF misc
14 55278 71661 8.0 MiB 8300 logo
15 71662 131061 29.0 MiB 8300 bk2
16 131062 134133 1.5 MiB FFFF modemst1
17 134134 137205 1.5 MiB FFFF modemst2
18 137206 137207 1024 bytes FFFF fsc
19 137208 262133 61.0 MiB 8300 bk3
20 262134 265205 1.5 MiB FFFF fsg
21 265206 327669 30.5 MiB 8300 bk4
22 327670 393205 32.0 MiB 8300 bk5
23 393206 524277 64.0 MiB 0700 modem
24 524278 557045 16.0 MiB FFFF boot
25 557046 589813 16.0 MiB FFFF recovery
26 589814 655349 32.0 MiB 0700 persist
27 655350 2293749 800.0 MiB 0700 system
28 2293750 3080181 384.0 MiB 0700 cache
29 3080182 15269854 5.8 GiB 0700 userdata
planning to make changes with this Partition table :-]
but thinking what to expand.......
Userdata or System by shrinking /Cache
:-]
will make thread soon with all info and guide .
OH NO!!!
I accidentally erased tz partition. So will 'dd'ing tz.mbn to /dev/sdb5(here) work? Please help, my phone is completely dead, not even fastboot. X|
generex144 said:
I accidentally erased tz partition. So will 'dd'ing tz.mbn to /dev/sdb5(here) work? Please help, my phone is completely dead, not even fastboot. X|
Click to expand...
Click to collapse
dnt wrry, i have gone through this..
this will help you..
http://en.miui.com/thread-54139-1-1.html
NOTE- donwload ,install usb 9006 & 9008 drivers properly and before start charge battery with external charger or with spare phone... battery should b in phone else it wont switch 9006 to 9008 mode...
Is the partition table not resetted if I fastboot flashed a stock img onto the phone? I've tried it thrice but it stops at the cache partition giving me this error:
Code:
Unspecified error(0x80004005: FAILED (remote: size too large)
Hi all! I have Kindle Fire HD 8.9 (root, stock 8.4.9), locked with password. My niece tried log in, she enters the password several times, but could not enter, then she just turned off(press power off button). When I tried to enter, the system is don’t requested a password, language was French, and all of the data disappeared since the beginning of 2015. Yes, I know, I need to backup, but I keep going use it.
Later I known in this model, if lead many times an incorrect password, it launch a factory reset, or proposes to do so, my niece does not know English, so ...............
I have read a few instructions, and was able to rooted again and download to my computer directly from the tablet dump memory:mmcblk0 from /dev/block/*. This is the largest unit, so that it should contain all the data, also i download mmcblkp13 /dev/block/platform/omap/omap_hsmmc.1/ *. It is the user's data. All in *.raw format. Scan R-studio and other programs, but all I found was data information from the default firmware.
I read that when you reset, the data do not disappear completely. Then I found one file, I think it only indicates what happened:
last log file:
Starting recovery on Fri Jul 15 18:33:45 2016
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/sda1 (null) 0
2 /system ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/system (null) 0
3 /cache ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache (null) 0
4 /data ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata (null) 0
5 /misc emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (null) 0
6 /boot emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/boot (null) 0
7 /recovery emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery (null) 0
8 /bootloader emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader (null) 0
9 /xloader emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/xloader (null) 0
I:Boot command: boot-recovery
I:Got arguments from /cache/recovery/command
Battery capacity = 99%
Battery temp = 235 (in dCdegree)
Battery status = discharging
stat() of /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata succeeded on try 1
Command: "/sbin/recovery" "--wipe_data" "--batt_level=40"
Recovery counter: 0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=8.4.7_user_4730020
ro.build.version.number=04730020
ro.build.version.name=8.4.7
ro.build.lab126.buildtype=Nightly
ro.build.lab126.build=300
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Aug 2 17:18:29 PDT 2013
ro.build.date.utc=1375489109
ro.build.type=user
ro.build.user=ubuntu
ro.build.host=ip-10-222-195-0
ro.build.tags=test-keys
ro.build.platform.version=UNKNOWN
ro.product.model=KFJWI
ro.product.brand=Amazon
ro.product.name=Kindle Fire
ro.product.device=Kindle
ro.product.board=blaze_tablet
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Amazon
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=jem
ro.build.description=jem-user 4.0.4 IMM76D 8.4.7_user_4730020 test-keys
ro.build.fingerprint=Android/jem/jem:4.0.4/IMM76D/8.4.7_user_4730020:user/test-keys
ro.build.characteristics=tablet
rild.libpath=/system/lib/libril-lab126qmi.so
com.ti.omap_enhancement=true
opencore.asmd=1
keyguard.no_require_sim=1
wifi.interface=wlan0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.sf.lcd_density=240
ro.opengles.version=131072
omap.audio.mic.main=AMic0
omap.audio.mic.sub=AMic1
omap.audio.power=PingPong
sys.usb.vid=1949
sys.usb.pid=0008
ro.camera.sound.forced=0
dolby.audio.sink.info=speaker
ro.lab126.skipscreenshots=1
persist.lab126.sys.usb.mtp=1
com.lab126.reap=1
com.lab126.trim=1
pcb.temp.sensor.sysfs.node=/sys/devices/platform/omap/omap_i2c.3/i2c-3/3-0070/temp1_input
batt.temp.sensor.sysfs.node=/sys/class/power_supply/bq27541/temp
cpu.temp.sensor.sysfs.node=/sys/devices/platform/omap/omap_temp_sensor.0/temp1_input
hotspot.temp.sensor.sysfs.node=/sys/class/thermal_sensor/thermal_sensor0/device/hotspot_temp
charge.current.sysfs.node=/sys/class/power_supply/smb347_usb/device/charge_current
ro.sf.hwrotation=90
telephony.sms.send=false
persist.whirlwind.enabled=0
persist.whirlwind.unplugged=0
persist.whirlwind.bandscan=0
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
hwui.render_dirty_regions=false
persist.hwc.mirroring.region=0:0:1920:1200
persist.hwc.mirroring.transform=1
persist.lab126.chargeprotect=1
persist.lab126.touchnoisereject=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=B0CC0603302501R0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=bowser
ro.revision=0
ro.product.processor=omap4470
init.svc.watchdog=running
init.svc.recovery=running
Formatting /data...
Creating filesystem with parameters:
Size: 60814262272
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14847232
Block groups: 454
Reserved block group size: 1024
Created filesystem with 11/3711904 inodes and 279050/14847232 blocks
Formatting /cache...
Creating filesystem with parameters:
Size: 681574400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6944
Inode size: 256
Journal blocks: 2600
Label:
Blocks: 166400
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41664 inodes and 5415/166400 blocks
Time spent in the recovery: 124.00 seconds
I'm worried about Null 0 operation - whats it is mean?
Its list of partitition:
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0boot0: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0boot0 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0boot1: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0boot1 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p13: 60.8 GB, 60814262272 bytes
4 heads, 16 sectors/track, 1855904 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p13 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p12: 681 MB, 681574400 bytes
4 heads, 16 sectors/track, 20800 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p11: 929 MB, 929038336 bytes
4 heads, 16 sectors/track, 28352 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p10: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p9: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p8: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p7: 67 MB, 67108864 bytes
4 heads, 16 sectors/track, 2048 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p6: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p5: 0 MB, 2048 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p4: 0 MB, 16384 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p3: 0 MB, 65536 bytes
4 heads, 16 sectors/track, 2 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p2: 0 MB, 262144 bytes
4 heads, 16 sectors/track, 8 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p2 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p1: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p1 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0: 62.5 GB, 62537072640 bytes
256 heads, 63 sectors/track, 7573 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/omap/omap_hsmmc.1/mmcblk0p1 1 7574 61071359+ ee EFI GPT
Maybe someone knows, there can be a way to raise the data may have some manipulation of data blocks or there are nothing here, all the data were erase and it makes no sense to do something(special firm ), so the question for those who understand?
I'm curious as to what command you used to dump the kindle data. If you used ADB's backup mechanisms, I don't see why you couldn't restore via ADB as well. If you directly ran dd (either on the device or through a shell on a computer connected to it), that's a little more complex. Also, how big are your backup files, and what partition(s) did you dump?
Hi! I used instructions in this thread http://forum.xda-developers.com/showthread.php?t=1818321
I found blocks of partition on my device in these paths: /dev/block/platform/omap/omap_hsmmc.1/* and /dev/block/* .They have mmcblk0* names, mmcblk0 and 13 parts, they have names mmcblk0p1-mmcblk0p13. Block mmcblk0 - largest, he contain all blocks, mmcblk0p13-user data, he also big. So I copy mmcblk0 (62,5gb) and mmcblk0p13(60,8gb) block in *.raw format directly to my PC( I have kindle with 64gb version). I scanned with the R-studio/R-Linux these blocks and i found nothing, only files and folders from usual default stock firmware. It looks like I have a new tablet from shop, all information that i have before it is gone(before it happened, my tablet was rooted, so in system folder left root checker app, and from previous google account, apps and also all that i did with system before-for example removed stock app-office ). So can you look in information that i found in last_log.txt file above. There the same date and time, when i think tablet launch factory reset itself, it contain "(null) 0" operation in each block of partitions and i think it erase permanently all my data. I think it didn’t was a usual factory reset, i think it feature was added by Amazon to reset all tablets they receive from buyers, but I didn’t know about that.