[X]Assistant

[vaalf]

The level of complexity of the topic: very difficult

A WARNING!!
IF YOU DO NOT UNDERSTAND THE RISK LEVEL AND THE MECHANISM OF OPERATED UTILITIES
- THAT YOU ARE BETTERDO NOT USEMATERIALS OF THIS TOPIC
--- because instead of recovery - you can MORE MORE KILL YOUR DEVICE
(and in this case, you better give the device to those who are more knowledgeable in these matters)

Before asking questions

1. need to studybasic concepts (at least): in the cap "Terms (definitions)"(all) +" General theory "(release "a bit old", but gives a general idea);
++ "Ideally" - to deal with the "Listopenquestions "
2. provide "absolute minimum" necessary info ("rules of the topic"):

1. links to//savagemessiahzine.com/ devdb /(description of the device) and the theme of the firmware (/ discussion) of the device onsavagemessiahzine.com
2. [under the spoiler!] info about internal sections memory - (preferably - with the size of the sections) (example); maybe ask / get in the subject of your device
3. [under the spoiler!] USB VID / PID of the machinein all combinations of buttons / battery: check all options
   
4. [under the spoiler!] what was done with the device before it was in such a state? What was tried out of the methods / approaches given in the topic? (in detail! )
   
5. [under the spoiler!] conclusionqblinfoone of the loaders (/ programmer) - with firmware (/ dump). (what for, another example of output )
   
6. How many hours on (native?) charge was the device before the diagnosis?(Flcb?); preferably also battery charge level (mV / mA)?
   
7. on how many PCs (/ what OS) was the diagnosis performed?
   
8. [under the spoiler!] own considerations / assumptions (/ doubts (/ questions)) regarding possible solutions

in the absence of an "absolute minimum" of the necessary info - message will be deleted.

PS: if you do not have the opportunity / desire to provide information on all the points above, but there is a desire to get advice from the participants of this topic - formulate the question in the subject of your device, and here - just a link to the corresponding. post in the subject of your device;
If any of the participants in this topic have the opportunity / desire, then you will receive an answer in the subject of your device
Zyy: (recommended) -How to ask questions?

call for compiling a table of correspondence between models of chipsets and equipment manufacturers to identifiers in certificates

how and what to do (for example, SBL *) , what already is ; + also:

[email protected], 02:27

The qblinfo utility is officially added to qtools.
Now the current build version for Windows can always be downloaded bythis link.

=====================
qfpr2 - script to get the contents of QFUSES

[email protected], 00:51

So far, only for one "type" of platforms - the 2nd, according to my classification. This includes, for example, MSM8x10, MSM8x26, MSM8962, MSM8974, MSM8x92, MSM8994, APQ8084, MDM9x25, MDM9x35. This class is characterized by PBL work in the Sahara, IRAM addresses 0xf8xxxxxx.

[email protected], 00:51

I suggest that all owners of devices on platforms of this type run this script and post the resulting out.txt with an indication of the model of the device.
In addition to the "theoretical" benefits in terms of the development of the platform, this should help in solving the practical problem of selecting loaders.

=====================

