yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] Chinaroad:
hi all, after flashing a rom through TWRP and after clicking reboot,the phone wont startup again, no boot no recovery and no fastboot, and even when i plug it in the pc there is nothing on the device manager, no new devices,and after trying the whole tutorial .

i'm afraid the phone is dead or something , i'm sure the partitions got damaged or something but how to repair it when the usb is not recognized(as i said i see nothing in the device manager even if i plug it while pushing power+vol+)

thx for the help

BTW the drivers are good because i tested a OP of a friend and a shows crectly in the MSMDownloader

EDIT:WOHOOOOOOOOOO?I DONT KNOW HOW BUT AFTER LEAVING IT CHARGING AND RETRYING IT GET DETECTED,FLASHED THE ROM AND IT'S WORKIIIINNNGGGG WOOOOHOOOOO THX FOR THE HELP OF EVERYONE(YES I READ ALL THE POSTS) IF SOMEONE NEEDS HELP PM ME
[ONE Q&A, Help & Troubleshooting] stevenswall:
^How long does this process take? Do I need to wait for an hour, or does it just take a few seconds?
[ONE Q&A, Help & Troubleshooting] Peninaa:
Ha!

This has happened to me before, I just plug it in a wall mounted charger and then it vibrates and comes to life :cool:
[ONE Q&A, Help & Troubleshooting] kronborn1:
Hi ! Actually I has no Sahara after flashing (not each time at least). My phone is disconnected right after attempt to flash it first time.

It's not visible in Device manager and has a *USB* string in MSMTool. I don't know how to resurrect it and stopped trying - just left it for the parts for another One (or probably any new solution like a JTag).

Actually if you have a Sahara each time - probably you could try to re-install the driver right after flashing, or re-connect it without pressing other buttons. Or, maybe - try QPST. If you'll have a 'cookie' issue like me - it's a hardware failure. Your case is very close to mine, but probably you have a little bit more chances for success.

Good luck!
[ONE Q&A, Help & Troubleshooting] nikolaouanes:
Hi there os_man I did the same thing with the lenovo k910 and the phone isn't turning on and screen is black with QHSUSB_BULK showing on windows. Since you have recovered the phone can you please reply what you did to recover the phone? :)
[ONE Q&A, Help & Troubleshooting] soralz:
Nice, I also recovered my phone after changing the bootlogo on CM12, this tool saved me!
[ONE Q&A, Help & Troubleshooting] os_man:
answer is k910 qpst rom and miflash flash tool, after you install right drivers of course.

http://www.androidbrick.com/download/miflash-2012-11-06-0/

http://www.androidbrick.com/download/qualcomm-qpst-diag-drivers/ ( whats your phone ?)
[ONE Q&A, Help & Troubleshooting] nikolaouanes:
Hey man thanks for getting back to me... I tried QPST and MiFlash on both windows 8 and XP and the results are as follows: I can't turn the LED on my phone to blue, it only blinks red for 1-2 seconds then restarts led blinks then restarts constantly.. That only happens if I launch QPST configuration or eMMc, otherwise it is just recognised as qualcomm hs-usb 9006. Now using eMMC i see the phone after clicking download (before program MMC device) BUT in the window that you see the drives I can see my hard drive and the phone but the status of the phone is NOT writable so I can't flash anything on it :( I tried MiFlash on XP, and the process finishes, but the phone gets recognized as BULK again in device manager and it still doesnt switch on... I think that the problem here is that I need to find a way to format the drives in the phone to disable the write protection on them.. Should I format them in windows? BIG thanks for your answer :) :good:

My phone is K910 vibe z dual sim.
[ONE Q&A, Help & Troubleshooting] boby08:
Hi ! I tried to apply this solution to my OpO... But when I plug my phone, windows (XP, 7 and 8) recognizes an "unknown device" and not a "QHSUSB_BULK" or "Qualcomm HS-USB QDLoader" device.... Any idea ? How can I fix it ? :confused:

