yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] eslame2014:
i'm downloading this file : ColorOS

This is respectively which you've done : ( Then followed these steps )

1- Unlock Bootloader

2- Install Custom Recovery (TWRP)

3- Root Device

4- Install Color OS

Notice

When I entered recovery mode

I did not find TWRP

I found only Orginal recovery.

ـــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ

I do not know what happened!! :(

[/MEDIA}=youtube]gKYAEf2j7_M[/MEDIA]

youtube.com/watch?v=gKYAEf2j7_M
[ONE Q&A, Help & Troubleshooting] -Already Exist-:
I have same problem but with CM11...
[ONE Q&A, Help & Troubleshooting] un1ocked:
i want to flash my phone so that i can read as disk partition on windows/linux

can i use QPST?
[ONE Q&A, Help & Troubleshooting] eslame2014:
When I entered recovery mode

I did not find TWRP

I found only Orginal recovery.

---------- Post added at 12:03 PM ---------- Previous post was at 11:39 AM ----------

I have already taken backup of twrp before anything.

When you press (vol + and power) Shows ( ColorOS recovery )
[ONE Q&A, Help & Troubleshooting] kronborn:
Same problem, did not find any solution yet.

Please notice me if you got any.

Thanks.
[ONE Q&A, Help & Troubleshooting] Lennydk87:
Hello.

I got the same problem with completly black screen, and I cant seem to get the drivers working, I've tried both the colorOS USB drivers and Qualcomm 2012 drivers, on a Windows 8.1 laptop and Windows XP laptop, both computers are displaying QHSUSB_BULK in device managers, but I cant seem to find a working driver, everytime I try a driver it says it's not working with the choosed device (QHSUSB_BULK).

Anybody who can help me sorting out the driver problem? :)
[ONE Q&A, Help & Troubleshooting] os_man:
Flash your phone why or how ? You dont do any flash in qpst, you only rescue damaged boot partitions.
[ONE Q&A, Help & Troubleshooting] un1ocked:
prgramming the bootloader via qpst?
[ONE Q&A, Help & Troubleshooting] kronborn1:
Can you please point me to solution for flashing these files via Msm8974DownloadTool.exe ?

I'm able to flash (probably) only 8974_msimage.mbn. After that my phone is disconnected and line in changed from Com to Usb. Qualcomm driver disappeared from the device manager.

Could you please describe how I can do this rught ?

I ques it probably can be done by changing the Setting.xml ?

---------- Post added at 11:20 PM ---------- Previous post was at 10:52 PM ----------

I don't understand how you can use driver from ColorOS. It has an ADB driver which has no VID_05C6&PID_9008&REV_0000

HW IDs in list.

How it was displayed in your device manager ?

Did you modify the ColorOS config files in any way before flashing ?

I has a 8974_msimage.mbn progressing in Msm8974DownloadTool.exe and after that phone is disconnected - don't you meet the same problem ?
[ONE Q&A, Help & Troubleshooting] remon1995:
Tried the solution on XP, drivers were no problem.

The program ran smootly and saw the color os boot logo.

But after a while the screen goes to black and my pc recognizes 4 drives :S.

1 drive is unaccessible, 2 needs to be formated to accesed and 1 show 2 folders with some weird files of which I attached a screenshot.

It cant see color os so I can only turn the phone off, it just doesnt boot the os.

I can get into the color os recovery screen but the fastboot screen is still black.

Can someone help me?

PS. when I run the md5 check in the color os zip it gives me some fails, is this normal. I downloaded it a couple of times.
[ONE Q&A, Help & Troubleshooting] Lennydk87:
Im very frustrated about this problem, because I can easily make the phone appear in device manager as qhsusb_bulk, but I can't install any drivers, I've tried all of these on Windows XP SP3, Windows 7 32 bit and Windows 8.1 pro 64 bit:

Qualcomm 2012 drivers, Color OS (as described in the guide), Oppo Find7, Oneplus USB.

