Develop Bugs

Need help with fixing IR Beam in my Rom

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

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

[Q] UnBricking the Hard brick with QPST?

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?

SD mount issues

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

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

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

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

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

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

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

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!