[Q] Wrong kernel : black screen, no fastboot, no adb, no factory reset

Search This thread

gavinhungry

Member
Apr 4, 2012
35
87
Could you please clarify following for me please (I have a pretty similar situation):
1. how long did you wait for 9006 device after flashing 8974_msimage.mbn ?
2. did you have a line green after flashing of 8974_msimage.mbn ? or it just ran quickly to a middle and device became disconnected ?
3. did you have a USB string in MSMTool after 8974_msimage.mbn flashing, or it looks different for you ?

Actually I tried hardware XP with no luck, but probably I waiting not enough after 8974_msimage.mbn...
Could you also take a look at my problem description here:
Can you say - how similar my problem to your one ?
Thank you in advance!
Glad to hear about your progress with unbricking ! )

1. In the VM, a few minutes with no activity. On the real install of XP, about 3 seconds before 9006 showed up. It did prompt me to install a driver for it. I just pointed it at the same folder I used for 9008 (in Qualcomm 2012 driver: fre/XP-Vista) and it installed right away.
2. I don't think there was a green line after 8974_msimage.mbn, it just flashed and stopped.
3. It did look different (from the rest of the lines) after 8974_msimage.mbn. I have no idea what it said.

I should have mentioned it in my last post, but after 9006 mode showed up, I did have to hit Stop in the tool and then start it again. It didn't try to flash 8974_msimage.mbn again, it just picked up where it left off and completed. Are you using the "Qualcomm 2012" drivers?

Read your post from the OnePlus forum. Do you never get 8974_msimage.mbn to complete? Even in the VM, that file always would flash for me. It was getting past that where I had trouble.
 
  • Like
Reactions: kronborn1

kronborn1

Member
Nov 12, 2014
11
0
1. In the VM, a few minutes with no activity. On the real install of XP, about 3 seconds before 9006 showed up. It did prompt me to install a driver for it. I just pointed it at the same folder I used for 9008 (in Qualcomm 2012 driver: fre/XP-Vista) and it installed right away.
2. I don't think there was a green line after 8974_msimage.mbn, it just flashed and stopped.
3. It did look different (from the rest of the lines) after 8974_msimage.mbn. I have no idea what it said.

I should have mentioned it in my last post, but after 9006 mode showed up, I did have to hit Stop in the tool and then start it again. It didn't try to flash 8974_msimage.mbn again, it just picked up where it left off and completed. Are you using the "Qualcomm 2012" drivers?

Read your post from the OnePlus forum. Do you never get 8974_msimage.mbn to complete? Even in the VM, that file always would flash for me. It was getting past that where I had trouble.

Thanks for your answers mate! I don't really know was the 8974_msimage.mbn completed for me or not - progress going very quickly (1-2 sec) and after that - device was disconnected. I asked you to describe your 8974_msimage.mbn flashing process to improve my understanding of that, but I'm still not clear - flashed it completely or not - I have no any green lines at least. As I remember - I waited for a minute or two after it (on a real XP) - no 9006 appeared in manager (or any similar or even just new) for me. If I press volume+ button (even without power) device has come back at the same state (9008). Yes I'm using the "Qualcomm 2012" drivers - seems like these ones are the mostly used and working.
Thank you very much for your info and any further (if any).
 

Jahdiel2011

Senior Member
Oct 30, 2011
109
40
Bogotá
Thanks for your answers mate! I don't really know was the 8974_msimage.mbn completed for me or not - progress going very quickly (1-2 sec) and after that - device was disconnected. I asked you to describe your 8974_msimage.mbn flashing process to improve my understanding of that, but I'm still not clear - flashed it completely or not - I have no any green lines at least. As I remember - I waited for a minute or two after it (on a real XP) - no 9006 appeared in manager (or any similar or even just new) for me. If I press volume+ button (even without power) device has come back at the same state (9008). Yes I'm using the "Qualcomm 2012" drivers - seems like these ones are the mostly used and working.
Thank you very much for your info and any further (if any).
I just brought mine back to life with this method.

