[Q] UnBricking the Hard brick with QPST? - T-Mobile Samsung Galaxy S II SGH-T989

If you have a hard bricked t989, and some other devices with Qualcomm chips, the device doesn't boot, or show any signs of life. You will see in device manager on Windows a Qualcomm download device. I loaded a drive I found here at XDA, and it is a COM port. In ODIN it is seen, but will never connect in trying to flash anything, it always hangs at "starting connection.." but QPST can see the device also! There are few guilds to building an image for QPST to flash. It requires a few files that I think are in the .md5 files for a device. Now QPST can build the image with an exe in one of its program's folders and the image files and an xml to set the partitions. I have a hard bricked phone and want to use this method to repair the phone. It could be ready to publish here with the files (minus the QPST parts, but anyone could get those via Google) and a clear tutorial if anyone would like to help me with this, just send me a message. If I work on this alone, it may take a few weeks. I need to learn about this device and the xml format for this process. I was handed this phone in a softbrick state with very little battery life in it. I went to ODIN stock image (I got the E4GT so I knew some of this from my own device) The image download I got here at XDA came with a PIT file and as I loaded the PDA file to flash I missed the PIT file had loaded too! With a little help I could have a free solution up in a few days. This is a multi-device solution. Many devices with Qualcomm Download mode could be recovered with this. No opening, JTAG tools, just your usb cable and your phone. Anybody think they know what I'm talking about and want to help?

200+ views!?
....and not even a troll.....:crying:

lets start
even i am on the same boat with hardbricked samsung sc-03d
daxxone said:
....and not even a troll.....:crying:
Click to expand...
Click to collapse

You got the driver loaded for Qualcomm download mode and no other signs of life on your device? I seen the dell streak 7 forms have this happening to them too. You know anything about the partition tables on your device? Have you ever used qpst or qxdm?
Sent from my SPH-D710 using xda app-developers app

If you made this post back in June when my phone was hardbricked, I might have been of some more use to you! I am completely in support of your efforts. I sent my to mobiletechvideos as my attempts to get it back were futile. I lacked the qualcomm processor, the programs, the electrodes or whatever the hell connects the phone motherboard to the processor. If you can achieve a ressurection via USB you will etch yourself a god amongst men
Once again good luck!
Levitating Via JMTX!

same brick t989
I already try to unbrick my t989 with QPST. it does not recognize partition.xml from available android firmware from other device witn 8660 cpu.
Now, I can set phone to usb storage with miflash. seems it use the same method. But while write modem.bin it stops work. maybe partitions.xml is wrong.
Code:
CEmergencyFlasher::IsQPSTServer(548): Not implemented(0x80004001)
COM20 0.06 Open serial port "\\.\COM20"
COM20 0.06 Load programmer "E:\Mioneplus_QDN43_fastboot_Android_4.0_d3d83nmdk2\images2\MPRG8660.hex"
COM20 0.08 Send parameters command
COM20 0.08 Write and verify address 0x2a000000, size 10240
COM20 0.14 Write and verify address 0x2a002800, size 10240
COM20 0.20 Write and verify address 0x2a005000, size 10240
COM20 0.27 Write and verify address 0x2a007800, size 10240
COM20 0.33 Write and verify address 0x2a00a000, size 10240
COM20 0.39 Write and verify address 0x2a00c800, size 10240
COM20 0.45 Write and verify address 0x2a00f000, size 10240
COM20 0.50 Write and verify address 0x2a011800, size 10240
COM20 0.56 Write and verify address 0x2a014000, size 10240
COM20 0.62 Write and verify address 0x2a016800, size 10240
COM20 0.69 Write and verify address 0x2a019000, size 10240
COM20 0.75 Write and verify address 0x2a01b800, size 10240
COM20 0.81 Write and verify address 0x2a01e000, size 10240
COM20 0.86 Write and verify address 0x2a020800, size 10240
COM20 0.92 Write and verify address 0x2a023000, size 10240
COM20 0.98 Write and verify address 0x2a025800, size 10240
COM20 1.04 Write and verify address 0x2a028000, size 1976
COM20 1.06 Jump to flash programmer(0x2a000000)
COM20 1.06 Open boot file "E:\Mioneplus_QDN43_fastboot_Android_4.0_d3d83nmdk2\images2\8660_msimage.mbn"
COM20 1.06 Send hello command 0
RobustWrite(32): A device attached to the system is not functioning.(0x8007001f)
RobustWrite(32): A device attached to the system is not functioning.(0x8007001f)
RobustWrite(32): A device attached to the system is not functioning.(0x8007001f)
RobustWrite(32): A device attached to the system is not functioning.(0x8007001f)
RobustWrite(32): The I/O operation has been aborted because of either a thread exit or an application request.(0x800703e3)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
ReceivePacket(238): Reached the end of the file.(0x80070026)
DownloadMiniKernel(517): Reached the end of the file.(0x80070026)
COM20 4.10 Send hello command 1
COM20 4.10 Enable trusted security mode
COM20 4.10 Open EMMC card USER partition
RobustRead(55): Reached the end of the file.(0x80070026)
COM20 4.30 StreamWrite address 00000000, size 20480
COM20 4.55 StreamWrite address 0x00a000, size 20480
COM20 4.79 StreamWrite address 0x014000, size 20480
COM20 5.04 StreamWrite address 0x01e000, size 20480
COM20 5.27 StreamWrite address 0x028000, size 20480
COM20 5.52 StreamWrite address 0x032000, size 20480
COM20 5.76 StreamWrite address 0x03c000, size 20480
COM20 5.99 StreamWrite address 0x046000, size 20480
COM20 6.25 StreamWrite address 0x050000, size 20480
COM20 6.49 StreamWrite address 0x05a000, size 20480
COM20 6.74 StreamWrite address 0x064000, size 20480
COM20 6.99 StreamWrite address 0x06e000, size 20480
COM20 7.22 StreamWrite address 0x078000, size 20480
COM20 7.46 StreamWrite address 0x082000, size 20480
COM20 7.74 StreamWrite address 0x08c000, size 20480
COM20 7.97 StreamWrite address 0x096000, size 20480
COM20 8.21 StreamWrite address 0x0a0000, size 20480
COM20 8.49 StreamWrite address 0x0aa000, size 20480
COM20 8.74 StreamWrite address 0x0b4000, size 20480
COM20 8.97 StreamWrite address 0x0be000, size 20480
COM20 9.27 StreamWrite address 0x0c8000, size 20480
COM20 9.50 StreamWrite address 0x0d2000, size 20480
COM20 9.78 StreamWrite address 0x0dc000, size 20480
COM20 10.02 StreamWrite address 0x0e6000, size 20480
COM20 10.25 StreamWrite address 0x0f0000, size 20480
COM20 10.55 StreamWrite address 0x0fa000, size 20480
COM20 10.78 StreamWrite address 0x104000, size 20480
COM20 11.06 StreamWrite address 0x10e000, size 20480
COM20 11.31 StreamWrite address 0x118000, size 20480
COM20 11.54 StreamWrite address 0x122000, size 20480
COM20 11.84 StreamWrite address 0x12c000, size 20480
COM20 12.09 StreamWrite address 0x136000, size 20480
COM20 12.36 StreamWrite address 0x140000, size 20480
COM20 12.61 StreamWrite address 0x14a000, size 20480
COM20 12.85 StreamWrite address 0x154000, size 20480
COM20 13.14 StreamWrite address 0x15e000, size 20480
COM20 13.40 StreamWrite address 0x168000, size 20480
COM20 13.70 StreamWrite address 0x172000, size 20480
COM20 13.93 StreamWrite address 0x17c000, size 20480
COM20 14.16 StreamWrite address 0x186000, size 20480
COM20 14.37 Close EMMC card USER partition
COM20 14.37 Reboot to mini kernel
COM20 14.41 Wait device connect 0
COM20 15.43 Wait device connect 1
COM20 16.54 Wait device connect 2
COM20 22.59 Dismount volume "\\?\Volume{19a5bc11-0b8e-11e2-924a-10bf48a1a907}"
COM20 22.62 Open disk "\\?\usbstor#disk&ven_qualcomm&prod_mmc_storage&rev_2.31#7&17ba28ff&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
COM20 22.62 Delete drive layout
COM20 22.70 Open program file "E:\Mioneplus_QDN43_fastboot_Android_4.0_d3d83nmdk2\images2\rawprogram0.xml"
COM20 22.70 Writing file "E:\Mioneplus_QDN43_fastboot_Android_4.0_d3d83nmdk2\images2\NON-HLOS.bin" to partition at 0x00000000000200
COM20 22.70 WriteFile position 0x00000000000200, size 1048576
i also have clockworkmod backup
Code:
.android_secure.vfat.tar │ 1536
boot.img │ 10 M
cache.ext4.tar │ 11776
data.ext4.tar │ 873 M
nandroid.md5 │ 296
recovery.img │ 10 M
system.ext4.tar │ 426 M
but as i know it does not have all partitions and partition table.

