yashsingh1/xdaforums huggingface dataset:
[ONE General] xAn0nYm3x:
Hi, first of all thanks for this awesome post !

I'll explain my problem.. I've tryed to upgrade my OPO to Oreo but the upgrade "fail" I mean the UI crash and never show. So I've downgraded to a previous version with was store on the phone. Here begin the problem, the flash success BUT unable to reboot into the ROM just stuck on the install cause the upgrade to Oreo crash the " com.android.phone" part.. so the phone just bootloop until he shutdown. I've no access to recovery and no access to fastboot mode.

I followed ALL the instructions and my OPO isn't detected by the soft..

by the way when I try to install the drivers, nothing show up so I don't know if there're installed.

First question: How can I make sure that drivers are good ?

Second question: when I press POWER + VOLUME UP, my phone start on the ROM or simply shutdown. I think this is not a good news for me and the OPO ?

If anybody can help me save this awesome phone..

Thanks

(Oh eh sorry I'm french :p )
[ONE General] vd30992:
Bricked OP3, No OS installed, No recovery Installed, Bootloader Locked

My phone is bricked, No OS installed, No recovery Installed, Most painful, Bootloader Locked. Do this Tool work this Condition?? Thanks
[ONE General] BitJockey82:
Hi, I need some help with a bricked OPO.

This phone just died a few days ago by itself (I wasn't flashing or anything). I thought it was the usual issue with battery not charging if it's completely drained. I tried all the usual things to make it charge again + some new things like opening it and disconnecting and reconnecting the battery connector but nothing worked, so I don't think anymore it's a battery issue. I'll order a new battery anyway but it will take a while to arrive.

The situation is that the phone won't turn, the screen and led never turn on but it vibrates if I keep the power button pressed (or other combinations). Adb don't recognize the device. Regarding adb, maybe I need to do something to make it work, like use key combinations to put in some mode. That's a bit more difficult than usual as I can't see anything on the screen.

This recovery tool recognize the phone, which is good but I'll prefer backing up the data before wiping it. Any suggestion about how to make adb work? Which combination of keys would put the phone into a mode that will 'activate' adb? If I can get adb to work then I can just back it up and then use the recovery tool (or throw it away).

Any other suggestion about how to revive the phone is highly appreciated. Also any clue on what happened? Just randomly bricked? Or some part just died?

Note: I flashed a few phones and I can use adb, but I'm not *that* expert on how to unbrick phones, never happened to me until now.

Thank you very much!
[ONE General] BitJockey82:
I just fixed it installing a new battery.
[ONE General] xinfernal:
--edit

solution for Unknown USB Device (Device Descriptor Request Failed)

seems random, didnt work on my desktop win 10, worked on my laptop win 10.

then after I gave up on everything for 2 hours I tried again and it worked on my desktop???

just keep trying and leave things to rest

///////////

Anyone have a solution to the msimage.mbn loop?

the phone disconnects when 80% of msimage.mbn is installed and it retries and loops from there.

-- edit

I solved this, by random it looks like.

I gave up yesterday evening and unplugged my phone from everything and put my pc to sleep.

This morning, started my pc (my cable was still in my pc but phone not connected).

Plugged my pc into my phone, it showed up in device monitor under ports as ""Qualcomm HS-USB QDLoader 9006 (COM7)", before it was ...9008 (COM6)

in the OPO tool, this time my opo showed up as AAIEe+ instead of com.

Previously it showed up as com and didnt work.

Now it worked

//////////

--edit

cyanogen loaded, but it keeps random reboot

and then it's hardbricked like before.

back to ...9008 and 'com' in the tool.

zzzzz

//////////

--edit

left it overnight unplugged again

this morning plugged it in, unknown device

unplugged, then held power button for 10 secs, then replugged into pc

shows up as --9006 in device manager

shows up as AAIEe+ in color os tool (no longer using the other tool just in case)

successfully rewrites

I go straight to fastboot and flash the stock OPO files

been working for 6 hrs now, should be ok.
[ONE General] padzi:
Hello all. My phone has not been working for a long time. I can not go on with the porro. has anyone encountered such a problem? The text is red, I usually stop at "sahara" and the green progress bar does not start at all.

[YOUTUBE]Z1VP0ln37DA[/YOUTUBE]

please help :confused:
[ONE General] MAGICPERF:
Issue with Tool

I see there is like a flash loop. It keeps trying to flash system.img and then starts all over again. Any thoughts?
[ONE General] pOLLYpOCKET:
Hey, I ran the tool and it did its thing. I got the green line and everything. Still stuck on the plus 1 screen, and if I boot to fastboot mode, my pc says there's a surge on the USB port. Any ideas?
[ONE General] josephiskandar:
Hi,

I currently have a similar problem.

Could you share how you did to recover your data ?

Thanks in advance!
[ONE General] arsaini:
This thread is a real life saver. Just followed the above instructions and wolla my A0001 is back from the dead. :D
[ONE General] rshoreview:
One plus one - bricked, does not unlock bootloader, no system partition

Please help - bricked my OPO bacon

Please help!!

I have messed up my oneplus one bacon

I was using lineageos 16 and all was fine. For some dumb reason 'Screen mirroring', I decided to go back to lineageos 15.1. Somewhere in the instructions I read, a clean wipe is recommended to go back to previous release.

I wiped all my partitions from twrp

As a result, my system partition is lost.

I tried to flash the stock recovery and stock ROM

Recovery flash was successful and so I am on CWM, but the ROM failed as the system partition could not be mounted/unmounted

Now, my phone's state is

ADB does not work.

Fastboot works, but am unable to unlock my bootloader, not sure how it got locked.

>fastboot oem unlock

OKAY [ 0.009s]

Finished. Total time: 0.019s

It simple reboots to the recovery without unlocking

>fastboot oem device-info

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

(bootloader) console_enabled: 0

(bootloader) exec_console_unconsole: 0

OKAY [ 0.021s]

Finished. Total time: 0.028s

I was hoping this thread would help me. But not sure how to apply this fix

I am unable to flash or boot as I get the following error

FAILED (remote: ' Device not unlocked cannot boot')

fastboot: error: Command failed

I also tried One plus recovery tool as well, but my phone is not being recognized when connected.
[ONE General] rshoreview:
Anybody? Any ideas on how to proceed?

I am purchasing OTG cable to try loading the scripts and patches directly to the phones and attempt to apply via Cyanogen Recovery.
[ONE General] upthedose88:
3) If drivers dont work or your device is not detected for whatever reason install the QPST tool.

what steps do i need to take with qpst tool to ensure my device is detected.

my device is stuck. im running windows 10 and cannot detect it at all beside kendacom usb devices and under Android Adb interface.

but if i run cmd and type fastboot i see my serial number now if i type in fastboot devices and deamon starts it doesnt read.

helpp? so i can move on? my deivce is bricked no tpwrp no rom no nothing. stuck on fastboot over and over and over.
[ONE General] pbaldw10:
Back from the dead!!!

thank you for this!!!!
[ONE General] nate0:
Hello guys. I waited a long time to unbrick my oneplus one. I screwed it up real good over 2 years ago, and waited on it until now. My question is this. I am up and going but back when I hard bricked it I wiped out critical QC partitions. Most importantly my issue is I have an unknown IMEI no bluetooth mac and non-existent wifi mac, none of them work, so far. I do not care so much about the IMEI, but getting wifi back and bluetooth would be good. Anyone point me to some info on xda to do that? Thanks much.
[ONE General] nate0:
Hi sorry about that. I found the information I need. Thank you.
[ONE General] david72262:
Try here https://xdaforums.com/oneplus-one/general/steps-how-to-recover-bad-imei-t3171452
[ONE General] nate0:
This led me in an even better direction. Got wifi and bluetooth back now. I will see about sorting out the imei soon. Thanks!
[ONE General] Athalef:
Hi all.

Maybe I could get any suggestions here:

I'm trying to resurrect my beloved OPO.

last working environment: LineageOS (not sure which version but probably 2-3 years old)

The device is on a bootloop.

Actually it tries to boot for 5 minutes showing LineageOS loading screen then reboots to show LineageOS' "Can't load Android system" https://i.imgur.com/1PbYuyx.jpeg

Problem is - I can't get to regular recovery mode nor fastboot mode - Volume UP + Power, Volume DOWN+Power - both do nothing and just boots the device to the same loop (5 minutes, reboot to error recovery message)

Recovery tool won't recognize my device at all.

I do get a "A0001" Device on device manager while on the error message and connected with original USB cable.

adb devices show as unauthorized and I can't do much with it (things like 'adb reboot fastboot' won't work)