I used this Qualcom driver which worked fine.

https://drive.google.com/file/d/0Bx5BQ5W7fk_7VFRpbW5WTzR0OGs/view?usp=sharing

As for installing the driver using Windows 7 i just deactivated the driver signature verification by pressing F8 when windows is booting and selecting the option to ignore that validation.

after that I just did the thing with the Color OS tools.

Thank you VERY MUCH for the post it is 100% effective.
 

salman.arif

New member
Jan 14, 2015
3
0
Worked 110% :d

OK, as promised I wanted to write up more detailed steps on how I unbricked my OPO. First, thanks to all who contributed, found the needed files and solution.

The solution is in fact to download Color.zip from https://mega.co.nz/#!BkpwyYSB!rkYSkFI28vFGuhtsIli-vyDdsb4ZZp1-MX1cLLtaiRo.
After downloading, unzip the archive.

Next, Windows drivers. If you're like me you've already tried different drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then, go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through.

Second note about drivers if that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations. I've tried overwriting these settings and spent half a day messing with it, and I never go the next steps to work properly. I ended up trying installing the drivers from Setup.exe and the following steps on my Windows 2003 server and things worked properly first time. I am not saying that you won't get this to work on Window 7 or 8, but if you're having troubles try Windows XP, that might make a difference.

Anyway, once you have the drivers straightened out, connect your phone to the computer, start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com devices. If you unplug the phone and move it to another port, or computer, it will show your bricked phone on a different line. There is no reason to click in or select at lines, the program knows where the phone is.

Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.

If you don't see your devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.

Anyway, once you see the phone in the list, click Start. You should see the programs starts writing different files to the phone. Each time it writes a file you'll see a progress bar. Once this is going you know you will be good to go... After all files are written, the line with your device will turn green. You're good, unplug and reboot your phone to ColorOS.

If there is a problems flashing the device, the line will turn Red. That's what I was getting on my Windows 7 after like 3 seconds after clicking Start. After moving to Windows 2003, everything worked like a charm.

Once you're on ColorOS and want to go to Cyanogenmod 11S, you have a few options. The easiest way if to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and run the following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin

Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.

That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue. If you're still getting stuck, let me know, I'll see if I can help.


Thumbs up :)
Worked for 100%. I got my phone hard bricked when I tried to install CM11S (the one for international version) on my Chinese version of OPO. Maybe there was a conflict between the two versions, or something like that. I got a bit worried at start but when I searched over XDA and OPO Forums, I came to know that this looks out to be a curable issue. This ColorOS solution brought my OPO back to life.
Based on my experience, following are some of the tips I would like to share:
1. Despite of trying several times this solution did not work for me on windows 7/8. The reason was obviously the unsigned drivers, which win 7/8 were blocking as they are unsigned. So I did it on Windows XP, and it worked in the first round.
2. Since Windows XP is hard to find now a days on any system, so instead of installing it on my laptop, I created a virtual machine of based on Windows XP OS. As it was a virtual machine, so the flashing took a bit long, but it was completed successfully.
3. When the flashing was complete, the line turned Green, (this is the key, it is the indication that Yes, everything went fine). If it is not turning Green, then most probably there is an issue and device is not flashed properly (as it was happening with me when I installed some Qualcomm 9008 drivers on Windows 7).
4. If after flashing, you are unable to load ColorOS (as it was the case with me) then don't panic. TBH, even after flashing ColorOS (most probably) you'll be going for CM11 or CM12 nightly. So just put your phone on Fast Boot and follow the steps as mentioned above.
5. If you are flashing CM11 on your phone and following the steps as mentioned above, then you'll be required to have Android SDK. Otherwise, your device would not be recognized as a Fastboot device in CMD (for windows).