• Objective: "to help seekers on the difficult path to restore bricks at Qualcomm"
  The main focus of the topic will be on the "latest versions" of SoC - MSM (/ APQ) 8x ** on eMMC,
  but since “general principles” - it will probably be useful for other SoC series (MDM (/ QSD) 7x ** on NAND (/ MTD)

Tasks

• to collect and systematize ("bring to a" user-friendly "form) general terminology and definitions
  
• systematize and find common methodological principles and approaches to recovery
  
• ...
  
• assemble working sets ("cases") of brick restoration at Qualcomm
  
• ...
  
• to develop standard recommendations for the compilation of "recovery cases" of Qualcomm devices for which there are no ready-made cases
  

____________

"Listopenquestions "

this is probably the most important section of the topic (after "Terms (definitions)" + "General theory")

• Is it possible to "assemble yourself" (for example, in a HEX editor) "boot" (* msi_image.mbn) from dumps (dd) respectively. partitions (sbl1 (/ 2 (/ 3)) + tz (/ + hyp)) from the working machine?see Answers
  
• Why to translate from 9008 to 9006 you need to flash the entire chain of loaders? (after all, they are being re-flashed once again when uploading the full firmware (/ dump of partitions) to 9006)?see Answers
  
• What are cookies (magic numbers) and why are they "generally" needed ("what is their meaning")?see Answers
  
• On all qualcomm devices, the method of "starting the boot of the device from the" External SD card "(1, 2) "in the 9008th mode ??depends on the values ​​in QFUSES
  
• ..
  

Answers

• answersSW. vvevvevve, : thank_you: - better to start from here - and further on the topic (minimum 2 pages)
  
• Is it possible to use the same programmer (xPRG ****. Hex (/ mbn))ondifferent devices but with the same SoC? answer1
  
• ...
  

_____________

PS: if after the "Answers" you still have "questions" - then before "restoring something":
or read the whole topic again
or give the device to restore those who are more knowledgeable in these matters

Motive

Motive (prehistory) + archive versions of the caps
__________________

Terms (definitions)

(will be replenished)
to be able to "carry on a dialogue" - the "common" definitions of "what is what"

• "brick"
  
• bootloader (bootloader)
  
• Secure Boot (Trusted Boot)
  
• Programmer (flasher) xPRG ****. Hex (/.mbn)
  
• **** _ msimage.mbn ("boot")
  
• Test Point
  

additionally:
Abbreviations
USB Vendor IDs:http: //developer.andro.../device.html#VendorIds

_________

General theory

"Think like .." - in this case Qualcomm))
--- i.e. you need to understand the "logic of thinking" ("look at questions from the point of view") of the SoC manufacturer ...

General features of Qualcomm architecture
Qualcomm download process
States in which can "is" apparatus
How to determine the status of the device
Protocols of work with the device
General "process architecture" recovery
For information....(by VVitaly, : thank_you :)
features of loading devices on a NAND flash drive(by vvevvevve, : thank_you :)
If SB does not work, then the main criterion is the "proximity" of platform generations.
A selection of all known signed programmers

____________

"literature" and related notes

prefab 1 ( "in the original theme" )
prefab 2

----------------
"interesting notes" (about fastboot) + "continuation"
nv parameter responsible for microphone amplification(by = S =, : thank_you :)

