Develop Bugs

Need help with fixing IR Beam in my Rom

I took a newer SYS from another device that doesn't have IR, as a simple test I merged it with the Dopod Trinity WM6 OEM and built the OS. Everything works fine except for the IR Beam. The Beam is in the Control Panel, and it's enabled. However I noticed if I uncheck the option, it stays checked. The SYS folder from the other device did not have IRDA and IRDA_Lang_049 folders so I'm assuming it's related to the irdastk.dll and corresponding registry entries.
I tried taking the two folders from the original Dopod rom and dumped them into the SYS folder of my newer build but when I flash the device hangs on the second splash screen. I've also tried taking the DLL and just making a package with the registry entries but the same problem, hangs on the second splash screen.
Anyone have any suggestions as to what I may be doing wrong or how I can fix the IR Beam as I've noticed a lot of rom revisions with "Fixed Beam" but haven't been able to find any solutions as to how if it is related to the problem I'm having.
Thanks

hmm, As I was saying in my first post, I added IRDA and IRDA_Lang_049 to my rom but when I flash it, the device gets stuck at the second splash screen. Thinking it was a space issue I removed the Transcriber packages and flashed, the OS booted fine.
The only problem, unless I'm reading this wrong, I should still have space. Am I right, and if so, anyone have any ideas as to why it may not be working without having to remove the Transcriber packages?
Part of Log from build process
~~~~~~~~~~~~~~~~~~
Adding IRDA and IRDA_Lang_049 (Device gets stuck at second splash screen)
ImgfsToNb 2.1rc2
Using bigstorage mode
Sector size is 0x200 bytes
Writing imgfs to offset byte 0x620000, sector 0x3100
Padding ImgFs from 0x335a600 bytes (0x19ad3 sectors)
to 0x3360000 bytes (0x19b00 sectors)
Not conservative mode. Changing imgfsEnd from 0x4000000 to 0x3980000
Partition entry before:
File System: 0x04
Start Sector: 0x00020000
Total Sectors: 0x00060000
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x200
Last Head: 0xff
Last Sector: 0x01
Last Track: 0x3ff
Partition entry after:
File System: 0x04
Start Sector: 0x0001cc00
Total Sectors: 0x00063400
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x1cc
Last Head: 0xff
Last Sector: 0x01
Last Track: 0x3ff
ImgFs Flash Region log blocks was 0x1cf, now is 0x19b
Storage Flash Region log block was 0xffffffff, now is 0xffffffff,
Done!
NBMerge 2.1rc2
Executing ..\imgfstools\NBMerge with data chunk size = 0x200 and extra chunk size = 0x8
on file newrom.nb
Partition 0: start sector: 0x00000002, total: 0x000018fe
first used: 0x00000002, used: 0x00001800
Partition 1: start sector: 0x00001900, total: 0x00001800
first used: 0x00001900, used: 0x00001349
Partition 2: start sector: 0x00003100, total: 0x00019b00
first used: 0x00003100, used: 0x00019ad3
Checking newrom.nb for bad NAND block marker
Checked 0x1cc00 sectors successfully!
Adding IRDA and IRDA_Lang_049 and remove Transcriber Packages (device boots fine)
Sector size is 0x200 bytes
Writing imgfs to offset byte 0x620000, sector 0x3100
Padding ImgFs from 0x334d600 bytes (0x19a6b sectors)
to 0x3360000 bytes (0x19b00 sectors)
Not conservative mode. Changing imgfsEnd from 0x4000000 to 0x3980000
Partition entry before:
File System: 0x04
Start Sector: 0x00020000
Total Sectors: 0x00060000
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x200
Last Head: 0xff
Last Sector: 0x01
Last Track: 0x3ff
Partition entry after:
File System: 0x04
Start Sector: 0x0001cc00
Total Sectors: 0x00063400
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x1cc
Last Head: 0xff
Last Sector: 0x01
Last Track: 0x3ff
ImgFs Flash Region log blocks was 0x1cf, now is 0x19b
Storage Flash Region log block was 0xffffffff, now is 0xffffffff,
Done!
NBMerge 2.1rc2
Executing ..\imgfstools\NBMerge with data chunk size = 0x200 and extra chunk size = 0x8
on file newrom.nb
Partition 0: start sector: 0x00000002, total: 0x000018fe
first used: 0x00000002, used: 0x00001800
Partition 1: start sector: 0x00001900, total: 0x00001800
first used: 0x00001900, used: 0x00001349
Partition 2: start sector: 0x00003100, total: 0x00019b00
first used: 0x00003100, used: 0x00019a6b
Checking newrom.nb for bad NAND block marker
Checked 0x1cc00 sectors successfully!