This is the guide you should look at. I think he even has the same processor as you do...
But there's no hope for you to be successful, unless you know exactly how your partition table should look...

Maybe QXDM is needed for the modem...or commands
alex9x said:
I already try to unbrick my t989 with QPST. it does not recognize partition.xml from available android firmware from other device witn 8660 cpu.
Now, I can set phone to usb storage with miflash. seems it use the same method. But while write modem.bin it stops work. maybe partitions.xml is wrong.
Code:
CEmergencyFlasher::IsQPSTServer(548): Not implemented(0x80004001)
COM20 0.06 Open serial port "\\.\COM20"
COM20 0.06 Load programmer "E:\Mioneplus_QDN43_fastboot_Android_4.0_d3d83nmdk2\images2\MPRG8660.hex"
COM20 0.08 Send parameters command
COM20 0.08 Write and verify address 0x2a000000, size 10240
COM20 0.14 Write and verify address 0x2a002800, size 10240
COM20 0.20 Write and verify address 0x2a005000, size 10240
COM20 0.27 Write and verify address 0x2a007800, size 10240
COM20 0.33 Write and verify address 0x2a00a000, size 10240
COM20 0.39 Write and verify address 0x2a00c800, size 10240
COM20 0.45 Write and verify address 0x2a00f000, size 10240
COM20 0.50 Write and verify address 0x2a011800, size 10240
COM20 0.56 Write and verify address 0x2a014000, size 10240
COM20 0.62 Write and verify address 0x2a016800, size 10240
COM20 0.69 Write and verify address 0x2a019000, size 10240
COM20 0.75 Write and verify address 0x2a01b800, size 10240
COM20 0.81 Write and verify address 0x2a01e000, size 10240
COM20 0.86 Write and verify address 0x2a020800, size 10240
COM20 0.92 Write and verify address 0x2a023000, size 10240
COM20 0.98 Write and verify address 0x2a025800, size 10240
COM20 1.04 Write and verify address 0x2a028000, size 1976
COM20 1.06 Jump to flash programmer(0x2a000000)
COM20 1.06 Open boot file "E:\Mioneplus_QDN43_fastboot_Android_4.0_d3d83nmdk2\images2\8660_msimage.mbn"
COM20 1.06 Send hello command 0
RobustWrite(32): A device attached to the system is not functioning.(0x8007001f)
RobustWrite(32): A device attached to the system is not functioning.(0x8007001f)
RobustWrite(32): A device attached to the system is not functioning.(0x8007001f)
RobustWrite(32): A device attached to the system is not functioning.(0x8007001f)
RobustWrite(32): The I/O operation has been aborted because of either a thread exit or an application request.(0x800703e3)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
RobustRead(55): Reached the end of the file.(0x80070026)
ReceivePacket(238): Reached the end of the file.(0x80070026)
DownloadMiniKernel(517): Reached the end of the file.(0x80070026)
COM20 4.10 Send hello command 1
COM20 4.10 Enable trusted security mode
COM20 4.10 Open EMMC card USER partition
RobustRead(55): Reached the end of the file.(0x80070026)
COM20 4.30 StreamWrite address 00000000, size 20480
COM20 4.55 StreamWrite address 0x00a000, size 20480
COM20 4.79 StreamWrite address 0x014000, size 20480
COM20 5.04 StreamWrite address 0x01e000, size 20480
COM20 5.27 StreamWrite address 0x028000, size 20480
COM20 5.52 StreamWrite address 0x032000, size 20480
COM20 5.76 StreamWrite address 0x03c000, size 20480
COM20 5.99 StreamWrite address 0x046000, size 20480
COM20 6.25 StreamWrite address 0x050000, size 20480
COM20 6.49 StreamWrite address 0x05a000, size 20480
COM20 6.74 StreamWrite address 0x064000, size 20480
COM20 6.99 StreamWrite address 0x06e000, size 20480
COM20 7.22 StreamWrite address 0x078000, size 20480
COM20 7.46 StreamWrite address 0x082000, size 20480
COM20 7.74 StreamWrite address 0x08c000, size 20480
COM20 7.97 StreamWrite address 0x096000, size 20480
COM20 8.21 StreamWrite address 0x0a0000, size 20480
COM20 8.49 StreamWrite address 0x0aa000, size 20480
COM20 8.74 StreamWrite address 0x0b4000, size 20480
COM20 8.97 StreamWrite address 0x0be000, size 20480
COM20 9.27 StreamWrite address 0x0c8000, size 20480
COM20 9.50 StreamWrite address 0x0d2000, size 20480
COM20 9.78 StreamWrite address 0x0dc000, size 20480
COM20 10.02 StreamWrite address 0x0e6000, size 20480
COM20 10.25 StreamWrite address 0x0f0000, size 20480
COM20 10.55 StreamWrite address 0x0fa000, size 20480
COM20 10.78 StreamWrite address 0x104000, size 20480
COM20 11.06 StreamWrite address 0x10e000, size 20480
COM20 11.31 StreamWrite address 0x118000, size 20480
COM20 11.54 StreamWrite address 0x122000, size 20480
COM20 11.84 StreamWrite address 0x12c000, size 20480
COM20 12.09 StreamWrite address 0x136000, size 20480
COM20 12.36 StreamWrite address 0x140000, size 20480
COM20 12.61 StreamWrite address 0x14a000, size 20480
COM20 12.85 StreamWrite address 0x154000, size 20480
COM20 13.14 StreamWrite address 0x15e000, size 20480
COM20 13.40 StreamWrite address 0x168000, size 20480
COM20 13.70 StreamWrite address 0x172000, size 20480
COM20 13.93 StreamWrite address 0x17c000, size 20480
COM20 14.16 StreamWrite address 0x186000, size 20480
COM20 14.37 Close EMMC card USER partition
COM20 14.37 Reboot to mini kernel
COM20 14.41 Wait device connect 0
COM20 15.43 Wait device connect 1
COM20 16.54 Wait device connect 2
COM20 22.59 Dismount volume "\\?\Volume{19a5bc11-0b8e-11e2-924a-10bf48a1a907}"
COM20 22.62 Open disk "\\?\usbstor#disk&ven_qualcomm&prod_mmc_storage&rev_2.31#7&17ba28ff&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
COM20 22.62 Delete drive layout
COM20 22.70 Open program file "E:\Mioneplus_QDN43_fastboot_Android_4.0_d3d83nmdk2\images2\rawprogram0.xml"
COM20 22.70 Writing file "E:\Mioneplus_QDN43_fastboot_Android_4.0_d3d83nmdk2\images2\NON-HLOS.bin" to partition at 0x00000000000200
COM20 22.70 WriteFile position 0x00000000000200, size 1048576
i also have clockworkmod backup
Code:
.android_secure.vfat.tar │ 1536
boot.img │ 10 M
cache.ext4.tar │ 11776
data.ext4.tar │ 873 M
nandroid.md5 │ 296
recovery.img │ 10 M
system.ext4.tar │ 426 M
but as i know it does not have all partitions and partition table.
Click to expand...
Click to collapse
Everyone says modem is a hidden partition. To make changes to NV memory in CDMA devices (and I assume this is similar on GSM), such as ESN rebuilding and some DATA parameter changes, you need to send a security code to unlock that section before writing to that area. This is common for samungs. They used 16 digits for their codes. If the code is sent via QXDM command then the modem memory should write just fine. The other post mentioned in this thred by E:V:A has some helpful bits. If it wasn't in a dev section I would post this little tip there to help. (I don't have enough posts just yet). Now an issue with using QXDM to send the security code, is QXDM will hold the com port even after closing the app. QPST may be able to use it, but I think it would just say the com is busy. There is a place to send this code to the device in QPST, I just don't know where. CDMA workshop will release the com port when the app is closed, so that would be one way to send the code and get back to program to flash the files.
The big thing here is getting a bootloader and a modem, mostly because ODIN needs a modem to open a com port to the usb on the phone. The security code must be in the modem.bin. As I remember one theory being that ODIN loads the modem to RAM (of some sort, vRAM? I'm not sure here) and it gets sent after a check, at boot time. CWM can just push it there with no check first. If you can boot after flashing your images, you should try flashing CWM, and then flashing a modem from there. You should be golden then.

I don't have this device anymore...
just to let you know. I have a D710 that I use daily on Cricket. I also got one the other day, it has i9100 bootloader and I'm looking to unbrick it. It boots, just no radios ( well bluetooth is on, just doesn't seem to get files sent ) and no usb. The phone I had that started me on this was not mine, and has been returned to the owner. All of this is related in one way or another, I seen a few devices that brick like this. This is a way around jtag, so some that know may not want it to be known. I tried talking with a guy on ebay doing the jtag about some of this, and he quit responding after I started talking about QPST and a usb unbrick. I don't see this as putting them out of work, just changing the way the work is done. It could be a remote service, done with a usb cable, or maybe a new kind of jig. It will happen at some point.

