FORUMS

Sunday Debate: Great Camera Hardware, or Software?

Join us in a fun Sunday Debate on phone cameras. Come with your opinions and feel … more

XDA Picks: Best Apps of the Week (Apr 25 – May 1)

Apps are at the front and center of any smartphone experience, and with over a … more

Lollipop Xposed Framework Alpha 4 Released

Good news to all Xposed Framework fans. XDA Senior Recognized … more

Do You Rock Two Phones?

A few people in the comments were surprised to find out that a number of the XDA staff actually use two phones … more
Post Reply Subscribe to Thread Email Thread

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

15th April 2015, 11:32 AM |#381  
Junior Member
Thanks Meter: 0
 
More
The only problem and others have is after you press start, it only do 8974_msimage.mbn and then stops.
The Oneplus disconnects, Qualcomm HS-USB QDLoader 9008 disappears from device manager.
Can someone focus on this problem, the Qualcomm HS-USB QDLoader 9008 disconnect after doing the first file 8974_msimage.mbn. Thnx.
Yes, we all followed the instructions to the letter before this, happend.
 
 
15th April 2015, 02:12 PM |#382  
pxdx's Avatar
Senior Member
Flag Kolkata
Thanks Meter: 120
 
More
Thumbs up
Quote:
Originally Posted by netbuzz

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/onep...s-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!rkYSkF...p1-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/onep...9-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/onep...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.

Thank youuuuuuuuuuuuuuuu.... Brilliant!!
18th April 2015, 11:13 PM |#383  
Junior Member
Thanks Meter: 0
 
More
thanks for saving my phone
You can press F8 on Win boot and choose “Disable Driver Signature Enforcement", solved my unsigned driver problem in win7 64

Quote:
Originally Posted by netbuzz

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/onep...s-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!rkYSkF...p1-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/onep...9-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/onep...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.

21st April 2015, 12:50 AM |#384  
Junior Member
Thanks Meter: 0
 
More
hanging at 1+1 logo, no fastboot
hello guys,
i have a big problem. 2 weeks ago i bought a OPO from a guy. the device was ok. He said that it is rooted. for me it wasnt a problem. Then one day i got an update. at restart the opo started till the 1+1 logo and freezes. I was not able to get to the fastboot or recovery mode. Everytime i hold power and vol+(vol-) button the phone does the same thing. It comes to 1+1 logo and freezes. I was not able to get to recovery mode, so i plugged it to my notebook ( win 8.1). First i saw "another device" at device manager. with drivers i managed the device manager to show "android phone" or "android composite interface" or something like that. But i cant see any device in windows explorer. I also tried the color os moethod. But the power and vol button combo didnt work. One day i opened the back cover. I couldnt believe my eyes. the volume button has no connection to the phone. It easily fell down. so i cant specify the problem. Maybe the recovery mode would work but the vol button isnt soldered. When i use the adb cmd a device is recognized but its offline. i have no idea how to unbrick my phone. Please help me guys!
25th April 2015, 12:24 PM |#385  
Junior Member
Thanks Meter: 0
 
More
No one an idea?
30th April 2015, 09:14 PM |#386  
Quote:
Originally Posted by netbuzz

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/onep...s-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!rkYSkF...p1-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/onep...9-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/onep...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.

Sir the mega link doesn't work for me.
I live in India Mega is banned in India.....can u provide a alternative link for Color.zip?
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in ONE Q&A, Help & Troubleshooting by ThreadRank