Develop Bugs

[DEV]Redmi 1s partition Table

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)

Unbricking the G Pad v410 in qualcomm hs_usb 9008

For weeks now I have been trying to unbrick the LG G Pad V410, there is no V410 support here on XDA, so this was the closest I could get.
I have tried everything, and what I have found is that if I take a SDCard and partition it to match it to the EMMC of the V410 then use WindowsLGExtract to extract the KDZ/DZ. Next I flashed all the .bin to the sdcard, inserted in into the GPAD then hooked to my computer. Now it goes from Qualcomm QDL mode to LG Electronics. With the partitioned semi flashed sdcard, while holding down power, it shows the battery at 0 and tells to charge it, while doing the same on charger, it only shows at 0% but does not charge.
Only problem, no charge, no charge no KDZ flash possibility using LG flash tool
Was curious, so did a search and found a modemst1.imq and modemst2.imq for the LG G2 and flashed those to the SDCARD. Now when using the read phone information via LG Flash tool now, it now tells me that the imei is not valid, did not exist before.
Well hoping somebody could dd the following bolded partitions on their own LG V410
1 16384 147455 64.0 MiB 0700 modem
2 147456 149503 1024.0 KiB FFFF sbl1
3 149504 150527 512.0 KiB FFFF rpm
4 150528 151551 512.0 KiB FFFF tz
5 151552 152575 512.0 KiB FFFF sdi
6 152576 156671 2.0 MiB FFFF aboot
7 156672 157695 512.0 KiB FFFF rpmb
8 157696 158719 512.0 KiB FFFF tzb
9 158720 162815 2.0 MiB FFFF abootb
10 162816 163839 512.0 KiB FFFF eksst
11 163840 167935 2.0 MiB 0700 pad
12 167936 174079 3.0 MiB FFFF modemst1
13 174080 180223 3.0 MiB FFFF modemst2
14 180224 212991 16.0 MiB FFFF misc
15 212992 278527 32.0 MiB 0700 persist
16 278528 327679 24.0 MiB FFFF laf
17 327680 376831 24.0 MiB FFFF boot
18 376832 425983 24.0 MiB FFFF recovery
19 425984 432127 3.0 MiB FFFF fsg
20 442368 443391 512.0 KiB FFFF fsc
21 443392 444415 512.0 KiB FFFF ssd
22 444416 446463 1024.0 KiB FFFF sbl1b
23 446464 447487 512.0 KiB FFFF encrypt
24 447488 448511 512.0 KiB FFFF rct
25 458752 459775 512.0 KiB FFFF DDR
26 459776 476159 8.0 MiB 0700 drm
27 476160 492543 8.0 MiB 0700 sns
28 492544 541695 24.0 MiB FFFF factory
29 541696 607231 32.0 MiB FFFF fota
30 622592 688127 32.0 MiB 0700 mpt
31 688128 901119 104.0 MiB 8300 cust
32 901120 5095423 2.0 GiB 0700 system
33 5095424 6946815 904.0 MiB 0700 cache
34 6946816 15253503 4.0 GiB 0700 userdata
35 15253504 15269854 8.0 MiB 0700 grow
These partitions are from the V400, tried to see if I had any better luck using the V400 KDZ, this did not work, reflashed the modem.bin, boot.bin etc... leaving the partitions as is and it worked. The V410 is differant, so please please, could somebody dd the above partitions.

bethnesbitt said:
For weeks now I have been trying to unbrick the LG G Pad V410, there is no V410 support here on XDA, so this was the closest I could get.
I have tried everything, and what I have found is that if I take a SDCard and partition it to match it to the EMMC of the V410 then use WindowsLGExtract to extract the KDZ/DZ. Next I flashed all the .bin to the sdcard, inserted in into the GPAD then hooked to my computer. Now it goes from Qualcomm QDL mode to LG Electronics. With the partitioned semi flashed sdcard, while holding down power, it shows the battery at 0 and tells to charge it, while doing the same on charger, it only shows at 0% but does not charge.
Only problem, no charge, no charge no KDZ flash possibility using LG flash tool
Was curious, so did a search and found a modemst1.imq and modemst2.imq for the LG G2 and flashed those to the SDCARD. Now when using the read phone information via LG Flash tool now, it now tells me that the imei is not valid, did not exist before.
Well hoping somebody could dd the following bolded partitions on their own LG V410
1 16384 147455 64.0 MiB 0700 modem
2 147456 149503 1024.0 KiB FFFF sbl1
3 149504 150527 512.0 KiB FFFF rpm
4 150528 151551 512.0 KiB FFFF tz
5 151552 152575 512.0 KiB FFFF sdi
6 152576 156671 2.0 MiB FFFF aboot
7 156672 157695 512.0 KiB FFFF rpmb
8 157696 158719 512.0 KiB FFFF tzb
9 158720 162815 2.0 MiB FFFF abootb
10 162816 163839 512.0 KiB FFFF eksst
11 163840 167935 2.0 MiB 0700 pad
12 167936 174079 3.0 MiB FFFF modemst1
13 174080 180223 3.0 MiB FFFF modemst2
14 180224 212991 16.0 MiB FFFF misc
15 212992 278527 32.0 MiB 0700 persist
16 278528 327679 24.0 MiB FFFF laf
17 327680 376831 24.0 MiB FFFF boot
18 376832 425983 24.0 MiB FFFF recovery
19 425984 432127 3.0 MiB FFFF fsg
20 442368 443391 512.0 KiB FFFF fsc
21 443392 444415 512.0 KiB FFFF ssd
22 444416 446463 1024.0 KiB FFFF sbl1b
23 446464 447487 512.0 KiB FFFF encrypt
24 447488 448511 512.0 KiB FFFF rct
25 458752 459775 512.0 KiB FFFF DDR
26 459776 476159 8.0 MiB 0700 drm
27 476160 492543 8.0 MiB 0700 sns
28 492544 541695 24.0 MiB FFFF factory
29 541696 607231 32.0 MiB FFFF fota
30 622592 688127 32.0 MiB 0700 mpt
31 688128 901119 104.0 MiB 8300 cust
32 901120 5095423 2.0 GiB 0700 system
33 5095424 6946815 904.0 MiB 0700 cache
34 6946816 15253503 4.0 GiB 0700 userdata
35 15253504 15269854 8.0 MiB 0700 grow
These partitions are from the V400, tried to see if I had any better luck using the V400 KDZ, this did not work, reflashed the modem.bin, boot.bin etc... leaving the partitions as is and it worked. The V410 is differant, so please please, could somebody dd the above partitions.
Click to expand...
Click to collapse
You have the Verizon model? I have one too. I've never done what you're asking and I'm not rooted but I am willing to try and help you out. I'm on lollipop.
Sent from my VS985 4G using Tapatalk