EDIT : It's ok !! After so many tries, my computer (win7) has reconized my OpO !! :)
[ONE Q&A, Help & Troubleshooting] mumumbas:
Hello ...after last update my phone is black screen, no fastboot, no adb, no factory reset, no power on. I read this topic but does not work. Win XP -- different driver -- no anti-virus & firewall. After 20s power on button i have Qualcom HS-USB QDLoader9008 (com4), but after 10s Power+VolUp i have unknown USB device. If I start flash my phone ---- 8974_msimage.mbn - 8974_msimage.mbn - 8974_msimage.mbn....

I try different cable and port .... and other computer.... different Windows

Please help me ... Thanks

PS: Sorry for my English
[ONE Q&A, Help & Troubleshooting] os_man:
"otherwise it is just recognised as qualcomm hs-usb 9006", it should be 9006 so miflsh recognizes it :) You can fallow my guide here ..

http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/
[ONE Q&A, Help & Troubleshooting] mumumbas:
Hello i read yours Ultimate Qualcomm Snapdragon Unbrick Guide but if i try to flash over MiFlash i have error 0x800700b

Help me pleas
[ONE Q&A, Help & Troubleshooting] os_man:
Did you tried Msm8974DownloadTool inside the rom packet, solves many bricks.
[ONE Q&A, Help & Troubleshooting] mumumbas:
Yes I try ... but not work .... my phone do not enter in "Qualcomm HS-USB Diagnostics 9006" after flash 8974_msimage.mbn
[ONE Q&A, Help & Troubleshooting] picasso82:
I got into my hands OPO 64GB. History unknown. What it does is: vibrates every 20sec when power button keep pressed. Nothing comes up on screen.

When VOL UP + Power pressed it appears in Device manager as QHSUSB_BULK.

So...looks like hard brick. After 2 days of reading posts I managed to perform:

Install proper drivers from Qualcomm 2012.rar

https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0

Also tried drivers from MiFlash folder. Same results.

1. Successful flashing with Msm8974DownloadTool - all according to http://xdaforums.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Result: nothing changed, still black screen, vibrates every 20 sec, no joy

Than I found Ultimate Qualcom Snapdragon Unbrick Guide and done as follows:

2. flashing with MiFlash - successful but again no joy - still black screen

Finally I done flashing with

3. QFIL

All files taken from Color.zip

guess...same result, nothing changed, brick brick brick

Please see screenshots as prove of completed flashing, programming, unbricking .... 2 days and no joy

Does it mean my OPO is dead ? Why it doesn't wake up ?

Motherboard from OPO donor is only solution ?

os_man You said in Your Ultimate guide You saved many bricked oneplus smartphones. Any idea what else can I do with my nice, shiny brick ?

Forgot to add - https://www.youtube.com/watch?v=7Bmftcxmz8U - video from flashing my OPO with Msm8974DownloadTool. Maybe somebody can make any use of it.
[ONE Q&A, Help & Troubleshooting] mumumbas:
Pleas show screen how you flash with MiFlash .... I have error 0x800700b Thanks
[ONE Q&A, Help & Troubleshooting] os_man:
After you flashed color os with miflash, as i can see you can do that already, try pressing power on key more then 30 seconds. Thats the trick after miflash flashing.

---------- Post added at 02:26 PM ---------- Previous post was at 02:14 PM ----------

In one picture i see you are on 9006, next you are on 9008. Which port are you on now ?
[ONE Q&A, Help & Troubleshooting] picasso82:
I'll try trick You mentioned with Miflash.

I knew it somebody gonna ask for that damy ports.

Reg ports: to open 9008 I press power + volup for 10 sec and OPO is detected in Device

manager as 9008.

