Nubia Z5s (Qualcomm MSM8974) Qhsusb_bulk Brick method Save mode (with Win7 in recovery recovery partition case)

Nubia Z5s in some unusual situation or press the combination key into the Qhsusb_bulk state, this mode of phenomenon, conjecture windows (instance win7) even in the data line, it will appear on the computer n download, and even will be prompted to format some partitions ( The emphasis here is not to format no matter what partition, or it may become the real brick just return to the factory.

About this model can be a reference to my previous article issued a post: http://blog.csdn.net/syhost/article/details/20435957

As mentioned in the above article, the Qhsusb_bulk mode is actually implemented in the SBL partition, but it is not necessary to know these details purely to save bricks!

When the z5s enters this mode and does not start other modes or systems properly, it is only considered to save the bricks in this mode, and the possible scenario for such a pattern is:

1 recovery partition and system (or boot) partition is damaged at the same time

2 boot partition may have an exception,

3 Press the combination of keys under certain conditions

Please be sure to keep this link for reprint:

http://blog.csdn.net/syhost/article/details/36972531

Such a pattern is due to mount the phone's entire partition, and from the above analysis may be nothing more than some boot partition errors, the intuitive idea is to restore the wrong partition.

Can first participate in my previous article, first familiar with the next z5s detailed zoning: http://blog.csdn.net/syhost/article/details/21818563

Note that the above article is based on the 16G version number for example analysis, assuming that 32G may be slightly different. Pay special attention to the next!

Here's how to recover z5s specific partitions under Win7. Take the recovery recovery partition as an example ( This method has been successfully verified by @ troubled song )

The tool to use is the DD command under Windows:

Http://dl.vmall.com/c06d47p1fn

Or

Https://mega.co.nz/#!B1lzlDJa!yfw8NrtWQCznodyxnaKbRIs6dboTyLHU1NNtky0waQw

Procedures such as the following:

1, the first is to ensure that the mobile phone has been stably implemented to the Qhsusb_bulk mode, and connected to the data line, in the computer system can see n multi-partition, to pay special attention do not follow the hint format no matter what partition, remember, otherwise it may be real bricks!

。

2, the above DD tool decompression, and then into the folder, assuming that the Win7 system, support in the current folder to open the terminal command line, operations such as the following, under the DD folder hold the SHIFT key, and then click the right mouse button. Select the current folder to open the Terminal command, you can!

3. Execute DD--list command to view all partition information of the computer (also including the partition information of the mounted phone) (@ Gone with the song ):

D:\222&GT;DD--listrawwrite dd for Windows version 0.5.Written by John newbigin <[email protected]>this Program is C  Overed by the GPL. See Copying.txt for DetailsWin32 Available Volume information\\.\volume{14f93446-ea7b-11e3-8baf-806e6f6e6963} link to \ \?
\DEVICE\HARDDISKVOLUME1 fixed media mounted on \\.\c:\\.\volume{27fc973e-92de-706b-3d39-ff3b00c9862e} link to \ \?
\device\harddiskvolume146 fixed media mounted on \\.\g:\\.\volume{4faebde7-671c-5533-0c1e-c5cd93452cb3} link to \\?\De vice\harddiskvolume154 fixed media mounted on \\.\h:\\.\volume{59fe28dd-13a6-f2dd-1105-5b6a173a6e79} link to \ \?
\device\harddiskvolume159 fixed media mounted on \\.\i:\\.\volume{94ed69a1-a69d-b0c4-7d06-8f5039f55fc8} link to \\?\De vice\harddiskvolume160 fixed media mounted on \\.\j:\\.\volume{87f74cb9-9950-8f5b-48a5-3e4aadedcb0b} link to \ \?
\device\harddiskvolume161 fixed media mounted on \\.\k:\\.\volume{a92c0db2-bc8f-cb01-bfd7-ca99575da6d6} link to \\?\De vice\harddiskvolume162 fixed media mounted on \\.\l:\\.\volume{41f4a435-9559-66a2-ecbc-925db9220510} link to \\?\Devic e\harddiskvolume163 fixed media mounted on \\.\m:\\.\volume{ca630bbc-e3bb-5e2d-d9ff-253b5188313b} link to \ \?
\device\harddiskvolume168 fixed media mounted on \\.\n:\\.\volume{14f93447-ea7b-11e3-8baf-806e6f6e6963} link to \\?\De Vice\harddiskvolume3 fixed media mounted on \\.\d:\\.\volume{14f93448-ea7b-11e3-8baf-806e6f6e6963} link to \ \?
\device\harddiskvolume4 fixed media mounted on \\.\e:\\.\volume{14f93449-ea7b-11e3-8baf-806e6f6e6963} link to \\?\Devi Ce\harddiskvolume5 fixed media mounted on \\.\f:nt Block Device objects\\?\device\harddisk0\partition0 link to \\?\devi Ce\harddisk0\dr0 Fixed hard disk media. Block size = 320072933376 size is a bytes\\?\device\harddisk0\partition1 link to \\?\device\harddiskvolume1\\?\device\ Harddisk0\partition2 link to \ \?
\device\harddiskvolume2 Fixed hard disk media. Block size = 21474836480 size is a bytes\\?\device\harddisk0\partition3 link to \\?\device\harddiskvolume3\\?
\device\harddisk0\partition4 link to \\?\device\harddiskvolume4 Fixed hard disk media. Block size = 85911928832 size is bytes\\?
\device\harddisk0\partition5 link to \\?\device\harddiskvolume5 Fixed hard disk media. Block size = 116023722496 size is a bytes\\?\device\harddisk1\partition0 link to \\?\device\harddisk1\dr8 Fixed hard Disk media. Block size = 15758000128 size is bytes\\?
\Device\Harddisk1\partition1 link to \ \?
\device\harddiskvolume146 Fixed hard disk media.  Block size = 67108864 size is a bytes\\?\device\harddisk1\partition10 link to \\?\device\harddiskvolume155 Fixed hard Disk media. Block size = 1572864 size is a bytes\\?\device\harddisk1\partition11 link to \\?\device\harddiskvolume156 Fixed hard Disk media. Block size = 1572864 size is a bytes\\?\device\harddisk1\partition12 link to \\?\device\harddiskvolume157 Fixed hard Disk media. Block size = 1048576 size is the bytes\\?\device\harddisk1\partition13 link to \ \?
\device\harddiskvolume158 Fixed hard disk media. Block size = 10485760 size is bytes\\?
\device\harddisk1\partition14 link to \\?\device\harddiskvolume159 Fixed hard disk media. Block size = 1288488960 size is bytes\\?
\device\harddisk1\partition15 link to \ \?
\device\harddiskvolume160 Fixed hard disk media. Block size = 2684354560 size is a bytes\\?\device\harddisk1\partition16 link to \\?\device\harddiskvolume161 Fixed ha RD Disk Media.  Block size = 33554432 size is a bytes\\?\device\harddisk1\partition17 link to \\?\device\harddiskvolume162 Fixed hard Disk media. Block size = 524288000 size is bytes\\?
\device\harddisk1\partition18 link to \ \?
\device\harddiskvolume163 Fixed hard disk media. Block size = 157286400 size is a bytes\\?\device\harddisk1\partition19 link to \\?\device\harddiskvolume164 Fixed har d Disk Media. Block size = 10485760 size is a bytes\\?\device\harddisk1\partition2 link to \\?\device\harddiskvolume147 Fixed hard Disk media. Block size = 524288 size is a bytes\\?\device\harddisk1\partition20 link to \\?\device\harddiskvolume165 Fixed hard D ISK Media. Block size = 1572864 size is a bytes\\?\device\harddisk1\partition21 link to \\?\device\harddiskvolume166 Fixed hard Disk media. Block size = bytes\\ size is 1024x768?
\device\harddisk1\partition22 link to \\?\device\harddiskvolume167 Fixed hard disk media. Block size = 8192 size is the bytes\\?\device\harddisk1\partition23 link to \ \?
\device\harddiskvolume168 Fixed hard disk media. Block size = 10523482624 size is a bytes\\?\device\harddisk1\partition3 link to \\?\device\harddiskvolume148 Fixed ha RD Disk Media. Block size = 32768 size is a bytes\\?\device\harddisk1\partition4 link to \\?\device\harddiskvolume149 Fixed hard dis K Media. Block size = 32768 size is bytes\\?
\device\harddisk1\partition5 link to \\?\device\harddiskvolume150 Fixed hard disk media. Block size = 524288 size is bytes\\?
\device\harddisk1\partition6 link to \\?\device\harddiskvolume151 Fixed hard disk media. Block size = 512000 size is bytes\\?
\device\harddisk1\partition7 link to \\?\device\harddiskvolume152 Fixed hard disk media. Block size = 10485760 size is the bytes\\?\device\harddisk1\partition8 link to \ \?
\device\harddiskvolume153 Fixed hard disk media. Block size = 512000 size is bytes\\?
\device\harddisk1\partition9 link to \\?\device\harddiskvolume154 Fixed hard disk media.           Block size = 1048576 size is bytesvirtual input devices/dev/zero (null data)/dev/random (pseudo-random data)- (Standard input) Virtual Output devices-(standard output)

then find the partition information of the phone from these partition information. Refer to my article on z5s partition information above. In contrast, you can easily find the partition number of the partition you want to recover (referring to the partition number identified under the DD command) and the disk number of the phone disk.

Take recovery partitioning as an example of how to infer a partition:

A, can be inferred by the size of the partition number. For example, the above article can see the recovery partition corresponding partition number is 19, and the above DD information can also see the Partition19 this partition number, and the general computer partition is not so much, so it can be inferred that this is the cell phone partition,

B, next to the method above, inferred is not recovery partition, by partition size. For example, the Partition19 on the DD command displays size 10485760 bytes (that is, 10485760 bytes). The size of the recovery partition as seen in the above article (32G may be different) is basically the same size as the 10240x1024=10485100 above DD command (as for why it is not completely the same). This basically can infer the DD command to get the Partition19 is the cell phone recovery partition (especially note that the general phone boot partition with the recovery partition size is the same, pay attention to distinguish, of course, the recovery write to the boot partition is no problem)!

C, inferred from the character segment Harddisk1 in front of Partition19. Own computer assumes only a hard disk, that its own hard disk should be Harddisk0, then here Harddisk1 should be the cell phone partition corresponding disk number!

4. After locating the required partition number. To be able to perform the DD recovery operation, the detailed method:

1) Place the IMG image file of the partition that needs to be restored in the directory where the DD command resides, assuming that the recovery or boot partition simply needs to put the recovery.img or boot.img in the brush package!