Windows is just telling me the drivers/software aren't right for this device. :confused:

I can provide with all kinds of log files from Color OS driver folder if that would be anyhelp?

Im just very frustrated because my OnePlus One have been in this state for over a week now. :eek:

I hope anyone can help me restoring my OPO back to life.
[ONE Q&A, Help & Troubleshooting] DirtyDroidX:
I've been in a similar position. I could not boot to fastboot but I could boot to CM recovery. So I chose sideload option and tried pushing a few zips of ROMs etc . They all failed but it must of aligned a partition . I was then able to boot to fastboot and restore to factory settings.
[ONE Q&A, Help & Troubleshooting] kronborn1:
Could please describe the exact steps you're following ?

---------- Post added at 09:38 PM ---------- Previous post was at 09:23 PM ----------

Could you please tell me which util on your attachement and how I can get it (URL) ?
[ONE Q&A, Help & Troubleshooting] djdenero:
I love you in a non gay way! :)

Man I fcuking luv YOU! I have been tearing my hair out. that worked! phewww
[ONE Q&A, Help & Troubleshooting] skyguy126:
If you can get into fastboot mode then you are golden. If not, you really don't have a choice. JTAG is probally your only option or send it into OnePlus for repair.
[ONE Q&A, Help & Troubleshooting] stefano1996:
Hello guys I have this problem too but my phone is stuck on bootloop

And I can't boot on fastboot and recovery plus someone help me
[ONE Q&A, Help & Troubleshooting] aleksik:
Ummm, you didn't read my next comments? I wasn't able to get into fastboot, but still got it working. I have had my OPO working for almost 3 months already :)

Sent from my OPO powered by Robbie's CM11 nightly & AK kernel
[ONE Q&A, Help & Troubleshooting] os_man:
Dear un1ocked, not programing, if your partition table is out of order (no boot partition, phone cant boot), you can send the flasher (MPRG8974.mbn, not hex, mbn format) and the bootpartition (8974_msimage.mbn) to the phone, the phone does not come alive but is ready complete system restore. Whats the exact problem ? Maybe there is an other way.

---------- Post added at 04:24 PM ---------- Previous post was at 04:21 PM ----------

Still talking about jtag ? :) Days passed, i think i proved no need for jtag as long as you have any port from the phone, cheers.
[ONE Q&A, Help & Troubleshooting] janguo:
os_man: I've been reading the forums (this and others) and I'm unable to find clear instructions on how to send just MPRG8974.mbn and 8974_msimage.mbn to the device. I've tried QPST 2.7 build 411, but to be honest, I have no idea what I'm doing, and it seems to want a .hex file (which I don't have)

I've looked through the QPST manual, and countless XDA threads, but haven't been able to get any further ahead.

Would you mind quickly explaining the process to do this? I haven't had any success getting the download tool from the Color OS image to flash my device, even though the drivers seem to be installed correctly. (I've tried on three XP boxes, one Vista, two Windows 7 and two Windows 8.1 computers) Both the ColorOS drivers and the Qualcomm drivers seem to work fine for me on every computer, and they all detect the phone just fine as 9008 sometimes as QHUSB__BULK, and sometimes as QHUSB_ARMPRG, but never any driver errors.)

Using the Qualcomm download tool in color.zip, the phone is detected, and appears to being processing the 8974_msimage.mbn, but then quickly turns red and stops.
[ONE Q&A, Help & Troubleshooting] os_man:
First of all, the port 9008 should turn to port 9006 (diag ) after the phone gets 8974_msimage.mbn and MPRG8974.mbn. No need for hex file as the mbn file is the same (mbn is qualcomm format). If drivers are ok as you say (seems so), oh and no need for Xp or Win7 32bit, you can do every step on a 64 bir 8.1 even ( as long as you work in Test Mode you can install any driver withou any problem).

