[G2 General] somboons:
I don't respond for What-So-Ever done any damage to your Phone, You must accept this risk with yourself..

I want to share the method and discussion about This method. Is it possible we can use to fix qhsusb_bulk (qualcomm 9006) ..

Hi all,

I'm trying find a new method to fix brick qhsusb_bulk(qualcomm 9006) . First I need to do my phone has brick before.I don't the right way

how to make my phone has brick No Download Mode/Recovery/qhsusb_bulk(qualcomm 9006) to test and If I'm doing a wrong way this is a risk for me. :D

Today I try to make my phone has bricked by flash stock LP boot without Bump (My current firmware is D80230b) . Oh it's show qhsusb_bulk(qualcomm 9006) in device manager and so many drive show in my computer .But I can enter to recovery mode .I think it is enough to simulate how to fix brick without to use Ubuntu,Then try to fix by dd for windows it's working.Maybe this is a choice for people to fix brick without to use Ubuntu.

Require program

1. dd for windows

2. AOMEI Partition Assistant Standard Edition

3. Bump boot for D80230b

How to work

1. After install AOMEI Partition Assistant Standard Edition > Open it

you will see in picture as below

2. In picture above Disk1,Disk2 is a Harddrive in my computer Disk3 is a Harddrive in my phone

3. In disk3 we focus in File system is Fat16/Other/Ext4 or something that isn't Unallocated.We can mapping in G2 partition ex.

In picture FAT16 is a first partition has size 64 MB When we are mapping to G2 partition it is modem or boot partition is a number

7 in G2 partition in AOMEI Partition we can mapping as picture below

- D802 Partition

Number Start (sector) End (sector) Size Code Name

1 32768 163839 64.0 MiB 0700 modem

2 163840 165887 1024.0 KiB FFFF sbl1

3 165888 166911 512.0 KiB FFFF dbi

4 196608 197631 512.0 KiB FFFF DDR

5 229376 231423 1024.0 KiB FFFF aboot

6 231424 233471 1024.0 KiB FFFF rpm

7 262144 294911 16.0 MiB FFFF boot

8 294912 296959 1024.0 KiB FFFF tz

9 296960 296961 1024 bytes 0700 pad

10 327680 333823 3.0 MiB FFFF modemst1

11 333824 339967 3.0 MiB FFFF modemst2

12 339968 339969 1024 bytes FFFF pad1

13 360448 393215 16.0 MiB FFFF misc

14 393216 458751 32.0 MiB 0700 persist

15 458752 491519 16.0 MiB FFFF recovery

16 491520 497663 3.0 MiB FFFF fsg

17 524288 525311 512.0 KiB FFFF fsc

18 525312 526335 512.0 KiB FFFF ssd

19 526336 526337 1024 bytes FFFF pad2

20 526338 527361 512.0 KiB FFFF encrypt

21 557056 573439 8.0 MiB 0700 drm

22 573440 589823 8.0 MiB 0700 sns

23 589824 655359 32.0 MiB FFFF laf

24 655360 720895 32.0 MiB FFFF fota

25 720896 786431 32.0 MiB 0700 mpt

26 786432 787455 512.0 KiB FFFF dbibak

27 787456 789503 1024.0 KiB FFFF rpmbak

28 789504 791551 1024.0 KiB FFFF tzbak

29 791552 791567 8.0 KiB FFFF rct

30 819200 6488063 2.7 GiB 0700 system

31 6488064 7733247 608.0 MiB 0700 cache

32 7733248 7897087 80.0 MiB 0700 tombstones

33 7897088 7929855 16.0 MiB 0700 spare

34 7929856 8028159 48.0 MiB 0700 cust

35 8028160 60948479 25.2 GiB 0700 userdata

36 60948480 61071326 60.0 MiB 0700 grow

4. After we get information of partition we can use dd for windows to fix that partition

dd if=droidth-boot.img of=\\?\Device\HarddiskVolume306

I use all concept then make useful tool for fix qhsusb_bulk (qualcomm 9006)

[TOOLS] SRK Tool 2.0 - Tool for LG Mobile - 20150501

[YOUTUBE]ERZvlJIC9dE[/YOUTUBE]