done with riffbox
today receive riff box and repair brick with jtag.
as i understand, it can be unbricked with QPST softwate with backup, maked with QPST...
or maybe with known address and bootblock... (manual write image to known address)
or maybe fullflash backup byte to byte...
riffbox flash about 16mb and i think it can be done with QPST software.
maybe later i found solution, today i going travel and when come back i will try to make a solution.

alex9x said:
today receive riff box and repair brick with jtag.
as i understand, it can be unbricked with QPST softwate with backup, maked with QPST...
or maybe with known address and bootblock... (manual write image to known address)
or maybe fullflash backup byte to byte...
riffbox flash about 16mb and i think it can be done with QPST software.
maybe later i found solution, today i going travel and when come back i will try to make a solution.
Click to expand...
Click to collapse
Did you find anything that may be of use?
Can you send me some pin out info for SPH-D710? I want to see if I can get a jig to open a com on my device.
Sent from my SPH-D710 using xda app-developers app

UnBricking the Hard brick with QPST
daxxone said:
If you have a hard bricked t989, and some other devices with Qualcomm chips, the device doesn't boot, or show any signs of life. You will see in device manager on Windows a Qualcomm download device. I loaded a drive I found here at XDA, and it is a COM port. In ODIN it is seen, but will never connect in trying to flash anything, it always hangs at "starting connection.." but QPST can see the device also! There are few guilds to building an image for QPST to flash. It requires a few files that I think are in the .md5 files for a device. Now QPST can build the image with an exe in one of its program's folders and the image files and an xml to set the partitions. I have a hard bricked phone and want to use this method to repair the phone. It could be ready to publish here with the files (minus the QPST parts, but anyone could get those via Google) and a clear tutorial if anyone would like to help me with this, just send me a message. If I work on this alone, it may take a few weeks. I need to learn about this device and the xml format for this process. I was handed this phone in a softbrick state with very little battery life in it. I went to ODIN stock image (I got the E4GT so I knew some of this from my own device) The image download I got here at XDA came with a PIT file and as I loaded the PDA file to flash I missed the PIT file had loaded too! With a little help I could have a free solution up in a few days. This is a multi-device solution. Many devices with Qualcomm Download mode could be recovered with this. No opening, JTAG tools, just your usb cable and your phone. Anybody think they know what I'm talking about and want to help?
Click to expand...
Click to collapse
Good luck to you on this. If I could help you I would. I have a SGS2 hard bricked serving as a wonderful looking paperweight on my desk. When I plug it into my PC it recognizes it and QPST is the how it looks in device manager. This is a result of an ODIN flash. So I will stay tuned.
Jewelz

Check this thread: http://forum.xda-developers.com/showthread.php?t=2136738

aNY uPDATE
Hi mates
Is there any update on resurrecting sgh tr989 with qpst
please help me

dingdong said:
Hi mates
Is there any update on resurrecting sgh tr989 with qpst
please help me
Click to expand...
Click to collapse
Link above your post?

RussianBear said:
Link above your post?
Click to expand...
Click to collapse
But the required files are not for my sgh t989, can you guide me on finding the required files
Cheer and thanks for replying

dingdong said:
But the required files are not for my sgh t989, can you guide me on finding the required files
Cheer and thanks for replying
Click to expand...
Click to collapse
You'll need to get with darkspr1te to see what you need.

RussianBear said:
You'll need to get with darkspr1te to see what you need.
Click to expand...
Click to collapse
thanks

dingdong said:
thanks
Click to expand...
Click to collapse
Just curious rather than 100 people sending darkspr1te a message separately I'd just ask you if you got any response from him or any further movement on the bricked phone? I'm in your same boat.

Can I help?
daxxone said:
If you have a hard bricked t989, and some other devices with Qualcomm chips, the device doesn't boot, or show any signs of life. You will see in device manager on Windows a Qualcomm download device. *snip* Anybody think they know what I'm talking about and want to help?
Click to expand...
Click to collapse
I have one hard bricked T989D, and two working stock firmware T989D phones here.
I can connect to the bricked phone using the QDLoader drivers and QPST software, but I have no clue what to do.
Would it be possible to backup the files from one (or both) good phones with QPST or ODIN and use them to restore the bricked phone?
What can I do to help out and to get my bricked phone back into service?

Related

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.

[6039y] **GUIDE** Repartitioning of the internal memory