The picture is taken from from Lenovo thread from a forum i cant remember, its for unbrick of Lenovo K910, but the way is the same. "flash_local.xml = Settings.xml in color os folder, you just correct the path's ( the path of 8974_msimage.mbn and MPRG8974.mbn ) by opening it. Then as decribed in the picture, unthick "Program MMC device", dont select it, we must first send mbn's, so only "Program Boot Loaders" should be selected. You just do first 3 steps, then hit Download, if the port turns from 9008 to 9006, the rest is easy, we will continue, please let me know if you can come this far.
[ONE Q&A, Help & Troubleshooting] os_man:
PS1: Qpst versiyon 411 is ok, dont change.

PS2: This can be also done with Download tool in color os rom folder, if that tool can send both mbn's ( done before), port turns to 9006. But try Qpst first.
[ONE Q&A, Help & Troubleshooting] kronborn1:
Could you please tell what this response mean in QPST?

Device mode = Sahara on port 10000

server event monitor enabled

path for selected COM port = "_HCD1!hub:0!dev:0"

Timeout waiting for device

device wait found 0 0
[ONE Q&A, Help & Troubleshooting] janguo:
When I follow these steps using eMMC Download tool, I get the error: Image Download Failed. Cookie(if present) not received. My device does not change from 9008 to 9006.

I have also tried with the download tool included in color.zip, and while it recognizes my phone, I can see that it starts trying to process 8974_msimage.mbn, but the line quickly turns red, and then the text changes to a line that includes the word Sahara. I can't read the rest of the text, which I presume is in Chinese.

Any ideas?
[ONE Q&A, Help & Troubleshooting] Lanchon:
hi,

my OPO is just fine. out of curiosity, i wanted to reach the qcomm download mode and see what can be done with it.

in particular, it seems that if the partition table or bootloader is borked, it goes into a mode in which it exports all of the eMMC as mass storage. at least that's what i understood by reading this thread.

is this true? what are the conditions?

also, if i press vol_up+power with the phone connected to my linux box i get this, the 9008 mode:

[747116.603750] usb 1-1.2.1: new high-speed USB device number 21 using ehci-pci

[747116.697320] usb 1-1.2.1: New USB device found, idVendor=05c6, idProduct=9008

[747116.697331] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[747116.697337] usb 1-1.2.1: Product: QHSUSB__BULK

[747116.697342] usb 1-1.2.1: Manufacturer: Qualcomm CDMA Technologies MSM

[747116.697921] qcserial 1-1.2.1:1.0: Qualcomm USB modem converter detected

[747116.698150] usb 1-1.2.1: Qualcomm USB modem converter now attached to ttyUSB0

what is it? it does not expose the eMMC which would be a terrible security whole. but what is it? where is the SoC running from? internal factory ROM? is the cpu expecting code to place in ram and run? then i supposed it has to be signed by qcom right?

what are 8974_msimage.mbn and MPRG8974.mbn that you can send in this mode? are they a monitor/debugger loaded in ram or something gets flashed to the eMMC? are they generic or specific for opo or colorOS?

thanks!
[ONE Q&A, Help & Troubleshooting] kevinf28:
hello all, my buddy has the OPO 64G and was in the same boat: regular/recovery boot stuck at boot logo. I have read all the page since netbuzz posted his legendary Color OS fix. which was successful (green) with Qualcom drivers. fastboot now has some chinese characters.

Fastboot Oem info reports:

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

Doing an oem unlock reboots back to logo, or back to fastboot with same state. I tried the fastboot boot twrp.img, which the chinese fastboot screen goes bright, but hangs there.

