Nubia Z5s (Qualcomm MSM8974) Qhsusb_bulk Mode Save Brick Method (take Win7 recovery partition as an example)

Nubia Z5s in the case of an exception or a combination of keys will enter the Qhsusb_bulk mode, the phenomenon is that if the windows (such as Win7) connected to the data cable, it will appear on the computer n multi-partition mount, and even prompted to format some of the partitions ( Here to emphasize is not to format any partition, otherwise it may become true brick only return to the factory )

About this model can refer to my previous 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 there is no need 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 possible to consider saving bricks in this mode, and the possibility of this pattern is:

1 Recovery partitions and system (or boot) partitions are 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

This mode is because it mounts all of the cell phone's partitions, and from the above analysis may be nothing more than some boot partition errors, the intuitive idea is to restore these errors of the partition.

You can refer to my previous article, first familiar with the following z5s specific zoning: http://blog.csdn.net/syhost/article/details/21818563

Note that the above article is a 16G version for example analysis, if the 32G may be slightly different, pay special attention!

Here's how to restore the z5s specific partition under Win7 to restore the recovery partition as an example ( This method has been successfully verified by the @ Troubled song )

The tool to use is the DD command under Windows:

Http://dl.vmall.com/c06d47p1fn

Or

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

The steps are as follows:

1, the first is to ensure that the mobile phone has been stable operation 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 prompts to format any partition, remember, otherwise it may really brick!!

2, the above DD tool decompression, and then into the folder, if it is Win7 system, support in the current directory open Terminal command line, operate as follows, in the DD folder, hold down the SHIFT key, then click the right mouse button, select the current directory to open the Terminal command, you can!

3. Run the DD--list command to view all of the computer's partition information (including, of course, the partition information of the mounted phone) (@ Troubled song offers ):

D:\222&GT;DD--listrawwrite dd for Windows version 0.5.Written by John Newbigin <[email protected]>this Progra  M is covered 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 \\?\De vice\harddiskvolume146 fixed media mounted on \\.\g:\\.\volume{4faebde7-671c-5533-0c1e-c5cd93452cb3} link to \\?\Devic e\harddiskvolume154 fixed media mounted on \\.\h:\\.\volume{59fe28dd-13a6-f2dd-1105-5b6a173a6e79} link to \\?\Device\H arddiskVolume159 fixed media mounted on \\.\i:\\.\volume{94ed69a1-a69d-b0c4-7d06-8f5039f55fc8} link to \\?\device\hard diskVolume160 fixed media mounted on \\.\j:\\.\volume{87f74cb9-9950-8f5b-48a5-3e4aadedcb0b} link to \\?\device\harddis kVolume161 fixed media mounted on \\.\k:\\.\volume{a92c0db2-bc8f-cb01-bfd7-ca99575da6d6} link to \\?\device\harddiskvo lume162  Fixed media mounted on \\.\l:\\.\volume{41f4a435-9559-66a2-ecbc-925db9220510} link to \\?\device\harddiskvolume163 fi  Xed 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 \\?\device\harddiskvolume3 fixed media Mounted on \\.\d:\\.\volume{14f93448-ea7b-11e3-8baf-806e6f6e6963} link to \\?\device\harddiskvolume4 fixed media Moun  Ted on \\.\e:\\.\volume{14f93449-ea7b-11e3-8baf-806e6f6e6963} link to \\?\device\harddiskvolume5 fixed media Mounted on \\.\f:nt Block Device objects\\?\device\harddisk0\partition0 link to \\?\device\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 Bytes\\?\device\harddisk0\partItion3 link to \\?\device\harddiskvolume3\\?\device\harddisk0\partition4 link to \\?\device\harddiskvolume4 Fixed hard Disk media.  Block size = 85911928832 size is a 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 a bytes\\?\device\harddisk1\partition1 link to \\?\device\harddiskvolume146 Fixed ha RD 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 Bytes\\?\device\harddisK1\partition13 link to \\?\device\harddiskvolume158 Fixed hard disk media.  Block size = 10485760 size is a bytes\\?\device\harddisk1\partition14 link to \\?\device\harddiskvolume159 Fixed hard Disk media. Block size = 1288488960 size is a bytes\\?\device\harddisk1\partition15 link to \\?\device\harddiskvolume160 Fixed ha RD 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 a bytes\\?\device\harddisk1\partition18 link to \\?\device\harddiskvolume163 Fixed har d 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\harddiskvolume1Fixed 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\\?\device\harddisk1\partition22 size is 1024x768 link to \\?\device\harddiskvolume167 Fixed hard dis K Media. Block size = 8192 size is a bytes\\?\device\harddisk1\partition23 link to \\?\device\harddiskvolume168 Fixed hard dis K 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 a bytes\\?\device\harddisk1\partition5 link to \\?\device\harddiskvolume150 Fixed hard dis K Media. Block size = 524288 size is Bytes\\?\devIce\harddisk1\partition6 link to \\?\device\harddiskvolume151 Fixed hard disk media. Block size = 512000 size is a bytes\\?\device\harddisk1\partition7 link to \\?\device\harddiskvolume152 Fixed hard di SK Media. Block size = 10485760 size is a bytes\\?\device\harddisk1\partition8 link to \\?\device\harddiskvolume153 Fixed hard Disk media. Block size = 512000 size is a bytes\\?\device\harddisk1\partition9 link to \\?\device\harddiskvolume154 Fixed hard di SK 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 from these partition information to find the cell phone partition information, refer to my above about z5s partition information, comparison can easily find the partition number you want to recover (refers to the DD command to identify the partition number) and the disk number of the phone disk.

Taking recovery partition as an example, the method of judging partition is introduced briefly:

A, can be judged by the size of the partition number, such as the above article can be seen recovery partition corresponding to the 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 you can judge this is the cell phone partition,

B, after the method above, to determine whether the recovery partition, through the partition size, such as the above Partition19 in the DD command to display the size of the 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 as the size of the 10240x1024=10485100 command (as for why it is not exactly the same), This basically can judge 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 boot partition also no problem)!

C, from the Partition19 in front of the character segment Harddisk1 judge, their own computer if only a hard disk, that its own hard disk should be Harddisk0, then this Harddisk1 should be the cell phone partition corresponding disk number!

4, find the required partition number, you can do DD recovery operation, the specific method:

1) Place the IMG image file of the partition that needs to be restored in the folder where the DD command is located, if it is recovery or boot partition, only need to put the recovery.img or boot.img in the brush package!

2) in the current directory, the terminal command line executes DD if=recovery.img of=\\?\device\harddisk1\partition19 can be seen 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 executing the command, the correct recovery of the recovery partition ( provided by the @ Troubled song ) is as follows:

At this point, the recovery partition has been completely restored, as long as you put the recovery.img is correct (here is correct for z5s is necessary to be with your brick before the baseband version, because some recovery can only be used in the corresponding baseband version).

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

In addition, special emphasis should be placed on If you use this method to recover other boot partitions (except the boot and recovery partitions), including: Aboot, SBL1, TZ, RPM, SDI these partitions must be restored together if you want to restore any of them, and the version corresponds to Or it's really brick! And these partition image files can be found in the official full ROM package, where aboot corresponds to the Emmc_appsboot.mbn file, other partitions to see the name corresponding to the filename!