==========
eMMC controller has switched to read-only mode:
General principles for restoring bootloaders to Qualcomm (Post acdev # 42655190)
+ ReadOnly on SD cards

PS: in the "last resort" - you can try to search andorder a memory (emmc chip) in china ...
==========
o IMEI:
General principles for restoring bootloaders to Qualcomm (Post kestua # 38839099)
General principles of restoring bootloaders on Qualcomm (Post = S = # 38869956)

Backup IMEI from QPST to Qualcomm Snapdragon 616:Xiaomi Redmi 3 - Official firmware MIUI 7 (OS 5.1.1) (Post purler # 48189506)

bootloader from source based on CAF - you can build! :General principles for restoring bootloaders to Qualcomm (Post S-trace # 48897765)

Big base of jtag pinouts formost smartphone modelsthank Vladimirs77,
General principles for restoring bootloaders to Qualcomm (Post Vladimirs77 # 50087863)

==========

USB Vendor IDs:http: //developer.andro.../device.html#VendorIds
OEM Drivers:http: //developer.andro..s/oem-usb.html#Drivers
Google USB Driver:http://developer.android.com/sdk/win-usb.html
Attention!! Regarding "Relink HS-USB QD Loader 9008 (COM *)":

Acdev @ 02.26.2016, 14:45

screw driver RELINK kosyachit and it must be removed.
For the place it is necessary to put Google or from the vendor.

+ QDLoader HS-USB Driver 32-64 bit
+ moreQualcomm HS-USB QDLoader 9008 driver for Windows x64 // x86
==========
How to generate the **** _ msimage.mbn (as an example; on Windows using QPST (emmcswdownload.exe))
General principles of restoring bootloaders on Qualcomm (Post wladimir_tm # 43253768)

====
Bootloader LuminesCollection of official firmware

Restore from the Hard Brick (9008) mode of the Nokia Lumia 525 (RM-998) smartphone.

UFS standards (Universal Flash Storage) - thank Kramar111,

About transferring phones to SD 650 to EDL by shorting USB D + to ground
Information, datasheets and schemes msm 8916
____________

"Ready recovery cases"

MSM7225A (HTC Desire C)
General principles of restoring bootloaders on Qualcomm (Post -Zhuk- # 50174000)
...
Qualcomm Snapdragon 200 MSM8612:
Lenovo A785e (China Telecom)General principles for restoring bootloaders to Qualcomm (Post grass7 # 41425745)

===
Qualcomm Snapdragon 400 MSM8228:
General principles of restoring bootloaders on Qualcomm (Post vvevvevve # 40862977)

===
Qualcomm Snapdragon S4 Pro APQ8064:
ZTE Nubia Z5 (NX501)

===
Qualcomm Snapdragon 800 MSM8974:
Lenovo K910SS
LG G2 + savagemessiahzine.com: (Post kestua # 39298647) (LG G2 - Unbrick)

===
Qualcomm Snapdragon 801 MSM8974AB:
ZTE Grand S II:Restore bricks! Method number 2! Repair IMEI!

Qualcomm Snapdragon 801 MSM8974AC v3:
Moto X Gen2 General principles for restoring bootloaders to Qualcomm (Post S5610_best # 50312537)

===
Qualcomm Snapdragon 805 MSM8084:
Unbrick Motorola Droid Turbo
===
Qualcomm Snapdragon S4 Pro APQ8064
Recovery Instructions Sony Xperia Z C6602 / C6603 / C6606 / C6616
===
HTC Desire X-Qualcomm Snapdragon S4 Play MSM8225
General principles of restoring bootloaders on Qualcomm (Post kestua # 71541490)
===
Qualcomm Snapdragon 430 MSM8937 (Honor 7C)
Instructions for firmware Board, raising bricks

___________

Utilities

QC-Privided:

QPST v2.7.474 + QFIL 2.0.1.9

QPST:

current QPST versions from the network (QPST2.7.422-437) - thanks! peter23,
General principles of restoring bootloaders on Qualcomm (Post peter23 # 50215409)

QPST.2.7.422 (qcom_Upgrade_Tool_20140422)


QFIL:
lenovo-forums.ru


______

OEM Provided

Miflash (Miphone / MIUI ROM Flashing Tool):
official page with manual (EN): Download MIUI ROM Flashing Tool (alwayslatestversion + xiaomi ROMs):http://en.miui.com/a-234.html

Malchik-solnce @ 01/27/2014, 6:30 PM

... Drivers / Utilities / Add-ons ->MiFlash
Download - MiPhone2.11.6 (Option 1)
Download - MiPhone20131108 (Option 2)
Download - MiPhone20140509 (Option 3)

MiPhone20141107:http: //bigota.d.miui.c...ls/MiPhone20141107.exe
MiPhone2015731 @savagemessiahzine.com: General principles of restoring bootloaders on Qualcomm (Post wladimir_tm # 42794251)
MiFlash 2016.03.30.0 (64bit)
MiFlash 2016.04.01.0 (64it)

QFIL (via Lenovo):
lenovo-forums.ru

utilities for working with IMEI -thankSW. ariafan link and uv. acdev, link


______

DEV-Provided

USBlyser:

Version: 2.1
Released: March 16, 2014
Size: 3,9 Mb
Limitations: Fully functional 33-day trial

[email protected], 22:41

If you want to understand seriously, then install and run a sniffer on this port - for example, USBlyzer, and post a log of such an attempt in QFIL.
Yes, when using USBlyser, you need in the settings: Capture - Capture Settings - URB Transfer Buffer Size Limit to set the maximum allowable value for your version of the program.

HEX automatic conversion file of gpt.bin values ​​(obtained dd if = / dev / block / mmcblk0 of = / sdcard / gpt.bin bs = 8 count = 2176) into text content rawprogram0.xmlexcel tools - thank Bazzz2,

qtools project:
github, General principles of restoring bootloaders on Qualcomm (Post vvevvevve # 40306059)
++ qblinfo how and what to do (for example, SBL *)

DFS Professional CDMA Tool:
http://cdmatool.com
General principles of restoring bootloaders on Qualcomm (Post Olezhek1975 # 38804787)
General principles of restoring bootloaders on Qualcomm (Post wladimir_tm # 38808958)

NV-items_reader_writer:
[TOOL / GUIDE] Full NV Backup and Restore [SIMPLE] [08-03-2012]
+ example of instructions for working in the program


recovery script for collecting the partitions info (mmcblk0info.sh/zip):
http: //forum.xda-devel...=56569542&postcount=71

EFS Professional:
http: //forum.xda-devel…-professional-t1308546

Brixfix:
http: //forum.xda-devel...owthread.php? t = 2136738

eMMC RAW Tool @savagemessiahzine.com: eMMC RAW Tool

boot-unlocker-gnex:General principles for restoring boot loaders to Qualcomm (Post nerwin # 40222279)

https://code.google.com/p/boot-unlocker-gnex/
BootUnlocker for Nexus Devices - Unlock your bootloader without fastboot.
This application REQUIRES a Galaxy Nexus (maguro, toro or toroplus), Nexus 4 (mako), Nexus 5 (hammerhead), Nexus 7 2013 (deb or flo), Nexus 10 (manta), or OnePlus One (bacon / A0001), with root.

Qualcomm Firmware Toolby vin2809

В®Partitions Backup & RestoreSome screenshots to explain the process:В®Partitions Backup & Restore (Post aleha81 # 39380773)
Partitions Backup & Restore v1.6.0 RUS- thank htc 600,

aureljared / unbrick_8960:https://github.com/aureljared/unbrick_8960

WriteDualIMEI utility (W + G_eMMC)ARK Benefit A3 - Official firmware

Maud. fastboot.exe, which "can" send the "reboot-edl" command to the bootloader "directly" (without the "oem" prefix)) - using the "fastboot_edl reboot-edl" command line;
thank emusic General principles of restoring bootloaders on Qualcomm (Post emusic # 50224890)


emmcdl:
thank peter23, "for the find" :)
Visible support for firehose, visible ability to read a USB flash drive from the phone, and not just write (first of all, this is interesting).
General principles of restoring bootloaders on Qualcomm (Post peter23 # 50287938)

+ Found a more recent version 2.15General principles of restoring bootloaders on Qualcomm (Post peter23 # 50314988)

a set of batch files for automated read / write sections via emmcdl - thanks emusic
General principles of restoring bootloaders on Qualcomm (Post emusic # 50332273)


______

______

Instructions

full dump flash drives:
* how to remove a full dump flash drive if there is no slot for an SD card + universal and platform-independent - script: thank_you: vvevvevve,
* and simpler (but "not guaranteed") General principles of restoring bootloaders on Qualcomm (Post wladimir_tm # 41497005)
* on habrahabr.ru: link to instructionsGeneral principles of restoring bootloaders on Qualcomm (Post Olezhek1975 # 43247628)
--------------
** "right on the (live) device" to make a "recovery SD"

"even on WinXP" - you need to "disable signature verification" drivers: thank_you: Magnat.mg

first 100MB backup (using app "Partitions Backup & Restore") General principles of restoring bootloaders on Qualcomm (Post wladimir_tm # 41429130)

Resistance for finding test points (resistor 75-100 ohm)

"instructions in pictures": QFIL Backup and restore EFS:Lenovo S90 - Firmwares (OS 4.4.4 - 5.X.X) (Post MATVE # 40689013)

Repair IMEI via qpstHighscreen Omega Prime Mini - Discussion General principles of recovery loaders on Qualcomm

"example" (read context):Translation instructions from Xiaomi.eu, adapted for increasing the section / data to 6 gigs (using parted)

"example" on the firmware using MiFlash:

Possible problems and solutions when working with MiFlash and Fastboot Mi3-W
http: // invalid link / faq / miflash /
Another interesting point, described by akzhol_b
PS: if there are no files, then you can "do not fill them";

example commands - to "see sections"

[GUIDE] How to make a backup of your computer without sdcard

approximate example:(Windows + VMWare Ubuntu) recovery chain loaders (from state 9006) (+ UBUNTU VMWARE IMAGES
orubuntu-14-04-1-lts-trusty-tahr-desktop-64-bit

as with Miflash (in "9008th mode") - you can flash "only selected partitions" + "dummy.img" = a good example of "dummy img-image"
______

Cap updates

================================
================================
== 4copying ==

absolute minimum CODE

in the header: [B] [URL = //savagemessiahzine.com/forum/index.php?showtopic=643084#aminimal animal "absolute minimum" required info: [/ url] [/ b]

version archive caps
================================
================================

20161108
About transferring phones to SD 650 to EDL by shorting USB D + to ground

20160915
fornewbiesin the subject:
A prerequisite for writing messages in this topic is: provide the "absolute minimum" of the necessary info for your device.
if it is not clear how to get this:
1. immediately look for a normal SC ("service center")
2. contact the appropriate forum section (=Tehnotrepalka)
PS: in case of non-fulfillment of this condition - messages of newcomers will be deleted (and of course - left unanswered)

If you do not have the opportunity / desire to provide information on all the points above, but there is a desire to get advice from the participants of this topic - formulate the question in the subject of your device, and here - just a link to the corresponding. post in the subject of your device;
if any of the participants of this topic have the opportunity / desire - then you will receive an answer in the subject of your device [/ i]

20160902
UFS standards (Universal Flash Storage) - thank Kramar111,

20160624

"absolute minimum" necessary info: [/ b] [background] [list = 1] [*] links to//savagemessiahzine.com/ devdb /(description of the device) and the theme of the firmware (/ discussion) of the device onsavagemessiahzine.com [*][under the spoiler!] info about internal affairs memory - with the size of sections (example)
PS: if you do not have the opportunity / desire to provide information on all the points above, but there is a desire to get advice from the participants of this topic - formulate the question in the subject of your device, and here - just a link to the corresponding. post in the subject of your device;
If any of the participants in this topic have the opportunity / desire, then you will receive an answer in the subject of your device

[*]If you do not have the opportunity / desire to provide information on all the points above, but there is a desire to get advice (possibly) from the participant of this topic - state your question in the subject of your device, and in this topic - only a link to the corresponding. post in the subject of your device;
If any of the participants in this topic have the opportunity / desire, then you will be answered in the subject of your device

20160612
a set of batch files for automated read / write sections via emmcdl - thanks emusic
General principles of restoring bootloaders on Qualcomm (Post emusic # 50332273)

20160611
change
"absolute minimum" required info
p.5<->p.1

Moto X Gen2(Snapdragon 801 MSM8974AC v3 / Krait 400)General principles for restoring bootloaders to Qualcomm (Post S5610_best # 50312537)

emmcdl:
thank peter23, "for the find" :)
Visible support for firehose, visible ability to read a USB flash drive from the phone, and not just write (first of all, this is interesting).
General principles of restoring bootloaders on Qualcomm (Post peter23 # 50287938)
+ Found a more recent version 2.15General principles of restoring bootloaders on Qualcomm (Post peter23 # 50314988)

20160609
Archive updates caps

MSM7225A (HTC Desire C)
General principles of restoring bootloaders on Qualcomm (Post -Zhuk- # 50174000)

Big base of jtag pinouts formost smartphone modelsthank Vladimirs77,
General principles for restoring bootloaders to Qualcomm (Post Vladimirs77 # 50087863)


Maud. fastboot.exe, which "can" send the "reboot-edl" command to the bootloader "directly" (without the "oem" prefix)) - using the "fastboot_edl reboot-edl" command line;
thank emusic General principles of restoring bootloaders on Qualcomm (Post emusic # 50224890)

20160608
current QPST versions from the network (QPST2.7.422-437) - thanks! peter23,
General principles of restoring bootloaders on Qualcomm (Post peter23 # 50215409)

20160524
MiFlash 2016.04.01.0 (64it)
Restore from the Hard Brick (9008) mode of the Nokia Lumia 525 (RM-998) smartphone.

utilities for working with IMEI -thankSW. ariafan link and uv. acdev, link

Partitions Backup & Restore v1.6.0 RUS- thank htc 600,

as with Miflash (in "9008th mode") - you can flash "only selected partitions" + "dummy.img" = a good example of "dummy img-image"


CORR:
[*][under the spoiler!] cmdline off firmware and lsusb (USB VID / PID) of your device in all button / battery combinations:check all combinations

20160513
modiff:before asking questions:

from:

before asking questions:
is necessary learn the basic concepts (at least): in the cap "Terms (definitions)" (all) + "General theory" (release "a bit old", but gives a general idea);
++ "Ideally" - to deal with the "Listopenquestions "
"absolute minimum" required info: [list = 1] [*] link to a topic with a discussion of the device / firmware
[*] What did you do with the device before it was in such a state? (in detail!)
[*] Are any firmware available for him in the form of files (a) images (a)? If yes, give a link to one of them.
[*] What is USB VID / PID now? (in the device manager) //+ Also switch "view" - "on connection": there may be several devices
[*](possibly) for (native) charging for several hours; after - try to turn it on again(Flcb?)
[*] try on another PC
[*]check all combinations of clamping volume control buttons when the device is turned on and a USB cable is connected to it; also with battery disconnected

to:

before asking questions:
withof todayand for the future:
for newbies -
A prerequisite for writing messages in this topic is: provide the cmdline and lsusb of your device.
if it is not clear how to get it:
1. immediately look for a normal SC ("service center")
2. contact the appropriate forum section (= "Technical Repairs")
PS: in case of non-fulfillment of this condition - messages of newcomers will be deleted (and of course - left unanswered)
also:is necessary learn the basic concepts (at least): in the cap "Terms (definitions)" (all) + "General theory" (release "a bit old", but gives a general idea);
++ "Ideally" - to deal with the "Listopenquestions "
"absolute minimum" required info: [list = 1] [*] link to //savagemessiahzine.com/ devdb / and the topic of the discussion / firmware device
[*] What was done with the device before it was in such a state? What was tried out of the methods / approaches given in the topic? (in detail! ) + own considerations / assumptions regarding possible solutions
[*]conclusionqblinfoone of the loaders (/ programmer) - with firmware (/ dump). (what for, another example of output )
[*] USB VID / PID (better - lsusb (-tv)) in all combinations:check all combinations of clamping volume control buttons when the device is turned on and a USB cable is connected to it; also with battery disconnected
[*] How many hours on (native?) charge was the unit before the diagnosis?(Flcb?); battery charge level (V / mA)?
[*] how many PCs (/ what OS) were diagnosed?
[*] (recommended) -How to ask questions?

20160416
bootloader from source based on CAF - you can build! :General principles for restoring bootloaders to Qualcomm (Post S-trace # 48897765)

В®Partitions Backup & Restore Some screenshots to explain the process: В®Partitions Backup & Restore (Post aleha81 # 39380773)

20160415
MiFlash 2016.03.30.0 (64bit)


20160412
Backup IMEI from QPST to Qualcomm Snapdragon 616:Xiaomi Redmi 3 - Official firmware MIUI 7 (OS 5.1.1) (Post purler # 48189506)


20160328
spoiler = DEV-Provided]
USBlyser ...

20160312
DEL
fresh versions of some kvalkommovskih utilities

20160229

header:
del
!!-- subject only in the initial stage of design --!!

Mission: "to make Qualcomm as recoverable as MTC"

change list

"absolute minimum" necessary info: [/ b] [/ background] [list = 1] [*]

20160226
Attention!! Regarding "Relink HS-USB QD Loader 9008 (COM *)":

Acdev @ 02.26.2016, 14:45

screw driver RELINK kosyachit and it must be removed.
For the place it is necessary to put Google or from the vendor.

+ QDLoader HS-USB Driver 32-64 bit
+ moreQualcomm HS-USB QDLoader 9008 driver for Windows x64 // x86

====
Bootloader LuminesCollection of official firmware

20160209

about fastboot) [/ url] +"continuation"

20160203
HEX automatic conversion file of gpt.bin values ​​(obtained dd if = / dev / block / mmcblk0 of = / sdcard / gpt.bin bs = 8 count = 2176) into text content rawprogram0.xmlexcel tools - thank Bazzz2,

20160123
PS: in the "last resort" - you can try to search and order a memory (emmc chip) in China ...

Archive updates caps

_________

Statistics of user posts in the topic

There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the topicI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through a buttonunder the messages to which you want to add links.

Post has been editedvaalf - 07.03.19, 23:50

Reason for editing: Qualcomm Snapdragon 430 MSM8937 (Honor 7C) Instructions for the firmware Board, raising bricks

[= S =]

where does it go? lay out a software somewhere ...

[DimaDagget]

nowhere. Brick it. Only determined by the computer as QHSUSB_DLOAD

[= S =]

If the flash drive is not dead, you can raise it, provided that there is a full firmware!

[wladimir_tm]

Danil_e71 @ 01.24.2013, 10:36

By the way, this is not a download mod !!!
This is something like a recovery mode for the software of a corpse!

then it may be worth looking at USB \ VID _ ???? & PID _ ??? (& MI_ ??) and searchhereor in * .inf files here

UdAvSt @ 02.23.2014, 10:19

Attachments
Drivers

what is it?)
+ if it is EhostDL - then it may be worth seeing* To provide a partial Open Source (Linux) replacement for QPST and QXDM

[email protected], 12:21

send a .hex loader to RAM, now I'm digging a protocol for working with it.

maybe it will tell you something* Qualcomm / Intel HEX files..)

[email protected], 12:21

Message structure:
0x7E (command 1 byte) (parameters) (crc16_ccitt 2 bytes) 0x7E

Well, very similar to the "console work"EFS Professional



Post has been editedwladimir_tm - 28.07.14, 15:12

Reason for editing: / + EFS Professional

[Grishanenko]

Olezhek1975 @ 03.02.2014, 12:05

QHUSB_DLOAD is happiness. Download the Raw copy tool and ask someone from your branch to send you a copy of the phone made by the same program. Then fill the image with HDD-Raw-Copy-Tool on your machine. In Qpst (also need to download), change the imei.

That's just first you need the appearance in the system device to fill the image.
Sony LT26w - QHSUSB_DLOAD Appears - VID_0FCE & PID_3DDE
The drivers picked up from the Cyclone programmer - SEMC Flash Device, but the Raw copy tool sees only the hard drive.

[Olezhek1975]

QHUSB_DLOAD says only that the Qualcomm drivers are not yet installed .... see the PID.
After installationQUALCOMM DRIVERSwe begin to understand exactly which port we are dealing with. If the port is 9006, 9026, then working with the restoration of such a device is certainly easier (not by time but by the need for action). Well, if, after installing port 9008, then you need to give the processor a command to raise the internal memory. And it is given at a low program level. In turn, the processor issues a series of low voltages with a certain frequency (several dozen cycles) by the controller, after which the processor accepts the command and starts the internal memory, and the port from 08 turns into 06 or 26. You can continue working with visible internal memory, marking out the internal memory and fill it with images of sections. Something like this)))

there is still a port FFC0 - this is already a diagnostic port, that is, a port for the diagnostic port of your device, with all the ensuing consequences))) see the drivers and think how to deal with them further.


Post has been editedOlezhek1975 - 10.09.14, 01:11

[= S =]

[email protected], 16:45

Well, very similar to the "work console" EFS Professional

this protocol is diagnostic qualcomm or ppp protocol

[Grishanenko]

Olezhek1975 10.09.2014, 00:04

Well, if, after installing port 9008, then you need to give the processor a command to raise the internal memory. And it is given at a low program level.

RIFF or are there ways to do it "on the knee"?
In this case, HTC Desire V, in devices it looks like a Qualcomm HS-USB QDLoader 9008. I know that even RIFF cannot cope with such a problem in 90% of cases, since This problem is not software, but hardware (memory chip dies).

[Olezhek1975]

[email protected], 22:22

because This problem is not software, but hardware

I have already raised 300 devices from such a port. No reefs.

[wladimir_tm]

[email protected], 21:22

Qualcomm HS-USB QDLoader 9008. I know that even RIFF with such a problem in 90% of cases can not cope, because This problem is not software, but hardware (memory chip dies).

not quite right .. - because the “memory chip” is most likely alive);
"just" - the basic bootloader was knocked down (the fact that Preloader is in QPST), which is "flashed" by * .hex programmer from QPST "together" with * .xml - memory markup
Text or: And RIFF - this "simply box" which without this • .hex - nothing costs :)
in fact - RIFF is the same QPST - only "it can work through the pins on the motherboard" (which still "really need to be understood where they are"))

Post has been editedwladimir_tm - 19.09.14, 11:26

[Olezhek1975]

very interesting article on the frequency unlock on kvalkomah.
UNLOCK ADITIONAL BANDS FOR QUALCOMM DEVICES
She, of course, considers the special case of 1 + 1, but it is quite possible to apply to other devices on this platform.

Post has been editedOlezhek1975 - 19.09.14, 14:39

[Grishanenko]

[email protected], 10:21

not quite right .. - because the “memory chip” is most likely alive);

The phone freezes in the game (or something else), after that it stops turning on, i.e. The problem seems to be not hardware. I shed the first 512 megabytes of dump through RIFF - there is such a file on the support and all the loaders are required to be in it. Then, if desired, markup is done through the plugin and you can flash it again. But it does not help. Replacing the flash drive, firmware - the phone came to life. How can this be explained?
Are hex and xml freely available? It would be interesting to try, just have another Desire V.

[wladimir_tm]

[email protected], 14:38

very interesting article on the frequency unlock on kvalkomah.
UNLOCK ADITIONAL BANDS FOR QUALCOMM DEVICES

particularly interesting nuance
"Code: setprop sys.usb.config diag, adb" :) - i.e. how to enable diag port on qualcomm - (except adb port)! ;)

[email protected], 14:47

Desire V.

I will not tell you; You can try from analog (percent) devices

[Olezhek1975]

[email protected], 17:07

how to enable diag port on qualcomm - (except adb port)!

*#7678#
and turn both on - no mistake. The same result will be

[wladimir_tm]

[email protected], 17:08

*#7678#

does not work for all users ..)

[Olezhek1975]

[email protected], 18:39

does not work for all users ..)

here it is necessary to look at the models. On the stock firmware of Nubia - it works for everyone)

[= S =]

[email protected], 00:23

I have already raised 300 devices from such a port. No reefs.

share the secret of reviving ..

[Olezhek1975]

= S = @ 09/19/2014, 20:28

share the secret of reviving ..

http://www.anyclub.org/
http://www.xda-developers.com/
https://www.codeaurora.org/forum/

There is always where to dig.)

[= S =]

Thank you for the links, but I wanted to see a specific example ... if it doesn’t bother you ...

[Olezhek1975]

= S = @ 09/19/2014, 10:39

Thank you for the links, but I wanted to see a specific example ... if it doesn’t bother you ...

nothing concrete happens. Each brick is unique, despite the fact that the source data is the same.