Q: My understanding is, that the COS method would unlock my device. It did NOT. Device still does not boot / unlock! What am I missing ??? I thought the included "persist.img" would fix the boot issue (http://xdaforums.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061/page2)

thanks again for all your hard work.
[ONE Q&A, Help & Troubleshooting] kevinf28:
Here are some helper information for other lost peoples:

Valid partition table QHSUSB mode: Vol+ & Power while USB CONNECTED

Broken partition table QHSUSB mode: Vol+ & Power while USB CONNECTED

appears in 9006 mode

Fastboot: Vol+ & Power while USB DISCONNECTED

Note: this failed message (top right button) is 100% okay.. the MsM tool does an Md5sum (checksum) on the files in your LOCAL directory, which have been modified by Netbuzz (eg: persist.img). I have seen many people in this thread thinking it is checking your phone. It is NOT

[IMG="Failed"]http://xdaforums.com/attachment.php?attachmentid=3043150&stc=1&d=1417457760[/IMG]

Msm8974DownloadTool.exe detecting a device in a com port in slot 1.

[IMG="Detected"]http://xdaforums.com/attachment.php?attachmentid=3043148&stc=1&d=1417457749[/IMG]

It switches from "COM" to text in the screen shot right after it switches to 9006 mode (after the first 1-2 files).

[IMG="successfully flashing partition"]http://xdaforums.com/attachment.php?attachmentid=3043298&stc=1&d=1417465178[/IMG]

MsM complete, shows device in green. Note: some people were confused why the buttons are greyed out still. This is intended for factory, so its constantly auto-detecting and flashing dozens of phones on multiple ports. "Stop" turns off this feature, so thats completely normal.

[IMG="done!"]http://xdaforums.com/attachment.php?attachmentid=3043149&stc=1&d=1417457749[/IMG]
[ONE Q&A, Help & Troubleshooting] bsquirrell:
I have read this thread from top to bottom, scared me witless. I haven't even unlocked the bootloader yet, Having trouble getting Fastboot on my computer, Windows 7-1 64 bit, and cmd says it cannot find the path specified, etc., etc., Now I'm not even sure if I want to try,, too chicken:confused:
[ONE Q&A, Help & Troubleshooting] kronborn1:
Great work for classification OPO devices mate )

But I cannot find my One there.

It appears in system as :

Driver Description Qualcomm HS-USB QDLoader 9008

Driver Date 30.11.2006

Driver Version 2.0.3.6

Driver Provider Qualcomm Incorporated

INF File oem127.inf

Hardware ID USB\VID_05C6&PID_9008&REV_0000

I have following screens:

Before start:

After start press:

After 1st file progress done:

After progress end device disappears from Device Manager.

This happens with all drivers on all platforms I tried.

Probably you have some propositions to try ?
[ONE Q&A, Help & Troubleshooting] kevinf28:
I am using ColorOS drivers for Fastboot, and Qualcomm 2012 drivers manually installed for Q_* (right click on device in Hardware Manager), ensure all others are uninstalled. I am directly connected (NO USB HUB), to Windows XP machine.

It switches from "COM" to text in the screen shot right after it switches to 9006 mode (after the first 1-2 files).

[IMG="successfully flashing partition"]http://xdaforums.com/attachment.php?attachmentid=3043298&stc=1&d=1417465178[/IMG]
[ONE Q&A, Help & Troubleshooting] kronborn1:
I see... I never got the 9006 mode enabled. I guess because of 1st file flashing interruption. I tried Qualcomm 2012 drivers too on XP, 7 and 2003 machines - behavior always the same...

Sometimes I see following screen:
[ONE Q&A, Help & Troubleshooting] kevinf28:
note: after it switches to 9006, i had to go back into device manager, and install the driver again. have you rebooted your PC ? I had to do that too, after the initial color drivers.

so, after it disapears from device manager, I assume you have unplugged and replugged the cable without hitting additional buttons? Absolutely nothing being shown in device manager sounds wrong IMO... maybe its hiding? Use a program like Aida 64 to look through all USB devices connected to system.
[ONE Q&A, Help & Troubleshooting] kronborn1:
Could you please clarify when the PC reboot is needed ?

I have no any visual problems with drivers re-installing or updating ...