[DEV][HOWTO] Extracting stock firmware files from .tot files

Hello everyone!
First off:
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE WHILE USING ANY OF THE INFORMATION LOCATED BELOW. IF YOU DO NOT UNDERSTAND WHAT IS BEING DONE, PLEASE DO NOT TRY ANYTHING DONE HERE!
This is still in a VERY basic phase. I am not sure how helpful it will be, but currently, I have been able to extract some of the smaller partitions from the AT&T firmware file.
Starting off, when LGNPST is used to image a phone, it creates a log file in C:\LG Electronics\LGNPST\Models\LOG\ For example, mine was called LS970Log_COM5.log. We are really only interested in one part of this file, located close to the bottom when the phone is actually being imaged. It should look something like this:
0Download mode locking
0Download : PrimaryGPT 0x 0 Size: 0x 512Kb, File Offset: 0x 100000
0 3.182994E-313mmc Init
0Partition Count : 35======================================================
0======================================================
0Download : modem 0x 800000 Size: 0x 54272Kb, File Offset: 0x 180000
0Download : sbl1 0x4800000 Size: 0x 512Kb, File Offset: 0x3680000
0Download : sbl2 0x4880000 Size: 0x 512Kb, File Offset: 0x3700000
0Download : sbl3 0x4900000 Size: 0x 1024Kb, File Offset: 0x3780000
0Download : aboot 0x4b00000 Size: 0x 512Kb, File Offset: 0x3880000
0Download : rpm 0x4b80000 Size: 0x 512Kb, File Offset: 0x3900000
0Download : boot 0x5000000 Size: 0x 7168Kb, File Offset: 0x3980000
0Download : tz 0x6800000 Size: 0x 512Kb, File Offset: 0x4080000
0(null)kip misc Partition
0Download : system 0xb000000 Size: 0x 131072Kb, File Offset: 0x4900000
0Download : system 0x13000000 Size: 0x 512Kb, File Offset: 0xc900000
0Download : system 0x1325e000 Size: 0x 129024Kb, File Offset: 0xc980000
0Download : system 0x1b1fd000 Size: 0x 129536Kb, File Offset: 0x14780000
0Download : system 0x2325e000 Size: 0x 129024Kb, File Offset: 0x1c600000
0Download : system 0x2b1fd000 Size: 0x 129536Kb, File Offset: 0x24400000
0Download : system 0x3325e000 Size: 0x 129024Kb, File Offset: 0x2c280000
0Download : system 0x3b1fd000 Size: 0x 129536Kb, File Offset: 0x34080000
0Download : system 0x4325e000 Size: 0x 129024Kb, File Offset: 0x3bf00000
0Download : system 0x4b1fd000 Size: 0x 76800Kb, File Offset: 0x43d00000
0Download : system 0x53000000 Size: 0x 512Kb, File Offset: 0x48800000
0Download : system 0x5b000000 Size: 0x 512Kb, File Offset: 0x48880000
0Download : system 0x63000000 Size: 0x 512Kb, File Offset: 0x48900000
0Download : persist 0x7a800000 Size: 0x 4608Kb, File Offset: 0x48980000
0Download : recovery 0x8b000000 Size: 0x 8192Kb, File Offset: 0x48e00000
0Download : BackupGPT 0xab380000 Size: 0x 512Kb, File Offset: 0x49600000
0
*********************************************************************************************
Click to expand...
Click to collapse
What do we see that is important here? Image sizes and offsets for data in the file! For example, lets take the boot partition.
0Download : boot 0x5000000 Size: 0x 7168Kb, File Offset: 0x3980000
Click to expand...
Click to collapse
We have a offset of 0x3980000 and a size of 7168Kb. That converts to an equivalent of an offset of 60293120 bytes and a size of 7340032 bytes (I really hope I got that right. As I'm sitting here writing this, I'm thinking of how many different ways I could have messed up that calculation...)
Here, I am using dd on linux in order to separate the partitions from the binary file, but it can be done using equivalent tools on windows.
$ dd bs=1 skip=60293120 count=7340032 if=LGE970AT-00-V10o-ATT-US-SEP-29-2012+0.tot of=boot.img
Click to expand...
Click to collapse
Basically, what I am doing here is copying 7340032 bytes, starting at byte 60293120, from the .tot file to boot.img.
Now, lets check out the backups made with FreeGee when you unlock, to see if it matches with what was actually written to the phone. In order to see if they are equal, we need to trim the backup, because the backup that is taken is actually of the entire partition, not just the actual data.
$ dd bs=1 count=7340032 if=boot-att-backup.img of=boot-att-backup-trimmed.img
Click to expand...
Click to collapse
This is doing basically the same, starting at the first byte, copying 7340032 bytes to boot-att-backup-trimmed.img. This is just making sure you only get the same amount of data that was written.
Now, If of course we want to see if the data is actually the same, so we will also use the diff command, also found on linux, and I'm sure is also available on windows.
$ diff -s boot.img boot-att-backup-trimmed.img
Click to expand...
Click to collapse
If both files are identical, which means everything was done correctly, this should result in the output "Files boot.img and boot-att-backup-trimmed.img are identical", which it does! (The -s flag makes diff report identical files.)
So, now that we know that we can successfully extract the boot partition, I also tried this with the aboot partition, and it worked as well! I have not had success extracting the system partition yet, as it is split up into several partitions. I was hoping that someone with more knowledge could piece together a system image. Enjoy