Any idea?
[ONE General] armlau1234:
Hello,

As many others I bricked my OnePlus One.

I has Lineage and tried to install Ubuntu Touch via UBPorts. I've been very successful doing it with other devices like Nexus 5.

But there, with OPO, it started flashing, did a self reboot and ... that was it. It was stuck on the boot screen (+ logo, Ubuntu Touch under it, UBPorts at the bottom).

- When off, pressing POWER for about 3s powers on the OPO, 3s regardless if any other key is press in the same time.

- Connecting USB to computer powers on the device and blocks at the same step.

- Pressing POWER button for 10s reboots the device and blocks at the same step.

- Pression POWER + DOWN buttons for 10s reboots and blocks at the same step.

- Pression POWER + UP buttons for 10s reboots and blocks at the same step.

- Pression POWER + UP + DOWN buttons for 10s reboots and blocks at the same step.

Any of these cases when connected to a computer shows any devices in the device tree. I tried Windows10, WinXP, OSX, Linux.

I tried a bit all of the methods described, loaded all possible drives (ColorOS, Qualcom tools, etc.). Nada !

At a point I even thought the USB was not working anymore and died when was flashing Ubuntu Touch, but I doubt.

Any idea?

Has anyone been in this situation?

Is there a way to "force a flashing" with a one way communication?

