OK, so I have been at this for a while now, trying to figure out how to pull boot.img. We need this in order to get a custom recovery image made.
The problem is that most of the help that's out there refers to doing a dump based on identifying the proper /proc/MTD. It's never that simple though. This phone doesn't have it (and we don't have a map of where to go from here).
Here is the partition info:
Code:
major minor #blocks name
7 0 13545 loop0
7 1 202829 loop1
7 2 31217 loop2
7 3 18743 loop3
7 4 13545 loop4
179 0 15679488 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 7168 mmcblk0p3
179 4 1 mmcblk0p4
179 5 28672 mmcblk0p5
179 6 204800 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 1024000 mmcblk0p12
179 13 1572864 mmcblk0p13
179 14 12288 mmcblk0p14
179 15 12599296 mmcblk0p15
179 16 15622144 mmcblk1
179 17 15621120 mmcblk1p1
254 0 13545 dm-0
254 1 202828 dm-1
254 2 31216 dm-2
254 3 18742 dm-3
254 4 13545 dm-4
Can anyone with a few more years on me in this racket give me a heads up on this? Perhaps a mapping for us to get started? Yeah, I know I'm totally wet behind the ears, but someone has to get this thing rolling. Hopefully that doesn't mean I'll be the first to brick my phone (had a close call tonight).
See what's mounted by typing "mount" first. It'll show you what mmcblk0pX maps to what (mounted, that is).
thecubed said:
See what's mounted by typing "mount" first. It'll show you what mmcblk0pX maps to what (mounted, that is).
Click to expand...
Click to collapse
ok, so here was the output (of what i assume is the relevant part):
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p12 /system ext3 ro,relatime,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p5 /persist ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
So 12 is system, 13 is data, 6 is cache, and 5 is persist. What I'm not seeing is boot. Am I missing anything here?
To find unnamed partitions, you might want to dump them to your SD card and try mounting the partitions on your PC.
You can copy a partition to a file on your SD card by using "dd if=/dev/block/mmcblk0pX of=/sdcard/mmcblk0pX.img bs=1024"
Then on your desktop, you can try running fdisk to see what the partition type is and issue a "mkdir /mnt/test" then "mount -o loop -t <type of partition from fdisk> /path/to/mmcblk0pX.img /mnt/test".
From there, you should be able to investigate what's in those partitions by poking around in /mnt/test on your desktop. Once you're done, "umount /mnt/test" to close the image file.
Referring to your list of partitions and sizes, partitions of 2048 blocks or less are probably not worth your time investigating, however I may be wrong.
Also, quick tip: mmcblk0 (with no pX) is the entire onboard storage as one unit. Don't bother dumping that to your SD card, since it contains all partitions, but will be a really big file and a big mess to figure out the partitions and mount it.
Good luck!
Outstanding, and THANKS A MILLION for the help. I've been banging my head against the wall here...
I should probably hit the sack, but I had started pulling those already, so I've got a head start.
Okay, good luck! I don't have this device, but a friend is getting one here soon (not sure how soon though) so I'm interested in getting CWM ported and some groundwork laid for CM7/etc on it.
Whenever you get time, I'm interested in seeing what you find the partitions are...
Thanks!
Went ahead and put a little more time into it...
used your method for dumping each individual partition.
A listing with file sizes:
Code:
2048 mmcblk0p1 4096 mmcblk0p11 2048 mmcblk0p2 4 mmcblk0p4 24576 mmcblk0p8
4096 mmcblk0p10 12288 mmcblk0p14 7168 mmcblk0p3 4096 mmcblk0p7 8192 mmcblk0p9
My common fdisk result (for all files) is:
Code:
fdisk -l mmcblk0p11
Disk mmcblk0p11: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf6908d66
Disk mmcblk0p11 doesn't contain a valid partition table
Maybe I need to look at this again when I'm a little less tired, but this is the result of every image file.
P11 looks to be just a placeholder partition. Try p3, p8, p9, and p14.
Usually /boot is a lower number partition...
If you could upload the dumps of those partitions somewhere, I may be able to tell you which is which. (PM the link, don't post public- I'm not sure how XDA would feel about that).
This shouldn't be too hard to identify which is which. If you're well versed in hex editing, you could run those images through a hex dumper and check the file's magic numbers. I'm not too familiar with this device, but I'd say it can't be much different than the HTC boot.img format. Grab a boot.img from somewhere and see if the first couple of bytes match up on the dumps you've got.
From there, that should give you a clue with which is which. I'm betting you'll find which is the kernel by just doing a "strings" on the dumps and looking for things like "kernel" or "linux".
Good luck!
EDIT: after doing some reading, looks like some of the partitions are the fastboot type. Fastboot images = kernel + ramdisk. And, at least one of those partitions will be the Qualcomm AMSS partition for the radio chipset. Do a "strings <filename> | grep -i qualcomm" (or replace qualcomm with things like 'amss' or 'radio') to find which is which.
QualComm didn't turn up anything, so I changed the search to "comm." I don't have much time to look at this, but here's a quick dump:
mmcblk0p1 = radio?
Code:
mmcblk0p1 | grep -i comm
Device Transfer: Failed to queue the transfer command
DMOV Issue Cmd: Command issued
DMOV Request not Valid: Command list not on 64-bit boundary
DMOV Request not Valid: Invalid number of commands
DMOV Get Chan %d Error: Command error occured
DMOV Get Chan %d Error: Command-phase bus error occured
DMOV Stop Handler: cannot stop channel %d, commands pending
DMOV Stop Handler: cannot stop channel %d, issuing commands
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
mmcblk0p2 = boot?
Code:
strings mmcblk0p2 | grep -i comm
QC_SMEM_PROC_COMM_CQ
ip_uint32 idev_comm_open( void )
dt_uint32 dt_CommOpen( void )
void idev_comm_close(ip_uint32 h)
void dt_CommClose(dt_uint32 h)
ip_commStatus_e idev_comm_queryCloseStatus(ip_uint32 h)
ip_commStatus_e idev_comm_queryConnectStatus(ip_uint32 h)
dt_CommStatus dt_QueryConnectStatus(dt_uint32 h)
const ip_int16 idev_comm_secureInitContext( void )
const dt_int16 dt_CommSecureInitContext( void )
void idev_comm_secureDeleteContext( void )
void dt_CommSecureDeleteContext( void )
EP0 command reply was not sent correctly %d [%d:%d]
Device Transfer: Failed to queue the transfer command
[AUE] update common code block (size):
[AUE] update common code block do_a_swap_ccb(size):
[AUE] Error: get common code block range
[AUE] Error: get common function block range
DMOV Issue Cmd: Command issued
DMOV Request not Valid: Command list not on 64-bit boundary
DMOV Request not Valid: Invalid number of commands
DMOV Get Chan %d Error: Command error occured
DMOV Get Chan %d Error: Command-phase bus error occured
DMOV Stop Handler: cannot stop channel %d, commands pending
DMOV Stop Handler: cannot stop channel %d, issuing commands
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot_local.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_hash_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_dload_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/unified_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/osbl_prog_boot_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_wm_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_android_ldr.c
void idev_comm_connect(ip_uint32 h, ip_char* addr, ip_uint16 PortNum, ip_int32 TimeOut)
void dt_CommConnect(dt_uint32 h, dt_char* addr, dt_uint16 PortNum, dt_int32 TimeOut)
void idev_comm_send(ip_uint32 h, ip_char* SendBuf, ip_uint32 SendLen, ip_int32 TimeOut)
void dt_CommSend(dt_uint32 h, dt_char* SendBuf, dt_uint32 SendLen, dt_int32 TimeOut)
ip_commStatus_e idev_comm_querySendStatus(ip_uint32 h, ip_uint32* SentLen)
dt_CommStatus dt_QuerySendStatus(dt_uint32 h, dt_uint32* SentLen)
void idev_comm_recv(ip_uint32 h, ip_char* RecvBuf, ip_uint32 RecvLen, ip_int32 Timeout)
void dt_CommRecv(dt_uint32 h, dt_char* RecvBuf, dt_uint32 RecvLen, dt_int32 Timeout)
ip_commStatus_e idev_comm_queryRecvStatus(ip_uint32 h, ip_uint32* RecvLen)
dt_CommStatus dt_QueryRecvStatus(dt_uint32 h, dt_uint32* RecvLen)
const ip_int16 idev_comm_setSecureInfo( ip_int32 protocolID, ip_uint32 cipherSuites[], ip_int32 cipherSuitesSize, ip_char certificate[], ip_int32 certificateSize)
const dt_int16 dt_CommSetSecureInfo( dt_int32 protocolID, dt_uint32 cipherSuites[], dt_int32 cipherSuitesSize, dt_char certificate[], dt_int32 certificateSize)
ip_commStatus_e idev_httpTerminateAsync( ip_httpInterface_s *httpInterface )
CH9: Received vendor specific command for device, but no handlers registered
CH9: Received reserved command for device, but no handlers registered
[AUE] Info: no common code block, this is not ARM region, do zipping instead
Info: no common func block, this is not ARM region, do zipping instead
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
cdc_handle_encapsulated_command
encapsulated_command_complete
hfat_common.c
EP0 command reply was not sent correctly %d [%d:%d]
CH9: Received vendor specific command for device, but no handlers registered
CH9: Received reserved command for device, but no handlers registered
The others returned nothing.
Just for shoots and giggles
I expanded the search for the word boot on 02, and here is what it revealed:
Code:
strings mmcblk0p2 | grep -i boot
/sys_boot/keystore/key.str
/sys_boot/keystore/store.pt
sys_boot
; Time Stamp unavailable from boot loader.
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_aarm_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_hash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_hw_init.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_mc_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_flash_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_setup_mpu_dal.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_adsp_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_load_ramfs.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_sd_img_update.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot_local.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_hash_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_dload_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/unified_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/osbl_prog_boot_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_wm_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_android_ldr.c
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
boothw_target.c
sys_boot
smem_boot_init: version %x does not match all procs!
boot_elf_loader
boot_elf_loader_factory
boot_sec_elf_loader
boot_sec_elf_loader_factory
boot_flash_trans_nand
boot_flash_trans_nand_factory
boot_flash_trans_nor
boot_flash_trans_nor_factory
boot_flash_trans_sdcc
boot_flash_trans_sdcc_factory
boot_flash_dev_nor
boot_flash_dev_nand
boot_flash_dev_sdcc
clkrgm_mpss_boot.c
/mmc1/IMAGE/APPSBOOT.MBN
/mmc1/IMAGE/BOOT.IMG
/mmc1/IMAGE/EMMCBOOT.MBN
EMMCBOOT.MBN
BOOT.IMG
/sys_boot/IMAGE/
/sys_boot/IMAGE2/
/sys_boot/IMAGE3/
bootsymmetrickey
E/boot/qcsbl
F/boot/oemsbl
F/boot/osbl
G/boot/appsbl
H/boot/apps
I/boot/modem
J/boot/modem_fs1
K/boot/modem_fs2
L/boot/fota
M/boot/qcsbl_cfg
P/boot/adsp
01, same search:
Code:
trings mmcblk0p1 | grep -i boot
sys_boot
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sflashc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_shared.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk_settings.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ddr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
sys_boot
smem_boot_init: version %x does not match all procs!
E/boot/qcsbl
F/boot/oemsbl
F/boot/osbl
G/boot/appsbl
H/boot/apps
I/boot/modem
J/boot/modem_fs1
K/boot/modem_fs2
L/boot/fota
M/boot/qcsbl_cfg
P/boot/adsp
02 - search for "home"
Code:
strings mmcblk0p2 | grep -i home
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_aarm_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_hash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_hw_init.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_mc_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_flash_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_setup_mpu_dal.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_adsp_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_load_ramfs.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_sd_img_update.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot_local.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_hash_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_dload_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/unified_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/osbl_prog_boot_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_wm_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_android_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/wiredconnectivity/hsusb/core/src/jslave/core/jusb_core.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/wiredconnectivity/hsusb/core/src/jslave/dcd/dcd_tdi_4x.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/wiredconnectivity/hsusb/core/src/jos/jos_bus.c
01 search for home
Code:
strings mmcblk0p1 | grep -i home
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sflashc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_shared.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk_settings.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ddr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
Remembering that factory reset is the sole function of the boot-loader on this device, I did a search for "factory"
02:
Code:
mmcblk0p2 | grep -i factory
boot_elf_loader_factory
boot_sec_elf_loader_factory
boot_flash_trans_nand_factory
boot_flash_trans_nor_factory
boot_flash_trans_sdcc_factory
01 - no results
I think we have a winner? I'd *almost* place money on 2 being boot, but I need a little insight here.
I should be able to pass you these files tonight. I'm just limited right now as I'm at work and remoting in on a slow connection.
Great work!
A few possible corrections:
Thought #1: From what I've read, AMSS (the radio) has multiple 'nvram partitions' where configuration is stored. The partitions with size 2048 look like those.
My updated guess:
P1 = hardware bootloader (like HBOOT on a HTC device)
P2 = second stage bootloader (references to android and wm_ldr)
The actual AMSS firmware is usually above 10MB in size, so the radio firmware is most likely a larger partition.
Thought #2: /boot is quite possibly a fastboot image. Those are usually compressed, hence you will not find any strings in it. It would be all binary.
If you can, run "hexdump -n 32 <filename>" on each of the dumps, and paste the output here.
With that hexdump information, I can tell you which partitions have the fastboot magic number and which are AMSS configuration partitions or ext3 filesystems.
As a side note, I wonder if this device supports fastboot commands... you could potentially try something like "fastboot reboot recovery" which should be harmless to see. Of course, you'd need Google's fastboot tools on your machine first though. (http://android-dls.com/wiki/index.php?title=Fastboot)
If it turns out that fastboot works, a nondestructive way of testing if the device is signed would be to extract the recovery image and replace it's ramdisk with one containing Clockwork. It may be as simple as "fastboot boot <newimage>" to boot the new image without actually changing anything on the phone.
Anyway, get those hex dumps, then we'll see where that leads...
Great work!
Alright - I'll get on that tonight when I get home (probably about another 2.5 hours from now including dinner).
The other thing that's been rattling around in my head, and I know I shouldn't be jumping this far ahead (nor do I want to derail this thread), is I (and the entire community) need to make some modifications to the android.policy.jar thus completing the migration from Bing on this phone. One string would make all the difference Unfortunately, it is odexed. I'm guessing this has many dependencies, and the best method to go about this would be to pretty much deodex the entire O.S.. Obviously, that's not something I feel comfortable with doing until we are completed with this, but my thought process is on track for what I need to do, right?
I also need to research if it is possible to dump my entire phone as an image as part of an Android AVM, so I don't end up bricking my phone. I had my entire phone lockup and go black last night. About had a heart attack.
Obviously, this takes precedence, but just wanted to throw all that out there while it was fresh in my mind (things get lost quickly - I have twenty browser windows open juggling about a dozen different thought processes).
Hex Dumps
P1:
Code:
0000000 dcd1 844b 1034 73d7 435a 7d0b ffff ffff
0000010 ffff ffff ffff ffff ffff ffff ffff ffff
0000020
P2:
Code:
0000000 000b 0000 0003 0000 0000 0000 0000 0450
0000010 31f8 0013 31f8 0013 31f8 0463 0000 0000
0000020
I'll have to do the fastboot install at home.
majorpay said:
Alright - I'll get on that tonight when I get home (probably about another 2.5 hours from now including dinner).
The other thing that's been rattling around in my head, and I know I shouldn't be jumping this far ahead (nor do I want to derail this thread), is I (and the entire community) need to make some modifications to the android.policy.jar thus completing the migration from Bing on this phone. One string would make all the difference Unfortunately, it is odexed. I'm guessing this has many dependencies, and the best method to go about this would be to pretty much deodex the entire O.S.. Obviously, that's not something I feel comfortable with doing until we are completed with this, but my thought process is on track for what I need to do, right?
I also need to research if it is possible to dump my entire phone as an image as part of an Android AVM, so I don't end up bricking my phone. I had my entire phone lockup and go black last night. About had a heart attack.
Obviously, this takes precedence, but just wanted to throw all that out there while it was fresh in my mind (things get lost quickly - I have twenty browser windows open juggling about a dozen different thought processes).
Click to expand...
Click to collapse
I believe I saw that it has been deodexed on stetsonaw's Twitter page. You may want to get in touch with him
Yeah, I saw he had claimed that over on androidforums. I should start checking that area more often. I put a post out to feel it out and see if he might be willing to throw it my way I think ultimately he is waiting patiently in the wings waiting for us to get done with this so he can release the ROM he is working on.
Just wanted to say keep up the good work. I plan to look into this more when I get home but sounds like you are definitely on the right track. Excited to see more progress soon.
I just got into the scene as this is my first droid phone but I have been reading up as quickly as possible to contribute to making roms.
OK, so I am back in the saddle.
I have run a ./fastboot reboot, and as expected, no response. (says waiting for device) I believe I still need to modify my hosts.
I expect you've seen my hex dumps. Any thoughts?
Edit: Phone went into "Download is in progress. Do not disconnect cable."
Real? I don't know, but this is hindering me from moving forward.
majorpay said:
P1:
Code:
0000000 dcd1 844b 1034 73d7 435a 7d0b ffff ffff
0000010 ffff ffff ffff ffff ffff ffff ffff ffff
0000020
P2:
Code:
0000000 000b 0000 0003 0000 0000 0000 0000 0450
0000010 31f8 0013 31f8 0013 31f8 0463 0000 0000
0000020
I'll have to do the fastboot install at home.
Click to expand...
Click to collapse
Great- now I just need hexdumps of the other partitions I listed: P3, P8, P9, and P14.
P1 and P2 are of little interest to us, we're looking for the one containing recovery and the main kernel+ramdisk.
As soon as we identify which is the recovery partition, we'll be super close to finding whether recovery is signed and one step closer to porting CWM.
PS: Fastboot reboot may have put your phone in download mode. If you're stuck in it, just try using "fastboot reboot recovery", then from there you should be able to select "reboot" and end up in Android again...
p3
Code:
0000000 ffff ffff ffff ffff ffff ffff ffff ffff
*
0000020
p8
Code:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0000020
p9
Code:
0000000 4e41 5244 494f 2144 66ac 0038 8000 0020
0000010 fb21 002f 0000 0120 0000 0000 0000 0110
0000020
p14
Code:
0000000 4e41 5244 494f 2144 66ac 0038 8000 0020
0000010 8cd9 0033 0000 0120 0000 0000 0000 0110
0000020
And ./fastboot devices consistently shows nothing. I added the device per Ubuntu guide, and restarted udev, but still nada.
Edit... I missed something on fastboot (I added the wrong device). I'll go back and recheck.
Edit 2: Still no luck.
As an update, it appears that holding the power button with the volume button up puts the device into what looks like a fastboot state (only when plugged into usb).
Edit: Maybe this is just a recovery mode / Emergency mode.
It is designated by a sign that reads: "Download is in progress. Do not disconnect cable."
According to my usb device information, it shows up as a LGE USB CDMA Modem.
Code:
lsusb
Bus 001 Device 025: ID 1004:6200 LG Electronics, Inc.
51-android.rules
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666", OWNER="<my username>"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004",ATTR{idProduct}=="6200", OWNER="<my username>"
"./fastboot devices" shows nothing
Hello
Not sure if this is the right place, but I don't think development is the right thread either as I simply need a one time tester and there is already a dev thread for the tool in Optimus Black Forums.
I have developed a tool that extracts LG's bin firmware. I extended it to extract tot files as well. As some of you might know the tot files splits some partitions up into multiple files. I already managed to extract the tot file into their various part, but I have only recently added the ability to merge the parts to it's partition
I don't have enough bandwidth to download one of your firmware files to test it so can someone please test the tool.
Heres the dev thread : link
Heres the git : link
You'll have to compile it with gcc/mingw. The tools name must be BinExtractor(.exe) or it won't remove the first argument (usually the tool path and then it will keep on showing the usage no matter what)
Run it with
Code:
BinExtractor -daph Path/To/Tot/File/firmware.tot
and see if it displays the header info. If that succeeds please test the extraction
Code:
BinExtractor -extract Path/To/Tot/File/firmware.tot
It should prompt you that it detected data blocks with identical names and ask you if you want to merge them. And you want to merge them . After it extracted the files can you please check that the various partitions that it extracted are correct.
To check the system partition mount or extract the system partition in Linux and in Windows use a tool like ext2read to check it.
If it fails with an error please post the results from -daph (and -extract if it happened there) and the first meg of the tot file you used.
If the partitions aren't extracted properly (or merged properly) and -daph succeeded please post just the output from -daph and in what way the output is faulty.
Thanks in advance.
Wow it moved out of page 1 already.
Bump.
It was ignored because the Nexus 4 doesn't use LG .bin files, it uses standard .img files.
Rusty! said:
It was ignored because the Nexus 4 doesn't use LG .bin files, it uses standard .img files.
Click to expand...
Click to collapse
Thanks for responding, but according to this: [Stock] Stock ROMs Collection US/CA/EU/AU
These files are in TOT format
Click to expand...
Click to collapse
And theres a DL link that I presume contains a tot file
LGE960AT-00-V10c-NXS-XX-OCT-25-2012-JVP15Q-USER+0
Click to expand...
Click to collapse
Can you please explain since the info I have atm is a bit contradictory.
Thanks for this xonar. Much appreciated.
Would anyone be able to compile a Windows binary for me and upload it please? Thanks.
Sent from my Nexus 4 using Tapatalk 2
efrant said:
Thanks for this xonar. Much appreciated.
Would anyone be able to compile a Windows binary for me and upload it please? Thanks.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I just compiled it with mingw, but it's not behaving as it's Linux counterpart.
If j is 1024 why isn't the output file 512kB ?!? (Tested with P970 bin)
Code:
for(j = 0; j < tmp.pent_arr[i].file_size; j++)
{
/*DO 512 BLOCK*/
fread(buff, sizeof(char), 512, f);
fwrite(buff, sizeof(char), 512, out);
}
fclose(out);
EDIT: Had a facepalm moment
Windows needs to specify reading and writing in binary. I'll give you exe in a moment.
EDIT2: I attached a zip with the exe inside.
To get it working in Windows I changed read access to binary everywhere theres a fopen and I initialized some thing to 0 as Windows unlike Linux doesn't start you of with a nice clean slate.
I'll push changes to git tomorrow morning to make it work on Windows aswel and from now on I'll actually test the windows exe on windows and not through wine.
Hope it works. I'm going to bed now.
xonar_ said:
I just compiled it with mingw, but it's not behaving as it's Linux counterpart.
If j is 1024 why isn't the output file 512kB ?!? (Tested with P970 bin)
Code:
for(j = 0; j < tmp.pent_arr[i].file_size; j++)
{
/*DO 512 BLOCK*/
fread(buff, sizeof(char), 512, f);
fwrite(buff, sizeof(char), 512, out);
}
fclose(out);
EDIT: Had a facepalm moment
Windows needs to specify reading and writing in binary. I'll give you exe in a moment.
EDIT2: I attached a zip with the exe inside.
To get it working in Windows I changed read access to binary everywhere theres a fopen and I initialized some thing to 0 as Windows unlike Linux doesn't start you of with a nice clean slate.
I'll push changes to git tomorrow morning to make it work on Windows aswel and from now on I'll actually test the windows exe on windows and not through wine.
Hope it works. I'm going to bed now.
Click to expand...
Click to collapse
Thanks so much. I'll try to give it a shot tomorrow. If it doesn't work, I guess I could always use cygwin.
Sent from my Nexus 4 using Tapatalk 2
Doesn't seem to work on Bell Optimus G:
Code:
BinExtractor.exe -extract "LGE973AT-00-V10f-BELL-CA-OCT-24-2012+0.tot"
Reading AP Header...
Unknown Magic Number at 0x8 : AF 33 BF DE
Writing Files...
Finished
Running the info command:
GPT HEADER
----------
Signature 45 46 49 20 50 41 52 54
Revision 65536
Header Size 92
CRC32 of Header B2 64 10 F5
Current Header LBA 1
Backup Header LBA 61071359
First Usable LBA 34
Last Usable LBA 61071326
Disk GUID 32 1B 10 98 E2 BB F2 4B A0 6E 2B B3 3D 00 0C 20
Start of Partition Entries 2
Number of Partition Entries 36
Size of Partition Entries 128
CRC32 of Partition Array 71 79 32 B7
PARTITION ENTRIES
-----------------
PARTITION ENTRY
---------------
Partition Type GUID A2 A0 D0 EB E5 B9 33 44 87 C0 68 B6 B7 26 99 C7
Unique Partition GUID 7B 6F 3E CF 28 B7 86 F3 6A AE 46 69 B1 BC 9A 08
First LBA 16384
Last LBA 147455
Attributes 8
Partition Name modem
PARTITION ENTRY
---------------
Partition Type GUID 2C BA A0 DE DD CB 05 48 B4 F9 F4 28 25 1C 3E 98
Unique Partition GUID BC D0 5B BC 05 A5 44 30 8E 88 59 5C 87 19 A1 08
First LBA 147456
Last LBA 148479
Attributes 0
Partition Name sbl1
PARTITION ENTRY
---------------
....
zivan56 said:
Doesn't seem to work on Bell Optimus G:
Code:
Unknown Magic Number at 0x8 : AF 33 BF DE
Click to expand...
Click to collapse
The tool doesn't support Bell OG yet. I made a guess at what the format could be but I can't say for certain that it will work. I'll push changes in a moment.
Someone tested it on another OG firmware, but it fails to mount the image with:
Code:
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Code:
EXT4-fs (loop0): bad geometry: block count 389120 exceeds size of device (360576 blocks)
Click to expand...
Click to collapse
Can anyone give me the output from -dgpt with at&t OG or sprint OG?
or the first meg of the tot file of Nexus 4 or Bell OG along with -dgpt output?
EDIT: If possible use pastebin to display dgpt output as it might be fairly long.
I known what the problem is. Great thanks to SnowLeopardJB for testing and correspondence
The file that was being created doesn't have 'space' up until the end of the partitions. (It was left out since thats where it stops in the file) but on the actual disk still has 'space' after the last bit of data.
So it can be fixed with
Code:
#VAL is the value that is supposedly outside the device from the err msg
VAL=389120
#This will say already that size, but the file itself will change size
resize2fs system.img $VAL
#Not sure if this last step is then necessary
fsck.ext4 -f system.img
#Now you can mount is as any other partition :laugh:
I'll make the program add the 'space' and see if it produces a immediately mountable file.
I also totally changed the way it handles 44 DD 55 AA files for future flexibility and it's a step closer to being able to make it use predefined files as formats.
The latest version in git seems to extract the Bell Optimus G firmware properly now. I tried mounting the resulting radio image section and it worked fine, so I assume it knows the proper partition boundaries now.
Btw, I would recommend posting some instructions how to compile it. Not everyone is savvy enough to know how to use gcc.
Likewise, your program is hardcoded to look for its name when looking for parameters. Since there was no makefile it defaulted to a.out, which, the way it is coded, would never accept any parameters unless renamed to LGBinExtractor.
zivan56 said:
The latest version in git seems to extract the Bell Optimus G firmware properly now. I tried mounting the resulting radio image section and it worked fine, so I assume it knows the proper partition boundaries now.
Click to expand...
Click to collapse
Only merged partitions was affected by 'space' bug, plain extraction should have been correct for Bell OB after bb697c27e5. I haven't commited 'space' fix yet.
In retrospect using fseek to create 'space' between image parts might not have been such a good idea either and might also be causing problems.
zivan56 said:
Btw, I would recommend posting some instructions how to compile it. Not everyone is savvy enough to know how to use gcc.
Click to expand...
Click to collapse
Adding a makefile is on my todo list.
zivan56 said:
Likewise, your program is hardcoded to look for its name when looking for parameters. Since there was no makefile it defaulted to a.out, which, the way it is coded, would never accept any parameters unless renamed to LGBinExtractor.
Click to expand...
Click to collapse
Yea, not one of my better choices. I changed it to remove the first arg if it doesn't start with '-'.
Okay Merging partitions should work now. I'm waiting for confirmation then I'll ask mod to close the thread.
xonar_ said:
Okay Merging partitions should work now. I'm waiting for confirmation then I'll ask mod to close the thread.
Click to expand...
Click to collapse
Hello i'm try test with LG Optimus tag working:laugh:
Code:
AP HEADER
----------
Magic Number 44 DD 55 AA
Number of Partitions 32
PARTITION ENTRIES
-----------------
PARTITION ENTRY
------------
Data Block Name MODEM
Data Block ID 1
Size on File 47104
File Offset 0
Size on Disk 65537
Disk Offset 0
PARTITION ENTRY
------------
Data Block Name SBL1
Data Block ID 2
Size on File 1024
File Offset 47104
Size on Disk 2048
Disk Offset 65537
PARTITION ENTRY
------------
Data Block Name SBL2
Data Block ID 3
Size on File 1024
File Offset 48128
Size on Disk 2048
Disk Offset 67585
PARTITION ENTRY
------------
Data Block Name EXT
Data Block ID 4
Size on File 1024
File Offset 49152
Size on Disk 12287
Disk Offset 69633
PARTITION ENTRY
------------
Data Block Name RPM
Data Block ID 5
Size on File 1024
File Offset 50176
Size on Disk 16384
Disk Offset 81920
PARTITION ENTRY
------------
Data Block Name SBL3
Data Block ID 6
Size on File 2048
File Offset 51200
Size on Disk 16384
Disk Offset 98304
PARTITION ENTRY
------------
Data Block Name ABOOT
Data Block ID 7
Size on File 2048
File Offset 53248
Size on Disk 16384
Disk Offset 114688
PARTITION ENTRY
------------
Data Block Name BOOT
Data Block ID 8
Size on File 15360
File Offset 55296
Size on Disk 32768
Disk Offset 131072
PARTITION ENTRY
------------
Data Block Name TZ
Data Block ID 9
Size on File 1024
File Offset 70656
Size on Disk 16384
Disk Offset 163840
PARTITION ENTRY
------------
Data Block Name MODEM_ST1
Data Block ID 10
Size on File 0
File Offset 71680
Size on Disk 16384
Disk Offset 180224
PARTITION ENTRY
------------
Data Block Name MODEM_ST2
Data Block ID 11
Size on File 0
File Offset 71680
Size on Disk 16384
Disk Offset 196608
PARTITION ENTRY
------------
Data Block Name PERSIST
Data Block ID 12
Size on File 16384
File Offset 71680
Size on Disk 16384
Disk Offset 212992
PARTITION ENTRY
------------
Data Block Name RECOVERY
Data Block ID 13
Size on File 17408
File Offset 88064
Size on Disk 32768
Disk Offset 229376
PARTITION ENTRY
------------
Data Block Name MDM
Data Block ID 14
Size on File 57344
File Offset 105472
Size on Disk 65536
Disk Offset 262144
PARTITION ENTRY
------------
Data Block Name M9K_EFS1
Data Block ID 15
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 327680
PARTITION ENTRY
------------
Data Block Name M9K_EFS2
Data Block ID 16
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 344064
PARTITION ENTRY
------------
Data Block Name M9K_EFS3
Data Block ID 17
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 360448
PARTITION ENTRY
------------
Data Block Name FSG
Data Block ID 18
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 376832
PARTITION ENTRY
------------
Data Block Name SSD
Data Block ID 19
Size on File 0
File Offset 162816
Size on Disk 32768
Disk Offset 393216
PARTITION ENTRY
------------
Data Block Name BSP
Data Block ID 20
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 425984
PARTITION ENTRY
------------
Data Block Name BLB
Data Block ID 21
Size on File 0
File Offset 162816
Size on Disk 32768
Disk Offset 442368
PARTITION ENTRY
------------
Data Block Name TOMBSTONES
Data Block ID 22
Size on File 1024
File Offset 162816
Size on Disk 147456
Disk Offset 475136
PARTITION ENTRY
------------
Data Block Name DRM
Data Block ID 23
Size on File 0
File Offset 163840
Size on Disk 16384
Disk Offset 622592
PARTITION ENTRY
------------
Data Block Name FOTA
Data Block ID 24
Size on File 0
File Offset 163840
Size on Disk 49152
Disk Offset 638976
PARTITION ENTRY
------------
Data Block Name MISC
Data Block ID 25
Size on File 0
File Offset 163840
Size on Disk 16384
Disk Offset 688128
PARTITION ENTRY
------------
Data Block Name TZ_BKP
Data Block ID 26
Size on File 0
File Offset 163840
Size on Disk 16384
Disk Offset 704512
PARTITION ENTRY
------------
Data Block Name SYSTEM
Data Block ID 27
Size on File 1720320
File Offset 163840
Size on Disk 1720320
Disk Offset 720896
PARTITION ENTRY
------------
Data Block Name CACHE
Data Block ID 28
Size on File 0
File Offset 1884160
Size on Disk 655360
Disk Offset 2441216
PARTITION ENTRY
------------
Data Block Name WALLPAPER
Data Block ID 29
Size on File 0
File Offset 1884160
Size on Disk 16384
Disk Offset 3096576
PARTITION ENTRY
------------
Data Block Name USERDATA
Data Block ID 30
Size on File 0
File Offset 1884160
Size on Disk 4587520
Disk Offset 3112960
PARTITION ENTRY
------------
Data Block Name MPT
Data Block ID 31
Size on File 0
File Offset 1884160
Size on Disk 32768
Disk Offset 7700480
PARTITION ENTRY
------------
Data Block Name GROW
Data Block ID 32
Size on File 20480
File Offset 1884160
Size on Disk 21000000
Disk Offset 7733248
Code:
Reading AP Header...
Writing Files...
Writing File : 1-MODEM.img -- DONE --
Writing File : 2-SBL1.img -- DONE --
Writing File : 3-SBL2.img -- DONE --
Writing File : 4-EXT.img -- DONE --
Writing File : 5-RPM.img -- DONE --
Writing File : 6-SBL3.img -- DONE --
Writing File : 7-ABOOT.img -- DONE --
Writing File : 8-BOOT.img -- DONE --
Writing File : 9-TZ.img -- DONE --
Writing File : 10-MODEM_ST1.img -- DONE --
Writing File : 11-MODEM_ST2.img -- DONE --
Writing File : 12-PERSIST.img -- DONE --
Writing File : 13-RECOVERY.img -- DONE --
Writing File : 14-MDM.img -- DONE --
Writing File : 15-M9K_EFS1.img -- DONE --
Writing File : 16-M9K_EFS2.img -- DONE --
Writing File : 17-M9K_EFS3.img -- DONE --
Writing File : 18-FSG.img -- DONE --
Writing File : 19-SSD.img -- DONE --
Writing File : 20-BSP.img -- DONE --
Writing File : 21-BLB.img -- DONE --
Writing File : 22-TOMBSTONES.img -- DONE --
Writing File : 23-DRM.img -- DONE --
Writing File : 24-FOTA.img -- DONE --
Writing File : 25-MISC.img -- DONE --
Writing File : 26-TZ_BKP.img -- DONE --
Writing File : 27-SYSTEM.img -- DONE --
Writing File : 28-CACHE.img -- DONE --
Writing File : 29-WALLPAPER.img -- DONE --
Writing File : 30-USERDATA.img -- DONE --
Writing File : 31-MPT.img -- DONE --
Writing File : 32-GROW.img -- DONE --
Finished
PS : @xonar_ If you need any flash file LG pm me i have all files LG
---------- Post added at 01:25 AM ---------- Previous post was at 12:25 AM ----------
LG Optimus LTE2 F160 working
Code:
GPT HEADER
----------
Signature 45 46 49 20 50 41 52 54
Revision 65536
Header Size 92
CRC32 of Header 93 23 A2 52
Current Header LBA 1
Backup Header LBA 30535679
First Usable LBA 34
Last Usable LBA 30535646
Disk GUID 32 1B 10 98 E2 BB F2 4B A0 6E 2B B3 3D 00 0C 20
Start of Partition Entries 2
Number of Partition Entries 32
Size of Partition Entries 128
CRC32 of Partition Array 2A A9 B7 BD
PARTITION ENTRIES
-----------------
PARTITION ENTRY
---------------
Partition Type GUID A2 A0 D0 EB E5 B9 33 44 87 C0 68 B6 B7 26 99 C7
Unique Partition GUID 72 05 1F 0E 0C 89 89 B5 F4 D4 0E 5D 04 65 52 1E
First LBA 16384
Last LBA 147455
Attributes 8
Partition Name modem
PARTITION ENTRY
---------------
Partition Type GUID 2C BA A0 DE DD CB 05 48 B4 F9 F4 28 25 1C 3E 98
Unique Partition GUID 9A 00 DF 9C DE F9 95 65 62 3C 0F 15 D6 1A 75 6B
First LBA 147456
Last LBA 148479
Attributes 0
Partition Name sbl1
PARTITION ENTRY
---------------
Partition Type GUID AD 52 6B 8C 9E 8A 98 43 AD 09 AE 91 6E 53 AE 2D
Unique Partition GUID F1 EC 20 B2 C4 FA 8B FC 06 D2 4F 33 72 B6 0F D2
First LBA 148480
Last LBA 149503
Attributes 0
Partition Name sbl2
PARTITION ENTRY
---------------
Partition Type GUID DF 44 E0 05 F1 92 25 43 B6 9E 37 4A 82 E9 7D 6E
Unique Partition GUID A8 87 F8 53 B8 47 22 FA A9 2B 91 26 94 F6 19 2B
First LBA 149504
Last LBA 151551
Attributes 0
Partition Name sbl3
PARTITION ENTRY
---------------
Partition Type GUID CD FD 0F 40 E0 22 E7 47 9A 23 F1 6E D9 38 23 88
Unique Partition GUID 2A D1 EA 8A 29 76 F5 14 50 CD FA D5 2D 9F 41 26
First LBA 151552
Last LBA 152575
Attributes 0
Partition Name aboot
PARTITION ENTRY
---------------
Partition Type GUID 93 F7 8D 09 12 D7 3D 41 9D 4E 89 D7 11 77 22 28
Unique Partition GUID F7 5A 4B 53 B7 53 FB FF 4C F1 26 3A AD 9D C9 12
First LBA 152576
Last LBA 153599
Attributes 0
Partition Name rpm
PARTITION ENTRY
---------------
Partition Type GUID 86 7F 11 20 85 E9 57 43 B9 EE 37 4B C1 D8 48 7D
Unique Partition GUID 7A C9 D2 E5 B5 2A 04 6C BE 24 C7 AE 35 55 01 B2
First LBA 163840
Last LBA 188415
Attributes 8
Partition Name boot
PARTITION ENTRY
---------------
Partition Type GUID 7F AA 53 A0 B8 40 1C 4B BA 08 2F 68 AC 71 A4 F4
Unique Partition GUID F9 09 61 B9 4F 99 AF 89 FF C3 F3 16 99 B0 E3 A9
First LBA 196608
Last LBA 197631
Attributes 0
Partition Name tz
PARTITION ENTRY
---------------
Partition Type GUID 38 68 4A 00 2A 06 DF 44 81 52 4F 34 0C 05 22 5D
Unique Partition GUID BC 83 9C AC D5 BF F4 36 1C 0F D4 63 6F AD 23 07
First LBA 197632
Last LBA 197633
Attributes 0
Partition Name pad
PARTITION ENTRY
---------------
Partition Type GUID 3E 37 13 20 C4 1A 31 41 B0 F8 91 58 F9 65 4F 4F
Unique Partition GUID 46 F4 88 C2 2C 7A 4A AD 17 28 DD 70 10 8B BD AD
First LBA 197634
Last LBA 203777
Attributes 0
Partition Name modemst1
PARTITION ENTRY
---------------
Partition Type GUID 3E 37 13 20 C4 1A 31 41 B0 F8 91 58 F9 65 4F 4F
Unique Partition GUID 0A E8 2B 7F B8 CF 52 3E C2 7E 52 26 3E 03 B5 35
First LBA 203778
Last LBA 209921
Attributes 0
Partition Name modemst2
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 85 78 29 24 17 62 3D 36 A4 4B E9 47 10 87 AD 67
First LBA 212992
Last LBA 229375
Attributes 8
Partition Name sns
PARTITION ENTRY
---------------
Partition Type GUID 54 05 D3 6C 5D 5F EF 40 82 FE 10 92 35 9F 92 EE
Unique Partition GUID DC BF D4 C1 2E 63 5D 16 3F 45 88 4F 2A 36 86 3C
First LBA 229376
Last LBA 262143
Attributes 0
Partition Name misc
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 8E C6 02 A3 3F DC 79 98 12 7F 02 BE 38 F7 D4 6B
First LBA 262144
Last LBA 2359295
Attributes 8
Partition Name system
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID E2 F2 D0 8D 3E D2 D0 90 E9 45 09 EA 7E 8F 2C 97
First LBA 2359296
Last LBA 29589503
Attributes 8
Partition Name userdata
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID F7 2D 03 28 16 E8 78 07 D0 84 1B 08 6F 5B 6D 39
First LBA 29589504
Last LBA 29605887
Attributes 8
Partition Name persist
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 21 6C AF DC 30 3D D9 D9 3F AE 56 42 4C 0F 66 AC
First LBA 29605888
Last LBA 30146559
Attributes 8
Partition Name cache
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 26 4F D8 D1 AC 24 CC CA EA 7F E1 F0 E5 6C FD 61
First LBA 30146560
Last LBA 30294015
Attributes 0
Partition Name tombstones
PARTITION ENTRY
---------------
Partition Type GUID 86 7F 11 20 85 E9 57 43 B9 EE 37 4B C1 D8 48 7D
Unique Partition GUID BB 74 76 DD 1D 6B 07 56 23 FB 94 96 7A 52 0A DC
First LBA 30294016
Last LBA 30318591
Attributes 8
Partition Name recovery
PARTITION ENTRY
---------------
Partition Type GUID 3E 37 13 20 C4 1A 31 41 B0 F8 91 58 F9 65 4F 4F
Unique Partition GUID 7C 48 3D 02 F0 90 E3 39 F7 14 BA D1 D9 BD 76 C8
First LBA 30318592
Last LBA 30324735
Attributes 8
Partition Name fsg
PARTITION ENTRY
---------------
Partition Type GUID 42 E7 86 2C 5E 74 DD 4F BF D8 B6 A7 AC 63 87 72
Unique Partition GUID 9B 2F 13 2B 51 11 1E C2 30 66 A0 E7 08 BC BF DF
First LBA 30324736
Last LBA 30324751
Attributes 8
Partition Name ssd
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 75 44 C3 7D E2 05 C3 88 22 1B 8A 2D D1 D9 E4 FA
First LBA 30326784
Last LBA 30343167
Attributes 0
Partition Name drm
PARTITION ENTRY
---------------
Partition Type GUID AC 9C 14 00 9B ED 01 48 9A E9 6D F9 60 3A 18 27
Unique Partition GUID 55 D9 D2 33 14 1A 58 56 F8 47 15 23 E1 B9 A4 07
First LBA 30343168
Last LBA 30408703
Attributes 0
Partition Name fota
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 38 9D 3B B9 01 35 EA F7 BA 61 44 35 4F AE 2C 73
First LBA 30408704
Last LBA 30474239
Attributes 0
Partition Name mpt
PARTITION ENTRY
---------------
Partition Type GUID BB 51 9C 73 F9 7A 0A 45 88 49 FF 4F 3D 94 CC AF
Unique Partition GUID EB 58 E9 92 44 82 6E A3 9C 07 F8 60 1D 46 AB 8E
First LBA 30474240
Last LBA 30475263
Attributes 0
Partition Name tzbak
PARTITION ENTRY
---------------
Partition Type GUID 11 84 CC 6A A5 68 18 41 BA B0 07 FA 12 72 B4 9B
Unique Partition GUID 8C 02 6E 7C 87 46 63 0D 71 93 68 7C 2A 4A D8 73
First LBA 30475264
Last LBA 30476287
Attributes 0
Partition Name rpmbak
PARTITION ENTRY
---------------
Partition Type GUID 95 F5 3E 32 7A AF FA 4A 80 60 97 BE 72 84 1B B9
Unique Partition GUID 47 79 8A 0B 52 C4 79 9B 2A 90 81 4E FC A8 E0 77
First LBA 30476288
Last LBA 30477311
Attributes 0
Partition Name encrypt
PARTITION ENTRY
---------------
Partition Type GUID 73 75 D2 A7 3C A5 E7 4C 87 BC 4D 35 12 FF C8 64
Unique Partition GUID 96 9C 90 E9 54 25 10 09 5A B6 CB 7E D3 1E 79 1D
First LBA 30490624
Last LBA 30523391
Attributes 8
Partition Name reserved
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 88 8D 1A E1 EF BF 80 A7 58 89 13 B3 AF AD 5E A3
First LBA 30523392
Last LBA 30535646
Attributes 0
Partition Name grow
Q:\LG\LG-F160L>
Not work on my G
it forceclose when i try to use -daph
KhmerHacker said:
it forceclose when i try to use -daph
Click to expand...
Click to collapse
What firmware did you try it on?
Succes with your tools
Thanks xonar. with your tools, I successed with Optimus Vu F100L rom: F100L29j_00.kdz. But the tools ext2read you metioned cannot see the ext4 26-SYSTEM.img, but I mount in linux and get the right result as below
mkdir
mount -t ext4 -o loop 26-SYSTEM.img /tmp
thanks very, a question:
after I make change to the img file, how can I repacked the img to tot file? need a change the wdb dll wdh file also?
anyone can give help is wellcome.
flyhigher76 said:
Thanks xonar. with your tools, I successed with Optimus Vu F100L rom: F100L29j_00.kdz. But the tools ext2read you metioned cannot see the ext4 26-SYSTEM.img, but I mount in linux and get the right result as below
mkdir
mount -t ext4 -o loop 26-SYSTEM.img /tmp
Click to expand...
Click to collapse
Not sure why ext2read don't work
,but if it works in Linux it should be correct.
flyhigher76 said:
thanks very, a question:
after I make change to the img file, how can I repacked the img to tot file? need a change the wdb dll wdh file also?
anyone can give help is wellcome.
Click to expand...
Click to collapse
It's possible to recreate the tot file from the extracted partitions,but a mistake can make your phone Hard Bricked. I wouldn't recommend doing that.
change Optimus Vu Languge
xonar_ said:
Not sure why ext2read don't work
,but if it works in Linux it should be correct.
It's possible to recreate the tot file from the extracted partitions,but a mistake can make your phone Hard Bricked. I wouldn't recommend doing that.
Click to expand...
Click to collapse
I like the Optimus Vu very much, fot it's unique size and it's first-class panel display attract me. But unfortunately, it is not in Chinese, also when I make a call I must choose to call local or call Korea. I'm tired of this, so I want to have a custom system for my own. The difficult is that I cannot get control the /system for root fails many times, so I cannot change any apk and jar in /system. I hope I can modify the rom as I have do with galaxy note, and forturely find this thread.
I know tot format file since I own this optimus Vu, so I have no idea about this format. Can you give me some information about this format, like some website?
vmt.
flyhigher76 said:
I know tot format file since I own this optimus Vu, so I have no idea about this format. Can you give me some information about this format, like some website?
vmt.
Click to expand...
Click to collapse
Theres the source code of my tool.
I got one of those original HP 16GB WIFI TouchPad. I had the famous too-discharged-won't-boot-anymore ( question-mark-battery-logo issue ) 3 times which I managed to resolve through usage of this forum ( Thank you! ) This time, I don't know what to do. Nothing on screen at all, I can only 'see' something through looking at what device the TouchPad appears as on the USB port:
Palm:
Product ID: 0x8070
Vendor ID: 0x0830 (Palm Inc.)
Version: 10.00
Speed: Up to 480 Mb/sec
Manufacturer: bootie
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 500
The other mode I can start the TouchPad in is the 'QHSUSB_DLOAD'
QHSUSB_DLOAD:
Product ID: 0x9008
Vendor ID: 0x05c6 (Qualcomm, Inc)
Version: 0.00
Speed: Up to 480 Mb/sec
Manufacturer: Qualcomm CDMA Technologies MSM
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 2
Taken from @jcsullins toolbox script, with the TouchPad booted in 'Palm' mode I can enter a few commands and eventually able to establish a SSH connection with my TouchPad.
$ dfu-util -d 0830:8070 -R -D ./tpdebrick-v004/moboot-dfu-v004
$ fastboot flash bootmem ./tpdebrick-v004/TPToolbox-Headless-v004
$ ssh -i ssh-key [email protected]
I can connect to the TouchPad, I have access to pretty all devices ( although screen is still blank ). I've even backed up the entire 16GB flash ( as it is now )
[email protected](none):/mnt# dd if=/dev/mmcblk0 | gzip -c | ssh [email protected] 'dd of=/Volumes/BACKUP_80GB/touchpad_full_image_backup20150124.gz'
Below is just ( for reference the list of the many parititions )
[email protected](none):/mnt# fdisk /dev/mmcblk0
Disk /dev/mmcblk0: 15.9 GB, 15923675136 bytes
1 heads, 16 sectors/track, 1943808 cylinders, total 31100928 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6d6c6150
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 204800 102400 c W95 FAT32 (LBA)
/dev/mmcblk0p2 * 204801 205800 500 4d QNX4.x
/dev/mmcblk0p3 205801 208800 1500 51 OnTrack DM6 Aux1
/dev/mmcblk0p4 208801 30969855 15380527+ 5 Extended
/dev/mmcblk0p5 262144 263143 500 47 Unknown
/dev/mmcblk0p6 393216 394715 750 45 Unknown
/dev/mmcblk0p7 524288 529287 2500 4c Unknown
/dev/mmcblk0p8 655360 675839 10240 48 Unknown
/dev/mmcblk0p9 786432 789431 1500 46 Unknown
/dev/mmcblk0p10 917504 923647 3072 4a Unknown
/dev/mmcblk0p11 1048576 1054719 3072 4b Unknown
/dev/mmcblk0p12 1054720 1062911 4096 f0 Linux/PA-RISC boot
/dev/mmcblk0p13 1062912 1128447 32768 83 Linux
/dev/mmcblk0p14 1179648 30969855 14895104 8e Linux LVM
That great! Now what?
Is my TouchPad really dead?
Can I use it still for Android?
How can I reflash or put back 'Web OS Recovery' ?
With all of the access I feel I have, do I need 'WebOS Recovery' at all?
Can't I just 'DD' one or more of the 14 partitions ?
Rastikan said:
I got one of those original HP 16GB WIFI TouchPad. I had the famous too-discharged-won't-boot-anymore ( question-mark-battery-logo issue ) 3 times which I managed to resolve through usage of this forum ( Thank you! ) This time, I don't know what to do. Nothing on screen at all, I can only 'see' something through looking at what device the TouchPad appears as on the USB port:
Palm:
Product ID: 0x8070
Vendor ID: 0x0830 (Palm Inc.)
Version: 10.00
Speed: Up to 480 Mb/sec
Manufacturer: bootie
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 500
The other mode I can start the TouchPad in is the 'QHSUSB_DLOAD'
QHSUSB_DLOAD:
Product ID: 0x9008
Vendor ID: 0x05c6 (Qualcomm, Inc)
Version: 0.00
Speed: Up to 480 Mb/sec
Manufacturer: Qualcomm CDMA Technologies MSM
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 2
Taken from @jcsullins toolbox script, with the TouchPad booted in 'Palm' mode I can enter a few commands and eventually able to establish a SSH connection with my TouchPad.
$ dfu-util -d 0830:8070 -R -D ./tpdebrick-v004/moboot-dfu-v004
$ fastboot flash bootmem ./tpdebrick-v004/TPToolbox-Headless-v004
$ ssh -i ssh-key [email protected]
I can connect to the TouchPad, I have access to pretty all devices ( although screen is still blank ). I've even backed up the entire 16GB flash ( as it is now )
[email protected](none):/mnt# dd if=/dev/mmcblk0 | gzip -c | ssh [email protected] 'dd of=/Volumes/BACKUP_80GB/touchpad_full_image_backup20150124.gz'
Below is just ( for reference the list of the many parititions )
[email protected](none):/mnt# fdisk /dev/mmcblk0
Disk /dev/mmcblk0: 15.9 GB, 15923675136 bytes
1 heads, 16 sectors/track, 1943808 cylinders, total 31100928 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6d6c6150
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 204800 102400 c W95 FAT32 (LBA)
/dev/mmcblk0p2 * 204801 205800 500 4d QNX4.x
/dev/mmcblk0p3 205801 208800 1500 51 OnTrack DM6 Aux1
/dev/mmcblk0p4 208801 30969855 15380527+ 5 Extended
/dev/mmcblk0p5 262144 263143 500 47 Unknown
/dev/mmcblk0p6 393216 394715 750 45 Unknown
/dev/mmcblk0p7 524288 529287 2500 4c Unknown
/dev/mmcblk0p8 655360 675839 10240 48 Unknown
/dev/mmcblk0p9 786432 789431 1500 46 Unknown
/dev/mmcblk0p10 917504 923647 3072 4a Unknown
/dev/mmcblk0p11 1048576 1054719 3072 4b Unknown
/dev/mmcblk0p12 1054720 1062911 4096 f0 Linux/PA-RISC boot
/dev/mmcblk0p13 1062912 1128447 32768 83 Linux
/dev/mmcblk0p14 1179648 30969855 14895104 8e Linux LVM
That great! Now what?
Is my TouchPad really dead?
Can I use it still for Android?
How can I reflash or put back 'Web OS Recovery' ?
With all of the access I feel I have, do I need 'WebOS Recovery' at all?
Can't I just 'DD' one or more of the 14 partitions ?
Click to expand...
Click to collapse
Try to (just) load this version of moboot-dfu instead:
https://goo.im/devs/jcsullins/tpdebrick/moboot-dfu-20150128
Do you see small text appear on the screen after loading it?
If so, are there two lines with "a6_test"? If so, what do they say. If not, what does it say on the screen.
If nothing appears on screen, does it show up when you run "fastboot devices" ?
If so, does it allow you to run "fastboot oem klogs 2>&1"? If so, upload the output and give link here.
jcsullins said:
Try to (just) load this version of moboot-dfu instead:
https://goo.im/devs/jcsullins/tpdebrick/moboot-dfu-20150128
Click to expand...
Click to collapse
Ok, from the 'Palm mode' ( POWER + HOME + VOLUME-UP ) for about 30 seconds ...
Code:
dfu-util -d 0830:8070 -R -D moboot-dfu-20150128
jcsullins said:
Do you see small text appear on the screen after loading it?
Click to expand...
Click to collapse
Yes!!! Thank you! I was beginning to think something was damaged as I didn't see anything on screen for long time ( although I was getting some access through SSH )
jcsullins said:
If so, are there two lines with "a6_test"? If so, what do they say. If not, what does it say on the screen.
Click to expand...
Click to collapse
Code:
(bootloader) [2100] a6_test: batt valid=1 percent=0 voltage=3225680
(bootloader) [2110] a6_test: batt temp=19 current=-312 coulombs=0
Although it does says 0 percent, I did let it charge the whole night ( as your tpdebrick tool suggests )
jcsullins said:
If nothing appears on screen, does it show up when you run "fastboot devices" ?
If so, does it allow you to run "fastboot oem klogs 2>&1"? If so, upload the output and give link here.
Click to expand...
Click to collapse
Yes, I see ( finally) stuff on the screen! Again, Thank you! I was beginning to think something was damaged as I didn't see anything on screen for long time.
http://forum.xda-developers.com/attachment.php?attachmentid=3139872&stc=1&d=1422547266
Now can I go ahead and load-up or run your full toolbox software and reformat/setup the entire flash device for Android ?