Don't worry if you got your device bricked, there is always a chance of pulling your OPO back to life (unless there is a hardware failure).

Thanks for the solution again :)
 

jeffsta

Senior Member
Dec 6, 2008
91
45
Thumbs up :)
Worked for 100%. I got my phone hard bricked when I tried to install CM11S (the one for international version) on my Chinese version of OPO. Maybe there was a conflict between the two versions, or something like that. I got a bit worried at start but when I searched over XDA and OPO Forums, I came to know that this looks out to be a curable issue. This ColorOS solution brought my OPO back to life.
Based on my experience, following are some of the tips I would like to share:
1. Despite of trying several times this solution did not work for me on windows 7/8. The reason was obviously the unsigned drivers, which win 7/8 were blocking as they are unsigned. So I did it on Windows XP, and it worked in the first round.
2. Since Windows XP is hard to find now a days on any system, so instead of installing it on my laptop, I created a virtual machine of based on Windows XP OS. As it was a virtual machine, so the flashing took a bit long, but it was completed successfully.
3. When the flashing was complete, the line turned Green, (this is the key, it is the indication that Yes, everything went fine). If it is not turning Green, then most probably there is an issue and device is not flashed properly (as it was happening with me when I installed some Qualcomm 9008 drivers on Windows 7).
4. If after flashing, you are unable to load ColorOS (as it was the case with me) then don't panic. TBH, even after flashing ColorOS (most probably) you'll be going for CM11 or CM12 nightly. So just put your phone on Fast Boot and follow the steps as mentioned above.
5. If you are flashing CM11 on your phone and following the steps as mentioned above, then you'll be required to have Android SDK. Otherwise, your device would not be recognized as a Fastboot device in CMD (for windows).

Don't worry if you got your device bricked, there is always a chance of pulling your OPO back to life (unless there is a hardware failure).

Thanks for the solution again :)

I had no problem with the ColorOS procedure but my device would not boot so I flashed CM11 like you suggested and everything went the way it should but it's still in a boot loop, did I miss out something guys?
 

rajarshi10

Senior Member
Aug 3, 2011
2,480
364
Kolkata
My device is getting recognized as this whenever I plug in, but it is not digitally signed so I guess MSM installer is not detecting it. What do I do now? :'(
Windows 7 here.

screenshot_122.png
 

salman.arif

New member
Jan 14, 2015
3
0
Bootloop

I had no problem with the ColorOS procedure but my device would not boot so I flashed CM11 like you suggested and everything went the way it should but it's still in a boot loop, did I miss out something guys?

Please explain what happened after when u flashed ColorOS? You were just unable to boot into the OS or there was a bootloop at that time also? If it was not in bootloop at that time then I think u did something wrong while flashing CM11.
 

derekk75j

Senior Member
Jul 4, 2014
126
30
Gorizia
Help! I bricked my opo! I installed colorOs (version anysys 2.0.42) and I had nice signal strenght. I tried to install modem of 44s (zip flashable) and the phone didn't turn on! Problem is: i can't install driver adb in win 7 (32 and 64 bit) and i so i can't try Oneplusrestore tool. I try so many drivers but nothing work.
In device manager i see QHUSB_Bulk and now i'm stuck. Any idea?

---------- Post added at 02:10 AM ---------- Previous post was at 01:30 AM ----------

I solved!! I try to explain how I made it:
http://en.oppo.com/downloads/firmware/driverForFind5.rar
I've downloaded driver for oppo find 5 (!!!) and manually installed it, picking up from here:
C:\Users\.........\Downloads\driverForFind5\chk\Windows7

