Hi - I have a rooted Galaxy Nexus running 4.0.3 ICS and decided to connect up to my work Exchange server. They enforce a security policy that requires the phone to be encrypted. I ran the hour long encryption process and it all runs fine. Now I want to remove work email and do a factory reset. This is where I run into problems.
I run the gui factory reset, the phone reboots but never resets. I boot into recovery mode and attempt the reset but it can't mount /sdcard so the reset doesn't happen.
Any ideas to assist would be appreciated.
OK, so after an entire day at work (!!) I managed to work out that I needed to blow away my /data/media (/sdcard on Galaxy Nexus) partition which was encrypted and recreate. That was no mean feat ! But now I am well versed in the use of ADB and Fastboot !
So I managed to push up the 'parted' tool to remove and create my partition 12. I then recreated it and converted to ext3 then ext4. So now I have a working phone again and will not be encrypting it again !
The problem I have is that I can not remember the original partition size. What I have recreated is shown below.
~ # 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
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 ext4 cache
12 1218MB 15.4GB 14.2GB ext4 userdata
(parted)
Can someone please tell me what their Galaxy Nexus partition table looks like ? I am not sure if it makes any difference, but I am with Telstra here in Australia and have a 16GB Nexus.
Any help is appreciated.
Sorry for my English.
I have NT 16G with CM7. After waking device from sleep, I was unable to toggle wi-fi state, it stuck on "Turning off.." message. When I tried to restart tablet, it shutdown but not boot up. Just stuck with blank screen and backlight on. So I held power button to shut it off. Then turn it on again.
After that, I can't change anything in internal memory. Device turns on and works for some time, but then restarts on it's own and go back to state before wi-fi problem. Any changes, as new/removed files, applications etc, revert back. Even full wipe via Ubuntu didn't work: after reboot everything back to previous state.
In dmesg I have message
Code:
mmcblk0: retrying using single block read
Any suggestions?
Can you boot into cwm? Try fixing permissions and try again.
soshite said:
Can you boot into cwm? Try fixing permissions and try again.
Click to expand...
Click to collapse
It didn't change anything. Looks like I have hardware damage. Is it possible?
Its a kernel regression, you need to format that mmcblk0 and re-create.
If this doesn't work sent for replacement as it may be a faulty chip.
How can I format it? It doesn't accept any changes. Is there any other way?
Reformatting the internal partition can be a screwy and hard thing to do. Not because it's hard to format, but simply because it's hard to retrieve the original table. Because the first 4 partitions are very secure, They need to be matching perfectly with Barnes & Noble's partition table. I recommend you just try my guide on unbricking stuff:
http://forum.xda-developers.com/showthread.php?t=1605664
I've tried your method too, with no results.
mm_d said:
I've tried your method too, with no results.
Click to expand...
Click to collapse
Interesting. :l Have you tried booting off the sdcard? What do your partition table look like? Do you have it by any chance?
Yes, I boot via sdcard into CWM, CM7, Ubuntu. From sdcard everything works.
parted output don't show anything unusual
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
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 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 13.6GB 12.0GB fat32 media msftres
11 13.6GB 15.9GB 2315MB ext4 userdata
mm_d said:
Yes, I boot via sdcard into CWM, CM7, Ubuntu. From sdcard everything works.
parted output don't show anything unusual
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
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 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 13.6GB 12.0GB fat32 media msftres
11 13.6GB 15.9GB 2315MB ext4 userdata
Click to expand...
Click to collapse
So everything looks fine. Have you dumped xloader bootloader recovery and boot partition using lavero.burgos. images??
Sent from my NookTablet using XDA
dd back the partitions, you will find a backup of them if you search the forum
I've tried it already. It didn't change anything.
Any errors?
No.
So remove partitions 1by1 format and re-create.
I cant see anything else to work.
You can use a custom recovery with excellent tools for you made by meghd00.
I recommend to use that.
After this report back.
I've tried meghd00t method already. No results.
parted log
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) print
print
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
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 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 13.6GB 12.0GB fat32 media msftres
11 13.6GB 15.9GB 2315MB ext4 userdata
(parted) rm 11
rm 11
(parted) rm 10
rm 10
(parted) rm 8
rm 8
(parted) print
print
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
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 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 13.6GB 12.0GB fat32 media msftres
11 13.6GB 15.9GB 2315MB ext4 userdata
Are you on linux?
Yes.
mm_d said:
Yes.
Click to expand...
Click to collapse
sudo fdisk /dev/block/mmcblk0
demetris_I said:
sudo fdisk /dev/block/mmcblk0
Click to expand...
Click to collapse
You talking about tablet or PC?
I have bricked Nook Tablet BNTV250A (8gb) that I can't flash on any Rom. My partishions are completly missied so I can't even Restore from Factory.
But I still can boot from SD.
When I look my partishon I see this
~ # cat proc/partitions
major minor #blocks name
179 0 7766016 mmcblk0
179 1 7764992 mmcblk0p1
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15632384 mmcblk1
179 97 50176 mmcblk1p1
~ #
Can somebody help me and can I boot this tablet into Rom anyway? As I undestend my factory info (as MAC address) is dead but if you have any ideas I be happy.
Thank you.
Have you tried using repart.img at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
digixmax said:
Have you tried using repart.img at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
Click to expand...
Click to collapse
When I try to restore Nook Tablet to stock i see red X. Now I try binary for repart
Binary from this thead and my recovery shows simulair error:
http://forum.xda-developers.com/showthread.php?t=1513583
I try and reply.
digixmax said:
Have you tried using repart.img at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
Click to expand...
Click to collapse
I do all correctly?
[email protected]:~$ adb shell
~ # cd sdcard
/sdcard # parted /dev/block/mmcblk0 print
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No? yes
yes
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? Fix
Fix
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 425952 blocks) or
continue with the current setting?
Fix/Ignore? Fix
Fix
Model: MMC 008G4B (sd/mmc)
Disk /dev/block/mmcblk0: 7952MB
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 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 5620MB 4010MB fat32 media
11 5620MB 7734MB 2114MB ext4 userdata
digixmax said:
Have you tried using repart.img at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
Click to expand...
Click to collapse
Thanks so mutch! I after first step flash stock recovery and it works!
Disclaimer: I am not responsible for bricked devices, obviously
Unlike most people here, I do not find the "dual-boot" feature particularly useful due to its buggyness and quirky configuration plus it made the available space for the /system partition divided, leaving only 600++ MB for each system1 and system2. This guide is using CWM v6.0.5.1 (R11) by furniel and donbo.
Prerequisites:
CWM Recovery V6.0.5.1
a Mi 3w (probably doable for the Mi 4 too)
ADB drivers installed
Not necessary, but do back up system1 if you wish to conserve your current ROM and config.
As parted cannot resize partitions, /system (system1) and /system1 (system2) partitions will have to be removed and re-created with the desired size, this is why backing up system1 is favourable.
Reboot to recovery and connect your phone
Open a cmd window (or terminal, if you're using linux), and connect through adb by typing;
Code:
adb devices
adb shell
If everything is fine and you get a shell input (#), start parted by typing;
Code:
parted /dev/block/mmcblk0
unit MB #to set storage unit as MB
print #shows partition table. do remember to screenshot this
Output of "print" should be something like this
Code:
Number Start End Size File system Name Flags
1 0.02MB 2.10MB 2.08MB sbl1
2 2.10MB 3.15MB 1.05MB rpm
3 3.15MB 4.19MB 1.05MB tz
4 4.19MB 5.24MB 1.05MB DDR
5 5.24MB 6.29MB 1.05MB ssd
6 6.29MB 7.34MB 1.05MB dbi
7 7.34MB 11.5MB 4.19MB aboot
8 11.5MB 16.8MB 5.24MB bk1
9 16.8MB 21.0MB 4.19MB misc
10 21.0MB 29.4MB 8.39MB logo
11 29.4MB 67.1MB 37.7MB bk2
12 67.1MB 68.7MB 1.57MB modemst1
13 68.7MB 70.3MB 1.57MB modemst2
14 70.3MB 70.3MB 0.00MB fsc
15 70.3MB 134MB 64.0MB bk3
16 134MB 136MB 1.57MB fsg
17 136MB 168MB 32.0MB bk4
18 168MB 201MB 33.6MB bk5
19 201MB 218MB 16.8MB boot
20 218MB 235MB 16.8MB boot1
21 235MB 252MB 16.8MB recovery
22 252MB 268MB 16.8MB ext4 persist
23 268MB 336MB 67.1MB fat16 modem
24 336MB 403MB 67.1MB fat16 modem1
25 403MB 1074MB 671MB ext4 system
26 1074MB 1745MB 671MB ext4 system1
27 1745MB 2147MB 403MB ext4 cache
28 2147MB 15758MB 13610MB ext4 userdata
Remove partition "system" (system1) and "system1" (system2);
Code:
rm 25
rm 26
Create new partitions after deleting them, partition size is up to you;
Code:
mkpartfs primary ext2 403 1645 # 403MB is the start of the partition ending at 1645 MB, this will be for system1
mkpartfs primary ext2 1645 1745 # Do the same for system2
print # show the partition table to confirm that the partitions are created
name 25 system # name the partition as "system" for system1
name 26 system1 # again for system2
print # check again
quit
Convert newly created partitions to ext4 from ext2;
Code:
#for system1;
tune2fs -j /dev/block/mmcblk0p25
e2fsck -fDp /dev/block/mmcblk0p25
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p25
e2fsck -fDp /dev/block/mmcblk0p25
# for system2;
tune2fs -j /dev/block/mmcblk0p26
e2fsck -fDp /dev/block/mmcblk0p26
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p26
e2fsck -fDp /dev/block/mmcblk0p26
Go back to parted to check whether it's applied;
Code:
parted /dev/block/mmcblk0
unit MB
print
It should be like this (if you followed my partition sizes)
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15758MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 0.02MB 2.10MB 2.08MB sbl1
2 2.10MB 3.15MB 1.05MB rpm
3 3.15MB 4.19MB 1.05MB tz
4 4.19MB 5.24MB 1.05MB DDR
5 5.24MB 6.29MB 1.05MB ssd
6 6.29MB 7.34MB 1.05MB dbi
7 7.34MB 11.5MB 4.19MB aboot
8 11.5MB 16.8MB 5.24MB bk1
9 16.8MB 21.0MB 4.19MB misc
10 21.0MB 29.4MB 8.39MB logo
11 29.4MB 67.1MB 37.7MB bk2
12 67.1MB 68.7MB 1.57MB modemst1
13 68.7MB 70.3MB 1.57MB modemst2
14 70.3MB 70.3MB 0.00MB fsc
15 70.3MB 134MB 64.0MB bk3
16 134MB 136MB 1.57MB fsg
17 136MB 168MB 32.0MB bk4
18 168MB 201MB 33.6MB bk5
19 201MB 218MB 16.8MB boot
20 218MB 235MB 16.8MB boot1
21 235MB 252MB 16.8MB recovery
22 252MB 268MB 16.8MB ext4 persist
23 268MB 336MB 67.1MB fat16 modem
24 336MB 403MB 67.1MB fat16 modem1
25 403MB 1645MB 1242MB ext4 system
26 1645MB 1745MB 99.8MB ext4 system1
27 1745MB 2147MB 403MB ext4 cache
28 2147MB 15758MB 13610MB ext4 userdata
You can quit adb now, process is finished. Reboot and restore your back up (if you have made one earlier) or flash a rom through CWM
Do comment/reply if you are having difficulties or otherwise
Thank you so much
{
"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"
}
One command is miswritten
mkpartfs primary ext2 1812 3070
It should be
mkpartfs primary ext2 1645 1745
shrisangram said:
One command is miswritten
mkpartfs primary ext2 1812 3070
It should be
mkpartfs primary ext2 1645 1745
Click to expand...
Click to collapse
Lol thanks! Fixed. Didn't notice that
can we use the remaining size of system to data partition?
cause i dont need big size of system, i need for app instead, can we do it?
Thanks,
Will this have any effect if I have to do fastboot of MIUI in future?
Is this method safe since we are playing with partition table?
arif920629 said:
Disclaimer: I am not responsible for bricked devices, obviously
Unlike most people here, I do not find the "dual-boot" feature particularly useful due to its buggyness and quirky configuration plus it made the available space for the /system partition divided, leaving only 600++ MB for each system1 and system2. This guide is using CWM v6.0.5.1 (R11) by furniel and donbo.
...
Do comment/reply if you are having difficulties or otherwise
Click to expand...
Click to collapse
why did these steps??
tune2fs -j /dev/block/mmcblk0p25
e2fsck -fDp /dev/block/mmcblk0p25
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p25
e2fsck -fDp /dev/block/mmcblk0p25
I was thinking this isn't possible all this while, thank you for posting this amazing tutorial! I have no use for the second system partition either, but instead, I actually needed more system space to flash bigger Gapps! Thank you so much!
Amruth Pillai said:
I was thinking this isn't possible all this while, thank you for posting this amazing tutorial! I have no use for the second system partition either, but instead, I actually needed more system space to flash bigger Gapps! Thank you so much!
Click to expand...
Click to collapse
Did u try it? Is it working?
I would like to know why you have changed the format of the file systems from ext3 to ext4.
srvoleti said:
I would like to know why you have changed the format of the file systems from ext3 to ext4.
Click to expand...
Click to collapse
Code:
[B]Ext4[/B]
[LIST]
[*]Ext4 stands for fourth extended file system.
[*]It was introduced in 2008.
[*]Starting from Linux Kernel 2.6.19 ext4 was available.
[*]Supports huge individual file size and overall file system size.
[*]Maximum individual file size can be from 16 GB to 16 TB
[*]Overall maximum ext4 file system size is 1 EB (exabyte). 1 EB = 1024 PB (petabyte). 1 PB = 1024 TB (terabyte).
[*]Directory can contain a maximum of 64,000 subdirectories (as opposed to 32,000 in ext3)
[*]You can also mount an existing ext3 fs as ext4 fs (without having to upgrade it).
[*]Several other new features are introduced in ext4: multiblock allocation, delayed allocation, journal checksum. fast fsck, etc. All you need to know is that these new features have improved the performance and reliability of the filesystem when compared to ext3.
[*]In ext4, you also have the option of turning the journaling feature “off”.
[/LIST]
With all these features, and an option to... who wouldn't?
Amruth Pillai said:
Code:
[B]Ext4[/B]
[LIST]
[*]Ext4 stands for fourth extended file system.
[*]It was introduced in 2008.
[*]Starting from Linux Kernel 2.6.19 ext4 was available.
[*]Supports huge individual file size and overall file system size.
[*]Maximum individual file size can be from 16 GB to 16 TB
[*]Overall maximum ext4 file system size is 1 EB (exabyte). 1 EB = 1024 PB (petabyte). 1 PB = 1024 TB (terabyte).
[*]Directory can contain a maximum of 64,000 subdirectories (as opposed to 32,000 in ext3)
[*]You can also mount an existing ext3 fs as ext4 fs (without having to upgrade it).
[*]Several other new features are introduced in ext4: multiblock allocation, delayed allocation, journal checksum. fast fsck, etc. All you need to know is that these new features have improved the performance and reliability of the filesystem when compared to ext3.
[*]In ext4, you also have the option of turning the journaling feature “off”.
[/LIST]
With all these features, and an option to... who wouldn't?
Click to expand...
Click to collapse
OK, Thank you for the info.
system2
Why is system2 still exist with 100MB size? I think it will cause error if you do OTA update because MI3 OTA update by default will flash update to system1 and then system2 in the next OTA. Unless if you stick to custom rom or always manually flash update to system1
srvoleti said:
I would like to know why you have changed the format of the file systems from ext3 to ext4.
Click to expand...
Click to collapse
changed? ext4 is default.
m11kkaa said:
changed? ext4 is default.
Click to expand...
Click to collapse
When I checked yesterday, the existing partitions it was shown as ext3 but now it is shown as ext4. That's why I asked that at that time.
This guide also works on Mi2S,its exact copy of it actually (except a minor difference in partition layout).
can anyone pls make a video of this tutorial?
got struck there
iwjy said:
Why is system2 still exist with 100MB size? I think it will cause error if you do OTA update because MI3 OTA update by default will flash update to system1 and then system2 in the next OTA. Unless if you stick to custom rom or always manually flash update to system1
Click to expand...
Click to collapse
Ah, yes, I have the same question, actually...we DO need system2 to be usable atleast, right?
naruse99 said:
can we use the remaining size of system to data partition?
cause i dont need big size of system, i need for app instead, can we do it?
Click to expand...
Click to collapse
can someone make tutorial to resize data partition?
Someone pls confirm the tutorial. Want to try very badly
what to do after step 1??
i am getting this...
anyone, pls help..
This thread assumes there is no ROM released for recovery and you need to start from scratch to build a recovery.
After doing a lot of searching I have put together of list of items needed to build your own partition.xml file based on your specific device.
#1 A rooted phone is a must! You need to be able to backup all partitions including the partition table. Using DD is your friend here.
To build the partition.xml file you'll need the to know the following items at a minimum-
1 partition label
2 size in kb
3 type
There are other parameters such as bootable, readonly and filename but for purposes of this post we'll only work with the first three
You can use a variety of commands to get the partition label and size. e.g.-
# cat /proc/partition
# mount
# df
# parted /dev/block/mmcblk0
# ls -l /dev/block/platform/"some number".sdhci/by-name
Probably the most useful command will come from parted. (Assuming you already have it installed in your system. How to install it is another topic I won't cover here to keep this topic on track)
Code:
[email protected]_STUDIO_C_5_5_LTE:/system/bin # 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
Model: MMC H8G1e (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 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 786kB tz
9 139MB 140MB 786kB tzbak
10 140MB 141MB 1049kB pad
11 141MB 143MB 1573kB modemst1
12 143MB 144MB 1573kB modemst2
13 144MB 145MB 1049kB misc
14 145MB 145MB 1024B fsc
15 145MB 145MB 8192B ssd
16 145MB 156MB 10.5MB splash
17 201MB 201MB 32.8kB DDR
18 201MB 203MB 1573kB fsg
19 203MB 203MB 16.4kB sec
20 203MB 237MB 33.6MB boot
21 237MB 2334MB 2097MB ext4 system
22 2334MB 2367MB 33.6MB ext4 persist
23 2367MB 2401MB 33.6MB ext4 apedata
24 2401MB 2669MB 268MB ext4 cache
25 2669MB 2703MB 33.6MB recovery
26 2703MB 2704MB 1049kB devinfo
27 2751MB 2752MB 524kB keystore
28 2752MB 2819MB 67.1MB oem
29 2819MB 2820MB 524kB config
30 2820MB 7818MB 4999MB ext4 userdata
You can see we can get the start, end and total size of each partition as well as the partition names.
Now we need to translate partition names into the "type" value in our partition.xml file. (Where type="some long string of numbers with dashes in between") Here is the list I have come up with so far assuming we have a GPT partition structure in our device. Always verify these values for your specific device! You have been warned.
Code:
098DF793-D712-413D-9D4E-89D711772228 rpm
0A288B1F-22C9-E33B-8F5D-0E81686A68CB modemst2
20117f86-E985-4357-B9EE-374BC1D8487D boot, recovery
20A0C19C-286A-42FA-9CE7-F64C3226A794 DDR
2C86E742-745E-4FDD-BFD8-B6A7AC638772 ssd
400FFDCD-22E0-47E7-9A23-F16ED9382388 aboot
57B90A16-22C9-E33B-8F5D-0E81686A68CB fsc
638FF8E2-22C9-E33B-8F5D-0E81686A68CB fsg
A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4 tz
D4E0D938-B7FA-48C1-9D21-BC5ED5C4B203 dbi or sdi depending on device
DEA0BA2C-CBDD-4805-B4F9-F428251C3E98 sbl1
EBBEADAF-22C9-E33B-8F5D-0E81686A68CB modemst1
EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 modem, pad, system, userdata, persist, cache
You can get these values from using the gptfdisk binary as seen in this post
forum.xda-developers.com/showpost.php?p=33358988&postcount=2 (Thanks to E:V:A)
or head on down to the spoiler section here and you can see what the labels look like- (Partition GUID Code)
https://translate.google.com/transl...ersion/index.php?t552073-420.html&prev=search
Lastly my assumption is that if the partition size is not evenly divisible by 1024 you would round up to the next nearest kb value.
33.6MB=33600kb
33600/1024=34406.4 (cant have a partial kb left over so round up)
34407
33.6MB=34407kb. Let's plug this vaule into our xml file
size_in_kb="34407"
I'm new at this. If ANY of this is wrong please comment and correct. I hope this will help!
Currently I am analysing partition.xml file in AndroidGo(nhlos) (chipset msm8909). I want to know what are the utilities of below parameters:
1) partition label
2) size in kb
3) type
4) bootable
5) readonly
For example: <partition label="boot" size_in_kb="32768" type="20117F86-E985-4357-B9EE-374BC1D8487D" bootable="false" readonly="true" filename="boot.img"/>
Please let me know , so that it will be helpful.