to open port 9006 I do the trick: open Msm8974 with admin rights, connect OPO to PC, it's recognised as 9008 and appears on the Msm list and then I press start, after flashing of first file OPO disappears from Device manager and after second it's connected back but with port 9006, than I press Stop button in Msm, close Msm8974 and voila - OPO stays connected with open port 9006. After that I start flashing with Miflash which ending up with success as You could see on screenshots.

Once I'm back from work I'll try trick with pressing power for over 30sec. once flashing is done.

By the way to come back to 9008 state I press power + vol up

I don't know what exactly theory lies behind these ports - but when I flash with with QFIL whole process it's done while port 9008 is open. It doesn't switch to 9006 at any of the flashing stages

-------------------------

Just came back home. Done another successful flashing with Miflash. Than was pressing power key for around 60sec and OPO was just vibrating every 5 sec and nothing. Again black screen.
[ONE Q&A, Help & Troubleshooting] nikolaouanes:
Hey man, your guide made me reach 99% to the solution! I am sure I am close, here it is: I flash it using MiFlash in Windows XP, everything is fine, it goes to 100%, it says operation finished, but still black screen. Only difference with your pics is that under device in your pics it shows the port (COM11 or COM9 or whatever) where mine it shows \\?\usbstor#disk&ven_qualcomm&prod_mmc_storage&rev_1.00#7&93e75f5&0&1234567890abcdef&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}... I thought maybe pc doesnt recognize the port correctly so during a flash i pulled the usb out and operation stopped because i unplugged phone. So it DOES recognize successfully the phone... so what is the problem i dont understand :(
[ONE Q&A, Help & Troubleshooting] picasso82:
Riddle of black screen after successful flash still unsolved. I posted my problem on oneplus one official form as well but there are people posting exactly same issue, no one came with solution so far. Is it possible that some part of motherboard is damaged ? Shall we wait and look for solution or it's hopeless case ?
[ONE Q&A, Help & Troubleshooting] WrathofIsaac:
Holy mother of god. Dude thanks a ton for this. I had given up. This worked like a charm. If anyone has questions ama. I did this on a windows 8.1 machine with no problems.
[ONE Q&A, Help & Troubleshooting] os_man:
i will give same answer, after miflash finishes, "operation succesfully", unplug the usb cable from opo, press the power key about 30 seconds until it vibrates, it should come alive.
[ONE Q&A, Help & Troubleshooting] nikolaouanes:
nono I have the K910 vibe z not the opo. I tried to flash different mprg i found online that the old one was not good but still nothing... Maybe there was something I didn;t do? But the Miflash says operation succesfully :/ You said you did it on the k910 before right?
[ONE Q&A, Help & Troubleshooting] os_man:
Yes many times, sorry asking this again, i dont read backwards, your k910 shows qualcomm 9006 port when connected to pc ? If yes, miflash is your saviour, but be carefull with qpst roms, there is a model named k910L too ( one sim ), dont mix the roms.

Did you tried Qfil from qualcomm as flasher ? Its new, replaces "emmcswdownload" from 411 build, i think its worth to try, you can download it from androidbrick.
[ONE Q&A, Help & Troubleshooting] visel7:
I followed the steps but after uninstalling the QHSUSB_BULK driver on my 1+1 my computer wont recognize the phone anymore
[ONE Q&A, Help & Troubleshooting] ogrillion:
Just wanted to reply to this amazing thread..

I am not a noobie when it comes to flashing and basically what happened to me made me very afraid to flash anything again.