And I never got color driver working for me (

It always writing somwthing like

Driver have been installed! ErrorCode(10): 183. ErrorCode(16): 0x000000b7

InstallDriver terminated.

Nope - I always holding the Power button for 20+ seconds before re-switching ... May this is mistake ?

Sometimes if I did not press Power for >20sec it appears as Unknown device, but I cannot do anything with it in that state (
[ONE Q&A, Help & Troubleshooting] kevinf28:
Reboot just after installing all the drivers for the first time.

get your device back to this:

"After 1st file progress done:

Attachment 3043281"

Check device manager for 9006 device / anything "unknown". Look at its properties for its hardware ID (a lot easier with Aida!!)... and see if it matches the device IDs I posted above.

Unplug and plug device back in without pushing any buttons.

Again check device manager / Aida.
[ONE Q&A, Help & Troubleshooting] jam90:
PROBLEM

You're on Windows 8.1 and the process goes like this:

1)

2) then click start, and it goes like this

3)and then, the device reboots itself as 9006, but msmdownload tool give you this error

SOLUTION

Just run Msm8974 Download Tool.exe as "Windows XP Service Pack 3" compatibility mod.
[ONE Q&A, Help & Troubleshooting] kevinf28:
ensure you "Run as Administrator"
[ONE Q&A, Help & Troubleshooting] jam90:
thanks, but the problem was the compatibility mod. I modified my previous post, so other people can see how to solve this kind of problem
[ONE Q&A, Help & Troubleshooting] kevinf28:
"mode" (sp) I assume? Glad it worked out.