Here it is as I promised.
This phone (the model with one sim card) is sold as a device with 8GB internal memory. In fact the memory chip inside is 16GB, so we can increase the available internal space.
PLEASE READ CAREFULLY AND IF SOMETHING IS NOT CLEAR DO NOT HESITATE TO ASK.
*** The data on your device will be untouched after this operation. But again please read carefully! ***
*** A good practice is always to make a backup of everything which will be changed. I do it and I've made a backup of the entire internal memory of the device before the start of the operation which is described below. ***
*** At the end of the post there is a link to a ZIP file which can be flashed through TWRP in order to perform the procedure automatically. Also includes a check for the size of the EMMC (as there are devices on which the resizing cannot be performed...their chip is smaller).***
1. You can go to this thread and to say Thanks! @meghd00t as his static build of gdisk is used in the recovery below.
2. What is needed:
- A different TWRP Recovery with gdisk inside. It can be downloaded from here twrp-2.8.7.0-idol3-6039y-with-gdisk.img - md5sum: 66b3f82a3e2e1afe14627b3b900a9319
- (Optional) An SD card for backup of the original GPT partition layout.
- Patience and careful reading.
- The Windows users probably need the drivers from this post, for access to the device in recovery mode.
3. How to do it (the output used below is from the terminal window from which I've done this operation on my device):
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3-6039y-with-gdisk.img
- go to the device
Code:
adb shell
- unmount all partitions of the internal memory
Code:
~ # umount /cache
~ # umount /sdcard
~ # umount /and-sec
- ensure that there are no mounted partitions from mmcblk0. The output from the mount command should looks like this:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=713016k,nr_inodes=157853,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=713016k,nr_inodes=157853)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
- start gdisk
Code:
~ # gdisk /dev/block/mmcblk0
all partitions can be listed by pressing 'p' but we are interested by the last two:
Code:
37 5000400 15269853 4.9 GiB FFFF userdata
38 15269854 30535646 7.3 GiB 0700 userdatabak
and their information which will be shown by pressing 'i' and entering the partition number:
Code:
Command (? for help): i
Partition number (1-38): 37
Partition GUID code: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335 (Unknown)
Partition unique GUID: BDD7FA27-93D4-40BC-B266-313E074E0E87
First sector: 5000400 (at 2.4 GiB)
Last sector: 15269853 (at 7.3 GiB)
Partition size: 10269454 sectors (4.9 GiB)
Attribute flags: 0000000000000000
Partition name: 'userdata'
Command (? for help): i
Partition number (1-38): 38
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: BD12CF41-10E7-BBF7-D096-5553B89882E7
First sector: 15269854 (at 7.3 GiB)
Last sector: 30535646 (at 14.6 GiB)
Partition size: 15265793 sectors (7.3 GiB)
Attribute flags: 0000000000000000
Partition name: 'userdatabak'
The information which is needed from the above output is Partition GUID code, First sector, Last sector and Partition name. You can write these somewhere (if your values are different from the above) from where can be pasted easily later (alternatively you can use the scrollback function of the terminal ).
- if you have an SD card make a backup of the partitions layout (in case that something goes wrong):
Code:
Command (? for help): b
Enter backup filename to save: /external_sd/gpt_partitions_table.backup
The operation has completed successfully.
- delete partitions 37 and 38:
Code:
Command (? for help): d
Partition number (1-38): 38
Command (? for help): d
Partition number (1-37): 37
- create a new partition 37, bigger in size with the same (as before) Partition GUID code, and the same (as before) start sector:
Code:
Command (? for help): n
Partition number (37-40, default 37): 37
First sector (34-30535646, default = 5000400) or {+-}size{KMGTP}: 5000400
Last sector (5000400-30535646, default = 30535646) or {+-}size{KMGTP}: 30535546
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
Changed type of partition to 'Unknown'
The difference here is in the last sector of the partition 30535546.
- create a new partition 38 with same Partition GUID code, but with different First sector:
Code:
Command (? for help): n
Partition number (38-40, default 38): 38
First sector (34-30535646, default = 34) or {+-}size{KMGTP}: 30535547
Information: Moved requested sector from 30535547 to 30535548 in
order to align on 2-sector boundaries.
Use 'l' on the experts' menu to adjust alignment
Last sector (30535548-30535646, default = 30535646) or {+-}size{KMGTP}: 30535646
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
Changed type of partition to 'Microsoft basic data'
Please note that here in the output after 'n' the default first sector is 34, so you explicitly must enter the value!!! As can be seen I've entered the next available sector (after partition 37) 305355547 but it has been corrected automatically to 30535548. So you can use directly 30535548 as a start sector. The last sector is at the end of the memory 30535646.
- write the names of the new partitions:
Code:
Command (? for help): c
Partition number (1-38): 37
Enter name: userdata
Command (? for help): c
Partition number (1-38): 38
Enter name: userdatabak
- if you list the partitions again (with 'p') the end of the table should looks like this:
Code:
37 5000400 30535546 12.2 GiB FFFF userdata
38 30535548 30535646 49.5 KiB 0700 userdatabak
- now it is safe to write the changes by pressing 'w':
Code:
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/block/mmcblk0.
The operation has completed successfully.
- resize the file system:
Code:
~ # resize2fs -p /dev/block/mmcblk0p37
resize2fs 1.42.9 (28-Dec-2013)
Please run 'e2fsck -f /dev/block/mmcblk0p37' first.
... hmm ... let's run it:
Code:
~ # e2fsck -f /dev/block/mmcblk0p37
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p37: 12519/321280 files (5.8% non-contiguous), 678615/1283425 blocks
~ # resize2fs -p /dev/block/mmcblk0p37
resize2fs 1.42.9 (28-Dec-2013)
Please run 'e2fsck -f /dev/block/mmcblk0p37' first.
... well the resize2fs have some checks and refuses to resize the file system therefore we must force the execution:
Code:
~ # resize2fs -fp /dev/block/mmcblk0p37
resize2fs 1.42.9 (28-Dec-2013)
Resizing the filesystem on /dev/block/mmcblk0p37 to 3191893 (4k) blocks.
The filesystem on /dev/block/mmcblk0p37 is now 3191893 blocks long.
The device now can be rebooted and its internal memory will be almost 12GB which compared to its previous size is a very nice upgrade. Screenshots before and after the repartitioning can be seen here.
Update (19.09.2015): This is a link to a flashabable zip which can be used from the TWRP to automate the process. Can be used with any TWRP recovery for 6039.
md5sum: c3f685310283bdc00cee5412fa33259c
Just tried it, and it worked like a charm. Thank you very much!
Wow ! Kudos to meghd00t and petrov.0. I just ordered this phone as a backup, waiting for my beloved Xperia Z1 Compact to be saved from watering (medium rain during less than 10min, so long Sony waterproof phones...). Can't wait to receive it and play with this extra storage !! Thank you :victory:
Here i'am, crazy thinking that if the 6039y(Single chip, SDcard and 8Gb) come with 8Gb worth of wasted money, that the 6039j dual chip and 16Gb non-SDCard version may very well come with a SDCard reader hardware worth of wasted money.
It would be like just changing the Chip Support slot thing or whatever...
Can someone support my craziness and post a picture of thi "where the chip stays" of the SDCard reader version of this phone??
Thanks a lot!!
evilinheaven said:
Here i'am, crazy thinking that if the 6039y(Single chip, SDcard and 8Gb) come with 8Gb worth of wasted money, that the 6039j dual chip and 16Gb non-SDCard version may very well come with a SDCard reader hardware worth of wasted money.
It would be like just changing the Chip Support slot thing or whatever...
Can someone support my craziness and post a picture of thi "where the chip stays" of the SDCard reader version of this phone??
Thanks a lot!!
Click to expand...
Click to collapse
Well ... I like crazy things. But is impossible just to add a chip.
The thread itself is for other things. I don't want more reminders from the moderators. So please use the general section next time.
Thank you in advance.
Here is the complete partition list for 8Gb single sim variant:
Code:
Disk /dev/block/mmcblk0: 30535680 sectors, 14.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 40 entries
First usable sector is 34, last usable sector is 30535646
Partitions will be aligned on 2-sector boundaries
Total free space is 256464 sectors (125.2 MiB)
Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 265215 1.5 MiB FFFF tunning
3 265216 267263 1024.0 KiB FFFF traceability
4 267264 267265 1024 bytes FFFF fsc
5 267266 267281 8.0 KiB FFFF ssd
6 267282 268305 512.0 KiB FFFF sbl1
7 268306 269329 512.0 KiB 0700 sbl1bak
8 269330 270353 512.0 KiB FFFF rpm
9 270354 271377 512.0 KiB 0700 rpmbak
10 271378 272401 512.0 KiB FFFF tz
11 272402 273425 512.0 KiB 0700 tzbak
12 273426 274449 512.0 KiB FFFF hyp
13 274450 275473 512.0 KiB 0700 hypbak
14 275474 278545 1.5 MiB FFFF modemst1
15 278546 281617 1.5 MiB FFFF modemst2
16 281618 283665 1024.0 KiB FFFF simlock
17 283666 286737 1.5 MiB FFFF efsdata
18 393216 393279 32.0 KiB FFFF DDR
19 393280 396351 1.5 MiB FFFF fsg
20 396352 396383 16.0 KiB FFFF sec
21 396384 398431 1024.0 KiB FFFF aboot
22 398432 400479 1024.0 KiB 0700 abootbak
23 400480 466015 32.0 MiB FFFF boot
24 466016 531551 32.0 MiB FFFF recovery
25 531552 4306427 1.8 GiB FFFF system
26 4325376 4390911 32.0 MiB FFFF persist
27 4390912 4407295 8.0 MiB FFFF splash
28 4407296 4448255 20.0 MiB 0700 tctpersist
29 4448256 4468735 10.0 MiB 0700 hdcp
30 4468736 4468751 8.0 KiB FFFF fota
31 4468752 4993039 256.0 MiB FFFF cache
32 4993040 4995087 1024.0 KiB FFFF misc
33 4995088 4996111 512.0 KiB FFFF keystore
34 4996112 4996175 32.0 KiB FFFF config
35 4996176 4996303 64.0 KiB FFFF oem
36 4996304 5000399 2.0 MiB FFFF FactoryRP
37 5000400 15269853 4.9 GiB FFFF userdata
38 15269854 30535646 7.3 GiB 0700 userdatabak
Maybe someone can post the list for 16Gb dual sim variant?
Ok, I bit the bullet and resized the "userdata" partition. Only that I did not create the smaller #38 partition, I did not see any reason to do it (if any update tries to store something inside it, will fail anyway; this partition does not look special, all *bak partitions have the same GUID). Plus there isn't any "userdatabak" partition on 16Gb models. Instead I made partition #37 up to the latest available sector (30535646). The phone is working just fine.
rioachim said:
Ok, I bit the bullet and resized the "userdata" partition. Only that I did not create the smaller #38 partition, I did not see any reason to do it (if any update tries to store something inside it, will fail anyway; this partition does not look special, all *bak partitionshave the same GUID). Plus there isn't any "userdatabak" partition on 16Gb models. Instead I made partition #37 up to the latest available sector (30535646). The phone is working just fine.
Click to expand...
Click to collapse
OK. But don't be fulled by the GUID. Most of the bak partitions contain data which is equivalent to the data in the primary ones (aboot, rpm, sbl1 etc.). The data is patched in both partitions with the same patch during an upgrade.
Script to repartition "internal memory"
Hello petrov.0, all
Is it possible to create a shell for all thoses commands ?
In this case if partitions are lost (upgrade, patchs....) we could apply it easily.
And nice discovered.
Regards
Google99
google99 said:
Hello petrov.0, all
Is it possible to create a shell for all thoses commands ?
In this case if partitions are lost (upgrade, patchs....) we could apply it easily.
And nice discovered.
Regards
Google99
Click to expand...
Click to collapse
No it is not:
Code:
GPT fdisk (aka gdisk) is a text-mode menu-driven program for creation and manipulation of partition tables.
Hi petrov.0 great news and thanks.
Just a doubt, a friend of mine will receive Idol 3 4,7" 8 GB tomorrow, he can made OTA update (that I think are available for security reasons as "stagefright" and another I know Alcatel get users a way to set SD as main memory) and then use your guide to expand memory t 16 Gb or for this operation is better been in a fresh unchained device not updated?
Because in this second option device become 16 Gb Rom but will be afected by stagefright and for the rest of his life
Thanks!
Romagnolo1973 said:
Hi petrov.0 great news and thanks.
Just a doubt, a friend of mine will receive Idol 3 4,7" 8 GB tomorrow, he can made OTA update (that I think are available for security reasons as "stagefright" and another I know Alcatel get users a way to set SD as main memory) and then use your guide to expand memory t 16 Gb or for this operation is better been in a fresh unchained device not updated?
Because in this second option device become 16 Gb Rom but will be afected by stagefright and for the rest of his life
Thanks!
Click to expand...
Click to collapse
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).
petrov.0 said:
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).
Click to expand...
Click to collapse
By the way is there any hope (other than getting Alcatel to push an update to put fastboot commands back in, cause is anyone that optimistic?) for people who have indeed updated to recover those?
Sent from my 6039Y using Tapatalk
Rorshan said:
By the way is there any hope (other than getting Alcatel to push an update to put fastboot commands back in, cause is anyone that optimistic?) for people who have indeed updated to recover those?
Sent from my 6039Y using Tapatalk
Click to expand...
Click to collapse
If you find a way to root the device after the update then may be there is a hope.
petrov.0 said:
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).
Click to expand...
Click to collapse
Understood the problem is new update that remove some action from fastboot needed for repartioning. Idol 3 was received and he resize rom from 8 to 16 with no issue with your guide, after that he made OTA update and they are working perfectly, no issue with the new partitioning size and device is working well.
Romagnolo1973 said:
Understood the problem is new update that remove some action from fastboot needed for repartioning. Idol 3 was received and he resize rom from 8 to 16 with no issue with your guide, after that he made OTA update and they are working perfectly, no issue with the new partitioning size and device is working well.
Click to expand...
Click to collapse
Not some but all fastboot commands are removed. Glad to see that you have made it though. The OTA update however is a mistake. Now you can't get root access nor the fastboot commands are available.
petrov.0 said:
Not some but all fastboot commands are removed. Glad to see that you have made it though. The OTA update however is a mistake. Now you can't get root access nor the fastboot commands are available.
Click to expand...
Click to collapse
Yes, it was risky but probably he is not interested in root, I only inform you that new partitioning with OTA is still there, I think is a goodnews and a base to start, now the perfect situation is if Alcatel made a future OTA as soon as possible with fastboot perfectly working.
Romagnolo1973 said:
Yes, it was risky but probably he is not interested in root, I only inform you that new partitioning with OTA is still there, I think is a goodnews and a base to start, now the perfect situation is if Alcatel made a future OTA as soon as possible with fastboot perfectly working.
Click to expand...
Click to collapse
There is nothing wrong with the fastboot commands prior the update. I have doubts that they will be returned. Thanks for the info though (despite that I already know this by looking in the update files). I can't live without root access however therefore there is no option to loose it.
I'm kinda confused here. Are all the steps done from a terminal on the computer or is some of that to be typed inside the TWRP terminal? Because as soon as I boot TWRP with gdisk I get a device not found from typing adb shell. I'm pretty sure I have all the drivers mentioned in the linked post (and even more too). Any kind soul to explain how stupid I am being (because I know that's the solution in the end, I'm a fool)
Rorshan said:
I'm kinda confused here. Are all the steps done from a terminal on the computer or is some of that to be typed inside the TWRP terminal? Because as soon as I boot TWRP with gdisk I get a device not found from typing adb shell. I'm pretty sure I have all the drivers mentioned in the linked post (and even more too). Any kind soul to explain how stupid I am being (because I know that's the solution in the end, I'm a fool)
Click to expand...
Click to collapse
Everything after adb shell must be done directly on the device. The VID & PID of the device are different in the recovery and you don't have the necessary drivers. Try to install the drivers mentioned in the first post (- The Windows users probably need the drivers from this post, for access to the device in recovery mode).

