You need a specific hex file and a boot image callied 8???_msimage.mbn
I don't know the contents of the .ta files but I doubt they will be the ones for this purpose.
For further info I've documented the whole research and dev part in my shv debrick thread, this explains what and why you need the hex files.
Sent from my SHV-E160L using Tapatalk 2
Device Info: P9070 Pantech Burst-- Networked Unlocked/Rooted--USA
Rom: CWR Mod Touch 6.0.x.x -- Gizmolord 4.0
Status: "QLOAD" -- bricked --
I want to contribute wiithout becoming a burden. I worked long, hard, and failed, to produce the dump information from my device due to my lack of expierence with linux. I appreciate your help.
Thank you for your time and consideration.
- list of files needed to be shared/ (if not all of them)
- basics of installing brixfix/(anyprogram) witin ubuntu/linux for file dumps
- any suggestions on how else I may be able to help
Can any one show me how to enter download mode again or qdloadmode
Cause After i flash full E160k firmware to my i717m then a can't enter download mode again
My phone screen now is blank
bust device till turn on and my pc recognize that 1 mtp samsung device and 1 samsung usb modem device
Did you make or found backup of working bootloader?
As I understand it, someone with a working xt907 runs the script, which dumps a section of internal storage containing the required file. This is then sent to darkspr1te for analysis/trimming. Or maybe the script can figure it out, I don't remember. Anyway you then get two files, one of which you need to run through hex2bin. Once that's done, you can upload them with qdloader and hopefully have a working phone. I'll check out the backup script and report back soon. As far as my old one is concerned, I wasn't able to find a working image for it. I should be able to get the required stuff off this one though.
Never lose hope
Edit: Just tried running the backup script. Got this python error:
Traceback (most recent call last):
File "..\getpartbin.py", line 53, in <module>
File "..\getpartbin.py", line 16, in mbr
partition = dict(zip(('boot', 'id', 'start', 'size'), unpack('4I', buf)))
struct.error: unpack requires a string argument of length 16
What'd I break?
edit2: Here's what backup.bat gave me. Although getpartbin.py didn't work, maybe something can be figured out with this?
By dakrspr1te ========Doc=V=1====
Thanks To :-
E:V:A, SLS, JCSullins(Rootz Wiki), Adam Outler, many more, sorry if i've missed you out.
Warning, Although i've tested this tool many times on my own devices, it always has the potential to damage both computer & cell phone device, YOU HAVE BEEN WARNED!!!!
This tool is designed to repair SHV-E160L Korean Galaxy Note 1 based on the MSM8660 & MDM9600 Qualcomm Chips
It Only works with devices that are stuck in QDLOAD mode or 05c6:9008 as the PID/VID
It uses Tool/info Written By Others as well as myself.
qdload - http://github.com/jcsullins/qdloader
getpartbin.py - http://blog.csdn.net/su_ky/article/details/7773273
hex2bin - hex2bin.sourceforge.net
connect Qualcomm based device to usb port on linux PC, not tested under windows via USB redirection,
on command line run
Follow on screen instructions, tool will detect device in QDLOAD mode (05c6:9008) and switch to DMSS protocol, upload a hex (converted to bin for this purpose)
the hex is then executed and the device switches to Streaming Protocol, at this point we write a .mbn file to the internal emmc chip, at the end of the emmc write process the device then reboots
after the reboot re-running brixfix with detect the device in the second stage for repair , the device's emmc is accssable as a sd-card, we then write back the damaged parts of the bootchain,
at a minimum you must write a new partition table or the device will always boot in sd-card mode, WARNING, failure to write the rest of the boot chain could leave your device in a situation
which give only black-screen, no usb enumeration, dead. The only way around that is jtag, or finding the Boot resistor which switches the device back to QDLOAD mode, or emergency boot.
goto http://forum.xda-developers.com/showthread.php?t=1914359 for further details.
Come give me thanks on XDA if this tool helped you
Additional Tools (DEV Level)
getpartbin.py - A tool for backing up the primary partition & extended parition tables and combines them into a writable parition0.bin file (python)
qdload.pl - A tool for talking in the HDLC framed DMSS & Streaming Protocol's used by Qualcomm (Perl)
switchmode.sh - A executes qdload.pl for msm8660 device upload
get-part.sh - **DEV** unfinished tool by darkspr1te for creating partition tables in sfdisk format and .csv format (to be used in the future to create parition0.bin plus more automated collection)
tools/ - Folder containing armv5 (arm7 compatible) tools for parition manipulation and data collection
SHV-E160L-16GB/ - Folder contain SHV-E160L bootloaders & pit file
ADB/ - Folder containing adb programs
extras/ - Folder containing odin and clock work mode recovery installers for 160l devices
QUALCOMM/ - Windows drivers (For QPST, Not required in linux, included for backwards compatability with older guides)
hex2bin - convert your xxxxMPRG.hex file to bin for use with qdload
I will accept brick qualcomm devices for developing further debricks. pm me via XDA Forums
It is possible, this tool makes use of the fact that these devices revert to dev board mode under certain conditions. There are major changes when it comes to partition layouts thought. But the principle remains the same, the hex file allows the CPU to start up in a way that you can then write to the emmc, once the .mbn/sdcard mode files are written you can then rewrite your factory partition.
It is still very much a work around though, some users are getting "cookie not received" errors which we still don't 100% know what it means, top answer are,
1. Not a signed hex, CPU rejects it
2. Damaged emmc, could be kernel wipe bug or true failure of emmc
3. Additional commands are required for further function.
Can I also ask that users that do have a hex file and associated files for the phone, please post what you have, further dissection of the files does assist in learning about how these devices run, e.g I learned everything from the 8960 docs and files before the 8660 files came about.
Also there are a few ports of this programs floating around, but none have been posted for others to research into.
Not to be confused with sister projects like HP touchpad debrick, my debrick contains code from that project and vice versa.
It has also come to light that it may be possible to run a hex from a similar device, but this is not yet confirmed.
I no longer have my Qualcomm device so I have not continued the research , if I get another one then I will.
Sent from my A210 using Tapatalk HD
Could someone help with APQ8064T hard bricked device (e980) please? I have one bricked and another fully operational phone, so all information needed can be extracted from the working phone.
All possible HEX files I found could not help me to put the device into SDCARD mode. I started thinking that digging into Qualcomm chip specs for a way to boot the device from external SD-card would be more productive...