Is there a way to convert KDZ to TOT? - LG G5 Questions & Answers

I wish to find some one to work together to build a tool that can covert kdz to TOT.
Now, XDA forum has a tool that extract kdz file,, I wish we can pack those extracted files into a "custom" tot file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When i extract custom LG H815 TOT which is only 4MB, I got follow information:
found file PrimaryGPT.bin
count parts partition found 4
Name grow First LBA 61046784 Last LBA 61071326
Name userdata First LBA 12419072 Last LBA 61046783
Name cache First LBA 9895936 Last LBA 12419071
Name cust First LBA 9363456 Last LBA 9887743
Name system First LBA 884736 Last LBA 9363455
Name raw_resourcesbak First LBA 876544 Last LBA 884735
Name raw_resources First LBA 868352 Last LBA 876543
Name fota First LBA 847872 Last LBA 868351
Name factory First LBA 753664 Last LBA 847871
Name mpt First LBA 688128 Last LBA 753663
Name sns First LBA 671744 Last LBA 688127
Name drm First LBA 655360 Last LBA 671743
Name recovery First LBA 573440 Last LBA 655359
Name boot First LBA 491520 Last LBA 573439
Name laf First LBA 393216 Last LBA 491519
Name spare2 First LBA 385024 Last LBA 393215
Name persistent First LBA 380928 Last LBA 385023
Name rct First LBA 379904 Last LBA 380927
Name eksst First LBA 378880 Last LBA 379903
Name encrypt First LBA 377856 Last LBA 378879
Name sec First LBA 376832 Last LBA 377855
Name DDR First LBA 372736 Last LBA 376831
Name keystore First LBA 371712 Last LBA 372735
Name ssd First LBA 370688 Last LBA 371711
Name fsc First LBA 369664 Last LBA 370687
Name fsg First LBA 366592 Last LBA 369663
Name modemst2 First LBA 363520 Last LBA 366591
Name modemst1 First LBA 360448 Last LBA 363519
Name persist First LBA 294912 Last LBA 360447
Name misc First LBA 262144 Last LBA 294911
Name spare1 First LBA 259072 Last LBA 262143
Name dpo First LBA 258048 Last LBA 259071
Name msadp First LBA 257024 Last LBA 258047
Name apdp First LBA 256000 Last LBA 257023
Name devinfo First LBA 254976 Last LBA 255999
Name limits First LBA 253952 Last LBA 254975
Name sdibak First LBA 252928 Last LBA 253951
Name abootbak First LBA 248832 Last LBA 252927
Name rpmbak First LBA 247808 Last LBA 248831
Name hypbak First LBA 246784 Last LBA 247807
Name tzbak First LBA 244736 Last LBA 246783
Name pmicbak First LBA 243712 Last LBA 244735
Name sbl1bak First LBA 241664 Last LBA 243711
Name aboot First LBA 237568 Last LBA 241663
Name rpm First LBA 236544 Last LBA 237567
Name hyp First LBA 235520 Last LBA 236543
Name sdi First LBA 234496 Last LBA 235519
Name tz First LBA 232448 Last LBA 234495
Name sbl1 First LBA 230400 Last LBA 232447
Name pmic First LBA 229376 Last LBA 230399
Name modem First LBA 32768 Last LBA 208895
found file EFI PAR
File Name LGH815AT-00-V20a-GLOBAL-COM-NOV-02-2015+00
Model Name VLG-H815
byte read position 1049096
found in TOT Header pos 45-46-49-20-50-41-52-54
byte read position 1049088
Not a KDZ file
found in KDZ Header pos 44-DD-55-AA-FF-FF-FF-FF
byte read position 0
KDZ file C:\Users\Administrator\Downloads\G4 series MSM Big core disable tool Install_v7.0\G4 series MSM Big core disable tool File_v7.0\MOS\H815T\LGH815AT-00-V20a-GLOBAL-COM-NOV-02-2015+00_RECOVERY_6.0.tot

anyone has the h811 tot file?

Related