SnowLeopardJB said:
Hello everyone!
First off:
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE WHILE USING ANY OF THE INFORMATION LOCATED BELOW. IF YOU DO NOT UNDERSTAND WHAT IS BEING DONE, PLEASE DO NOT TRY ANYTHING DONE HERE!
This is still in a VERY basic phase. I am not sure how helpful it will be, but currently, I have been able to extract some of the smaller partitions from the AT&T firmware file.
Starting off, when LGNPST is used to image a phone, it creates a log file in C:\LG Electronics\LGNPST\Models\LOG\ For example, mine was called LS970Log_COM5.log. We are really only interested in one part of this file, located close to the bottom when the phone is actually being imaged. It should look something like this:
What do we see that is important here? Image sizes and offsets for data in the file! For example, lets take the boot partition.
We have a offset of 0x3980000 and a size of 7168Kb. That converts to an equivalent of an offset of 60293120 bytes and a size of 7340032 bytes (I really hope I got that right. As I'm sitting here writing this, I'm thinking of how many different ways I could have messed up that calculation...)
Here, I am using dd on linux in order to separate the partitions from the binary file, but it can be done using equivalent tools on windows.
Basically, what I am doing here is copying 7340032 bytes, starting at byte 60293120, from the .tot file to boot.img.
Now, lets check out the backups made with FreeGee when you unlock, to see if it matches with what was actually written to the phone. In order to see if they are equal, we need to trim the backup, because the backup that is taken is actually of the entire partition, not just the actual data.
This is doing basically the same, starting at the first byte, copying 7340032 bytes to boot-att-backup-trimmed.img. This is just making sure you only get the same amount of data that was written.
Now, If of course we want to see if the data is actually the same, so we will also use the diff command, also found on linux, and I'm sure is also available on windows.
If both files are identical, which means everything was done correctly, this should result in the output "Files boot.img and boot-att-backup-trimmed.img are identical", which it does! (The -s flag makes diff report identical files.)
So, now that we know that we can successfully extract the boot partition, I also tried this with the aboot partition, and it worked as well! I have not had success extracting the system partition yet, as it is split up into several partitions. I was hoping that someone with more knowledge could piece together a system image. Enjoy
Click to expand...
Click to collapse
would it be possible to guide me through this from the very beginning? i want to start cooking for this device, but i need a legit flashable Rom. Please and Thank you.

You are most likely better off just pulling a system image off your device. So, if you are rooted, you can pull your system with something like this:
# busybox tar cf /sdcard/system.tar /system/*
Click to expand...
Click to collapse
That should give you all of the system files all together in a tar archive on your internal sdcard.

I messaged you, but is there any way to use this on the Sprint version to create a flashable .zip?