Is there other pins on the phone where I can hook and to it?

I'll appreciate any help.

Thanks
[ONE General] armlau1234:
Ok, new update.

I was able to reboot in recovery mode, after several full days trying without success.

The phone not being connected to USB:

1 - I removed the cover, removed the camera/flash cover to unplug the battery.

2 - I unplugged the battery

3 - left it unplugged when "drained" the cap by "jumping" the 2 connection of the power button with a screw driver for a minute or so.

3 - Then, I plugged the battery back

4 - with one screw driver I jumped the two right connection of the volUp button, then keeping the jump, I jumped th Power button connection for about 10s.

5 - the phone vibrated and rebooting in the Ubuntu Touch recovery

6 - plugged I was able to restart UBPorts flashing. All went well, the phone rebooted couple times itself and is now up and running Ubuntu Touch.

I don't know if it's a hardware problem (buttons not keeping contact correctly when booting) or if disconnected the battery fixed the problem. But it's fixed. Worse trying for other who like me tried everything without success.
[ONE General] Thedoczz:
Hi guys, sorry if i post to this old thread, i have a OPO that had the usual sign of hardbrick. So i tried this tool, before using it the led did turn on while charging and became green occasionally, now after i used it(it recognized everything correclty and did everything as it should, flashed, the line became green etc..) it just doesn't do anything, i can still enter fastboot and i've tried rerunning the tool multiple times, i also tried the CM one but didn't help either. The log of the tool shows a lot of FAILED partitions. The led now doesn't even lit up while on charge!
[ONE General] SoundDrill:
This worked! I recovered my OPO from a bad logo.bin flash.

I installed qualcomm drivers, rebooted my PC into disable driver signature enforcement mode(safe mode menu+7)

Ran this tool, connected the cable, waited 1-2 seconds. While it was connected, I held vol up and power for about 1-2 seconds.

It detected my phone and the rest was history.

Sim works flawlessly btw.
[ONE General] Braaainz:
Thanks WEM97,

I was signed in as Admin and opened the programs as administrator.

The phone did go into fastboot mode for a bit, but was unrecogized by ADB, device manager and nothing changed on to recovery tool.

I tried again,but lost fastboot mode. I did manage to transfer drivers though.

Device manager still doesot recognize it, but there are ONEPLUS drivers supposedly on the device.

thoughs/ideas?
[ONE General] Braaainz:
Hey, I did manage to get into TWRP recovery. Any chance I can fix it thru this?

My OS is apparently gone. Would a twrp nandroid replace everything I need?

I was thinking I could possibly use USB OTG and a USB memory stick to load a nandroid.

I was hoping I could use ADB sideload, but don't know if it'd get that far with the driver issues I've been having.
[ONE General] leenwen:
Very useful!
[ONE General] Consan:
My phone is total black, I cant get into fastboot mode vol up + power :/ is it hard bricked? have don everything. install drivers from the folder, open program as admin, insert USB when I do that I get messege from Windows saying new device found , installring qhsusb_bulk drivers and 5 sec later , cant install drivers , no found