Another way to reconstruct providers ROMS

The current form of rebuilding ROM for Niki, using the kitchen Kaiser, this very well but I think that this method is more simple and the ROM is identical to the source.
I rebuilt two well ROM Spanish, tested by makoky. I donĀ“t have this model.
The structure of ROM is the AsianWWE identities.
You need attached file and tree first parts extracted from your machine.
Code:
E:\Extract\niki.es>COPY /B inicio.bin+Part00.raw+Part01.raw os.nb.base
inicio.bin
Part00.raw
Part01.raw
1 archivos copiados.
E:\Extract\niki.es>COPY /B relleno.bin+Part02.raw imgfs.bin
relleno.bin
Part02.raw
1 archivos copiados.
E:\Extract\niki.es>..\Tools\ImgfsToNb.exe imgfs.bin OS.NB.base os.nb.payload
ImgfsToNb 2.1rc2
Using bigstorage mode
Sector size is 0x800 bytes
Writing imgfs to offset byte 0x6a0000, sector 0xd40
Padding ImgFs from 0x5060000 bytes (0xa0c0 sectors)
to 0x5060000 bytes (0xa0c0 sectors)
Not conservative mode. Changing imgfsEnd from 0x59c0000 to 0x5700000
Partition entry before:
File System: 0x25
Start Sector: 0x00000d40
Total Sectors: 0x0000a640
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x35
Last Head: 0x3f
Last Sector: 0x01
Last Track: 0x2cd
Partition entry after:
File System: 0x25
Start Sector: 0x00000d40
Total Sectors: 0x0000a0c0
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x35
Last Head: 0x3f
Last Sector: 0x01
Last Track: 0x2b7
Partition entry before:
File System: 0x04
Start Sector: 0x0000b380
Total Sectors: 0x0000ff40
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x2ce
Last Head: 0x3f
Last Sector: 0x01
Last Track: 0x2ca
Partition entry after:
File System: 0x04
Start Sector: 0x0000ae00
Total Sectors: 0x000104c0
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x2b8
Last Head: 0x3f
Last Sector: 0x01
Last Track: 0x2ca
ImgFs Flash Region log blocks was 0x299, now is 0x283
Storage Flash Region log block was 0xffffffff, now is 0xffffffff,
Done!
E:\Extract\niki.es>..\Tools\NBMerge.exe -kaiser OS.NB
NBMerge 2.1rc2
Executing ..\Tools\NBMerge.exe with data chunk size = 0x800 and extra chunk size
= 0x8
on file OS.NB
Partition 0: start sector: 0x00000002, total: 0x0000063e
first used: 0x00000002, used: 0x00000600
Partition 1: start sector: 0x00000640, total: 0x00000700
first used: 0x00000640, used: 0x000005df
Partition 2: start sector: 0x00000d40, total: 0x0000a0c0
first used: 0x00000dc0, used: 0x0000a040
Checking OS.NB for bad NAND block marker
Checked 0xae00 sectors successfully!
Done.
E:\Extract\niki.es>
In attached file, you have two files extracted from AsianWEE, Ones is the header of ROM and another are some free bytes at start of imgfs.
If someone finds any error, please say so.
PD. Sorry for my bad english
Can someone confirm this methode of working? Or should we still hang on to the Kaiser methode?
mastogo the best!
Eres el mejor mastogo
Un Saludo.
FatalZero said:
Can someone confirm this methode of working? Or should we still hang on to the Kaiser methode?
Click to expand...
Click to collapse
I am waiting for several friends selected for testing, but still have not received their niki.
But I can say that the structure of the ROM seems perfect and teory must operate.
Work
And I can say that this method works correctly, the two ROMs have been tested by makoky in his Niki work and perfect.
This method is much simpler and faster than the one currently used on the basis of the cuisine of the Kaiser and the ROM is identical to the original.
It is necessary to use uSPL or HardSPL only by the signature tool.
If you need these spanish roms, you can get here.
is this method intended only for Spanish Niki phones/users or anyone can follow this method to reconstruct his rom?
thx
So afterward i get a complete Rom ready to flash?
Still need a way to backup my german rom.
Don't wanna switch to niki projct rom without a chance to get back.
Hallo Thyraz,
ich habe das Verfahren erfolgreich getestet. Ich hatte einen Dump mit itsutils gemacht, mit dem Verfahren von mastsogo ein rebuild gemacht, mit kaiserkitchen_01-20-08 erfolgreich geflashed.
Aber daran denken: Hard-SPL installieren.
Danke
Werd mich die Tage dann auch mal ransetzen.
eroG said:
is this method intended only for Spanish Niki phones/users or anyone can follow this method to reconstruct his rom?
thx
Click to expand...
Click to collapse
This method is valid for roms of other languages as well.
Thyraz said:
So afterward i get a complete Rom ready to flash?
Still need a way to backup my german rom.
Don't wanna switch to niki projct rom without a chance to get back.
Click to expand...
Click to collapse
Once rebuilt only in the ROM required to sign HTC Rom Tool to be able to flash.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This utility can be found in this thread: http://forum.xda-developers.com/showthread.php?t=311909&highlight=htcrt