sorry about the resurrection,
but has there been any progress made on this? More of a curiosity, then anything.
Thanks

SD mount issues

hi!
I have an issue with internal sd
when my phone is waking from sleep android tells me "preparing sdcard..."
This occurs in all ROM's
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7733 MB, 7733248000 bytes
4 heads, 16 sectors/track, 236000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
[email protected]:/ # fdisk -l /dev/block/mmcblk1
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk1: 62333952 sectors, 59.4M
Logical sector size: 512
Disk identifier (GUID): 17b21fb6-f50d-4cf6-9a00-664d68cc276f
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 62333918
Number Start (sector) End (sector) Size Code Name
1 2048 62332927 59.4M 0700
Code:
heimdall print-pit --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Entry Count: 18
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 0
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SMD
Flash Filename: emmc.img
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 6
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BCT
Flash Filename: bct.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PT
Flash Filename:
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EBT
Flash Filename: bootloader.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EB2
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 8
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GP1
Flash Filename: fusetrigger.bin
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 24
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 1200
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APP
Flash Filename: factoryfs.img
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 624
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CAC
Flash Filename: cache.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 7681
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: IMS
Flash Filename:
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MSC
Flash Filename:
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UDA
Flash Filename: data.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MDM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 10
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SOS
Flash Filename: recovery.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: LNX
Flash Filename: boot.img
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename:
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HID
Flash Filename: hidden.img
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GPT
Flash Filename:
FOTA Filename:
Ending session...
Releasing device interface...
Re-attaching kernel driver...
how to fix the partition table
I want to change the partitions, in such a way that only the FAT partition was on the memory card and delete the internal FAT and extended EXT partition for programs etc., but first I must fix partition table

croolyc said:
hi!
I have an issue with internal sd
when my phone is waking from sleep android tells me "preparing sdcard..."
This occurs in all ROM's
how to fix the partition table
I want to change the partitions, in such a way that only the FAT partition was on the memory card and delete the internal FAT and extended EXT partition for programs etc., but first I must fix partition table
Click to expand...
Click to collapse
are you sure its not just external sd card?
You may read http://forum.xda-developers.com/showthread.php?t=1503595
I can send you my pit file, and you can format internal sd card in TWRP recovery.

I created a new partition on the external memory card
Unfortunately, the message "preparing sd card" still appears
fdisk now show partitions correctlyon /dev/block/mmcblk1:
Code:
Disk /dev/block/mmcblk1: 31.9 GB, 31914983424 bytes
255 heads, 63 sectors/track, 3880 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 3825 30724281 b Win95 FAT32
/dev/block/mmcblk1p2 3826 3880 441787+ 82 Linux swap
but /dev/block/mmcblk0 still shows:
Code:
Disk /dev/block/mmcblk0: 7733 MB, 7733248000 bytes
4 heads, 16 sectors/track, 236000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
bubor said:
I can send you my pit file, and you can format internal sd card in TWRP recovery.
Click to expand...
Click to collapse
what is PIT file? is this something like MBR??
yes - in TWRP I can format, but i can't delete, resize, create paritions on internal storage

croolyc said:
I created a new partition on the external memory card
Unfortunately, the message "preparing sd card" still appears
fdisk now show partitions correctlyon /dev/block/mmcblk1:
Code:
Disk /dev/block/mmcblk1: 31.9 GB, 31914983424 bytes
255 heads, 63 sectors/track, 3880 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 3825 30724281 b Win95 FAT32
/dev/block/mmcblk1p2 3826 3880 441787+ 82 Linux swap
but /dev/block/mmcblk0 still shows:
Code:
Disk /dev/block/mmcblk0: 7733 MB, 7733248000 bytes
4 heads, 16 sectors/track, 236000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
what is PIT file? is this something like MBR??
yes - in TWRP I can format, but i can't delete, resize, create paritions on internal storage
Click to expand...
Click to collapse
Pit file contain partition table and more. Partition table simething like MBR.
You couldnt partition with recovery, and you may brick the phone when you try it.

Someone know how to push to push recovery or .img/.bin files via Ubuntu?