did color OS boot fully? recovery? was your device locked before? did it unlock your device? I got all the way green, but im still stuck :( http://xdaforums.com/showpost.php?p=57173624&postcount=248
[ONE Q&A, Help & Troubleshooting] jam90:
all went perfectly!

You have to right-click on the exe of Msm8974 tool, check the "Compatibility" page and set it as "Windows XP Service Pack 3". And you'll see that the process won't stuck anymore
[ONE Q&A, Help & Troubleshooting] kronborn1:
Mate, I installed the AUDA64 finally and it find my device almost always in mode "Valid partition table QHSUSB mode: Vol+ & Power while USB CONNECTED".

Is this a valid mode for using with MSMTools ?

Or I need to use some tools to move it to another one ? (9006?)

Still the same problem - device disconnected after flashing and AIDA cannot find it too (
[ONE Q&A, Help & Troubleshooting] jeroservice:
thank you

Thanks for Nia topic I've recently come across the same problem
[ONE Q&A, Help & Troubleshooting] kevinf28:
Yes, that is the correct mode. As long as you are directly connected to a physical (not Virtual Machine), using no USB hub, running as administrator, no modified files in Color OS, installed Qualcom 2012 drives, and a quality USB cable, there is no reason for it to disconnect like that.
[ONE Q&A, Help & Troubleshooting] kevinf28:
Progress! I was able to Unlock my bootloader without a ROM, thanks to os_man, a full 1024KB aboot.img and MsMDownloadTool. Will post a guide later.

Downloaded http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH44S-bacon-signed-fastboot.zip

plus downloaded persist and reserve4.img from http://xdaforums.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

I still can't boot system or recovery. OPO hangs at the OnePlus boot logo. :( :( :(

What am I missing ??
[ONE Q&A, Help & Troubleshooting] mehernosh:
Thank you so much [MENTION=4645240]netbuzz[/MENTION] your effort is really appreciated.
[ONE Q&A, Help & Troubleshooting] skyguy126:
If fastboot works try and flash a custom recovery and adb sideload a ROM into it.
[ONE Q&A, Help & Troubleshooting] kevinf28:
fastboot boot recovery.img hangs in fastboot (screen backlight turns on is all).

---------- Post added at 08:35 AM ---------- Previous post was at 08:34 AM ----------

https://www.dropbox.com/s/659jmf2wr2arn8y/emmc_appsboot.mbn?dl=0 this is a full 1024K UNLOCKED aboot.img, pulled from a working phone with cm-11.0-XNPH44S-bacon-signed-fastboot.zip installed (CM11 / ColorOS only provide 300K file).

Instructions:

-Follow the OP https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/ but with these changes

-Download the patched aboot.img

-Replace emmc_appsboot.mbn in ColorOS folder with my copy

-Run MsM Download Tool as instructed

-Wait until it goes green.

You now have an unlocked bootloader, even if your ROM is broken / won't load / bootloop.

fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: true

(bootloader) Charger screen enabled: false

OKAY [ 0.005s]

finished. total time: 0.005s

Didn't solve my problem completely, but brought me one step closer. Now fastboot erase/flash/boot cmds don't give permission denied.
[ONE Q&A, Help & Troubleshooting] Lanchon:
so you have working fastboot, but still cant make ur phone go? can you fastboot boot a kernel? what happens if you boot a recovery?
[ONE Q&A, Help & Troubleshooting] Orvils:
I am not sure if this is right place to ask but I recently got OnePlus One and it doesn't turn on. When I connect it to charger (doesn't matter what charger, tried original, note 4, G2, S4 or pc usb port) it vibrates constantly. All the time it is connected to charging cable it just vibrates. If I disconnect it will continue to vibrate for some time (I guess until battery is depleted) I can neither turn it on or turn off the vibration by holding any of the buttons.

Sometimes the camera flash also turn on when connected to charger.

Has anyone had similar issue?
[ONE Q&A, Help & Troubleshooting] Lanchon:
and this is the result of you doing what?
[ONE Q&A, Help & Troubleshooting] anandbibek:
Have you tried power + volume down for turning on?
[ONE Q&A, Help & Troubleshooting] Orvils:
Yup. I tried power, power + volume down and power + volume up. Nothing works. Phone just vibrates.
[ONE Q&A, Help & Troubleshooting] anandbibek:
What happens if you connect to PC? Anything shows up in device manager? At least any unknown device?
[ONE Q&A, Help & Troubleshooting] nickizm:
I have a problem with my recovery. I can't fastboot oem unlock, factory reset, or boot into recovery.. each time I try any of those my device reboots into the 1+ logo and crashes and therefore I can't unlock my phone. My fastboot does work apart from not being able unlock it. everything else works on my opo, but the recovery. I was wondering if I could use this method to repair it?

Cheers,

Nick
[ONE Q&A, Help & Troubleshooting] Nikouy:
Do the capacitive buttons blink?

Try holding volume up + power and then connect it to the computer.

Open the adb terminal and type: adb devices and then fastboot devices? Do you get anything?

If the answer is no, hold the two vol buttons + power, connect it to the computer, adb, anything?

Something similar happened to me and I was able to access to the shell: adb shell, and reboot the phone from there and it booted.
[ONE Q&A, Help & Troubleshooting] Orvils:
From what I read for different phones is that maybe power button is stuck. I will put motherboard in alcohol bath over night and will try the things you suggested tomorrow.
[ONE Q&A, Help & Troubleshooting] Lanchon:
if you are rooted, or can root, you can unlock your fastboot via a root command from android. if you can't root, then you would usually be SOL. but then there is this method, that apparently doesnt even need anything in the eMMC, and so should always work, no matter the state of the phone. but... afterwards you will still need your "efs" data, so if that gets lost at some point and you dont have a backup, you will loose your imei forever.
[ONE Q&A, Help & Troubleshooting] nickizm:
My device isn't rooted and it's also locked. basically I can't oem unlock because my recovery is corrupted or damage? when i fastboot oem unlock it goes to reboot and crashes.. I've no idea what SOL is or even start eMMC.. If there is a step by step tutorial I would definitely give it a try. I would also need to know how to back up my efs data..

I was thinking colorOS might help if it can be done on a locked device???
[ONE Q&A, Help & Troubleshooting] Lanchon:
SOL means $#!+ out of luck :(

eMMC is the internal "hard drive" of the phone

color might work, read this whole thread and try it