[Q] My device (16GB) seems to be completely broken and ID in adb is 0000000000000000

Unfortunately, I don't have a backup of mmcblk0p5, but even if I try (out of desperation) to flash someone else's mmcblk0p5, ID doesn't change from zeros. I managed to run CM7 from external sdcard, but installing CM onto mmc doesn't seem to work.
Ubuntu Total Reflash from this forum flashed al successfully, but failed on recovering stage and since then it just bootloops to that point (boot -> factory reset fails -> reboot).
Now trying to flash stock ROM 1.4.0, but don't think it'll work. Any advice?
P.S. Now found something strange: mmcblkp7 (seventh partition is gone, and that seem to repeat after every recovery option I try).
Code:
Number Start (sector) End (sector) Size Code Name
1 256 511 128.0 KiB 8300 xloader
2 512 1023 256.0 KiB 8300 bootloader
3 1024 31743 15.0 MiB 8300 recovery
4 32768 65535 16.0 MiB 8300 boot
5 65536 163839 48.0 MiB 8300 rom
6 163840 262143 48.0 MiB 8300 bootdata
8 1019904 2273279 612.0 MiB 8300 system
9 2273280 3145727 426.0 MiB 8300 cache
10 3145728 5242879 1024.0 MiB 8300 media
11 5242880 30535639 12.1 GiB 8300 userdata
UPD.: Paste from parted's print after I create partition 7 (factory):
Code:
(parted) print
print
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
Your NT's factory installed device info (ProductID, manufactured data, etc.) and individual device data (serial no., MAC address, security encryption keys, etc.) are stored in p5 and p7, if you reformatted these two partitions all that info was wiped out and the individual device data can't be replaced with data from another NT. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more details.
digixmax said:
Your NT's factory installed device info (ProductID, manufactured data, etc.) and individual device data (serial no., MAC address, security encryption keys, etc.) are stored in p5 and p7, if you reformatted these two partitions all that info was wiped out and the individual device data can't be replaced with data from another NT. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more details.
Click to expand...
Click to collapse
Oh, that's unfortunate. I didn't wipe it by myself, it just suddenly got stuck after i got ~4% of battery charge the other day. Can I do something for it?
P.S. Or, if nothing can be done, what's the most simplistic/minimalistic yet full-[stock]-feature ROM for sdcard available? Disregarding Android verion.
digixmax said:
Your NT's factory installed device info (ProductID, manufactured data, etc.) and individual device data (serial no., MAC address, security encryption keys, etc.) are stored in p5 and p7, if you reformatted these two partitions all that info was wiped out and the individual device data can't be replaced with data from another NT. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more details.
Click to expand...
Click to collapse
Huh, seems like I did it. I even can't recall all the steps I performed, but it included just little more messing up with gdisk/parted, trying to wipe all data and caches through CWM and install CM10.1, but that failed as usually, so I just uploaded Veronica's mmcblk0p5 again, then I thought "wtf, let's give it another try" and applied Ubuntu Total Reflash procedure and it worked! All of a sudden, I have my factory-state Nook (saying nothing about case cracks and fractures ^_^).
So, now I'm going to share link to this post with all the people I think are relevant to this question and ask them: is that normal? Can I try to flash CM 10.1 now without *too much* risk of getting my dear brick again? Thanks in advance.
UPD: Checked ID, MAC and so on - seems to be different from 00...0, but I'm not sure whether it's still unique (i reckon that they are like Veronica's now).
UPD2: Installed CM 10.1 rather successfully. I guess, someone can add to FAQ that even with broken mmcblk0p5 one still could help himself.

S3 LTE Partition Resizing?

I dont know about anyone else but the partition layout on the S3 LTE really bother's me it just wastes so much
has any work been done on seeing if resizing causes any problems
as im tempted to resize cache,system,hidden to pull back 1971mb of space wasted by samsung
then make a custom full odin package with the new partition sizes and flash
clearly i wouldnt be able to use standard samsung packages anymore and would have to make my own
which isnt a problem
All sizes are in true Megabyte/Gigabyte what is called Mib/Gib by people of late
to try and differentiate from the stupid ass rounding hd manufacturers started
TOMBSTONES = 256mb
CACHE = 1024mb
SYSTEM = 1536mb
HIDDEN = 560mb
Leaving 10.8GB for userdata
Im unsure what the tombstones dir is used for so i would be inclined to leave it
but cache can be dropped to 100mb if not using ota updates which i dont
system i could drop to 1024mb and be fine
i dont think hidden is used on the s3 lte
so i could pull back around 1971mb of wasted space
for userdatea with partitions like below
CACHE = 100mb
SYSTEM = 1024mb
HIDDEN = 1mb
Here's the current layout
Note it isnt even 16 fake GB
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1506MB 1074MB ext4 CACHE
13 1506MB 3116MB 1611MB ext4 SYSTEM
14 3116MB 3704MB 587MB ext4 HIDDEN
15 3704MB 3712MB 8389kB OTA
16 3712MB 15.8GB 12.0GB ext4 USERDATA
ShonkUK said:
I dont know about anyone else but the partition layout on the S3 LTE really bother's me it just wastes so much
has any work been done on seeing if resizing causes any problems
as im tempted to resize cache,system,hidden to pull back 1971mb of space wasted by samsung
then make a custom full odin package with the new partition sizes and flash
clearly i wouldnt be able to use standard samsung packages anymore and would have to make my own
which isnt a problem
All sizes are in true Megabyte/Gigabyte what is called Mib/Gib by people of late
to try and differentiate from the stupid ass rounding hd manufacturers started
TOMBSTONES = 256mb
CACHE = 1024mb
SYSTEM = 1536mb
HIDDEN = 560mb
Leaving 10.8GB for userdata
Im unsure what the tombstones dir is used for so i would be inclined to leave it
but cache can be dropped to 100mb if not using ota updates which i dont
system i could drop to 1024mb and be fine
i dont think hidden is used on the s3 lte
so i could pull back around 1971mb of wasted space
for userdatea with partitions like below
CACHE = 100mb
SYSTEM = 1024mb
HIDDEN = 1mb
Click to expand...
Click to collapse
You can do it with PIT Magic i did this before for S2 I'd like to do the same thing with s3 but i don't have the PIT file for the international version (My Phone )

cant modify ANY parttions - I want to totally ZAP the flash

I have a NOOK tablet 16GB that is somehow locked from modifying partitions
I have tried
the repart image , which has worked many times for me in the past
the AdamOutler Ubuntu Disk
formatting / wiping options in various versions of CWM and TWRP
fastboot erases
fastboot formats
dd'ing /zero to various partitions
parted
sgdisk
a zillion scripts
something at a low level is preventing modifications to the partitions
Im wasting far too much time on this , but I hate being beat (-:
I have a backup of rom and factory , and dd images of stock parttions so I am 100% comfortable with something that
will COMPLETELY ZAP the device
if I boot a known good CM10 image from SD card, it fails to boot , I was assuming if I could get a running android from the card, I'd have access to lots of tools... , but it just fails to tun CM10
any help appreciated.
Thanks
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
sagirfahmid3 said:
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
Click to expand...
Click to collapse
Thanks for responding, Yes, I have tried multiple ways to to zap the table and it doesnt stick.
sgdisk -Z, sgdisk -z parted,
no matter what I do the partitions remain untouched.
I reboot and it still boots into an old stock OS that has a FC shortly after startup, and the internal recovery (factory) , which I can not overwrite, gives the please restart and try again message.
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
mikeataol said:
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
Click to expand...
Click to collapse
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
sagirfahmid3 said:
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
Click to expand...
Click to collapse
Hi, no, I didnt forget to "write" after the "o"
/tmp # ./gdisk /dev/block/mmcblk0
./gdisk /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.
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): o
o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
y
Command (? for help): w
w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
y
OK; writing new GUID partition table (GPT) to /dev/block/mmcblk0.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
/tmp # q
/tmp #
after reboot
Command (? for help): p
p
Disk /dev/block/mmcblk0: 31105024 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): CE21388C-B927-4A5C-91CE-DBD1DE4AB3BC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30535678
Partitions will be aligned on 256-sector boundaries
Total free space is 1285 sectors (642.5 KiB)
Number Start (sector) End (sector) Size Code Name
1 256 511 128.0 KiB 8300 xloader
2 512 1023 256.0 KiB 8300 bootloader
3 1024 31743 15.0 MiB 8300 recovery
4 32768 65535 16.0 MiB 8300 boot
5 65536 163839 48.0 MiB 8300 rom
6 163840 262143 48.0 MiB 8300 bootdata
7 262144 1019903 370.0 MiB 8300 factory
8 1019904 2273279 612.0 MiB 8300 system
9 2273280 3145727 426.0 MiB 8300 cache
10 3145728 5242879 1024.0 MiB 8300 media
11 5242880 30535639 12.1 GiB 8300 userdata
Humm...wow, that's pretty crazy. Try writing zeroes to your emmc and then retrying.
# dd if=/dev/zero of=/dev/block/mmcblk0