2) Run DD if=recovery.img of=\\?\device\harddisk1\partition19 on the terminal command line in the current folder, you can see here recovery.img That is, you put the partition image of the file name, and \\?\device\harddisk1\partition19 is the above DD--list command to obtain the recovery partition number information, completely copied over!

After you run the command. Correct recovery of the recovery partition (by

From=feed&loc=at "style=" text-decoration:none; Color:rgb (10,140,210); line-height:23px; Background-color:rgb (250,250,250) ">@ of the troubled song" provided) for example the following:

So far. Has completely restored the recovery partition, just want you to put the recovery.img is correct (here said correct for Z5s is sure to be with your brick before the baseband version number, because some recovery can only be used in the corresponding baseband version number).

Seemingly complex, in fact only two points: one is the DD command correctly infer the partition number you want to restore the partition, the second is the command to enter the correct and partition image recovery file must be correct.

In addition, special emphasis should be placed on assume that the other boot partitions (except the boot and recovery partitions) are restored with this method, including: Aboot, SBL1, TZ, RPM, SDI these partitions assume that any one of them will have to be restored, and that the version number corresponds , or it's really brick. These partitioned image files can be found in the official full ROM package. The aboot corresponding to the Emmc_appsboot.mbn file. Other partitions to see the name of the corresponding file name!

Copyright notice: This article Bo Master original articles, blogs, without consent may not be reproduced.

Nubia Z5s (Qualcomm MSM8974) Qhsusb_bulk Brick method Save mode (with Win7 in recovery recovery partition case)