[IMG="image"]http://i.gyazo.com/66bb7f63e6d7ea3b7ac09d4eaced7d9b.png[/IMG]
[ONE General] funCrash93:
indeed a Life-Saver.! :angel:

THANK YOU !!!
[ONE General] Consan:
why do it work for you all and not for me ? I have done everything its says and stil get that ****ty BULK driver error and the tool dont find my phone
[ONE General] Consan:
How Can I enter the qualcomm debugging? I have read but I dont get it what you mean I have done everything it says on first page?

No the phone is dead. Vol up+ power dont work, vol down and power dont work....

When download the tool i do exact in the video!! I extract the driver.iso and install the EXE file. When open the Tool with admin access I put the cable in and the computer show a new device is detected and starts to download QHSUSB_BULK drivers for 10sec and then stops and it says: cant find drivers. At the same time when the tool is open I hold vol up and power but stil dont show any device. so what im I doing wrong when I follow the guide? :(
[ONE General] Zyxxeil:
You should be able to adb sideload a nandroid backup if your in recovery or better yet flash it using an OTG device. If that does not work then this tool might be useful.

First your going to want to completely power off the device and MAKE SURE THAT the phone is CONNECTED TO THE PC. Once the phone is off and connected to pc just hold Power + Volume up until your computer recognizes the device (The phone won't light up or anything so rely on your computers device noise). Once that happens it should install the proper drivers if you used the ones that are included in the tool. From there you should be set to go.

If that does not work try uninstalling ALL previous drivers you installed and install the ones in the tool.
[ONE General] Consan:
Nope didnt work at all! I did everything in EXACT order you wrote and what was saying in the guide everytime I tried. Did a full uninstall on every driver with USBreview and did All over again. could not get it to work, everytime that after installning the drivers that is included in the tool I got QHSUSB_BULK drivers error when I plugged in the phone in computer.. I read and read and read for 4 hours and found other had same problem !! This is what some other guy wrote:

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.

I also deactivate unsigned driver installation but still same fail... I found a Qualcomm HS-USB QDLoader 9008 2.1.0.5 for Windows 7 that I used. I opened the Device Manager, I found my device named QHSUSB_BULK with an yellow triangle. I pressed udate drivers , choose from computer and installed that Qualcomm HS-USB QDLoader 9008 2.1.0.5 I donwloaded. AFTER THAT the tool found my phone and I was manage to flash ROM :) took me half a day. I cant have done wrong , somethnig must be wrong with the drivers in the tool for w7 64bit or something . this was the first time I have hard bricked a phone EVER and I have flashed a lot . But im glad it worked out with that Qualcomm HS-USB QDLoader 9008 driver since that guy also had same problem as me and later got it to work with that driver. Qualcomm HS-USB Drivers
[ONE General] mrsim:
Hey [MENTION=3929963]Zyxxeil[/MENTION].....is it possible to link the drivers from [MENTION=3598682]Consan[/MENTION] in post #40 into the OP just in case other people run into the same problem..at least they will have an alternative to try...makes sense...;)
[ONE General] Moatmonster:
You my friend are a legend and my hero. After 4 months i finally have my phone back.

Thank you so much.

---------- Post added at 11:57 AM ---------- Previous post was at 11:51 AM ----------

Great stuff with the link to the qualcom drivers mate, once i pointed my driver search to this file on my desktop the phone restore was all over in minutes.Cheers and thanks
[ONE General] Consan:
didnt work for me, as I wrote before. I reboot the computer and pressed F8 and disabled driver signature verification for my Windows 7

( and im guess its same for 8) but same error anyway, what saved me was Qualcomm driver. apparently they are something wrong with your drivers (or is it my computer there is a problem with , but when other have same problem I doubt it) because they do not work on all Windows machines since other report same error. rather than blame me and other for doing it wrong, you can just thank and be grateful instead that there is another workaround this problem and face the facts!

Nice to hear that it also worked for you :)
[ONE General] Consan:
You can believe what you want mate :) no problem. I have done exactly as it says 4 times and did not get it to work and im a experienced data and mobile user and tried everything, and since other also says its not workin? I dont know?? maybe we is doing it wrong even though follow the guide to 100%. that is was you say basically with finer words. Well Our discussion does not seem to lead anywhere .Thanks for good program and not so good drivers ;) If someone else read whats been said and have same problem just use the drivers I linked to. have a nice day.
[ONE General] SkandaH:
[MENTION=3929963]Zyxxeil[/MENTION] & [MENTION=4148474]WEM97[/MENTION]

