Nubia Z5S (Qualcomm MSM8974) QHSUSB_BULK mode brick rescue method (taking restoring the recovery partition under win7 as an example)

Nubia Z5S enters the QHSUSB_BULK mode in case of an exception or combination of buttons. This mode means that if the data line is connected to windows (such as win7, there will be n multi-partition mounting on the computer, and even a prompt will be prompted to format some partitions (here we should emphasize that do not format any partition, or else it may become a real brick, only after the factory)

For details about this mode, refer to an article I posted earlier: 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 if it is purely for Brick saving!

When Z5S enters this mode and cannot start other modes or systems normally, you only need to consider saving bricks in this mode. The possible situation of this mode is:

1. The recovery partition and system (or boot) partition are damaged at the same time.

2. An exception may occur in the boot partition,

3. Press the button combination under certain conditions.

In this mode, all partitions of the mobile phone are mounted, and the preceding analysis may result in some startup partition errors. The intuitive idea is to restore these wrong partitions.

Can first refer to my previous article, first familiar with the specific partition of Z5S: http://blog.csdn.net/syhost/article/details/21818563

Note that the above article uses the 16G version as an example. If it is 32G, it may be slightly different. Please pay special attention to it!

The following describes how to restore a specific Z5S partition under Windows 7 7 (This method has been successfully verified by @ aliyunge)

The tool to be used is the dd command in windows ,:

Http://dl.vmall.com/c06d47p1fn

Or

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

The procedure is as follows:

1. First, ensure that the mobile phone has run stably to the QHSUSB_BULK mode, and connect to the data line. You can see n multiple partitions in the computer system. Be careful not to format any partitions as prompted. Remember, otherwise it may be real !!

2. decompress the preceding dd tool and enter the folder. For Windows 7, you can open the terminal command line in the current directory as follows, hold down the shift key in the dd folder, right-click it, and select the terminal command in the current directory!

3. Run the dd -- list command to view all the partition information of the Computer (including the partition information of the mounted mobile phone, of course ):

D:\222>dd --listrawwrite dd for windows version 0.5.Written by John Newbigin <jn@it.swin.edu.au>This program 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 \\?\Device\HarddiskVolume146  fixed media  Mounted on \\.\g:\\.\Volume{4faebde7-671c-5533-0c1e-c5cd93452cb3}\  link to \\?\Device\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 \\?\Device\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 \\?\Device\HarddiskVolume162  fixed media  Mounted on \\.\l:\\.\Volume{41f4a435-9559-66a2-ecbc-925db9220510}\  link to \\?\Device\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 \\?\Device\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 \\?\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 = 512  size is 320072933376 bytes\\?\Device\Harddisk0\Partition1  link to \\?\Device\HarddiskVolume1\\?\Device\Harddisk0\Partition2  link to \\?\Device\HarddiskVolume2  Fixed hard disk media. Block size = 512  size is 21474836480 bytes\\?\Device\Harddisk0\Partition3  link to \\?\Device\HarddiskVolume3\\?\Device\Harddisk0\Partition4  link to \\?\Device\HarddiskVolume4  Fixed hard disk media. Block size = 512  size is 85911928832 bytes\\?\Device\Harddisk0\Partition5  link to \\?\Device\HarddiskVolume5  Fixed hard disk media. Block size = 512  size is 116023722496 bytes\\?\Device\Harddisk1\Partition0  link to \\?\Device\Harddisk1\DR8  Fixed hard disk media. Block size = 512  size is 15758000128 bytes\\?\Device\Harddisk1\Partition1  link to \\?\Device\HarddiskVolume146  Fixed hard disk media. Block size = 512  size is 67108864 bytes\\?\Device\Harddisk1\Partition10  link to \\?\Device\HarddiskVolume155  Fixed hard disk media. Block size = 512  size is 1572864 bytes\\?\Device\Harddisk1\Partition11  link to \\?\Device\HarddiskVolume156  Fixed hard disk media. Block size = 512  size is 1572864 bytes\\?\Device\Harddisk1\Partition12  link to \\?\Device\HarddiskVolume157  Fixed hard disk media. Block size = 512  size is 1048576 bytes\\?\Device\Harddisk1\Partition13  link to \\?\Device\HarddiskVolume158  Fixed hard disk media. Block size = 512  size is 10485760 bytes\\?\Device\Harddisk1\Partition14  link to \\?\Device\HarddiskVolume159  Fixed hard disk media. Block size = 512  size is 1288488960 bytes\\?\Device\Harddisk1\Partition15  link to \\?\Device\HarddiskVolume160  Fixed hard disk media. Block size = 512  size is 2684354560 bytes\\?\Device\Harddisk1\Partition16  link to \\?\Device\HarddiskVolume161  Fixed hard disk media. Block size = 512  size is 33554432 bytes\\?\Device\Harddisk1\Partition17  link to \\?\Device\HarddiskVolume162  Fixed hard disk media. Block size = 512  size is 524288000 bytes\\?\Device\Harddisk1\Partition18  link to \\?\Device\HarddiskVolume163  Fixed hard disk media. Block size = 512  size is 157286400 bytes\\?\Device\Harddisk1\Partition19  link to \\?\Device\HarddiskVolume164  Fixed hard disk media. Block size = 512  size is 10485760 bytes\\?\Device\Harddisk1\Partition2  link to \\?\Device\HarddiskVolume147  Fixed hard disk media. Block size = 512  size is 524288 bytes\\?\Device\Harddisk1\Partition20  link to \\?\Device\HarddiskVolume165  Fixed hard disk media. Block size = 512  size is 1572864 bytes\\?\Device\Harddisk1\Partition21  link to \\?\Device\HarddiskVolume166  Fixed hard disk media. Block size = 512  size is 1024 bytes\\?\Device\Harddisk1\Partition22  link to \\?\Device\HarddiskVolume167  Fixed hard disk media. Block size = 512  size is 8192 bytes\\?\Device\Harddisk1\Partition23  link to \\?\Device\HarddiskVolume168  Fixed hard disk media. Block size = 512  size is 10523482624 bytes\\?\Device\Harddisk1\Partition3  link to \\?\Device\HarddiskVolume148  Fixed hard disk media. Block size = 512  size is 32768 bytes\\?\Device\Harddisk1\Partition4  link to \\?\Device\HarddiskVolume149  Fixed hard disk media. Block size = 512  size is 32768 bytes\\?\Device\Harddisk1\Partition5  link to \\?\Device\HarddiskVolume150  Fixed hard disk media. Block size = 512  size is 524288 bytes\\?\Device\Harddisk1\Partition6  link to \\?\Device\HarddiskVolume151  Fixed hard disk media. Block size = 512  size is 512000 bytes\\?\Device\Harddisk1\Partition7  link to \\?\Device\HarddiskVolume152  Fixed hard disk media. Block size = 512  size is 10485760 bytes\\?\Device\Harddisk1\Partition8  link to \\?\Device\HarddiskVolume153  Fixed hard disk media. Block size = 512  size is 512000 bytes\\?\Device\Harddisk1\Partition9  link to \\?\Device\HarddiskVolume154  Fixed hard disk media. Block size = 512  size is 1048576 bytesVirtual input devices /dev/zero   (null data) /dev/random (pseudo-random data) -           (standard input)Virtual output devices -           (standard output)

Then, find the mobile phone's partition information from the partition information. Refer to my article on z5s partition information above, by comparison, you can easily find the Partition Number of the partition you want to restore (the Partition Number identified by the dd command) and the disk Number of the mobile phone disk.

Taking the recovery partition as an example, we will briefly introduce how to judge the partition:

A. You can determine the Partition Number size. For example, in the previous article, we can see that the partition number corresponding to the recovery partition is 19, and in the dd information above, we can also see the Partition Number Partition19, generally, there are not so many computer partitions, so we can determine that this is the cell phone partition,

B. Use the following method to determine whether the partition is a rediscovery partition. For example, the preceding Partition19 command shows that the partition size is 10485760 bytes (10485760 bytes ), the size of the recovery partition shown in the above article (32 GB may be different) the value 10240x1024 = 10485100 is basically the same as the size obtained by the dd command above (as to why it is not the same ), this basically determines that the obtained Partition19 In the dd command is the rediscovery partition of the mobile phone (note that the boot partition of the mobile phone is the same as the size of the rediscovery partition. Note the difference, of course, writing recovery into the boot partition is okay )!

C. Judging from the character segment Harddisk1 before Partition19, if your computer has only one hard disk, the hard disk should be Harddisk0, here, Harddisk1 should be the disk number corresponding to the cell phone partition!

4. After finding the required partition number, you can perform the dd recovery operation. The specific method is as follows:

1) Place the img image file of the partition to be restored to the folder where the dd command is located. If it is a recovery or boot partition, you only need to recovery in the recovery. img or boot. put img in!

2) execute dd if = recovery. img of =\\? in the terminal command line in the current directory \\? \ Device \ Harddisk1 \ Partition19. here we can see that recovery. img is the name of the partition image you put, and \\? \ Device \ Harddisk1 \ Partition19 is the Partition Number of the recovery partition obtained by the dd -- list command above. It is completely copied! After the command is executed, the correct restore of the recovery partition (provided by @) is as follows:

Now, you have completely restored the recovery partition, as long as you release the recovery. img is correct (this is correct. For z5s, it must be matched with the baseband version before the brick, because some recovery s can only be used under the corresponding baseband version ).

It seems complicated. In fact, there are only two points: first, the dd command correctly determines the partition number you want to restore the partition, and second, the command must be entered correctly and the partition image recovery file must be correct!

In addition,If you use this method to restore other boot partitions (except boot AND recovery partitions), including partition T, sbl1, tz, rpm, and sdi partitions, if you want to restore any of these partitions,All must be restored together, and the corresponding version is required.Otherwise, it will be real! These partition image files can be found in the complete official rom package. The mirror T corresponds to the emmc_appsboot.mbn file. For other partitions, see the corresponding file name!