Automatically has installed the driver and QHUSB_BULK became qualcomm hs-9008 (i don't remember exactly, but the number was right).
Suddenly I started Oneplus one recovery tool and it worked!!! 44s stock! I spent 6 hours for this!!
 

dabanhfreak

Senior Member
Feb 23, 2013
177
59
Melbourne
OnePlus One
solved!! I try to explain how I made it:
http://en.oppo.com/downloads/firmware/driverForFind5.rar
I've downloaded driver for oppo find 5 (!!!) and manually installed it, picking up from here:


Automatically has installed the driver and QHUSB_BULK became qualcomm hs-9008 (i don't remember exactly, but the number was right).
Suddenly I started Oneplus one recovery tool and it worked!!! 44s stock! I spent 6 hours for this!!

Confirmed working for me

Don't use the CM11 restore in the other thread, use ColorOS
Be sure to hit F8 upon boot to disable Signature thingy in Win7

Phone unbricked... I had it sitting for 10 days next to me sweating for a solution.
 

jeffsta

Senior Member
Dec 6, 2008
91
45
Please explain what happened after when u flashed ColorOS? You were just unable to boot into the OS or there was a bootloop at that time also? If it was not in bootloop at that time then I think u did something wrong while flashing CM11.

Yea it was still in a boot loop after I successfully flashed ColorOS and also I cannot get into recovery.
 

nathlynn22

Senior Member
Apr 8, 2013
2,098
241
When I click start in program in color zip folder. Msmdownloader 1 it keeps going red? I'm on windows 7 and got that far. Please help
 

derekk75j

Senior Member
Jul 4, 2014
126
30
Gorizia
Problem is driver. I spent 6 hours to install it. I installed a lot of driver, when i used find5 driver and forced them manually, i resolved. Did you try this?
 

yoitsjustin

Senior Member
Aug 23, 2013
135
13

Thank you so much! This will work even if my phone won't turn on, correct? :)

---------- Post added at 10:25 AM ---------- Previous post was at 10:03 AM ----------


I got this to come up on my W7 comp, but it fails. I don't have access to a WXP comp, can I do this on a mac?

---------- Post added at 11:04 AM ---------- Previous post was at 10:25 AM ----------

I'm having this same issue, it has to do with driver verification which W7 automatically does. I can't find a way to fix it but supposedly on XP there isn't this problem. I don't have access to XP though so I have no idea what I'm gonna do now :(

---------- Post added at 11:19 AM ---------- Previous post was at 11:04 AM ----------

Thank you so much. You just saved my phone!!! This worked for me on W7 with a bricked OPO, I cannot thank you enough!!!
 

derekk75j

Senior Member
Jul 4, 2014
126
30
Gorizia
My device is getting recognized as this whenever I plug in, but it is not digitally signed so I guess MSM installer is not detecting it. What do I do now? :'(
Windows 7 here.

screenshot_122.png

http://forum.xda-developers.com/showpost.php?p=57202390&postcount=257

It seems you are in same condition. Try again. Don't worry, there must be a solution, you have to try and try ...
I had resigned myself after 6 hours(!!!!) but in the end, I did it. Before start to modding, it's absolutely necessary to install driver adb/fastboot in windows/linux. With bricked phone it's very hard.
Do you know anybody who have a opo working? With a opo working, it's easy install driver, and then you'll be able to unbrick your phone.
 
Last edited:

hamzahrmalik

Senior Member
May 31, 2013
1,658
2,018
OK, as promised I wanted to write up more detailed steps on how I unbricked my OPO. First, thanks to all who contributed, found the needed files and solution.

The solution is in fact to download Color.zip from https://mega.co.nz/#!BkpwyYSB!rkYSkFI28vFGuhtsIli-vyDdsb4ZZp1-MX1cLLtaiRo.
After downloading, unzip the archive.

Next, Windows drivers. If you're like me you've already tried different drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then, go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through.

Second note about drivers if that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations. I've tried overwriting these settings and spent half a day messing with it, and I never go the next steps to work properly. I ended up trying installing the drivers from Setup.exe and the following steps on my Windows 2003 server and things worked properly first time. I am not saying that you won't get this to work on Window 7 or 8, but if you're having troubles try Windows XP, that might make a difference.

Anyway, once you have the drivers straightened out, connect your phone to the computer, start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com devices. If you unplug the phone and move it to another port, or computer, it will show your bricked phone on a different line. There is no reason to click in or select at lines, the program knows where the phone is.

Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.

If you don't see your devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.

Anyway, once you see the phone in the list, click Start. You should see the programs starts writing different files to the phone. Each time it writes a file you'll see a progress bar. Once this is going you know you will be good to go... After all files are written, the line with your device will turn green. You're good, unplug and reboot your phone to ColorOS.

If there is a problems flashing the device, the line will turn Red. That's what I was getting on my Windows 7 after like 3 seconds after clicking Start. After moving to Windows 2003, everything worked like a charm.

Once you're on ColorOS and want to go to Cyanogenmod 11S, you have a few options. The easiest way if to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and run the following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin

Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.

That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue. If you're still getting stuck, let me know, I'll see if I can help.

My opo, when plugged in doesnt show in device manager
What can i do

EDIT
fixed mustve done something wrong first time

now it shows up
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 58
    EDIT 1/29/2015
    I am leaving the original post below the line, however please be advised that I created a new forum thread with updated instructions and workarounds for Windows 7 and Windows 8 users. This thread is located at: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
    =====================================================================================================


    OK, as promised I wanted to write up more detailed steps on how I unbricked my OPO. First, thanks to all who contributed, found the needed files and solution.

    The solution is in fact to download Color.zip from https://mega.co.nz/#!BkpwyYSB!rkYSkFI28vFGuhtsIli-vyDdsb4ZZp1-MX1cLLtaiRo.
    After downloading, unzip the archive.

    Next, Windows drivers. If you're like me you've already tried different drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then, go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through.

    Second note about drivers if that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations. I've tried overwriting these settings and spent half a day messing with it, and I never go the next steps to work properly. I ended up trying installing the drivers from Setup.exe and the following steps on my Windows 2003 server and things worked properly first time. I am not saying that you won't get this to work on Window 7 or 8, but if you're having troubles try Windows XP, that might make a difference.

    Anyway, once you have the drivers straightened out, connect your phone to the computer, start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com devices. If you unplug the phone and move it to another port, or computer, it will show your bricked phone on a different line. There is no reason to click in or select at lines, the program knows where the phone is.

    Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.

    If you don't see your devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.

    Anyway, once you see the phone in the list, click Start. You should see the programs starts writing different files to the phone. Each time it writes a file you'll see a progress bar. Once this is going you know you will be good to go... After all files are written, the line with your device will turn green. You're good, unplug and reboot your phone to ColorOS.

    If there is a problems flashing the device, the line will turn Red. That's what I was getting on my Windows 7 after like 3 seconds after clicking Start. After moving to Windows 2003, everything worked like a charm.

    Once you're on ColorOS and want to go to Cyanogenmod 11S, you have a few options. The easiest way if to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and run the following commands in fastboot mode:
    fastboot flash boot boot.img
    fastboot flash userdata userdata.img
    fastboot flash system system.img
    fastboot flash recovery recovery.img
    fastboot flash cache cache.img
    fastboot flash modem NON-HLOS.bin
    fastboot flash sbl1 sbl1.mbn
    fastboot flash dbi sdi.mbn
    fastboot flash aboot emmc_appsboot.mbn
    fastboot flash rpm rpm.mbn
    fastboot flash tz tz.mbn
    fastboot flash LOGO logo.bin

    Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.

    That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue. If you're still getting stuck, let me know, I'll see if I can help.
    9
    Unbricked mine which was in "Qualcomm HS-USB QDLoader 9008"

    I bricked my OPO today, it was shown as Qualcom HS-USB QDLoader 9008 in the device manager of my computer.

    YOU ARE DOING THIS AT YOUR OWN RISK

    Steps to unbrick (only if you are in 9008 mode) :
    1. Download: []https://mega.co.nz/#!BkpwyYSB!rkYSkFI28vFGuhtsIli-vyDdsb4ZZp1-MX1cLLtaiRo[]
    2. Open: Msm8974DownloadTool.exe
    3. One line should look a bit different then the other (in my picture you cannot see this cause mine is not in 9008 mode)
    4. Select the line looking different and click start.
    5. If there is no other looking line unplug your phone and press Vol+ & Power for about 10 seconds. After this replug your phone. And one line should look different.
    After this you are on ColorOS search the oneplus forums for introductions returning to cm.

    PS: I cannot guarantee that it will work and that your device will brick harder ^^. For me it worked.
    6
    Hi @os_man,

    I can help you to find the 3 files you need .....

    Promise us that you will teach us in details (step by step with image) , how to recover hard bricked 1+1 using QPST.
    ok?

    here you will find the 3 required files...

    Open the xml and you will find the partition details and mapping...

    Go there
    https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/

    Download the file ..
    https://mega.co.nz/#!BkpwyYSB!rkYSkFI28vFGuhtsIli-vyDdsb4ZZp1-MX1cLLtaiRo
    807.3MB

    View attachment 2900345

    The exe Msm8974DownloadTool.exe might help , but I can not understand the Chinese lang

    View attachment 2900361


    @timmaaa, kindly help him to use QPST to solve this issue, If he get success, we can learn a new thing from him...
    Thanks


    Of course i will, like i said i recovered a lenovo k910 before (qualcomm snapdragon 800) exactly in same position (blank screen, no lights, no bootloader, no fasboot) but i had all the necessary files like i said, now my opo is in qdloader mode 9008 too ( or 9006, not much a diffrent, 9006 is messed up partition table ). Let me start to work tomorrow (tonight im dealing with the encryted imei of oppo 7). I wish everything goes ok and i recover opo too, the knowledge after to share with who needs, promise. And Thank you.
    5
    find me these 3 files, ill help you to recover your opo (mines too), opo should send us those files ( as moppo does it for find series)



    MPRG8974.mbn
    patch0.xml
    rawprogram0.xml

    All the other files , images i already have in my backups.
    And dont be so sorry, you flashed wrong kernel, ok it was a mistake, but many had their phones in 9008 too, they just wanted to return to color od from that silly cm rom's. Mine is dead too (has the diag port still, thank God), opo should, "must" even send us those files, the rest is on me,
    Greetings.

    WRONG INFORMATION !
    Web is full of info how to recover from 9008 mode with the right files of course, why you keep saying that ???

    Hi @os_man,

    I can help you to find the 3 files you need .....

    Promise us that you will teach us in details (step by step with image) , how to recover hard bricked 1+1 using QPST.
    ok?

    here you will find the 3 required files...

    Open the xml and you will find the partition details and mapping...

    Go there
    https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/

    Download the file ..
    https://mega.co.nz/#!BkpwyYSB!rkYSkFI28vFGuhtsIli-vyDdsb4ZZp1-MX1cLLtaiRo
    807.3MB

    color_os_official_opo.jpg

    The exe Msm8974DownloadTool.exe might help , but I can not understand the Chinese lang

    Msm8974DownloadTool.jpg

    Yeah you can recover, with a jtag. If you know how to do it without jtagging the device please enlighten us.

    Transmitted via Bacon
    @timmaaa, kindly help him to use QPST to solve this issue, If he get success, we can learn a new thing from him...
    Thanks
    4
    I just noticed that it's showing up as QHSUSB_BULK on your PC, you're bricked. I believe the only possible solution is to have a jtag repair done on it. But, you're probably gonna have a hard time finding someone that does jtag repairs on this phone.

    All in all, you've learned a really important (and expensive) lesson here. XDA is made up of device-specific sections, when you own a device you absolutely must stay within your device's subforum.

    Transmitted via Bacon