Database Users

Bricked OP2 after flashing Nexus Stock ROM

Bricked OP2 ...
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance

If you flashed a ROM that's not for you're phone you're more than likely screwed

Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi

Bhups said:
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Click to expand...
Click to collapse
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again

mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.

Heisenberg said:
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Click to expand...
Click to collapse
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance

mG!X said:
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
Click to expand...
Click to collapse
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.

Heisenberg said:
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Click to expand...
Click to collapse
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something

mG!X said:
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
Click to expand...
Click to collapse
I just can say, your device is not hard bricked and will be recoverable.
You just need to be a bit patient. For the OPO, there was the ColorOs emergency recovery available (which helped me already 2x unbricking my OPO after I compiled a faulty kernel).
I just have not yet seen something similar for the OP2. But as you get the bulk_device still recognized via USB, this means the Qualcomm emergency boot loader is still intact and once the recovery stuff leaks somewhere, you will be able to fully recover your OP2.
Don't ask me when this will be available, think it also took weeks for the OPO before it was posted somewhere.
All the best!
Andi

mG!X said:
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
Click to expand...
Click to collapse
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck

yanick76 said:
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
Click to expand...
Click to collapse
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.

Heisenberg said:
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Click to expand...
Click to collapse
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)

yanick76 said:
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
Click to expand...
Click to collapse
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.

Heisenberg said:
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Click to expand...
Click to collapse
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose

Just to assure you that the hard brick issue on OPT is completely curable since I've revived two OPTs. No panic needed. I will update the complete procedure as well as the necessary files later today.

yanick76 said:
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Click to expand...
Click to collapse
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.

Heisenberg said:
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Click to expand...
Click to collapse
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it

yanick76 said:
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
Click to expand...
Click to collapse
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.

mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Tutorial posted here http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

Heisenberg said:
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
Click to expand...
Click to collapse
From this point I agree it was wrong advice.
I hope I never will be in situation like this But if, I will try to fix it based on what I suggest him + hours of google for correct files, correct drivers and correct download tool. I think this "misunderstood" was based on my advice like "here is direction and google for more", this is forum if he can find answer himself (google) he need not to ask for help here

OnePlus just hard-bricked my device and don't give a ____.