softbrick Fire Tv in EDL/QDLoader 9008 mode

So I've got bricked AFTV 1st gen. It stuck on amazon logo then reboot in to black /grey flickering board .White led blink slowly . ADB via USB A-to-A adapter is not responding. USB keyboard didn't work. Few times It boot to QDLoader 9008 but no to QDLoader 9006 that was described on many occasions . I have downloaded 5.0.5 stock and 5.2.1.2 rooted .Also I did install qualcomm drivers and QFIL tool. Any steps to unbrick this box ?
steps should be like this https://forum.xda-developers.com/go...ualcomm-hs-t3043301/post59154061#post59154061 as I dint found any way to use QFIL . I assume that partition table and rawprogram0.xml will be needed exacly for 5.0.5 firmware .
Found Fire TV partition table
[[email protected]:~]$ sudo gdisk -l /dev/mmcblk0
GPT fdisk (gdisk) version 0.8.10
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/mmcblk0: 15269888 sectors, 7.3 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 20 entries
First usable sector is 34, last usable sector is 15269854
Partitions will be aligned on 2-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 34 16417 8.0 MiB 8300 persist
2 16418 32801 8.0 MiB 8300 goldpersist
3 32802 65569 16.0 MiB 0700 modem
4 65570 65825 128.0 KiB FFFF sbl1
5 65826 66337 256.0 KiB FFFF sbl2
6 66338 67361 512.0 KiB FFFF sbl3
7 67362 68385 512.0 KiB FFFF tz
8 68386 69409 512.0 KiB FFFF rpm
9 69410 71457 1024.0 KiB FFFF aboot
10 71458 91937 10.0 MiB FFFF boot
11 91938 112417 10.0 MiB FFFF recovery
12 112418 177953 32.0 MiB 8300 diag
13 177954 180513 1.2 MiB 8300 splash480p
14 180514 186017 2.7 MiB 8300 splash720p
15 186018 198305 6.0 MiB 8300 splash1080p
16 198306 198321 8.0 KiB FFFF ssd
17 198322 200369 1024.0 KiB FFFF misc
18 200370 1773233 768.0 MiB 8300 system
19 1773234 3346097 768.0 MiB 8300 cache
20 3346098 15269854 5.7 GiB 8300 userdata
Click to expand...
Click to collapse
rawprogram0.xml is missing and need to be created manually . rawprogram0.xml and readable_partition.txt is an example of nexus 5 16GB implementation from above thread
does anyone with rooted 5.0.5 can provide me with files and confirm partition table ? I have some of those files from official 5.0.5 firmware package
I it possible to flash whole flash this way?
Is BoardDiag compatible to the fire TV? What AP Chipset are you going to select? My previous attempts with the software always gave me an error with partition.txt, although I've used a AFTV pt.bin..
Very curious to see the results of your attempts!
Any positive update on your attempts? I've tried so many things already, but unfortunately, I can't achieve any success. So many tutorials for unbricking Qualcomm chips, but so far, I haven't got a single advance with reflashing it or exiting the 9008 state.. :crying:
nicefile said:
steps should be like this https://forum.xda-developers.com/go...ualcomm-hs-t3043301/post59154061#post59154061 as I dint found any way to use QFIL . I assume that partition table and rawprogram0.xml will be needed exacly for 5.0.5 firmware .
Found Fire TV partition table
rawprogram0.xml is missing and need to be created manually . rawprogram0.xml and readable_partition.txt is an example of nexus 5 16GB implementation from above thread
does anyone with rooted 5.0.5 can provide me with files and confirm partition table ? I have some of those files from official 5.0.5 firmware package
I it possible to flash whole flash this way?
Click to expand...
Click to collapse
walkabouts said:
Any positive update on your attempts? I've tried so many things already, but unfortunately, I can't achieve any success. So many tutorials for unbricking Qualcomm chips, but so far, I haven't got a single advance with reflashing it or exiting the 9008 state.. :crying:
Click to expand...
Click to collapse
sorry to resurrect an old thread same here. I am on the same situation. any of you able to successfully recover or no chance of it? off all the devices in youtube and everywhere with unbricking tutorials and QFIL versions the fire tv is the only one missing. :-/
Its nearly 2019, and after all this time, there are - not to my knowledge - any instructions on how to ressucitate the original FTV on a 9008 state... Which is sad, because its still a very competent piece of hardware..
walkabouts said:
Its nearly 2019, and after all this time, there are - not to my knowledge - any instructions on how to ressucitate the original FTV on a 9008 state... Which is sad, because its still a very competent piece of hardware..
Click to expand...
Click to collapse
I've replaced my with stick 4k that can be found for 35Euro here . No need to look back . Also old 1st gen remote works great so don't have pull the plug from kids room