PartitioningTool.py fails on 1 kb partition

This is my partition table as generated by gdisk
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 313196 sectors (152.9 MiB)
Code:
# Name Start (sector) End (sector) Size Size (Sectors) Partition GUID Code
1 modem 131072 262143 64 MB 131072 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
2 sbl1 262144 263167 512KiB 1024 DEA0BA2C-CBDD-4805-B4F9-F428251C3E98
3 sbl1bak 263168 264191 512KiB 1024 DEA0BA2C-CBDD-4805-B4F9-F428251C3E98
4 aboot 264192 266239 1024KiB 2048 400FFDCD-22E0-47E7-9A23-F16ED9382388
5 abootbak 266240 268287 1024KiB 2048 400FFDCD-22E0-47E7-9A23-F16ED9382388
6 rpm 268288 269311 512KiB 1024 098DF793-D712-413D-9D4E-89D711772228
7 rpmbak 269312 270335 512KiB 1024 098DF793-D712-413D-9D4E-89D711772228
8 tz 270336 271871 768KiB 1536 A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4
9 tzbak 271872 273407 768KiB 1536 A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4
10 pad 273408 275455 1024KiB 2048 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
11 modemst1 275456 278527 1.5MiB 3072 EBBEADAF-22C9-E33B-8F5D-0E81686A68CB
12 modemst2 278528 281599 1.5MiB 3072 0A288B1F-22C9-E33B-8F5D-0E81686A68CB
13 misc 281600 283647 1024KiB 2048 82ACC91F-357C-4A68-9C8F-689E1B1A23A1
14 fsc 283648 283649 1024Bytes 2 57B90A16-22C9-E33B-8F5D-0E81686A68CB
15 ssd 283650 283665 8KiB 16 2C86E742-745E-4FDD-BFD8-B6A7AC638772
16 splash 283666 304145 10MiB 20480 20117F86-E985-4357-B9EE-374BC1D8487D
17 DDR 393216 393279 32KiB 64 20A0C19C-286A-42FA-9CE7-F64C3226A794
18 fsg 393280 396351 1.5MiB 3072 638FF8E2-22C9-E33B-8F5D-0E81686A68CB
19 sec 396352 396383 16KiB 32 303E6AC3-AF15-4C54-9E9B-D9A8FBECF401
20 boot 396384 461919 32MiB 65536 20117F86-E985-4357-B9EE-374BC1D8487D
21 system 461920 4557919 2GB 4096000 97D7B011-54DA-4835-B3C4-917AD6E73D74
22 persist 4557920 4623455 32MiB 65536 6C95E238-E343-4BA8-B489-8681ED22AD0B
23 apedata 4623456 4688991 32MiB 65536 6C95E238-E343-4BA8-B489-8681ED22AD0B
24 cache 4688992 5213279 256MiB 524288 5594C694-C871-4B5F-90B1-690A6F68E0F7
25 recovery 5213280 5278815 32MiB 65536 9D72D4E4-9958-42DA-AC26-BEA7A90B0434
26 devinfo 5278816 5280863 1024KiB 2048 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
27 keystore 5373952 5374975 512KiB 1024 DE7D4029-0F5B-41C8-AE7E-F6C023A02B33
28 oem 5374976 5506047 64MiB 131072 7DB6AC55-ECB5-4E02-80DA-4D335B973332
29 config 5506048 5507071 512KiB 1024 91B72D4D-71E0-4CBF-9B8E-236381CFF17A
30 userdata 5507072 15269854 4.7GiB 9762783 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
My version of the tool is this
Code:
!/usr/bin/python
#===========================================================================
# This script parses "partition.xml" and creates numerous output files
# specifically, partition.bin, rawprogram.xml
# REFERENCES
# $Header: //source/qcom/qct/core/pkg/bootloaders/rel/1.2/boot_images/core/storage/tools/jsdcc/partition_load_pt/PartitioningTool.py#2 $
# $DateTime: 2012/01/12 16:00:13 $
# $Author: coresvc $
# when who what, where, why
# -------- --- -------------------------------------------------------
# 2011-03-22 ah rawprogram for GPT for 'grow' partition, since mjsdload.cmm couldn't handle big number
# 2011-03-22 ah Corrected final disk size patch (off by 1 sector), corrected GPT labels (uni-code)
# 2011-03-18 ah Fixed default bug for DISK_SIGNATURE, align_wpb -> align
# 2011-03-16 ah New DISK_SIGNATURE tag added for MBR partitions, Split partition0.bin into
# MBR0.bin and EBR0.bin, Corrected bug in backup GPT DISK patching
# 2011-03-10 ah Removes loadpt.cmm, splits partition0.bin to MBR0.bin, EBR0.bin
# 2011-03-09 ah Much more error checking, cleaner, adds "align_wpb" tag
# 2011-02-14 ah Added patching of DISK for GPT
# 2011-02-02 ah Allow MBR Type to be specified as "4C" or "0x4C"
# 2011-25-01 ah Outputs "patch.xml" as well, allows more optimal partition alignment
# 2010-12-01 ah Matching QPST, all EXT partitions 64MB aligned (configurable actually)
# More error checking, Removed CHS option, GPT output is 2 files (primary and backup)
# 2010-10-26 ah better error checking, corrected typo on physical_partition for > 0
# 2010-10-25 ah adds GPT, CFILE output, various other features
# 2010-10-08 ah released to remove compile errors of missing PERL script modules
I am purposely trying to keep my fsc partition to 1kb. I can make the change in my xml file to 2kb and the tool will continue. If I leave it at 1kb it will error out. Anyone else have this issue?
Should have held off asking. Once I found a newer version of the tool that issue is solved. Case closed.

Categories

Resources