Can someone tell me how to push recovery or .img/.bin files via Ubuntu?
Issue: When flashing Clodyg5 2.5 ATT was chosen instead of Tmobile
I have already search all the threads and forums unless I missed something. I have tried all the methods and only seems to be hope in Ubuntu
Here's what I have already tried so far:
1. KDZ and TOT methods and both fail.
2. I tried forcing the device into QHUSB 9008/ Test mode and using BoardDiag3.99c.exe and that also fails with the error displayed to put the device into Dload mode.
3. ADB with fastboot. Does not detect device even though it shows LGE Android device in device manager
4. Used Latest drivers
5. Used XP, Win 7 and Win 8 same results
6. What I can do is see the partitions in Ubuntu. I need the correct command to push the .bin/.img files extracted from the TOT or KDZ and push them via Ubuntu. I was able to do it to an SD Card to try to boot off of it as done for the G2. In other words I copied the bin and recovery to a micro sd and tried to boot off of it but nothing happened.
So this is as far as I can get in Ubuntu:
~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5
[email protected]:~# gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Disk /dev/sda: 41943040 sectors, 20.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 86525607-AEFC-47E3-A2D2-06EB166B5267
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 41943006
Partitions will be aligned on 2048-sector boundaries
Total free space is 6077 sectors (3.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 39845887 19.0 GiB 8300 Linux filesystem
5 39847936 41940991 1022.0 MiB 8200 Linux swap
[email protected]:~# gdisk -l /dev/sda1
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Disk /dev/sda1: 39843840 sectors, 19.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3FFEC32B-2D8F-483A-9325-437E5CC6AB8D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 39843806
Partitions will be aligned on 2048-sector boundaries
Total free space is 39843773 sectors (19.0 GiB)
Number Start (sector) End (sector) Size Code Name
[email protected]:~# gdisk -l /dev/sda2
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Warning! Main partition table overlaps the first partition by 32 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sda2: 2 sectors, 1024 bytes
Logical sector size: 512 bytes
Disk identifier (GUID): D87AD6B9-A79F-4AB6-9139-171BE2D5DDC4
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 18446744073709551584
Partitions will be aligned on 2-sector boundaries
Total free space is 18446744073707458527 sectors (8.0 ZiB)
Number Start (sector) End (sector) Size Code Name
1 2 2093057 1022.0 MiB 8200 Linux swap
[email protected]:~# gdisk -l /dev/sda5
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Disk /dev/sda5: 2093056 sectors, 1022.0 MiB
Logical sector size: 512 bytes
Disk identifier (GUID): 57A1286F-0AD3-467A-A46B-457AA89BC218
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2093022
Partitions will be aligned on 2048-sector boundaries
Total free space is 2092989 sectors (1022.0 MiB)
Number Start (sector) End (sector) Size Code Name
[email protected]:~#
I have already extracted the TOT and KDZ and have recovery.img just don't want to fully brick it.
Links I used as reference:
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/showthread.php?t=2582142
http://forum.xda-developers.com/showthread.php?t=2600575

Issue resolved, please close this thread. Thanks to everyone who chimed in with their suggestions.

leeco le2 firmware install using qfil

Validating Application Configuration
Load APP Configuration
COM:10
SAHARA:True
SAHARA:C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\prog_emmc_firehose_8976_ddr.mbn
SEARCHPATH:C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:True
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)
RAWPROGRAM file path: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\rawprogram0.xml
PATCH file path:C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\patch0.xml
Programmer Path:C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\prog_emmc_firehose_8976_ddr.mbn
Image Search Path: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)
RAWPROGRAM file path: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\rawprogram0.xml
PATCH file path:C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\patch0.xml
Start Download
Program Path:C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\prog_emmc_firehose_8976_ddr.mbn
COM Port number:10
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:10
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
FireHose Log: [email protected] [email protected]
Request payload size 0xc000 is not the same as support payload size, change to 0x100000
Request payload size 0x100000 is too big, reduce to 0x20000
FireHose Log: [email protected] [email protected]
Set TxBuffer 0x20000, RxBuffer 0x4000
Firehose configure packet sent successfully!
ReadBackMode:No_Readback
Disable read back
Total Bytes To Program 0xD264FEA0
Download Image
PROGRAM: Replace the partition sectors number 0x2a000 to file size in sector 0x289ad
PROGRAM: Partition 0, Sector: 131072, Length: 166317 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\NON-HLOS.bin
FireHose Log: start 131072, num 166317
FireHose Log: Finished sector address 297389
PROGRAM: Written Bytes 0x5135a00 (64)
Program Size: 81.21 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x2ca
PROGRAM: Partition 0, Sector: 393234, Length: 714 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\sbl1.mbn
FireHose Log: start 393234, num 714
FireHose Log: Finished sector address 393948
PROGRAM: Written Bytes 0x59400 (64)
Program Size: 0.35 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x2ca
PROGRAM: Partition 0, Sector: 394258, Length: 714 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\sbl1.mbn
FireHose Log: start 394258, num 714
FireHose Log: Finished sector address 394972
PROGRAM: Written Bytes 0x59400 (64)
Program Size: 0.35 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x148
PROGRAM: Partition 0, Sector: 395282, Length: 328 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\rpm.mbn
FireHose Log: start 395282, num 328
FireHose Log: Finished sector address 395610
PROGRAM: Written Bytes 0x29000 (64)
Program Size: 0.16 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x148
PROGRAM: Partition 0, Sector: 396306, Length: 328 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\rpm.mbn
FireHose Log: start 396306, num 328
FireHose Log: Finished sector address 396634
PROGRAM: Written Bytes 0x29000 (64)
Program Size: 0.16 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x4f3
PROGRAM: Partition 0, Sector: 397330, Length: 1267 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\tz.mbn
FireHose Log: start 397330, num 1267
FireHose Log: Finished sector address 398597
PROGRAM: Written Bytes 0x9e600 (64)
Program Size: 0.62 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x4f3
PROGRAM: Partition 0, Sector: 401426, Length: 1267 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\tz.mbn
FireHose Log: start 401426, num 1267
FireHose Log: Finished sector address 402693
PROGRAM: Written Bytes 0x9e600 (64)
Program Size: 0.62 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x90
PROGRAM: Partition 0, Sector: 405522, Length: 144 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\hyp.mbn
FireHose Log: start 405522, num 144
FireHose Log: Finished sector address 405666
PROGRAM: Written Bytes 0x12000 (64)
Program Size: 0.07 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x90
PROGRAM: Partition 0, Sector: 406546, Length: 144 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\hyp.mbn
FireHose Log: start 406546, num 144
FireHose Log: Finished sector address 406690
PROGRAM: Written Bytes 0x12000 (64)
Program Size: 0.07 MB
PROGRAM: Partition 0, Sector: 407570, Length: 32768 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\adspso.bin
FireHose Log: start 407570, num 32768
FireHose Log: Finished sector address 440338
PROGRAM: Written Bytes 0x1000000 (64)
Program Size: 16.00 MB
PROGRAM: Partition 0, Sector: 446482, Length: 2 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\oemconfig.img
FireHose Log: start 446482, num 2
FireHose Log: Finished sector address 446484
PROGRAM: Written Bytes 0x400 (64)
Program Size: 0.00 MB
PROGRAM: Partition 0, Sector: 655360, Length: 64 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\ddr.bin
FireHose Log: start 655360, num 64
FireHose Log: Finished sector address 655424
PROGRAM: Written Bytes 0x8000 (64)
Program Size: 0.03 MB
PROGRAM: Replace the partition sectors number 0x20 to file size in sector 0x1
PROGRAM: Partition 0, Sector: 658496, Length: 1 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\sec.dat
FireHose Log: start 658496, num 1
FireHose Log: Finished sector address 658497
PROGRAM: Written Bytes 0x200 (64)
Program Size: 0.00 MB
PROGRAM: Replace the partition sectors number 0x19000 to file size in sector 0x11cc4
PROGRAM: Partition 0, Sector: 658528, Length: 72900 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\splash.img
FireHose Log: start 658528, num 72900
FireHose Log: Finished sector address 731428
PROGRAM: Written Bytes 0x2398800 (64)
Program Size: 35.60 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x453
PROGRAM: Partition 0, Sector: 760928, Length: 1107 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\emmc_appsboot.mbn
FireHose Log: start 760928, num 1107
FireHose Log: Finished sector address 762035
PROGRAM: Written Bytes 0x8a600 (64)
Program Size: 0.54 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x453
PROGRAM: Partition 0, Sector: 762976, Length: 1107 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\emmc_appsboot.mbn
FireHose Log: start 762976, num 1107
FireHose Log: Finished sector address 764083
PROGRAM: Written Bytes 0x8a600 (64)
Program Size: 0.54 MB
PROGRAM: Replace the partition sectors number 0x20000 to file size in sector 0x5483
PROGRAM: Partition 0, Sector: 765024, Length: 21635 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\boot.img
FireHose Log: start 765024, num 21635
FireHose Log: Finished sector address 786659
PROGRAM: Written Bytes 0xa90600 (64)
Program Size: 10.56 MB
PROGRAM: Replace the partition sectors number 0x20000 to file size in sector 0x6c87
PROGRAM: Partition 0, Sector: 896096, Length: 27783 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\recovery.img
FireHose Log: start 896096, num 27783
FireHose Log: Finished sector address 923879
PROGRAM: Written Bytes 0xd90e00 (64)
Program Size: 13.57 MB
PROGRAM: Partition 0, Sector: 1179648, Length: 262160 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_1.img
FireHose Log: start 1179648, num 262160
FireHose Log: Finished sector address 1441808
PROGRAM: Written Bytes 0x8002000 (64)
Program Size: 128.01 MB
PROGRAM: Partition 0, Sector: 1443848, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_2.img
FireHose Log: start 1443848, num 16
FireHose Log: Finished sector address 1443864
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1447928, Length: 256000 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_3.img
FireHose Log: start 1447928, num 256000
FireHose Log: Finished sector address 1703928
PROGRAM: Written Bytes 0x7d00000 (64)
Program Size: 125.00 MB
PROGRAM: Partition 0, Sector: 1703936, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_4.img
FireHose Log: start 1703936, num 16
FireHose Log: Finished sector address 1703952
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1708016, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_5.img
FireHose Log: start 1708016, num 258056
FireHose Log: Finished sector address 1966072
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 1966080, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_6.img
FireHose Log: start 1966080, num 16
FireHose Log: Finished sector address 1966096
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1968136, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_7.img
FireHose Log: start 1968136, num 16
FireHose Log: Finished sector address 1968152
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1972216, Length: 256000 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_8.img
FireHose Log: start 1972216, num 256000
FireHose Log: Finished sector address 2228216
PROGRAM: Written Bytes 0x7d00000 (64)
Program Size: 125.00 MB
PROGRAM: Partition 0, Sector: 2228224, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_9.img
FireHose Log: start 2228224, num 16
FireHose Log: Finished sector address 2228240
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 2232304, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_10.img
FireHose Log: start 2232304, num 258056
FireHose Log: Finished sector address 2490360
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 2490368, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_11.img
FireHose Log: start 2490368, num 16
FireHose Log: Finished sector address 2490384
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 2492424, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_12.img
FireHose Log: start 2492424, num 16
FireHose Log: Finished sector address 2492440
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 2496504, Length: 256000 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_13.img
FireHose Log: start 2496504, num 256000
FireHose Log: Finished sector address 2752504
PROGRAM: Written Bytes 0x7d00000 (64)
Program Size: 125.00 MB
PROGRAM: Partition 0, Sector: 2752512, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_14.img
FireHose Log: start 2752512, num 16
FireHose Log: Finished sector address 2752528
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 2756592, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_15.img
FireHose Log: start 2756592, num 258056
FireHose Log: Finished sector address 3014648
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 3014656, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_16.img
FireHose Log: start 3014656, num 16
FireHose Log: Finished sector address 3014672
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 3016712, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_17.img
FireHose Log: start 3016712, num 16
FireHose Log: Finished sector address 3016728
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 3020792, Length: 256000 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_18.img
FireHose Log: start 3020792, num 256000
FireHose Log: Finished sector address 3276792
PROGRAM: Written Bytes 0x7d00000 (64)
Program Size: 125.00 MB
PROGRAM: Partition 0, Sector: 3276800, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_19.img
FireHose Log: start 3276800, num 16
FireHose Log: Finished sector address 3276816
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 3280880, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_20.img
FireHose Log: start 3280880, num 258056
FireHose Log: Finished sector address 3538936
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 3538944, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_21.img
FireHose Log: start 3538944, num 16
FireHose Log: Finished sector address 3538960
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 3541000, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_22.img
FireHose Log: start 3541000, num 16
FireHose Log: Finished sector address 3541016
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 3545080, Length: 256000 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_23.img
FireHose Log: start 3545080, num 256000
FireHose Log: Finished sector address 3801080
PROGRAM: Written Bytes 0x7d00000 (64)
Program Size: 125.00 MB
PROGRAM: Partition 0, Sector: 3801088, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_24.img
FireHose Log: start 3801088, num 16
FireHose Log: Finished sector address 3801104
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 3805168, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_25.img
FireHose Log: start 3805168, num 258056
FireHose Log: Finished sector address 4063224
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 4063232, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_26.img
FireHose Log: start 4063232, num 16
FireHose Log: Finished sector address 4063248
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 4067312, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_27.img
FireHose Log: start 4067312, num 258056
FireHose Log: Finished sector address 4325368
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 4325376, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_28.img
FireHose Log: start 4325376, num 16
FireHose Log: Finished sector address 4325392
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 4329456, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_29.img
FireHose Log: start 4329456, num 258056
FireHose Log: Finished sector address 4587512
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 4587520, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_30.img
FireHose Log: start 4587520, num 16
FireHose Log: Finished sector address 4587536
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 4591600, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_31.img
FireHose Log: start 4591600, num 258056
FireHose Log: Finished sector address 4849656
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 4849664, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_32.img
FireHose Log: start 4849664, num 16
FireHose Log: Finished sector address 4849680
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 4853744, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_33.img
FireHose Log: start 4853744, num 258056
FireHose Log: Finished sector address 5111800
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 5111808, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_34.img
FireHose Log: start 5111808, num 16
FireHose Log: Finished sector address 5111824
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 5115888, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_35.img
FireHose Log: start 5115888, num 258056
FireHose Log: Finished sector address 5373944
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 5373952, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_36.img
FireHose Log: start 5373952, num 16
FireHose Log: Finished sector address 5373968
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 5378032, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_37.img
FireHose Log: start 5378032, num 258056
FireHose Log: Finished sector address 5636088
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 5636096, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_38.img
FireHose Log: start 5636096, num 16
FireHose Log: Finished sector address 5636112
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 5640176, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_39.img
FireHose Log: start 5640176, num 258056
FireHose Log: Finished sector address 5898232
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 5898240, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_40.img
FireHose Log: start 5898240, num 16
FireHose Log: Finished sector address 5898256
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 5902320, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_41.img
FireHose Log: start 5902320, num 258056
FireHose Log: Finished sector address 6160376
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 6160384, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_42.img
FireHose Log: start 6160384, num 16
FireHose Log: Finished sector address 6160400
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 6164464, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_43.img
FireHose Log: start 6164464, num 258056
FireHose Log: Finished sector address 6422520
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 6422528, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_44.img
FireHose Log: start 6422528, num 16
FireHose Log: Finished sector address 6422544
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 6426608, Length: 258056 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_45.img
FireHose Log: start 6426608, num 258056
FireHose Log: Finished sector address 6684664
PROGRAM: Written Bytes 0x7e01000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 6684672, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_46.img
FireHose Log: start 6684672, num 16
FireHose Log: Finished sector address 6684688
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 6688752, Length: 88280 Sectors, Sector Size: 512 Bytes
File: C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_47.img
FireHose Log: start 6688752, num 88280
PROGRAM: Send raw data fail code 17
PROGRAM: Send raw data fail
Failed to write C:\Users\ranjith\Documents\o\s2_india_sparse_images(2)\system_47.img to the device
Download Fail:FireHose Fail FireHose Fail:Failed to Upload the emmc images to the phone using Firehose.
Finish Download
..........................................................xxxxxxxxxxxxxxx................................xxxxxxxxxxxxx........................................
hii guys this is my qfil log i have some issses for installing firmware so please suggest to clear my doubts:crying:

ranjithbobby89 said:
Validating Application Configuration.........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is specific to your device and variants.
https://forum.xda-developers.com/le-2
With that guidance...
you should be able to obtain some member guidance within one of the following threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3632277
https://forum.xda-developers.com/showthread.php?t=3725302
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Tandy TRS-80.

did you resolved it? i have the same problem, i have the phone unusable. Some one has fixed it or downloaded other rom qfil?