Willing to try
I actually did once flash the vz kdz to it and it semi worked. Since it is hard core bricked wouldn't mind giving it a shot. If you could that would be awesome. Thinking that I could possibly modify the modemst to match my model and repair the imei.

LG G4 MMCBLK0 Daatabase

Hi guys,
there are tones of LG G4 phones that are bricked, i have tested a technic to get them back to life ( tested with H811) , but such a technic needs Emmc dumps ( all mmcblk0 partitions except userdata cache data and system ) so please i propose to make a database of all G4 dumps in Google drive or somewhere else to help people having bricked LG G4 phones
For me i need H815 dump now
Thanks

leptdre said:
Hi guys,
there are tones of LG G4 phones that are bricked, i have tested a technic to get them back to life ( tested with H811) , but such a technic needs Emmc dumps ( all mmcblk0 partitions except userdata cache data and system ) so please i propose to make a database of all G4 dumps in Google drive or somewhere else to help people having bricked LG G4 phones
For me i need H815 dump now
Thanks
Click to expand...
Click to collapse
Tell me more of your technique? I have an H811 sitting here that could use that. Is it copying the partition table to a microSD card? I've not had luck with that so far, maybe you could elucidate? Thanks!
I'm working on getting some firehose action going on. I think I've got most of the code and tools necessary to prepare the custom files needed, but it's such a steep task, especially as I don't understand its ways yet.

pretty sure we need root for this..
there's alot of interesting file here
http://downloads.codefi.re/autoprime/LG/LG_G4

leptdre said:
Hi guys,
there are tones of LG G4 phones that are bricked, i have tested a technic to get them back to life ( tested with H811) , but such a technic needs Emmc dumps ( all mmcblk0 partitions except userdata cache data and system ) so please i propose to make a database of all G4 dumps in Google drive or somewhere else to help people having bricked LG G4 phones
For me i need H815 dump now
Thanks
Click to expand...
Click to collapse
For now, here you have a list of all particions into 'mmcblk0':
HTML:
Number Start End Size File_system Name
1 16777216B 106954751B 90177536B fat16 modem
2 117440512B 117964799B 524288B pmic
3 117964800B 119013375B 1048576B sbl1
4 119013376B 120061951B 1048576B tz
5 120061952B 120586239B 524288B sdi
6 120586240B 121110527B 524288B hyp
7 121110528B 121634815B 524288B rpm
8 121634816B 123731967B 2097152B aboot
9 123731968B 124780543B 1048576B sbl1bak
10 124780544B 125304831B 524288B pmicbak
11 125304832B 126353407B 1048576B tzbak
12 126353408B 126877695B 524288B hypbak
13 126877696B 127401983B 524288B rpmbak
14 127401984B 129499135B 2097152B abootbak
15 129499136B 130023423B 524288B sdibak
16 130023424B 130547711B 524288B limits
17 130547712B 131071999B 524288B devinfo
18 131072000B 131596287B 524288B apdp
19 131596288B 132120575B 524288B msadp
20 132120576B 132644863B 524288B dpo
21 132644864B 134217727B 1572864B spare1
22 134217728B 150994943B 16777216B misc
23 150994944B 184549375B 33554432B ext4 persist
24 184549376B 186122239B 1572864B modemst1
25 186122240B 187695103B 1572864B modemst2
26 187695104B 189267967B 1572864B fsg
27 189267968B 189792255B 524288B fsc
28 189792256B 190316543B 524288B ssd
29 190316544B 190840831B 524288B keystore
30 190840832B 192937983B 2097152B DDR
31 192937984B 193462271B 524288B sec
32 193462272B 193986559B 524288B encrypt
33 193986560B 194510847B 524288B eksst
34 194510848B 195035135B 524288B rct
35 195035136B 197132287B 2097152B persistent
36 197132288B 201326591B 4194304B spare2
37 201326592B 251658239B 50331648B laf
38 251658240B 293601279B 41943040B boot
39 293601280B 335544319B 41943040B recovery
40 335544320B 343932927B 8388608B ext4 drm
41 343932928B 352321535B 8388608B ext4 sns
42 352321536B 385875967B 33554432B ext4 mpt
43 385875968B 434110463B 48234496B factory
44 434110464B 444596223B 10485760B fota
45 444596224B 448790527B 4194304B raw_resources
46 448790528B 452984831B 4194304B raw_resourcesbak
47 452984832B 4794089471B 4341104640B ext4 system
48 4794089472B 5062524927B 268435456B ext4 cust
49 5066719232B 6358564863B 1291845632B ext4 cache
50 6358564864B 31255953407B 24897388544B ext4 userdata
51 31255953408B 31268519423B 12566016B grow