G4 Hard Bricked? QFIL Flash not working

Hi People,
I think I've hard bricked my G4 (H815 International TWN model)
I made a mistake flashing with TWRP after following @steadfasterX brilliant H815 unlock guide. The unlock worked perfectly but I was trying different custom ROMs ended up bricking the phone by flashing a boot image in TWRP.
It is completely dead, no fastboot, no download mode, only black screen. The phone does vibrate when holding power button after inserting battery but nothing happens no USB device when plugged in.
I followed a guide for using QFil to flash my phone. I shorted the test pins and it booted in 9008, I used SteadfasterX's H815 recovery files from another thread (https://forum.xda-developers.com/g4/general/guide-proper-h815-unbrick-qfil-files-t3709212) and flashed device, all goes well and the flash completes, albeit after 3.20min. But once this is done and the phone is restarted I still end up in the same position of no download or fast boot, exactly the same.
Is this a true dead phone or am I doing something wrong in Qfil?
My QFIL log is here:
Code:
Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:Z:\Shared\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Programmer Path:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
Image Search Path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Image Search Path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Image Search Path: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing
RAWPROGRAM file path: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\rawprogram0.xml
PATCH file path:C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\patch0.xml
Programmer Path:C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\prog_emmc_firehose_8992_lite.mbn
FireHose Configuration Cancelled
FireHose Configuration Cancelled
Start Download
Program Path:C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\prog_emmc_firehose_8992_lite.mbn
COM Port number:3
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:3
Sending NOP
FireHose Log: Binary build date: Mar 3 2015 @ 19:29:19
FireHose Log: fh.attrs.Verbose is set to 0
FireHose Log: Chip serial num: 28732866 (0x1b66dc2)
FireHose Log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
FireHose Log: Host's hash buffer size not provided or 0; using 8192
FireHose Log: fh.attrs.MaxPayloadSizeToTargetInBytes > FIREHOSE_CHANNEL_BUFFER_SIZE
FireHose Log: Calling hotplug_poll_device('MMC')
Invalid response NAK
Set TxBuffer 0x2000, RxBuffer 0x1000
Firehose configure packet sent successfully!
ReadBackMode:No_Readback
Disable read back
Total Bytes To Program 0x71316A0
Download Image
PROGRAM: Replace the partition sectors number 0x2b000 to file size in sector 0x2566d
PROGRAM: Partition 0, Sector: 32768, Length: 153197 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\NON-HLOS.bin
FireHose Log: start 32768, num 153197
FireHose Log: Finished sector address 185965
PROGRAM: Written Bytes 0x4acda00 (64)
Program Size: 74.80 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x4a
PROGRAM: Partition 0, Sector: 229376, Length: 74 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\pmic.mbn
FireHose Log: start 229376, num 74
FireHose Log: Finished sector address 229450
PROGRAM: Written Bytes 0x9400 (64)
Program Size: 0.04 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x511
PROGRAM: Partition 0, Sector: 230400, Length: 1297 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\sbl1.mbn
FireHose Log: start 230400, num 1297
FireHose Log: Finished sector address 231697
PROGRAM: Written Bytes 0xa2200 (64)
Program Size: 0.63 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x449
PROGRAM: Partition 0, Sector: 232448, Length: 1097 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\tz.mbn
FireHose Log: start 232448, num 1097
FireHose Log: Finished sector address 233545
PROGRAM: Written Bytes 0x89200 (64)
Program Size: 0.54 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x38
PROGRAM: Partition 0, Sector: 234496, Length: 56 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\sdi.mbn
FireHose Log: start 234496, num 56
FireHose Log: Finished sector address 234552
PROGRAM: Written Bytes 0x7000 (64)
Program Size: 0.03 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0xb9
PROGRAM: Partition 0, Sector: 235520, Length: 185 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\hyp.mbn
FireHose Log: start 235520, num 185
FireHose Log: Finished sector address 235705
PROGRAM: Written Bytes 0x17200 (64)
Program Size: 0.09 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x176
PROGRAM: Partition 0, Sector: 236544, Length: 374 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\rpm.mbn
FireHose Log: start 236544, num 374
FireHose Log: Finished sector address 236918
PROGRAM: Written Bytes 0x2ec00 (64)
Program Size: 0.18 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x487
PROGRAM: Partition 0, Sector: 237568, Length: 1159 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\emmc_appsboot.mbn
FireHose Log: start 237568, num 1159
FireHose Log: Finished sector address 238727
PROGRAM: Written Bytes 0x90e00 (64)
Program Size: 0.57 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x511
PROGRAM: Partition 0, Sector: 241664, Length: 1297 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\sbl1.mbn
FireHose Log: start 241664, num 1297
FireHose Log: Finished sector address 242961
PROGRAM: Written Bytes 0xa2200 (64)
Program Size: 0.63 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x4a
PROGRAM: Partition 0, Sector: 243712, Length: 74 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\pmic.mbn
FireHose Log: start 243712, num 74
FireHose Log: Finished sector address 243786
PROGRAM: Written Bytes 0x9400 (64)
Program Size: 0.04 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x449
PROGRAM: Partition 0, Sector: 244736, Length: 1097 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\tz.mbn
FireHose Log: start 244736, num 1097
FireHose Log: Finished sector address 245833
PROGRAM: Written Bytes 0x89200 (64)
Program Size: 0.54 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0xb9
PROGRAM: Partition 0, Sector: 246784, Length: 185 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\hyp.mbn
FireHose Log: start 246784, num 185
FireHose Log: Finished sector address 246969
PROGRAM: Written Bytes 0x17200 (64)
Program Size: 0.09 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x176
PROGRAM: Partition 0, Sector: 247808, Length: 374 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\rpm.mbn
FireHose Log: start 247808, num 374
FireHose Log: Finished sector address 248182
PROGRAM: Written Bytes 0x2ec00 (64)
Program Size: 0.18 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x487
PROGRAM: Partition 0, Sector: 248832, Length: 1159 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\emmc_appsboot.mbn
FireHose Log: start 248832, num 1159
FireHose Log: Finished sector address 249991
PROGRAM: Written Bytes 0x90e00 (64)
Program Size: 0.57 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x38
PROGRAM: Partition 0, Sector: 252928, Length: 56 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\sdi.mbn
FireHose Log: start 252928, num 56
FireHose Log: Finished sector address 252984
PROGRAM: Written Bytes 0x7000 (64)
Program Size: 0.03 MB
PROGRAM: Replace the partition sectors number 0x18000 to file size in sector 0x1228c
PROGRAM: Partition 0, Sector: 393216, Length: 74380 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\laf.img
FireHose Log: start 393216, num 74380
FireHose Log: Finished sector address 467596
PROGRAM: Written Bytes 0x2451800 (64)
Program Size: 36.32 MB
Total Size: 115.26 MB
Total Time: 201 Seconds
Throughput: 0.57 MB/Seconds
PATCH: Partition 0, Sector: 14, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 14 with 03A3DFDE
PATCH: Partition 0, Sector: 0, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 61071339 with 03A3DFDE
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 1 with 03A3DFDE
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 61071359 with 03A3DFDE
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
FireHose Log: Patched sector 1 with 03A3DFFF
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
FireHose Log: Patched sector 61071359 with 03A3DFFF
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
FireHose Log: Patched sector 61071359 with 03A3DFDF
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,6656)
FireHose Log: crc start sector 2, over bytes 6656
FireHose Log: Patched sector 1 with E5D978C3
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,6656)
FireHose Log: crc start sector 61071327, over bytes 6656
FireHose Log: Patched sector 61071359 with E5D978C3
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
FireHose Log: Patched sector 1 with 00000000
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
FireHose Log: crc start sector 1, over bytes 92
FireHose Log: Patched sector 1 with 775E7F97
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
FireHose Log: Patched sector 61071359 with 00000000
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
FireHose Log: crc start sector 61071359, over bytes 92
FireHose Log: Patched sector 61071359 with CB712F9F
Total download file size: 115.2642MB
Total download time: 3 Min 21 Sec
Throughput: 0.5733199MB/s
Finish Download
Rich Rich said:
Hi People,
I think I've hard bricked my G4 (H815 International TWN model)
I made a mistake flashing with TWRP after following @steadfasterX brilliant H815 unlock guide. The unlock worked perfectly but I was trying different custom ROMs ended up bricking the phone by flashing a boot image in TWRP.
It is completely dead, no fastboot, no download mode, only black screen. The phone does vibrate when holding power button after inserting battery but nothing happens no USB device when plugged in.
I followed a guide for using QFil to flash my phone. I shorted the test pins and it booted in 9008, I used SteadfasterX's H815 recovery files from another thread (https://forum.xda-developers.com/g4/general/guide-proper-h815-unbrick-qfil-files-t3709212) and flashed device, all goes well and the flash completes, albeit after 3.20min. But once this is done and the phone is restarted I still end up in the same position of no download or fast boot, exactly the same.
Is this a true dead phone or am I doing something wrong in Qfil?
My QFIL log is here:
Code:
Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:Z:\Shared\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Programmer Path:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
Image Search Path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Image Search Path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: Z:\Shared\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:Z:\Shared\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Image Search Path: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing
RAWPROGRAM file path: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\rawprogram0.xml
PATCH file path:C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\patch0.xml
Programmer Path:C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\prog_emmc_firehose_8992_lite.mbn
FireHose Configuration Cancelled
FireHose Configuration Cancelled
Start Download
Program Path:C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\prog_emmc_firehose_8992_lite.mbn
COM Port number:3
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:3
Sending NOP
FireHose Log: Binary build date: Mar 3 2015 @ 19:29:19
FireHose Log: fh.attrs.Verbose is set to 0
FireHose Log: Chip serial num: 28732866 (0x1b66dc2)
FireHose Log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
FireHose Log: Host's hash buffer size not provided or 0; using 8192
FireHose Log: fh.attrs.MaxPayloadSizeToTargetInBytes > FIREHOSE_CHANNEL_BUFFER_SIZE
FireHose Log: Calling hotplug_poll_device('MMC')
Invalid response NAK
Set TxBuffer 0x2000, RxBuffer 0x1000
Firehose configure packet sent successfully!
ReadBackMode:No_Readback
Disable read back
Total Bytes To Program 0x71316A0
Download Image
PROGRAM: Replace the partition sectors number 0x2b000 to file size in sector 0x2566d
PROGRAM: Partition 0, Sector: 32768, Length: 153197 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\NON-HLOS.bin
FireHose Log: start 32768, num 153197
FireHose Log: Finished sector address 185965
PROGRAM: Written Bytes 0x4acda00 (64)
Program Size: 74.80 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x4a
PROGRAM: Partition 0, Sector: 229376, Length: 74 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\pmic.mbn
FireHose Log: start 229376, num 74
FireHose Log: Finished sector address 229450
PROGRAM: Written Bytes 0x9400 (64)
Program Size: 0.04 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x511
PROGRAM: Partition 0, Sector: 230400, Length: 1297 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\sbl1.mbn
FireHose Log: start 230400, num 1297
FireHose Log: Finished sector address 231697
PROGRAM: Written Bytes 0xa2200 (64)
Program Size: 0.63 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x449
PROGRAM: Partition 0, Sector: 232448, Length: 1097 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\tz.mbn
FireHose Log: start 232448, num 1097
FireHose Log: Finished sector address 233545
PROGRAM: Written Bytes 0x89200 (64)
Program Size: 0.54 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x38
PROGRAM: Partition 0, Sector: 234496, Length: 56 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\sdi.mbn
FireHose Log: start 234496, num 56
FireHose Log: Finished sector address 234552
PROGRAM: Written Bytes 0x7000 (64)
Program Size: 0.03 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0xb9
PROGRAM: Partition 0, Sector: 235520, Length: 185 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\hyp.mbn
FireHose Log: start 235520, num 185
FireHose Log: Finished sector address 235705
PROGRAM: Written Bytes 0x17200 (64)
Program Size: 0.09 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x176
PROGRAM: Partition 0, Sector: 236544, Length: 374 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\rpm.mbn
FireHose Log: start 236544, num 374
FireHose Log: Finished sector address 236918
PROGRAM: Written Bytes 0x2ec00 (64)
Program Size: 0.18 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x487
PROGRAM: Partition 0, Sector: 237568, Length: 1159 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\emmc_appsboot.mbn
FireHose Log: start 237568, num 1159
FireHose Log: Finished sector address 238727
PROGRAM: Written Bytes 0x90e00 (64)
Program Size: 0.57 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x511
PROGRAM: Partition 0, Sector: 241664, Length: 1297 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\sbl1.mbn
FireHose Log: start 241664, num 1297
FireHose Log: Finished sector address 242961
PROGRAM: Written Bytes 0xa2200 (64)
Program Size: 0.63 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x4a
PROGRAM: Partition 0, Sector: 243712, Length: 74 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\pmic.mbn
FireHose Log: start 243712, num 74
FireHose Log: Finished sector address 243786
PROGRAM: Written Bytes 0x9400 (64)
Program Size: 0.04 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x449
PROGRAM: Partition 0, Sector: 244736, Length: 1097 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\tz.mbn
FireHose Log: start 244736, num 1097
FireHose Log: Finished sector address 245833
PROGRAM: Written Bytes 0x89200 (64)
Program Size: 0.54 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0xb9
PROGRAM: Partition 0, Sector: 246784, Length: 185 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\hyp.mbn
FireHose Log: start 246784, num 185
FireHose Log: Finished sector address 246969
PROGRAM: Written Bytes 0x17200 (64)
Program Size: 0.09 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x176
PROGRAM: Partition 0, Sector: 247808, Length: 374 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\rpm.mbn
FireHose Log: start 247808, num 374
FireHose Log: Finished sector address 248182
PROGRAM: Written Bytes 0x2ec00 (64)
Program Size: 0.18 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x487
PROGRAM: Partition 0, Sector: 248832, Length: 1159 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\emmc_appsboot.mbn
FireHose Log: start 248832, num 1159
FireHose Log: Finished sector address 249991
PROGRAM: Written Bytes 0x90e00 (64)
Program Size: 0.57 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x38
PROGRAM: Partition 0, Sector: 252928, Length: 56 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\sdi.mbn
FireHose Log: start 252928, num 56
FireHose Log: Finished sector address 252984
PROGRAM: Written Bytes 0x7000 (64)
Program Size: 0.03 MB
PROGRAM: Replace the partition sectors number 0x18000 to file size in sector 0x1228c
PROGRAM: Partition 0, Sector: 393216, Length: 74380 Sectors, Sector Size: 512 Bytes
File: C:\Documents and Settings\Administrator\Desktop\h815_full_working\flashing\laf.img
FireHose Log: start 393216, num 74380
FireHose Log: Finished sector address 467596
PROGRAM: Written Bytes 0x2451800 (64)
Program Size: 36.32 MB
Total Size: 115.26 MB
Total Time: 201 Seconds
Throughput: 0.57 MB/Seconds
PATCH: Partition 0, Sector: 14, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 14 with 03A3DFDE
PATCH: Partition 0, Sector: 0, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 61071339 with 03A3DFDE
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 1 with 03A3DFDE
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 61071359 with 03A3DFDE
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
FireHose Log: Patched sector 1 with 03A3DFFF
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
FireHose Log: Patched sector 61071359 with 03A3DFFF
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
FireHose Log: Patched sector 61071359 with 03A3DFDF
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,6656)
FireHose Log: crc start sector 2, over bytes 6656
FireHose Log: Patched sector 1 with E5D978C3
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,6656)
FireHose Log: crc start sector 61071327, over bytes 6656
FireHose Log: Patched sector 61071359 with E5D978C3
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
FireHose Log: Patched sector 1 with 00000000
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
FireHose Log: crc start sector 1, over bytes 92
FireHose Log: Patched sector 1 with 775E7F97
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
FireHose Log: Patched sector 61071359 with 00000000
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
FireHose Log: crc start sector 61071359, over bytes 92
FireHose Log: Patched sector 61071359 with CB712F9F
Total download file size: 115.2642MB
Total download time: 3 Min 21 Sec
Throughput: 0.5733199MB/s
Finish Download
Click to expand...
Click to collapse
yea..
consider to read the UsU FAQ and the UsU OP Limitations.. in particular: FAQ #23) I wanna / I have flashed with QFIL. Is/Was that a good idea? in the UsU thread
but hey.. you asked the god of G4 unbricking right ? (lol.... JK!)
.... ok so what you CAN do in the current state is:
in the QFIL folder: replace the file emmc_appsboot.mbn with the file aboot_UsU.img of the UsU unlock zip.
flash with QFIL again afterwards (bridge the 2 pins) and you should be back to life
to be fully UsU'd again you need to flash the files as well afterwards:
Code:
fastboot flash raw_resources rawres_UsU.img
fastboot flash laf laf_UsU.img
For anyone else reading the above: DO NOT FOLLOW THAT GUIDE IF YOU HAVE NOT UsU'd A H815 device!
... or you will damage your device permanently.
-
steadfasterX said:
yea..
consider to read the UsU FAQ and the UsU OP Limitations.. in particular: FAQ #23) I wanna / I have flashed with QFIL. Is/Was that a good idea? in the UsU thread
but hey.. you asked the god of G4 unbricking right ? (lol.... JK!)
.... ok so what you CAN do in the current state is:
in the QFIL folder: replace the file emmc_appsboot.mbn with the file aboot_UsU.img of the UsU unlock zip.
flash with QFIL again afterwards (bridge the 2 pins) and you should be back to life
to be fully UsU'd again you need to flash the files as well afterwards:
Code:
fastboot flash raw_resources rawres_UsU.img
fastboot flash laf laf_UsU.img
For anyone else reading the above: DO NOT FOLLOW THAT GUIDE IF YOU HAVE NOT UsU'd A H815 device!
... or you will damage your device permanently.
-
Click to expand...
Click to collapse
Thank you!! Worked perfectly. Right back into TWRP.
I still have an issue when trying to flash a custom ROM though. It comes up with the screen in the attachment, seems my device ID is corrupt somewhere.
Also when in download mode it doesnt appear as a usb device in windows for LGUP flashing.
Rich Rich said:
Thank you!! Worked perfectly. Right back into TWRP.
I still have an issue when trying to flash a custom ROM though. It comes up with the screen in the attachment, seems my device ID is corrupt somewhere.
Also when in download mode it doesnt appear as a usb device in windows for LGUP flashing.
Click to expand...
Click to collapse
that happens as you ignored the fastboot commands in the above guide..
-.
steadfasterX said:
that happens as you ignored the fastboot commands in the above guide..
-.
Click to expand...
Click to collapse
Thanks for the help. It's all up and running now, sent you a little donation for putting up with my stupid mistakes :silly:
Flashed CypherOS but it's laggy so I'll give HROM a try.
@steadfasterX
So I've spotted your post about UsU Cypher OS and tried installed that. I flash the modem, wipe, then the ROM and it fails to boot (green screen during boot).
I'm guessing that somewhere down the line with flashing I've ended up with a non-MM bootloader so tried step 20 in your FAQ for flashing MM bootloader using files extracted with SALT.
When i flash all the files and reboot I end up back in 9008 and have to reflash with QFIL. Where am I going wrong here?
EDIT: It's working now. I re-downloaded and flashed again and it boots!

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?

Categories

Resources