Thanks for making this compilation :highfive:

My story is almost same as Consan's one. Under Windows, the drivers for the Qualcomm debug COM port is a real PITA, because:

1. Most of us use Windows 7/8.x x64, which demands driver signing enforcement.

2. The Chinese ColorOS driver installer installs fine, but doesn't show any failure notification on such operating systems.

3. Also its created by Inno Setup with some custom addition so that it can't be unpacked by available unpackers to extract the driver.

4. Even with the extracted driver (source), we need to disable driver signing enforcement.

Interestingly, Nokia Care Suite PST installs an WHQL driver for this device ID which is acting like a low level communication channel while flashing Lumia phones. I have that already installed, so it detect the bricked OPO but there is a catch! The Qualcomm downloader tool expect a virtual COM port whereas the Nokia driver creates a USB device.

Looks like it is also possible to turn on this downloading mode on various HTC devices, but again there is no available driver. Fortunately I'm able to locate an x86 WHQL driver of the COM port for Qualcomm Quanta IS7 from Microsoft Update Server! Then its a piece of cake to get the x64 one.

Qualcomm HS-USB QDLoader 9008 2.1.0.5

x86: http://download.windowsupdate.com/m..._d2d9d13c011c3be79fc5589b3cc30caf53d237ff.cab

x64: http://download.windowsupdate.com/m..._ed08f7139a2028da454a6668162f44ac311facc0.cab

They are fully WHQL certified (thus no need to turn of driver signing enforcement) & created for Windows upto 8.1.

Tested on:

Windows 7 SP1 x86

Windows 8.1 with November update x64

BTW, you need to update the thread title. ;)
[ONE General] Chr0sy:
Thank you. I just wanted to restore to CM11S after a boring experience with CM12 :)
[ONE General] brightedge:
Yes, yes, yes....oh wait, nope.

I was so hopeful after following the steps outlined in the OP. I did have to install the Qualcomm drivers mentioned a few posts back before the app would recognize my device. It flashed everything and the text turned green as described, however, it still won't boot.

Pressing pwr for 10 seconds or so will cause a vibration, but the screen doesn't turn on. The LED doesn't light up when connected to power. Pressing vol up + pwr will make it vibrate, but still nothing on the screen. Results are the same with vol down + pwr.

Not sure what else to do. It all started last night. It was running fine on the latest LiquidSmooth ROM (LS-LP-v4.0-2015-01-07-liquid_bacon.zip). I decided to try out the nightly CM12 by following the directions I used to update to LiquidSmooth (copied over zip, entered TWRP recovery, wiped everything, rebooted, entered TWRP recovery again, installed zip, installed gapps, rebooted.) It came up fine, so I walked through the standard initial setup. It downloaded all of my apps and such. When finished, I noticed the "USB Debugging mode enabled" notification, and tapped it to turn it off. It rebooted twice, and then powered itself off completely. Had more than 60% battery at the time.

Thoughts? Do you think it's bricked beyond recovery?

Thanks!

UPDATE!!

I left it plugged into power for 4 hours, and pressed pwr for 10s. It vibrated, but nothing else. Unplugged USB, and hit power again for 10s. This time I got the 1+ logo!!! It booted into CM11S just fine! Thank you for putting together this toolkit. Much appreciated!
[ONE General] h.jain2020:
my tool is not able to detect it.. plz explain how to do it! in details.
[ONE General] jamesst20:
Thanks for taking the time to read the OP :)
[ONE General] jamesst20:
My Opo wasn't broken but I have tested flawlessly on my Windows 8.1 64 Bits. First disable driver verification signature check, installed the drivers, did the vol up + power trick and worked on first time on the tool. A driver installation popup for a few minutes before it finally works.

To those wondering !

It does not relock the bootloader!

Unlocked bootloader isn't required !

Custom images can be flashed ! Tested TWRP

Edit : Why don't we use this to flash TWRP & root without unlocking the bootloader ?
[ONE General] carloswii5:
Hey guys sorry to be a bother but can anyone provide me some assistance with this? I cant get it to recognize the device no matter what i do any help would be appreciated.
[ONE General] Consan:
Try my method http://xdaforums.com/showpost.php?p=58074662&postcount=40