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
Related
Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
dan15 said:
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
Click to expand...
Click to collapse
Yes my Android version is 4.4.2 build version is 18.2.A.1.14
ok, as my D5103 is ugrade to .17, i have to wait for a solution, if i don't want to downgrade, but i'm not sure that the rot will stay if i upgrade after root on .14...
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Abhinav2 said:
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Click to expand...
Click to collapse
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
CreasingMass Dev said:
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
Click to expand...
Click to collapse
None of them has AFAIK. Can u give some example of device which might have? Because recovery is basically flashed in FOTA partition
AJ
Al parecer no existe recovery
Xenon1978 said:
Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Click to expand...
Click to collapse
No se si alguno de ustedes o tengo instalar un gestor de recuperación (Recovery) anteriormente a este modelo
Ahora he intentado hacerlo y puff.. el paquete ABD me dice que no EXISTE
Code:
FAILED <remote: Recovery partición doesn't founded>
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)
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available.
After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
IlyaKol said:
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
Click to expand...
Click to collapse
Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045
If you need help pm me
macdaddie87 said:
Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045
If you need help pm me
Click to expand...
Click to collapse
I'm a system engineer (server support, etc.) so I should be able to handle it. Just needed to be pointed in the right direction. I shall post up tomorrow.
macdaddie87 said:
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available.
After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Click to expand...
Click to collapse
Scratch that, evidently root is only available for the EU H815 and mine is the Taiwan one, from what I know. I'll see if I get lucky somehow, but by the looks of it I won't be able to provide the dump since I can't achieve root.
Some help
http://forum.xda-developers.com/g4/development/rom-docs-testrom-t3126728
Code:
major minor #blocks name
253 0 721772 zram0
179 0 30535680 mmcblk0
179 1 88064 mmcblk0p1
179 2 512 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 1536 mmcblk0p24
179 25 1536 mmcblk0p25
179 26 1536 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 512 mmcblk0p29
179 30 2048 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 512 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 4096 mmcblk0p36
259 5 49152 mmcblk0p37
259 6 40960 mmcblk0p38
259 7 40960 mmcblk0p39
259 8 8192 mmcblk0p40
259 9 8192 mmcblk0p41
259 10 32768 mmcblk0p42
259 11 47104 mmcblk0p43
259 12 10240 mmcblk0p44
259 13 4096 mmcblk0p45
259 14 4096 mmcblk0p46
259 15 4239360 mmcblk0p47
259 16 262144 mmcblk0p48
259 17 1261568 mmcblk0p49
259 18 24313856 mmcblk0p50
259 19 12271 mmcblk0p51
179 32 4096 mmcblk0rpmb
DDR -> /dev/block/mmcblk0p30
aboot -> /dev/block/mmcblk0p8
abootbak -> /dev/block/mmcblk0p14
apdp -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p38
cache -> /dev/block/mmcblk0p49
cust -> /dev/block/mmcblk0p48
devinfo -> /dev/block/mmcblk0p17
po -> /dev/block/mmcblk0p20
drm -> /dev/block/mmcblk0p40
eksst -> /dev/block/mmcblk0p33
encrypt -> /dev/block/mmcblk0p32
factory -> /dev/block/mmcblk0p43
fota -> /dev/block/mmcblk0p44
fsc -> /dev/block/mmcblk0p27
fsg -> /dev/block/mmcblk0p26
grow -> /dev/block/mmcblk0p51
hyp -> /dev/block/mmcblk0p6
hypbak -> /dev/block/mmcblk0p12
keystore -> /dev/block/mmcblk0p29
laf -> /dev/block/mmcblk0p37
limits -> /dev/block/mmcblk0p16
misc -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p24
modemst2 -> /dev/block/mmcblk0p25
mpt -> /dev/block/mmcblk0p42
msadp -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p23
pmic -> /dev/block/mmcblk0p2
pmicbak -> /dev/block/mmcblk0p10
raw_resources -> /dev/block/mmcblk0p45
raw_resourcesbak -> /dev/block/mmcblk0p46
rct -> /dev/block/mmcblk0p34
recovery -> /dev/block/mmcblk0p39
rpm -> /dev/block/mmcblk0p7
rpmbak -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p3
sbl1bak -> /dev/block/mmcblk0p9
sdi -> /dev/block/mmcblk0p5
sdibak -> /dev/block/mmcblk0p15
sec -> /dev/block/mmcblk0p31
sns -> /dev/block/mmcblk0p41
spare1 -> /dev/block/mmcblk0p21
spare2 -> /dev/block/mmcblk0p36
ssd -> /dev/block/mmcblk0p28
system -> /dev/block/mmcblk0p47
tz -> /dev/block/mmcblk0p4
tzbak -> /dev/block/mmcblk0p11
userdata -> /dev/block/mmcblk0p50
I can't unlock the BL as I'm a TW phone not an EU phone. Sorry OP.
Hello
I want to split userdata partition of my M9 into two parts. What is the right tool for it?
I tried android-gptfdisk but it shows that GPT partition table is very strange.
After I run gdisk from the package above I can see the following message.
[email protected]_himauhl:/ # gdisk /dev/block/mmcblk0
GPT fdisk (gdisk) version 1.0.0
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
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.
****************************************************************************
Command (? for help): p
Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 72 entries
First usable sector is 34, last usable sector is 60932095
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 65 16.0 KiB FFFF board_info
2 66 8257 4.0 MiB FFFF pg1fs
3 8258 10305 1024.0 KiB FFFF sbl1
4 10306 12353 1024.0 KiB FFFF pmic
5 12354 94273 40.0 MiB 0700 dummy
6 94274 98303 2.0 MiB 0700 reserve_1
7 98304 98815 256.0 KiB FFFF mfg
8 98816 147325 23.7 MiB FFFF pg2fs
9 147326 148349 512.0 KiB FFFF rpm
10 148350 152445 2.0 MiB FFFF tz
11 152446 152637 96.0 KiB FFFF sdi
12 152638 156733 2.0 MiB FFFF hyp
13 156734 158781 1024.0 KiB FFFF aboot
14 158782 179261 10.0 MiB 0700 tool_diag
15 179262 199741 10.0 MiB 0700 sp1
16 199742 201789 1024.0 KiB FFFF ddr
17 201790 203837 1024.0 KiB 0700 rfg_0
18 203838 205885 1024.0 KiB 0700 rfg_1
19 205886 207933 1024.0 KiB 0700 rfg_2
20 207934 209981 1024.0 KiB 0700 rfg_3
21 209982 212029 1024.0 KiB 0700 rfg_4
22 212030 214077 1024.0 KiB 0700 rfg_5
23 214078 216125 1024.0 KiB 0700 rfg_6
24 216126 218173 1024.0 KiB 0700 rfg_7
25 218174 221245 1.5 MiB FFFF fsg
26 221246 342079 59.0 MiB 0700 radio
27 342080 383039 20.0 MiB 0700 adsp
28 383040 383041 1024 bytes FFFF limits
29 383042 393215 5.0 MiB 0700 reserve_2
30 393216 438271 22.0 MiB FFFF persist
31 438272 458751 10.0 MiB 0700 ramdump
32 458752 460799 1024.0 KiB FFFF misc
33 460800 463871 1.5 MiB FFFF modem_st1
34 463872 466943 1.5 MiB FFFF modem_st2
35 466944 507903 20.0 MiB 0700 fataldevlog
36 507904 569343 30.0 MiB 0700 devlog
37 569344 569855 256.0 KiB 0700 pdata
38 569856 569887 16.0 KiB 0700 control
39 569888 570015 64.0 KiB 0700 extra
40 570016 572063 1024.0 KiB 0700 cdma_record
41 572064 572065 1024 bytes 0700 fsc
42 572066 572081 8.0 KiB FFFF ssd
43 572082 573105 512.0 KiB 0700 sensor_hub
44 573106 573361 128.0 KiB FFFF sec
45 573362 575409 1024.0 KiB FFFF abootbak
46 575410 575429 10.0 KiB 0700 cir_img
47 575430 577991 1.3 MiB 0700 local
48 577992 579015 512.0 KiB 0700 frp
49 579016 583111 2.0 MiB FFFF cpe
50 583112 624071 20.0 MiB 0700 carrier
51 624072 624583 256.0 KiB 0700 skylink
52 624584 624839 128.0 KiB 0700 rfg_8
53 624840 625095 128.0 KiB 0700 rfg_9
54 625096 625351 128.0 KiB 0700 rfg_10
55 625352 625607 128.0 KiB 0700 rfg_11
56 625608 625863 128.0 KiB 0700 rfg_12
57 625864 626119 128.0 KiB 0700 rfg_13
58 626120 626375 128.0 KiB 0700 rfg_14
59 626376 626631 128.0 KiB 0700 rfg_15
60 626632 659399 16.0 MiB 0700 absolute
61 659400 688127 14.0 MiB 0700 reserve
62 688128 819199 64.0 MiB FFFF hosd
63 819200 950271 64.0 MiB FFFF boot
64 950272 1081343 64.0 MiB FFFF recovery
65 1081344 1736703 320.0 MiB 0700 cache
66 1736704 10911743 4.4 GiB 0700 system
67 10911744 60194815 23.5 GiB 0700 userdata
68 60194816 60788735 290.0 MiB 0700 apppreload
69 60788736 60911615 60.0 MiB 0700 cota
70 60911616 60932095 10.0 MiB FFFF battery
Click to expand...
Click to collapse
It looks like GPT partition table and/or MBR are specific. Nevertheless my M9 works well I can boot it and use it.
Could somebody give me a hint about working with M9 GPT partition table?
Hi all!
I cant open thread in other channel so i post here. sorry about it.
I've compiled a custom kernel for Samsung S9, but the kernel is bigger than the BOOT partition size. I want to create a new partition (over USERDATA partition) and boot from the new one.
This is the initial GPT /dev/block/sda partition:
Code:
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2677 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 15614335 53.1 GiB 0700 USERDATA
I've tried to re-partition /dev/block/sda with sgdisk like this:
Code:
~ # sgdisk --delete 25 /dev/block/sda
~ # sgdisk --new 25:1697152:1716972 /dev/block/sda
~ # sgdisk --change-name 25:BOOT2 /dev/block/sda
~ # sgdisk --typecode 25:0700 /dev/block/sda
~ # sgdisk --new 26:1716973:15614335 /dev/block/sda
~ # sgdisk --change-name 26:USERDATA /dev/block/sda
~ # sgdisk --typecode 26:0700 /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2678 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT2
26 1716974 15614335 53.0 GiB 0700 USERDATA
~ # exit
~ adb reboot recovery
~ adb wait-for-any && adb shell
~ # ~ # ls /dev/block/platform/11120000.ufs/by-name/ -la
drwxr-xr-x 2 root root 580 Nov 19 15:32 .
drwxr-xr-x 4 root root 720 Nov 19 15:32 ..
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT2 -> /dev/block/sda25
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CACHE -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 Nov 19 15:32 CPEFS -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CP_DEBUG -> /dev/block/sda24
lrwxrwxrwx 1 root root 16 Nov 19 15:32 DQMDBG -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTB -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTBO -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 Nov 19 15:32 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 Nov 19 15:32 HIDDEN -> /dev/block/sda22
lrwxrwxrwx 1 root root 15 Nov 19 15:32 KEYSTORAGE -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Nov 19 15:32 MISC -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 Nov 19 15:32 NAD_REFER -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Nov 19 15:32 ODM -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 Nov 19 15:32 OMR -> /dev/block/sda23
lrwxrwxrwx 1 root root 15 Nov 19 15:32 PARAM -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Nov 19 15:32 PERSISTENT -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RADIO -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RECOVERY -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 Nov 19 15:32 STEADY -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 Nov 19 15:32 SYSTEM -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 Nov 19 15:32 UP_PARAM -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Nov 19 15:32 USERDATA -> /dev/block/sda26
lrwxrwxrwx 1 root root 16 Nov 19 15:32 VENDOR -> /dev/block/sda19
~ # dd if=newboot.img of=/dev/block/sda25
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 7CE83C10-10C6-4E3D-A6B4-92B66586A716
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --partition-guid=10:R /dev/block/sda
~ # sgdisk --partition-guid=25:52444E41-494F-2044-424F-4F5400000000 /dev/block/sda
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 6F5BCACB-2AF9-4F16-B2A3-B4B12085EB8F
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --change-name 10:BOOT1 /dev/block/sda
~ # sgdisk --change-name 25:BOOT /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 13900040 sectors (53.0 GiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT1
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT
~ # exit
~ adb reboot
By this process I've written my custom boot image on the new BOOT partition, and replaced both the partition name and GUID with the original BOOT partition's.
After this, the phone still boots the real image (verified with /proc/version). What am I missing here?
I've also tried writing the original boot image to the new boot partition and zero out the original boot partition (sda10) to see what happens and the device didn't boot.
DuduFaruk said:
Hi all!
I cant open thread in other channel so i post here. sorry about it.
I've compiled a custom kernel for Samsung S9, but the kernel is bigger than the BOOT partition size. I want to create a new partition (over USERDATA partition) and boot from the new one.
This is the initial GPT /dev/block/sda partition:
Code:
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2677 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 15614335 53.1 GiB 0700 USERDATA
I've tried to re-partition /dev/block/sda with sgdisk like this:
Code:
~ # sgdisk --delete 25 /dev/block/sda
~ # sgdisk --new 25:1697152:1716972 /dev/block/sda
~ # sgdisk --change-name 25:BOOT2 /dev/block/sda
~ # sgdisk --typecode 25:0700 /dev/block/sda
~ # sgdisk --new 26:1716973:15614335 /dev/block/sda
~ # sgdisk --change-name 26:USERDATA /dev/block/sda
~ # sgdisk --typecode 26:0700 /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2678 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT2
26 1716974 15614335 53.0 GiB 0700 USERDATA
~ # exit
~ adb reboot recovery
~ adb wait-for-any && adb shell
~ # ~ # ls /dev/block/platform/11120000.ufs/by-name/ -la
drwxr-xr-x 2 root root 580 Nov 19 15:32 .
drwxr-xr-x 4 root root 720 Nov 19 15:32 ..
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT2 -> /dev/block/sda25
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CACHE -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 Nov 19 15:32 CPEFS -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CP_DEBUG -> /dev/block/sda24
lrwxrwxrwx 1 root root 16 Nov 19 15:32 DQMDBG -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTB -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTBO -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 Nov 19 15:32 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 Nov 19 15:32 HIDDEN -> /dev/block/sda22
lrwxrwxrwx 1 root root 15 Nov 19 15:32 KEYSTORAGE -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Nov 19 15:32 MISC -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 Nov 19 15:32 NAD_REFER -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Nov 19 15:32 ODM -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 Nov 19 15:32 OMR -> /dev/block/sda23
lrwxrwxrwx 1 root root 15 Nov 19 15:32 PARAM -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Nov 19 15:32 PERSISTENT -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RADIO -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RECOVERY -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 Nov 19 15:32 STEADY -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 Nov 19 15:32 SYSTEM -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 Nov 19 15:32 UP_PARAM -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Nov 19 15:32 USERDATA -> /dev/block/sda26
lrwxrwxrwx 1 root root 16 Nov 19 15:32 VENDOR -> /dev/block/sda19
~ # dd if=newboot.img of=/dev/block/sda25
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 7CE83C10-10C6-4E3D-A6B4-92B66586A716
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --partition-guid=10:R /dev/block/sda
~ # sgdisk --partition-guid=25:52444E41-494F-2044-424F-4F5400000000 /dev/block/sda
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 6F5BCACB-2AF9-4F16-B2A3-B4B12085EB8F
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --change-name 10:BOOT1 /dev/block/sda
~ # sgdisk --change-name 25:BOOT /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 13900040 sectors (53.0 GiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT1
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT
~ # exit
~ adb reboot
By this process I've written my custom boot image on the new BOOT partition, and replaced both the partition name and GUID with the original BOOT partition's.
After this, the phone still boots the real image (verified with /proc/version). What am I missing here?
I've also tried writing the original boot image to the new boot partition and zero out the original boot partition (sda10) to see what happens and the device didn't boot.
Click to expand...
Click to collapse
you might need the big guns for this issue. @AthieN you got any words of wisdom for this?
For those who will experience it in the future.
After I reversed S-Boot I notice the bootloader load partition from internal PIT file and the boot section in the GPT is not connected to the boot order.