Hello xda members, yes you heard right, OnePlus bricked my device, did you had a problem with the OnePlus support too?
Here's a sum up what happened:
> I buyed the one in january 2015
> batterylife on Cyanogen OS was terrible, so I switched like many other users to custom roms
> the batterylife was better, but not good not bad, normal
> many users are saying that Oxygen OS has amazing battery life
> so i searched and found out that there isn't an official flashable version, i found out that the support flash it by every user manually with a remote session
> so i contacted the support, made a meeting
> the support was nice, but then...
> 12pm (est) on monday 28.03.16
> the remote session started, there standed that it will get recorded on my windows vista pc(does anyone know where? i dont find it, but i have the chat between me and the tecnicer, see the attached file
> the technicer installed drivers and flashed afaik per adb, but it dont found my device, he did something with drivers and said i need to reboot my pc
> i did it
> still dont work
> my phone was ok
> so he used a chinese tool
> then he wrote he's very sorry and that my device has a hardware issue and that he will send me to their RMA/RRR(he wrote both, its afaik the devicechange support)
> I was sad looked to my phone: dead, hardbrick, idk how, he just hardbricked it, but ok its not full dead just hardbrick, its able to fix(i found athread on xda, but the problem is that my device got bricked by flashing oxygen OS, so I think I need to give my device to the support, they need to fix what they did)
>I was only sad, not angry, he did his best, so i waited for an email from the support
> I got one with my adress and they asked if its true
> it's #sotrue
> after 2 days i still didn't got an email, so i am now angry af
> many of you are thinking now 'just chill dude they are humans too and you are not the only one which need the device change support, but guys, you need to know that this guys which need the support to droped for example their device in water and want that 1+ fix it, but i didnt dropped it and didnt bricked it, so oneplus need to care about me, its their fault, but they still dont answered after 2 days, guys i need my device, they know that i am angry because they bricked my device, ok 12 hours before i get an answer is ok they are humans too, but not 2 damn days, they bricked my device, not I.
I dont wanna hate against oneplus, i just write this because i am very angry that THEY bricked my device and don't give a ****, that's not a good support!!
so please dont remove this thread admins, if something is not ok contact me i will edit it
Had you guys a problem with the support too? Write it and vote in the survey!

I'm sorry that you are unhappy with the phone.
I'm own of the same device since rough about the same date like you.
First of all I've install an own recovery menu (TRWin) and use uo from this time CM 5 / 5.1 and now 6.x
I couldn't say that I've the same problems like you. The battery life is independent of the OS and which apps are are used. At minimum the akku reached for 3 day's or more( look how much % does you display used).
In the case that I'll have your issue : boot into the recovery at make a wipe of = cache / Dalvik cache and data ( factory reset). After that reinstall your apps fresh from the market.
Also install Aps Ops to control the access of the apk's. If a Apk check every. 5 Min something of an update, the battery drains... thats normal.

Mad07 said:
I'm sorry that you are unhappy with the phone.
I'm own of the same device since rough about the same date like you.
First of all I've install an own recovery menu (TRWin) and use uo from this time CM 5 / 5.1 and now 6.x
I couldn't say that I've the same problems like you. The battery life is independent of the OS and which apps are are used. At minimum the akku reached for 3 day's or more( look how much % does you display used).
In the case that I'll have your issue : boot into the recovery at make a wipe of = cache / Dalvik cache and data ( factory reset). After that reinstall your apps fresh from the market.
Also install Aps Ops to control the access of the apk's. If a Apk check every. 5 Min something of an update, the battery drains... thats normal.
Click to expand...
Click to collapse
Sorry bro i already tried everything, bbs(there were gservice wakelocks which cant get killed, i installed other roms there were again other wakelocks and more), elixier 2, gsam, this what you said that if a app drains every 5 minutes and more, at least the batterylife was normal. At least only 3 hours on screen time. Thats the reason why i wanted to try out oxygen os.

In this moment I use the TRWin Recovery ( wipe Cache / Dalvik / Data) ; CM 13 ( Android 6.0) and Google Apk ( not the big one / Small or medium packages) for marshmallow.
I've ~ 170 Apps on the phone - without any issues ( ok, the batteryife was a little bit better with 5.0, but that's all ( here the compare is not 100%, because more Apps : but at the beginning the phone was running around 6-7 day's)
Does the PC see something, if you connect the Phone via USB?
If yes, you can bring it back to life

Mad07 said:
In this moment I use the TRWin Recovery ( wipe Cache / Dalvik / Data) ; CM 13 ( Android 6.0) and Google Apk ( not the big one / Small or medium packages) for marshmallow.
I've ~ 170 Apps on the phone - without any issues ( ok, the batteryife was a little bit better with 5.0, but that's all ( here the compare is not 100%, because more Apps : but at the beginning the phone was running around 6-7 day's)
Does the PC see something, if you connect the Phone via USB?
If yes, you can bring it back to life
Click to expand...
Click to collapse
Hi, yes, i already tested it, its a hardbrick and the pc detect it.
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I am thinking about to fix it self, but then i wont have Oxygen OS because i think it will do again a full brick. But i need my phone on monday because i am then 3 weeks on a work placement and need my phone. :/

If your PC see an unknown Device, the phone is ot hardbricked. Its a hard Softbrick
If I remember right, you will find a link in the Oneplus forum for the needed driber. With this one, you can bring back your phone to life. A recovery menu is in a normal case enough.
( like Twrp (that's tbe right name )
https://www.androidfilehost.com/?fid=24399994186369589
Bacon is the pseudonym for the Oneplus one
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
pls have a look to the description
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136

Mad07 said:
If your PC see an unknown Device, the phone is ot hardbricked. Its a hard Softbrick
If I remember right, you will find a link in the Oneplus forum for the needed driber. With this one, you can bring back your phone to life. A recovery menu is in a normal case enough.
( like Twrp (that's tbe right name )
https://www.androidfilehost.com/?fid=24399994186369589
Bacon is the pseudonym for the Oneplus one
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
pls have a look to the description
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
Click to expand...
Click to collapse
Thanks guy i think i'll unbrick it self

sorry for not helping and ur post had just made it clear we should know what we r doing with our phone eveyrtime.

If the pc can identify the phone in fastboot mode, then there is hope.
https://www.reddit.com/r/oneplus/comments/31sf0x/guide_how_to_return_from_oxygenos_to_stock_cm11s/
or follow the guide you linked to

kenboyles72 said:
If the pc can identify the phone in fastboot mode, then there is hope.
https://www.reddit.com/r/oneplus/comments/31sf0x/guide_how_to_return_from_oxygenos_to_stock_cm11s/
or follow the guide you linked to
Click to expand...
Click to collapse
bruh, its a hard softbrick, there's no fastboot.

PlayersHeaders said:
bruh, its a hard softbrick, there's no fastboot.
Click to expand...
Click to collapse
Brah, try this method. It's a ported tool for the OPO that I used to restored my OPT when I was about to use it as a paperweight LOL.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Also have a look to the post #40 on the same thread
http://forum.xda-developers.com/showpost.php?p=58074662&postcount=40
Hope this helps!

Hellfireworks said:
Brah, try this method. It's a ported tool for the OPO that I used to restored my OPT when I was about to use it as a paperweight LOL.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Also have a look to the post #40 on the same thread
http://forum.xda-developers.com/showpost.php?p=58074662&postcount=40
Hope this helps!
Click to expand...
Click to collapse
Is it for the problem what i have? I have no fastboot, boot, recovery, is this tool for bricks which I have?

PlayersHeaders said:
Is it for the problem what i have? I have no fastboot, boot, recovery, is this tool for bricks which I have?
Click to expand...
Click to collapse
Yep, if you connect the OPO to a PC is it recognized something like "Qualcomm device"? If it is, this tool is for you. Once you have the tool opened and the phone connected to the PC, press Volume up + Power, the phone should vibrate and then it should appear under Device Manager. Here's additional information of this process, found on the OPT thread:
qwsdert4 said:
First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here
Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)
Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.
Click to expand...
Click to collapse
Check the post #40 on the URL provided early:
Consan said:
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
Click to expand...
Click to collapse
Hope this helps man. Greetings!

EDIT: just noticed I linked the same as @Hellfireworks, disregard. Hope you get it fixed up.
This tool had been out for the one plus one specifically for the longest time. I wouldn't use the one plus two tool because it is for the op two.
http://forum.xda-developers.com/showthread.php?t=2991851
I haven't had to use this myself, but others have, and the forum is full of success stories. I have however fixed my buddies one plus two via an unbrick tool, and was almost the exact same process.
This tool has the proper firmware specifically for the one plus one, hence why i recommend it over the op two tool.
Sent from my A0001 using Tapatalk

[Hardbrick] Oneplus 2 Only fastboot, OEM and device locked.

So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
Nevertheless, i will state my problem here:
Right now, my phone and my limited knowledge about it have come to an dead end. with the help of online tutorials and so on, (I have downloaded almost 40 gigabytes worth of space to do stuff to my phone), i was able to only get the fastboot mode to work again.
It started with me uninstalling a system app from google (I don't know which one exactly, but i had the resurrection remix 5.69 or something like it, and in that ones system app remover it was one of the lowest google apps). I don't know if this is important, but at the time i did that i was in plane mode.
After some time i ran into some loading issues with games and restarted my phone. the first time i got in, i booted up normally and could do my pattern normally, but then there was only a black screen and i could pull that info bar thing down. as soon as i wanted to open the settings, everything froze and i decided to restart the phone. Once it was shut down i then got greeted by a bootloop which i aborted by shutting down after about 3 minutes. then nothing was working anymore, so i wanted to see if the fastboot mode was still available. it was, but after shutting down from that and trying again ( just to be sure) even that was gone.
so i went online and downloaded basically everything you can find online to recover a harbricked op2.
turns out, after i got my fastboot working again, the OEM and the device were locked (still not sure if those are different things or the same) and because i couldnt get in the android system, i could not enable it.
the ADB commands do not work at all because there is no device detected for it, though it is detected for fastboot. the command fastboot OEM unlock does not work because OEM unlocking is disabled...
so far i have been able to connect my phone in 3 modes and names for those, them being:
Android Bootloader interface (Fastboot)
Qualcomm HS-USB Diagnostics 900E (Connected while holding VolUp)
RELINK HS-USB QDLoader 9008 (Connected while holding VolUp + VolDown)
I am also unable to flash anything on the phone because the OEM is locked
I will not be able to answer for some time (probably 2-3 weeks) but i wanted to start this thread so I could already have an answer when i come back home again (traveling with fam, and its somewhat hard to take a PC tower with you on trips)
Thanks for helping me! :fingers-crossed:

I'm having the exact same issue as OP.
I'm not sure exactly what I did, but I can only boot to fastboot. Typing fastboot continue does not work, I can't flash ANYTHING or use any of the recovery tools, because my device is locked, and there's no system to boot to so I can run fastboot oem unlock (have to turn on debugging, which I can't do). I have read just about every guide there is, and also downloaded a boatload of purported "fix" tools/drivers/packages. My phone remains able to boot only into fastboot, and I can't get anything working.
Installing the device drivers did work for me, so I'm about half a step ahead of some other people with this issue, but none of the tools or scripts I've found, or manual methods, have brought my OP2 back to life.
I'm really, really hoping someone here is able to help with this.

Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk

Coolmfarshard said:
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.

http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

Lonemaster said:
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
Click to expand...
Click to collapse
Its working bro tried several phones with this tool
You cant know its working or not without trying

Coolmfarshard said:
Its working bro tried several phones with this tool
You cant know its working or not without trying
Click to expand...
Click to collapse
Ok, Thanks. Don't know what i was thinking back then.
I will reply again when i am Home and tried it. (Currently i am just using Internet cafes.)

MickyFoley said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Oh, it is that one. I had already tried this one, in all listed modes posted above. The problem with that one is that everytime I hit the start button, the green progress bar does not show up and it does not a single thing... because I am staying at a place with a internet café for 3 days, I can download some stuff and try it again.
EDIT: I don't know if that was the reason It didn't work, but I may or may not have forgotten to install the driver because it was deleted off the onedrive page and I just forgot about it afterwards. if I can find a replacement for it, I will ink it here for future users with the same problem. otherwise, I would be GLaD if someone would do that for me...

Have you tried flashing a stock ROM with the qcom download tool

abdur10567 said:
Have you tried flashing a stock ROM with the qcom download tool
Click to expand...
Click to collapse
I am not sure if it is that one (it gets pretty messy wehen you have downloaded 50 gigs), but i think it wouldn't let Me because of the locked OEM.

Lonemaster said:
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
etc. etc.
Thanks for helping me! :fingers-crossed:
Click to expand...
Click to collapse
For some reason, after doing it for the what felt like the billionth time whith the restore tool it finally worked (I have NO ****ING IDEA why tho.)
Thanks for everybody who helped me.

HELP! Asus Zenfone Max(8939)

So I have an Asus Zenfone Max(ZC550KL) which is more or less unusable at the moment. I had been using it for a year and 4 months now and it worked like charm. But for the last few weeks, It had gotten incredibly slow. So day before yesterday, when I got some free time on my hand, I decided to flash it with a custom ROM.
Basically I checked xda for some good ROMS and decided which ones to flash. Also had to unlock the bootloader which I did using the app from the official Asus website. Also managed to get twrp recovery and root it. I somehow managed to flash a custom ROM but it wasn't working like I expected(No wifi or network) and so many other things. So I decide to flash the stock ROM back and this is where I screwed up in probably more ways than one.
So I went on to search as to how I could go about flashing the stock ROM and one of the instructions said it was as simple as using the firmware from the Asus website and installing the zip through twrp. At the moment I wasn't aware that the 16GB and 32GB were actually different variants, one which had Snapdragon 4XX and the other had 620 processor. The website initially listed only 8916 firmware. I didn't think a whole lot about it and used twrp to flash it. Since then the phone isn't booting up, can't get it into the CSC mode or recovery mode. Later on I managed to search a Asus website a little more extensively and somehow managed to find the 8939 as well. But without being able to boot into the bootloader mode or recovery, I don't know how to go about it.
I am not getting the charging symbol either, and whenever I plug into the PC, nothing is recognized. But from time to time, if I press the power button long enough, My PC says an unrecognized device is plugged. Is their anything I can do to to revive the phone or should I lose hope at this point? Also I understand changing the motherboard could fix it, but is the price worth it or would I be better off buying a new phone? Any help would be highly appreciated.

deon610 said:
So I have an Asus Zenfone Max(ZC550KL) which is more or less unusable at the moment. I had been using it for a year and 4 months now and it worked like charm. But for the last few weeks, It had gotten incredibly slow. So day before yesterday, when I got some free time on my hand, I decided to flash it with a custom ROM.
Basically I checked xda for some good ROMS and decided which ones to flash. Also had to unlock the bootloader which I did using the app from the official Asus website. Also managed to get twrp recovery and root it. I somehow managed to flash a custom ROM but it wasn't working like I expected(No wifi or network) and so many other things. So I decide to flash the stock ROM back and this is where I screwed up in probably more ways than one.
So I went on to search as to how I could go about flashing the stock ROM and one of the instructions said it was as simple as using the firmware from the Asus website and installing the zip through twrp. At the moment I wasn't aware that the 16GB and 32GB were actually different variants, one which had Snapdragon 4XX and the other had 620 processor. The website initially listed only 8916 firmware. I didn't think a whole lot about it and used twrp to flash it. Since then the phone isn't booting up, can't get it into the CSC mode or recovery mode. Later on I managed to search a Asus website a little more extensively and somehow managed to find the 8939 as well. But without being able to boot into the bootloader mode or recovery, I don't know how to go about it.
I am not getting the charging symbol either, and whenever I plug into the PC, nothing is recognized. But from time to time, if I press the power button long enough, My PC says an unrecognized device is plugged. Is their anything I can do to to revive the phone or should I lose hope at this point? Also I understand changing the motherboard could fix it, but is the price worth it or would I be better off buying a new phone? Any help would be highly appreciated.
Click to expand...
Click to collapse
What is the device model exactly , the 8916 or 8939 CPU ? How exactly is the device showing up when you connect to pc, showing up as a number of local drives or what ?

jide1 said:
What is the device model exactly , the 8916 or 8939 CPU ? How exactly is the device showing up when you connect to pc, showing up as a number of local drives or what ?
Click to expand...
Click to collapse
Not showing up at all. sometime back, if I pressed the power button long enough, My pc would tell me there is some unrecognized device connected. Now that isn't happening either. Its the 32 GB Variant with Snapdragon 625, So 8939. But I flashed the phone through twrp, that too with 8916 firmware.

deon610 said:
Not showing up at all. sometime back, if I pressed the power button long enough, My pc would tell me there is some unrecognized device connected. Now that isn't happening either. Its the 32 GB Variant with Snapdragon 625, So 8939. But I flashed the phone through twrp, that too with 8916 firmware.
Click to expand...
Click to collapse
Send me a PM, maybe i can help (maybe).

Zen fone max ZC550KL
I have a similar problem. If there is a solution, please post the solution.

CL Lau said:
I have a similar problem. If there is a solution, please post the solution.
Click to expand...
Click to collapse
I need full details of your issue, so send me a private message.

How to fix OnePlus 8 pro won't turn on

Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.

Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger

jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You all are flashing wrong xbl img. Wrong ram versions

what do u mean xbl img? I remember I have read about the ram versions but I think it wasn't the 8 pro...

duxler said:
Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.
Click to expand...
Click to collapse
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
Im am sorry for you guys but you hard bricked your phones for real.
The only thing you can do now is to replace the motherboard.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com

jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11

AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.

xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Unfortunately that's the case...

jimger said:
Unfortunately that's the case...
Click to expand...
Click to collapse
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.

xtcislove said:
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.
Click to expand...
Click to collapse
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...

jimger said:
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...
Click to expand...
Click to collapse
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.

xtcislove said:
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.
Click to expand...
Click to collapse
Yeah tbh I have every photo etc backed up. Also run my daily swiftkey backup before updating. But the big big bummer now is that I have no way to restore banking apps to tablet atm... Anyway let's hope at least they replace it...

As I understand it, the phone can be thrown away

how will Qualcomm ® Package Manager help if the computer does not see the device.
AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse

duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Tbh at least I hope they replace it... For now found an Mi A1 from a friend...

I know this topic has been brought up before. But there is not always a half and full explanation.I have Oneplus 8 pro too. I can't enter recovery mode. Boots into fastboot. I've printed a wide variety of msm tools files from edl. It writes smoothly, but when opening the boot screen, it says "your device is corrupted it cannot be trusted and may not work properly" and does not open. What could be the reason? Android 10 11 msm roms, Coloros Hydrogenos all but all tried. There is no recovery. I can't open the oem lock, I can't do anything.

xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager

AkayamiShurui said:
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager
Click to expand...
Click to collapse
Im sorry my friend i dont understand your post.

xtcislove said:
Im sorry my friend i dont understand your post.
Click to expand...
Click to collapse
If your got discord I can show you

duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Hold up. I'm looking for a dead OP8 Pro. I have started a conversation with you; check notification.