Basically I was running CM12 nightly - no issues but I wanted to go back to stock since they announced that the end of march `12s was coming out.. For once I wanted to be receive an OTA.. I know its silly but whatever.

But yeah I also saw a ressurrected post about an automated tool to recover your Oneplus one (its from Oneplus offically supposedly) Well I didn't use the tool but I looked over what the batch file does.

I saw two things i never flash persistent.img and reserve4.img

I figured hey since I am going to stock maybe I will give those a shot since its from an official tool.

Well I flashed everything normally and did persisent and reserve4.. no errors.. I then booted into TWRP just to get supersu (wanted to keep stock recovery). Flashed supersu, no errors.. Rebooted..

And bam nothing.. I held the power button after a few minutes, and just a vibration.. Tried all the hold volum and power etc.. nothing.

Then I found this thread and saw I bricked my device some how.. Maybe it was those two files idk.. Only thing different I ever did.

But I did the coloros.zip and couldn't get the drivers to work, but the other ones floating around Qcom 2012 or whatever, those worked.. And I got coloros to install.

However I couldn't boot the OS? It was just a red 1+ logo then eventually the screen would go off and never respond again without holding the power button.

I was able to get to fastboot now and flash stock 11s.. Whew.. back to normal.

Anyways thank you XDA and thank you everyone who contributed to fixing this, saved me from having to buy a new phone. Love this website you guys are the best
[ONE Q&A, Help & Troubleshooting] riahc3:
Wow.

I just read the entire thread and I must say: More than 50% of the posts are complete random links (DropBox, Mega, etc.) which should NEVER be used and/or stupidity.

First, who the **** flashes kernels from one phone to one that is COMPLETELY different? Its like putting a Ferrari engine into a Ford. Come on. Think and read people.

Further more, what has been done has never been explained and this is (suppose to be, even though I disagree) a developer's forum.

When you flash (either flashboot and/or dd) what you are actually doing is writing bytes into a specific sector of a specific partition that is organized and structured by the GUID Partition Table. Your eMMC (internal hard drive? I would ***** slap anyone that even says that. Its the internal flash storage at best) is formatted in ext4 (thats why you can't read your drives and/or it says it needs to format it in Windows, dumbasses) and holds this partition table which defines each partition's start sector and finish sector and names it so it can be properly identified. What you put into between in these, really Linux (almost) gives a rat's ass about.

The problem comes when the position and/or size of each partition is changed (even by 1). Linux (I wouldnt even mention Windows) isnt a big fan of this (in Linux there are tools to fix it fdisk and sfdisk come to min). When you flash something stupid, like most of you have done, you completely change the entire partition table structure, so when the phone tries to load, maybe instead of loading "video_driver.ko", you idiots are making the system load "iver.ko dis" and of course, that is not a valid file. Or worst you overwrite "video.driver_ko" with "watchdog"

Moral of the story: ****ing read, read, read, read and if you have any questions, post what you are about to do, and ask for a second opinion on if it is safe.

And yeah, you read right: Not ONCE in my post did I mention "Android" and/or "OnePlus One". This applies to all Linux devices.
[ONE Q&A, Help & Troubleshooting] evronetwork:
Mine seems to be too! but I just fastboot a damn boot logo file :( I've opened a thread before reading this(my phone has similar behaviour), here's a link to the thread I've open maybe my case is easier? (yeah right :p )

http://xdaforums.com/oneplus-one/help/soft-brick-t3058987/post59547356#post59547356

My case is different, result is similar :P

This is easy, mine was saying just QHSUSB_BULK but if you click on it go properties->details->hardware id you should see PID_9008 that's how I check it out
[ONE Q&A, Help & Troubleshooting] 18th.abn:
Every device forum has a thread like this. I think there should be a dedicated "face palm thread" in every forum just like there is a comp. Roll up lol
[ONE Q&A, Help & Troubleshooting] hari.cool:
I can't see where there is a different looking line?? When I connect my phone and press vol up and power I hear a beep but nothing comes in the phone as well as in the toolkit.. What should I do.. Pl help..
[ONE Q&A, Help & Troubleshooting] rezor92:
First of all in which state is your Device? Have you installed the correct Driver?

If yes:

Disconnect your phone and press power for 20 seconds. After this step your One is powered off. Then press [power] + [vol-up] and connect your phone. Run the tool as administrator.
[ONE Q&A, Help & Troubleshooting] mad_hat:
Had similar problems. Try one or more of the following:

1. Change the cable, USB port or computer.

2. Uninstall and re-install the drivers.

3. Switch off the OPO - press and hold Power button for 20+ seconds and attempt to re-start in FastBoot mode.

4. Check if the device is seen in the Device Manager - esp if you see something like QHSUSB_BULK with a yellow triangle. If so you will have to do something about certification in command mode and then restart the PC.

I just have done the above and got the OPO working after $h!tting in my pants all night searching for solutions.

Thanks to all the great guys in the forums who have given their experience, inputs, advices and instructions. This is my first (and hopefully last) Hard Brick, I guess, and I know the agony of $h!tting hard bricks !!!!!
[ONE Q&A, Help & Troubleshooting] hari.cool:
Thanks but I got it working again, I updated the drivers after changing signature permissions, then used OPO toolkit to find the port which my phone is connected to and flashed the phone entirely. Then I flashed my phone back to 44s.
[ONE Q&A, Help & Troubleshooting] xBunNx:
Hi Guys, today my OPO became bricked all of a sudden. The phone was in my bag and when I want to use my phone, took it out and realize my phone was burning. Tried to off my phone but it did not react at all. Was flashed and had custom rom on my OPO. I had zero idea as to why my OPO was bricked.

Tried to unbrick but to no avail. I do not know why after the process it was not highlighted in green. Please please help me, really appreciate it!
[ONE Q&A, Help & Troubleshooting] xBunNx:
I did everything correctly, it read my device as qualcomm HS-UDB QDLOADER 9008. Used Msm8974DownloadTool and it stops after it overwrites one file. It was not highlighted in green like many of you did. I do not not what went wrong since i follow every single step. :crying:

EDIT: I realize when i was using Msm8974DownloadTool, right after i pressed start it was going well for the first overwrite however nothing happened after that. I check my driver and realized it was not show in my device manager. It disconnect? Any idea what went wrong?
[ONE Q&A, Help & Troubleshooting] herwigk21:
I tried to install the "setup.exe" of the "DRIVER.iSO", but the installation program won´t start (it pops up for a second and vanishes immediately).

The big square button in the upper right shows..:

can i simply use the android sdk usb drivers??

thanks :)
[ONE Q&A, Help & Troubleshooting] jdfeos:
You just saved my phone. God Bless you.
[ONE Q&A, Help & Troubleshooting] sarayevo:
this is the same problem im having the setup.exe installs und i can see oneplus in program files but nothing happens only Qhsusb_bulk device error and msm8974 cant see the phone what ever (volume up+power) :( only when i update the qhsusb_bulk to Hs-udb Qloader 9008 using Qualcomm drivers the program start seeing my bricked device when i press (volume up+power) once i click start the program flashes one img and stops and the device disconnects even from device manager im runnig everything as administrator and on windows xp please help i need another way around im trying everything i even formated my desktop and installed Windows xp again for a clean start
[ONE Q&A, Help & Troubleshooting] ogrillion:
I had that similar thing happen. I think it boots the phone in some kind of recovery mode.

My phone came up in device manager as a new device with no drivers so I just updated the drivers and pointed to the directory I extracted the Qualcomm drivers I got from this thread. So then it worked.

Tldr: when it pushes that one file check device manager you probably have to reinstall the driver again
[ONE Q&A, Help & Troubleshooting] akkin1993:
i need Msm 8974 Download Tool.exe can you plz upload it
[ONE Q&A, Help & Troubleshooting] sarayevo:
It is found in the color.zip when you extract

Sent from my A0001

---------- Post added at 01:35 AM ---------- Previous post was at 01:14 AM ----------

Please guys i need this to work when i connect my bricked opo i get this error (unknown device) in device manager

When i press (vol+_power) it becomes (qualcomm hs-usb qloader 9008)

I start msmtool it recognizes the phone on a port press start it flashes the first img then disconnects don't turn 9006 instead it is in device manager seen with a yellow mark as usb composite device and nothing more happens

Sent from my A0001
[ONE Q&A, Help & Troubleshooting] roor523:
I am having exactly the same problem and I tried to fix it with the XP compatibility mode and run as admin..anyway..it did not work..the phone reboots itself to 9006 after the Msm8974DownloadTool tries to send the '8974_msimage.mbn' file. I hope someone can help me with this. Using win7
[ONE Q&A, Help & Troubleshooting] XGrinder911:
Help

Can anyone please help me with uninstalling drivers? No matter what i do Windows always auto installs the drivers even though it is turned off. i tried installing from qualcom and the color.zip but none work and now when i click on the msm.exe file it just gives me a dialog and closes. Please help!
[ONE Q&A, Help & Troubleshooting] cresto2:
This is all you need for a Bricked device and you can run it in Windows 8, I just recovered from mine.

Follow these steps and use the provided driver and your OnePlus One will be back to normal.

https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/

use this for the usb driver:

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

***** Note **** I take no credit for these postings as it took me hours to come up with a solution, all credit goes to the talented DEVS.
[ONE Q&A, Help & Troubleshooting] DSwissK:
Actually isn't this a proof that my partition still exist? I get something like that when I write "gdisk -l /dev/sdc"

Number Start (sector) End (sector) Size Code Name
1 16384 147455 64.0 MiB 0700 modem
2 147456 148479 512.0 KiB FFFF sbl1
3 148480 148543 32.0 KiB FFFF dbi
4 163840 163903 32.0 KiB FFFF DDR
5 180224 182271 1024.0 KiB FFFF aboot
6 182272 183271 500.0 KiB FFFF rpm
7 196608 229375 16.0 MiB FFFF boot
8 229376 230375 500.0 KiB FFFF tz
9 230376 232423 1024.0 KiB 0700 pad
10 232424 235495 1.5 MiB FFFF modemst1
11 235496 238567 1.5 MiB FFFF modemst2
12 238568 259047 10.0 MiB FFFF oppodycnvbk
13 259048 279527 10.0 MiB FFFF oppostanvbk
14 294912 3006463 1.3 GiB 0700 system
15 3006464 3071999 32.0 MiB FFFF persist
16 3072000 4120575 512.0 MiB FFFF cache
17 4120576 4153343 16.0 MiB FFFF recovery
18 4153344 4156415 1.5 MiB FFFF fsg
19 4161536 4161537 1024 bytes FFFF fsc
20 4161538 4161553 8.0 KiB FFFF ssd
21 4161554 4163601 1024.0 KiB FFFF misc
22 4163602 4196369 16.0 MiB FFFF LOGO
23 4196370 4261905 32.0 MiB FFFF DRIVER
24 4261906 4327441 32.0 MiB FFFF reserve1
25 4327442 4360209 16.0 MiB FFFF reserve2
26 4360210 4376593 8.0 MiB FFFF reserve3
27 4376594 4507665 64.0 MiB FFFF reserve4
28 4521984 121543063 55.8 GiB FFFF userdata
29 121552896 122142686 288.0 MiB 0700 grow
[ONE Q&A, Help & Troubleshooting] Heisenberg:
It looks like they do exist still, but they're probably borked. The QHSUSB when you connect to your PC is a dead giveaway that your device is bricked. By all means keep trying to save it, I'm just saying my opinion is that jtag is the only way. I hope I'm wrong for your sake.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] bender_007:
Kernel wouldn't bork your partitions. Can you write me down a line you used to dd the kernel back?

You might also dd all partitions to their places. Just look the posotipn of partitions.
[ONE Q&A, Help & Troubleshooting] DSwissK:
Thanks for your answer. This is what I wrote :

dd if=/home/swiss/Bureau/boot.img of=/dev/sdc7

dd if=/home/swiss/Bureau/recovery.img of=/dev/sdc17

dd if=/home/swiss/Bureau/system.img of=/dev/sdc14

Problem is... I don't know if I've to push other files nor where to find them