Variant: H811
Version: v20o
fdisk --> list:
Code:
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 56 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 32768 208895 86.0M 0700 modem
2 229376 230399 512K 0700 pmic
3 230400 232447 1024K 0700 sbl1
4 232448 234495 1024K 0700 tz
5 234496 235519 512K 0700 sdi
6 235520 236543 512K 0700 hyp
7 236544 237567 512K 0700 rpm
8 237568 241663 2048K 0700 aboot
9 241664 243711 1024K 0700 sbl1bak
10 243712 244735 512K 0700 pmicbak
11 244736 246783 1024K 0700 tzbak
12 246784 247807 512K 0700 hypbak
13 247808 248831 512K 0700 rpmbak
14 248832 252927 2048K 0700 abootbak
15 252928 253951 512K 0700 sdibak
16 253952 254975 512K 0700 limits
17 254976 255999 512K 0700 devinfo
18 256000 257023 512K 0700 apdp
19 257024 258047 512K 0700 msadp
20 258048 259071 512K 0700 dpo
21 259072 262143 1536K 0700 spare1
22 262144 294911 16.0M 0700 misc
23 294912 360447 32.0M 0700 persist
24 360448 363519 1536K 0700 modemst1
25 363520 366591 1536K 0700 modemst2
26 366592 369663 1536K 0700 fsg
27 369664 370687 512K 0700 fsc
28 370688 371711 512K 0700 ssd
29 371712 372735 512K 0700 keystore
30 372736 376831 2048K 0700 DDR
31 376832 377855 512K 0700 sec
32 377856 378879 512K 0700 encrypt
33 378880 379903 512K 0700 eksst
34 379904 380927 512K 0700 rct
35 380928 385023 2048K 0700 persistent
36 385024 393215 4096K 0700 spare2
37 393216 491519 48.0M 0700 laf
38 491520 573439 40.0M 0700 boot
39 573440 655359 40.0M 0700 recovery
40 655360 671743 8192K 0700 drm
41 671744 688127 8192K 0700 sns
42 688128 753663 32.0M 0700 mpt
43 753664 770047 8192K 0700 eri
44 770048 778239 4096K 0700 raw_resources
45 778240 786431 4096K 0700 raw_resourcesbak
46 786432 819199 16.0M 0700 operatorlogging
47 819200 901119 40.0M 0700 carrier
48 901120 917503 8192K 0700 felica
49 917504 1011711 46.0M 0700 factory
50 1011712 1015807 2048K 0700 spare3
51 1015808 1036287 10.0M 0700 fota
52 1036288 1048575 6144K 0700 spare4
53 1048576 9822207 4284M 0700 system
54 9822208 12345343 1232M 0700 cache
55 12345344 61046783 23.2G 0700 userdata
56 61046784 61071326 11.9M 0700 grow
parted --> print:
Code:
Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name F
1 16.8MB 107MB 90.2MB fat16 modem
2 117MB 118MB 524kB pmic
3 118MB 119MB 1049kB sbl1
4 119MB 120MB 1049kB tz
5 120MB 121MB 524kB sdi
6 121MB 121MB 524kB hyp
7 121MB 122MB 524kB rpm
8 122MB 124MB 2097kB aboot
9 124MB 125MB 1049kB sbl1bak
10 125MB 125MB 524kB pmicbak
11 125MB 126MB 1049kB tzbak
12 126MB 127MB 524kB hypbak
13 127MB 127MB 524kB rpmbak
14 127MB 129MB 2097kB abootbak
15 129MB 130MB 524kB sdibak
16 130MB 131MB 524kB limits
17 131MB 131MB 524kB devinfo
18 131MB 132MB 524kB apdp
19 132MB 132MB 524kB msadp
20 132MB 133MB 524kB dpo
21 133MB 134MB 1573kB spare1
22 134MB 151MB 16.8MB misc
23 151MB 185MB 33.6MB ext4 persist
24 185MB 186MB 1573kB modemst1
25 186MB 188MB 1573kB modemst2
26 188MB 189MB 1573kB fsg
27 189MB 190MB 524kB fsc
28 190MB 190MB 524kB ssd
29 190MB 191MB 524kB keystore
30 191MB 193MB 2097kB DDR
31 193MB 193MB 524kB sec
32 193MB 194MB 524kB encrypt
33 194MB 195MB 524kB eksst
34 195MB 195MB 524kB rct
35 195MB 197MB 2097kB persistent
36 197MB 201MB 4194kB spare2
37 201MB 252MB 50.3MB laf
38 252MB 294MB 41.9MB boot
39 294MB 336MB 41.9MB recovery
40 336MB 344MB 8389kB ext4 drm
41 344MB 352MB 8389kB ext4 sns
42 352MB 386MB 33.6MB ext4 mpt
43 386MB 394MB 8389kB eri
44 394MB 398MB 4194kB raw_resources
45 398MB 403MB 4194kB raw_resourcesbak
46 403MB 419MB 16.8MB operatorlogging
47 419MB 461MB 41.9MB carrier
48 461MB 470MB 8389kB felica
49 470MB 518MB 48.2MB factory
50 518MB 520MB 2097kB spare3
51 520MB 531MB 10.5MB fota
52 531MB 537MB 6291kB spare4
53 537MB 5029MB 4492MB ext4 system
54 5029MB 6321MB 1292MB ext4 cache
55 6321MB 31.3GB 24.9GB ext4 userdata
56 31.3GB 31.3GB 12.6MB grow
---
Diagnosis: 9008, non-ILAPO, caused by me accidentally flashing the v20i bootstack.
I [shoddily] customized gpt_parser.py(based on source from here) to create partition.xml, which I then fed to ptool.py (source) to create the rawprogram0.xml and patch0.xml. Then I fed those into msp.py to create a singleimage.bin that I dd'd over to a microSD card. I inserted the microSD and surprisingly enough my G4 sprang to life instantly!
I booted into TWRP to copy over the what I thought were the correct v20o images to correct the faulty v20i images I had initially used to kill the mofo. That seems to have resulted in a total brick, when I rebooted there was no signs of life at all now, no 9008, no USB peeps at all now. But! the microSD card trick did bring it back from 9008, only it seems I shucked when I should have jived. (me >= woe.)
So maybe I flashed the wrong images *again*? Goddamnit. I should have dipped right into LAF download mode and flashed the stock KDZ. I've been a fool.
Anyway, I'm including the files I used to make all this happen in case anyone finds them useful: [download]
It turns out creating the partition.xml, rawprogram0.xml, and patch0.xml is incredibly simple. Too bad I could not get Firehose to work, it kept throwing this error at me whenever I tried:
Code:
{ERROR: OpenPort:4197 It took 10.01600000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I *was* using a firehose 8992_lite.mbn file from who knows where, that could be why maybe? That is one file I'm not sure how to create yet, though the code to create it is in the same repo at the ptool.py link I posted above.

culot said:
Variant: H811
Version: v20o
fdisk --> list:
Code:
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 56 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 32768 208895 86.0M 0700 modem
2 229376 230399 512K 0700 pmic
3 230400 232447 1024K 0700 sbl1
4 232448 234495 1024K 0700 tz
5 234496 235519 512K 0700 sdi
6 235520 236543 512K 0700 hyp
7 236544 237567 512K 0700 rpm
8 237568 241663 2048K 0700 aboot
9 241664 243711 1024K 0700 sbl1bak
10 243712 244735 512K 0700 pmicbak
11 244736 246783 1024K 0700 tzbak
12 246784 247807 512K 0700 hypbak
13 247808 248831 512K 0700 rpmbak
14 248832 252927 2048K 0700 abootbak
15 252928 253951 512K 0700 sdibak
16 253952 254975 512K 0700 limits
17 254976 255999 512K 0700 devinfo
18 256000 257023 512K 0700 apdp
19 257024 258047 512K 0700 msadp
20 258048 259071 512K 0700 dpo
21 259072 262143 1536K 0700 spare1
22 262144 294911 16.0M 0700 misc
23 294912 360447 32.0M 0700 persist
24 360448 363519 1536K 0700 modemst1
25 363520 366591 1536K 0700 modemst2
26 366592 369663 1536K 0700 fsg
27 369664 370687 512K 0700 fsc
28 370688 371711 512K 0700 ssd
29 371712 372735 512K 0700 keystore
30 372736 376831 2048K 0700 DDR
31 376832 377855 512K 0700 sec
32 377856 378879 512K 0700 encrypt
33 378880 379903 512K 0700 eksst
34 379904 380927 512K 0700 rct
35 380928 385023 2048K 0700 persistent
36 385024 393215 4096K 0700 spare2
37 393216 491519 48.0M 0700 laf
38 491520 573439 40.0M 0700 boot
39 573440 655359 40.0M 0700 recovery
40 655360 671743 8192K 0700 drm
41 671744 688127 8192K 0700 sns
42 688128 753663 32.0M 0700 mpt
43 753664 770047 8192K 0700 eri
44 770048 778239 4096K 0700 raw_resources
45 778240 786431 4096K 0700 raw_resourcesbak
46 786432 819199 16.0M 0700 operatorlogging
47 819200 901119 40.0M 0700 carrier
48 901120 917503 8192K 0700 felica
49 917504 1011711 46.0M 0700 factory
50 1011712 1015807 2048K 0700 spare3
51 1015808 1036287 10.0M 0700 fota
52 1036288 1048575 6144K 0700 spare4
53 1048576 9822207 4284M 0700 system
54 9822208 12345343 1232M 0700 cache
55 12345344 61046783 23.2G 0700 userdata
56 61046784 61071326 11.9M 0700 grow
parted --> print:
Code:
Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name F
1 16.8MB 107MB 90.2MB fat16 modem
2 117MB 118MB 524kB pmic
3 118MB 119MB 1049kB sbl1
4 119MB 120MB 1049kB tz
5 120MB 121MB 524kB sdi
6 121MB 121MB 524kB hyp
7 121MB 122MB 524kB rpm
8 122MB 124MB 2097kB aboot
9 124MB 125MB 1049kB sbl1bak
10 125MB 125MB 524kB pmicbak
11 125MB 126MB 1049kB tzbak
12 126MB 127MB 524kB hypbak
13 127MB 127MB 524kB rpmbak
14 127MB 129MB 2097kB abootbak
15 129MB 130MB 524kB sdibak
16 130MB 131MB 524kB limits
17 131MB 131MB 524kB devinfo
18 131MB 132MB 524kB apdp
19 132MB 132MB 524kB msadp
20 132MB 133MB 524kB dpo
21 133MB 134MB 1573kB spare1
22 134MB 151MB 16.8MB misc
23 151MB 185MB 33.6MB ext4 persist
24 185MB 186MB 1573kB modemst1
25 186MB 188MB 1573kB modemst2
26 188MB 189MB 1573kB fsg
27 189MB 190MB 524kB fsc
28 190MB 190MB 524kB ssd
29 190MB 191MB 524kB keystore
30 191MB 193MB 2097kB DDR
31 193MB 193MB 524kB sec
32 193MB 194MB 524kB encrypt
33 194MB 195MB 524kB eksst
34 195MB 195MB 524kB rct
35 195MB 197MB 2097kB persistent
36 197MB 201MB 4194kB spare2
37 201MB 252MB 50.3MB laf
38 252MB 294MB 41.9MB boot
39 294MB 336MB 41.9MB recovery
40 336MB 344MB 8389kB ext4 drm
41 344MB 352MB 8389kB ext4 sns
42 352MB 386MB 33.6MB ext4 mpt
43 386MB 394MB 8389kB eri
44 394MB 398MB 4194kB raw_resources
45 398MB 403MB 4194kB raw_resourcesbak
46 403MB 419MB 16.8MB operatorlogging
47 419MB 461MB 41.9MB carrier
48 461MB 470MB 8389kB felica
49 470MB 518MB 48.2MB factory
50 518MB 520MB 2097kB spare3
51 520MB 531MB 10.5MB fota
52 531MB 537MB 6291kB spare4
53 537MB 5029MB 4492MB ext4 system
54 5029MB 6321MB 1292MB ext4 cache
55 6321MB 31.3GB 24.9GB ext4 userdata
56 31.3GB 31.3GB 12.6MB grow
---
Diagnosis: 9008, non-ILAPO, caused by me accidentally flashing the v20i bootstack.
I [shoddily] customized gpt_parser.py(based on source from here) to create partition.xml, which I then fed to ptool.py (source) to create the rawprogram0.xml and patch0.xml. Then I fed those into msp.py to create a singleimage.bin that I dd'd over to a microSD card. I inserted the microSD and surprisingly enough my G4 sprang to life instantly!
I booted into TWRP to copy over the what I thought were the correct v20o images to correct the faulty v20i images I had initially used to kill the mofo. That seems to have resulted in a total brick, when I rebooted there was no signs of life at all now, no 9008, no USB peeps at all now. But! the microSD card trick did bring it back from 9008, only it seems I shucked when I should have jived. (me >= woe.)
So maybe I flashed the wrong images *again*? Goddamnit. I should have dipped right into LAF download mode and flashed the stock KDZ. I've been a fool.
Anyway, I'm including the files I used to make all this happen in case anyone finds them useful: [download]
It turns out creating the partition.xml, rawprogram0.xml, and patch0.xml is incredibly simple. Too bad I could not get Firehose to work, it kept throwing this error at me whenever I tried:
Code:
{ERROR: OpenPort:4197 It took 10.01600000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I *was* using a firehose 8992_lite.mbn file from who knows where, that could be why maybe? That is one file I'm not sure how to create yet, though the code to create it is in the same repo at the ptool.py link I posted above.
Click to expand...
Click to collapse
i just wan ask a simple question. If you didn't see a signe of the EMMC memory, so why you bother creating rawprogram etc , i had the same phone , i downgraded from 10N , and i had a hard brick . i was able to turn it back on by the SDcard methode and never been able to see the emmc in TWRP ( /dev directory)

Emmc was fully fleshed out, I perused it before I began dd'ing partitions over to it. Everything seemed normal.

For the H815 variant. I found a working Dump that i flashed into an SD card. I was able to enter download mode and flash a firmware. but as expected the firmware goes to the SD card and the phone is unstable. I have IMEI = 0 and i could not unlock the bootloader.
Bottom line. Ithink that there is some hope of getting the phone to detects the EMMC memory, i dont know how may be a hardware switch or some custum SD card.
I hope that it will soon available

culot said:
Emmc was fully fleshed out, I perused it before I began dd'ing partitions over to it. Everything seemed normal.
Click to expand...
Click to collapse
what did you do to get the 9008 mode working please share :'(

leptdre said:
what did you do to get the 9008 mode working please share :'(
Click to expand...
Click to collapse
It's all right there in my post. Not sure what else to say.? ?

culot said:
It's all right there in my post. Not sure what else to say.? ��
Click to expand...
Click to collapse
i want to know what software did you use and did the phone show sign of life without SD card , cause i have a H811 that i got working with just the SD card and no tweaking what so ever

leptdre said:
i want to know what software did you use and did the phone show sign of life without SD card , cause i have a H811 that i got working with just the SD card and no tweaking what so ever
Click to expand...
Click to collapse
The software I used is detailed in my above post. If you have any specific questions about that let me know.
It was the typical 9008 mode, no signs of life other than showing a 9008 port when USB was plugged in -- that's with no SD card.
I inserted the microSD I formatted with the singleimage.bin, then as soon as I inserted the battery the phone gave its little vibe and began to boot normally. I rebooted into TWRP so I could flash the proper partitions, and then after I rebooted it was dead. Apparently I flashed the wrong ones? I'm not sure, but the microSD trick definitely worked to get it into a state where repair is possible. I should have put it into LAF download mode and flashed a KDZ.
I was overconfident, thinking that no matter what I'd be able to bring it back with that same microSD card. That is not the case: it turns out that whatever I flashed has well and truly bricked it, as now it shows no life signs at all. I was careless, stupid, reckless. So close!
How did you microSD method work? Just flashed full image to the microSD? Details and files are always nice.

culot said:
The software I used is detailed in my above post. If you have any specific questions about that let me know.
It was the typical 9008 mode, no signs of life other than showing a 9008 port when USB was plugged in -- that's with no SD card.
I inserted the microSD I formatted with the singleimage.bin, then as soon as I inserted the battery the phone gave its little vibe and began to boot normally. I rebooted into TWRP so I could flash the proper partitions, and then after I rebooted it was dead. Apparently I flashed the wrong ones? I'm not sure, but the microSD trick definitely worked to get it into a state where repair is possible. I should have put it into LAF download mode and flashed a KDZ.
I was overconfident, thinking that no matter what I'd be able to bring it back with that same microSD card. That is not the case: it turns out that whatever I flashed has well and truly bricked it, as now it shows no life signs at all. I was careless, stupid, reckless. So close!
How did you microSD method work? Just flashed full image to the microSD? Details and files are always nice.
Click to expand...
Click to collapse
1- first you need to resize you micro sd card with SD formatter ( give it its original size)
2- you must low level format it ( not quick format )
3- flash your bin file with win 32 Disk imager ( or DD command in linux ) ( if you dont have a working dump i will upload this evening)
4- put the sd card into the phone , put the battery on , press vol up button and plug a usb cable
5- now you will be able to enter download mode and flash a firmware using LG UP ( flash 10N or above )
obviously the firmware is going to the SD card , from twrp i listed the /dev/block directory , i found no sign of the EMMC memory what so ever, if someone happen to find it please share

culot said:
Variant: H811
Version: v20o
fdisk --> list:
Code:
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 56 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 32768 208895 86.0M 0700 modem
2 229376 230399 512K 0700 pmic
3 230400 232447 1024K 0700 sbl1
4 232448 234495 1024K 0700 tz
5 234496 235519 512K 0700 sdi
6 235520 236543 512K 0700 hyp
7 236544 237567 512K 0700 rpm
8 237568 241663 2048K 0700 aboot
9 241664 243711 1024K 0700 sbl1bak
10 243712 244735 512K 0700 pmicbak
11 244736 246783 1024K 0700 tzbak
12 246784 247807 512K 0700 hypbak
13 247808 248831 512K 0700 rpmbak
14 248832 252927 2048K 0700 abootbak
15 252928 253951 512K 0700 sdibak
16 253952 254975 512K 0700 limits
17 254976 255999 512K 0700 devinfo
18 256000 257023 512K 0700 apdp
19 257024 258047 512K 0700 msadp
20 258048 259071 512K 0700 dpo
21 259072 262143 1536K 0700 spare1
22 262144 294911 16.0M 0700 misc
23 294912 360447 32.0M 0700 persist
24 360448 363519 1536K 0700 modemst1
25 363520 366591 1536K 0700 modemst2
26 366592 369663 1536K 0700 fsg
27 369664 370687 512K 0700 fsc
28 370688 371711 512K 0700 ssd
29 371712 372735 512K 0700 keystore
30 372736 376831 2048K 0700 DDR
31 376832 377855 512K 0700 sec
32 377856 378879 512K 0700 encrypt
33 378880 379903 512K 0700 eksst
34 379904 380927 512K 0700 rct
35 380928 385023 2048K 0700 persistent
36 385024 393215 4096K 0700 spare2
37 393216 491519 48.0M 0700 laf
38 491520 573439 40.0M 0700 boot
39 573440 655359 40.0M 0700 recovery
40 655360 671743 8192K 0700 drm
41 671744 688127 8192K 0700 sns
42 688128 753663 32.0M 0700 mpt
43 753664 770047 8192K 0700 eri
44 770048 778239 4096K 0700 raw_resources
45 778240 786431 4096K 0700 raw_resourcesbak
46 786432 819199 16.0M 0700 operatorlogging
47 819200 901119 40.0M 0700 carrier
48 901120 917503 8192K 0700 felica
49 917504 1011711 46.0M 0700 factory
50 1011712 1015807 2048K 0700 spare3
51 1015808 1036287 10.0M 0700 fota
52 1036288 1048575 6144K 0700 spare4
53 1048576 9822207 4284M 0700 system
54 9822208 12345343 1232M 0700 cache
55 12345344 61046783 23.2G 0700 userdata
56 61046784 61071326 11.9M 0700 grow
parted --> print:
Code:
Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name F
1 16.8MB 107MB 90.2MB fat16 modem
2 117MB 118MB 524kB pmic
3 118MB 119MB 1049kB sbl1
4 119MB 120MB 1049kB tz
5 120MB 121MB 524kB sdi
6 121MB 121MB 524kB hyp
7 121MB 122MB 524kB rpm
8 122MB 124MB 2097kB aboot
9 124MB 125MB 1049kB sbl1bak
10 125MB 125MB 524kB pmicbak
11 125MB 126MB 1049kB tzbak
12 126MB 127MB 524kB hypbak
13 127MB 127MB 524kB rpmbak
14 127MB 129MB 2097kB abootbak
15 129MB 130MB 524kB sdibak
16 130MB 131MB 524kB limits
17 131MB 131MB 524kB devinfo
18 131MB 132MB 524kB apdp
19 132MB 132MB 524kB msadp
20 132MB 133MB 524kB dpo
21 133MB 134MB 1573kB spare1
22 134MB 151MB 16.8MB misc
23 151MB 185MB 33.6MB ext4 persist
24 185MB 186MB 1573kB modemst1
25 186MB 188MB 1573kB modemst2
26 188MB 189MB 1573kB fsg
27 189MB 190MB 524kB fsc
28 190MB 190MB 524kB ssd
29 190MB 191MB 524kB keystore
30 191MB 193MB 2097kB DDR
31 193MB 193MB 524kB sec
32 193MB 194MB 524kB encrypt
33 194MB 195MB 524kB eksst
34 195MB 195MB 524kB rct
35 195MB 197MB 2097kB persistent
36 197MB 201MB 4194kB spare2
37 201MB 252MB 50.3MB laf
38 252MB 294MB 41.9MB boot
39 294MB 336MB 41.9MB recovery
40 336MB 344MB 8389kB ext4 drm
41 344MB 352MB 8389kB ext4 sns
42 352MB 386MB 33.6MB ext4 mpt
43 386MB 394MB 8389kB eri
44 394MB 398MB 4194kB raw_resources
45 398MB 403MB 4194kB raw_resourcesbak
46 403MB 419MB 16.8MB operatorlogging
47 419MB 461MB 41.9MB carrier
48 461MB 470MB 8389kB felica
49 470MB 518MB 48.2MB factory
50 518MB 520MB 2097kB spare3
51 520MB 531MB 10.5MB fota
52 531MB 537MB 6291kB spare4
53 537MB 5029MB 4492MB ext4 system
54 5029MB 6321MB 1292MB ext4 cache
55 6321MB 31.3GB 24.9GB ext4 userdata
56 31.3GB 31.3GB 12.6MB grow
---
Diagnosis: 9008, non-ILAPO, caused by me accidentally flashing the v20i bootstack.
I [shoddily] customized gpt_parser.py(based on source from here) to create partition.xml, which I then fed to ptool.py (source) to create the rawprogram0.xml and patch0.xml. Then I fed those into msp.py to create a singleimage.bin that I dd'd over to a microSD card. I inserted the microSD and surprisingly enough my G4 sprang to life instantly!
I booted into TWRP to copy over the what I thought were the correct v20o images to correct the faulty v20i images I had initially used to kill the mofo. That seems to have resulted in a total brick, when I rebooted there was no signs of life at all now, no 9008, no USB peeps at all now. But! the microSD card trick did bring it back from 9008, only it seems I shucked when I should have jived. (me >= woe.)
So maybe I flashed the wrong images *again*? Goddamnit. I should have dipped right into LAF download mode and flashed the stock KDZ. I've been a fool.
Anyway, I'm including the files I used to make all this happen in case anyone finds them useful: [download]
It turns out creating the partition.xml, rawprogram0.xml, and patch0.xml is incredibly simple. Too bad I could not get Firehose to work, it kept throwing this error at me whenever I tried:
Code:
{ERROR: OpenPort:4197 It took 10.01600000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I *was* using a firehose 8992_lite.mbn file from who knows where, that could be why maybe? That is one file I'm not sure how to create yet, though the code to create it is in the same repo at the ptool.py link I posted above.
Click to expand...
Click to collapse
plz give me the link of this file firehose 8992_lite.mbn for h811

leptdre said:
1- first you need to resize you micro sd card with SD formatter ( give it its original size)
2- you must low level format it ( not quick format )
3- flash your bin file with win 32 Disk imager ( or DD command in linux ) ( if you dont have a working dump i will upload this evening)
4- put the sd card into the phone , put the battery on , press vol up button and plug a usb cable
5- now you will be able to enter download mode and flash a firmware using LG UP ( flash 10N or above )
obviously the firmware is going to the SD card , from twrp i listed the /dev/block directory , i found no sign of the EMMC memory what so ever, if someone happen to find it please share
Click to expand...
Click to collapse
please give me link bin file for g4 h811
thanks

I kept getting Secure Boot Error when I figured out how to do this. We should just be able to use the KDZ, since everything is on there that is needed to get into Download mode.
LG still holding my phone hostage since the 16th...not happy!

Noksucow1 said:
I kept getting Secure Boot Error when I figured out how to do this. We should just be able to use the KDZ, since everything is on there that is needed to get into Download mode.
LG still holding my phone hostage since the 16th...not happy!
Click to expand...
Click to collapse
Was your bootloadwr previously unlocked?

can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it....

T.E.I.M said:
can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it....
Click to expand...
Click to collapse
you can use it you just need a clean SD card like i sad

culot said:
Was your bootloadwr previously unlocked?
Click to expand...
Click to collapse
No, I had the Unlock OEM checked, other than that no...It's not on the list.

boot S9 from another GPT partition.

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.

Increasing boot_a size

Hi,
I want to increase boot_a to a minimum of 64 MiB. I saw that Google Pixel 2 XL has last_parti free with size 76 MiB, but when I typed sgdisk new it ended in failure:
Code:
# sgdisk --new=42:332585:352250 --change-name=42:boot_a --typecode=42:20117F86-E985-4357-B9EE-374BC1D8487D
Could not create partition 42 from 332585 to 352250
Setting name!
partNum is 41
REALLY setting name!
Unable to set partition 42's name to 'boot_a'!
Could not change partition 42's type code to 20117F86-E985-4357-B9EE-374BC1D8487D!
Error encountered; not saving changes.
Why it could not create a partition? I tried with 8 instead of 42, but the error is the same. Current part table:
Code:
taimen:/ # sgdisk --print /dev/block/sde
Disk /dev/block/sde: 352256 sectors, 1.3 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 25C6DACF-4929-0791-2561-11DD6D31D595
Partition table holds up to 64 entries
First usable sector is 6, last usable sector is 352250
Partitions will be aligned on 1-sector boundaries
Total free space is 19666 sectors (76.8 MiB)
Number Start (sector) End (sector) Size Code Name
1 6 133 512.0 KiB FFFF rpm_a
2 134 645 2.0 MiB FFFF tz_a
3 646 773 512.0 KiB FFFF hyp_a
4 774 901 512.0 KiB FFFF pmic_a
5 902 21381 80.0 MiB 0700 modem_a
6 21382 21637 1024.0 KiB FFFF abl_a
7 21638 21765 512.0 KiB FFFF keymaster_a
8 21766 32005 40.0 MiB FFFF boot_a
9 32006 32133 512.0 KiB FFFF cmnlib_a
10 32134 32261 512.0 KiB FFFF cmnlib64_a
11 32262 32293 128.0 KiB FFFF devcfg_a
12 32294 32309 64.0 KiB FFFF vbmeta_a
13 32310 34357 8.0 MiB FFFF dtbo_a
14 34358 162357 500.0 MiB FFFF vendor_a
15 162358 162485 512.0 KiB FFFF rpm_b
16 162486 162997 2.0 MiB FFFF tz_b
17 162998 163125 512.0 KiB FFFF hyp_b
18 163126 163253 512.0 KiB FFFF pmic_b
19 163254 183733 80.0 MiB FFFF modem_b
20 183734 183989 1024.0 KiB FFFF abl_b
21 183990 184117 512.0 KiB FFFF keymaster_b
22 184118 194357 40.0 MiB FFFF boot_b
23 194358 194485 512.0 KiB FFFF cmnlib_b
24 194486 194613 512.0 KiB FFFF cmnlib64_b
25 194614 194645 128.0 KiB FFFF devcfg_b
26 194646 194661 64.0 KiB FFFF vbmeta_b
27 194662 196709 8.0 MiB FFFF dtbo_b
28 196710 324709 500.0 MiB FFFF vendor_b
29 324710 324773 256.0 KiB FFFF apdp
30 324774 324837 256.0 KiB FFFF msadp
31 324838 324869 128.0 KiB FFFF storsec
32 324870 325381 2.0 MiB FFFF fsg
33 325382 325413 128.0 KiB FFFF sec
34 325414 325414 4.0 KiB FFFF devinfo
35 325415 325670 1024.0 KiB FFFF dip
36 325671 325671 4.0 KiB FFFF dpo
37 325672 325672 4.0 KiB FFFF limits
38 325673 325928 1024.0 KiB FFFF toolsfv
39 325929 327976 8.0 MiB FFFF logfs
40 327977 328488 2.0 MiB FFFF sti
41 328489 332584 16.0 MiB FFFF metadata
42 332585 352250 76.8 MiB FFFF last_parti
taimen:/ #
I uploaded also a backup of my /dev/block/sde. I tried to test also on /dev/loop on my PC, but still nothing. I can't also delete last_parti, because it doesn't exist. Interestingly, this range is free:
Code:
taimen:/ # sgdisk --first-in-largest /dev/block/sde
332585
taimen:/ # sgdisk --end-of-largest /dev/block/sde
352250
Edit: solved by resizing vendor_b to 250 MiB and added boot_a after vendor_b.