Database Info

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

I rooted the phone properly, then I installed a wrong kernel : hells-Core_b47-kk-CM_anykernel.zip (http://d-h.st/users/hellsgod/?fld_id=28949#files)
The phone doesn't boot up anymore, no fastboot, no adb, no hard factory reset. The only thing I can do is connect it to linux and send dd commands. I tried to push a new boot.img through that way but it didn't change anything. (I followed this guide : http://forum.xda-developers.com/showthread.php?t=2582142 with another boot.img obviously)
In Windows I get the QHSUSB_BULK USB device error.
Anyone could help me out?
Thanks!

= someone should pull boot partition for him so he can flash it.

With device off, you still have download/fastboot mode (Power & Volume + button) ?
If you have, find another PC with drivers properly installed.
Reflash all : http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

luminouche said:
With device off, you still have download/fastboot mode (Power & Volume + button) ?
If you have, find another PC with drivers properly installed.
Reflash all : http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Click to expand...
Click to collapse
How do you mean "Power & Volume + button"? When I hold power and volume button (I tried up, down and both together) it doesn't work. Screen stays black.

Power & Volume+ (Up, highest part of vol button) you should have fastboot mode.

luminouche said:
Power & Volume+ (Up, highest part of vol button) you should have fastboot mode.
Click to expand...
Click to collapse
Nope, that's not working.

Exactly which device is that kernel for and where did you find it? I think you've borked your partitions.
Transmitted via Bacon

timmaaa said:
Exactly which device is that kernel for and where did you find it? I think you've borked your partitions.
Transmitted via Bacon
Click to expand...
Click to collapse
It's for nexus4. I found it here I guess.

You guess? You didn't find it here, not in the OnePlus One section. My guess is you wandered into the N4 subforum by mistake. That's one very costly mistake. Unfortunately this is how flashing a kernel that's interned for an entirely different device usually ends. If you know it's for the Nexus, why on earth would you flash it on your OnePlus One?
Transmitted via Bacon

timmaaa said:
You guess? You didn't find it here, not in the OnePlus One section. My guess is you wandered into the N4 subforum by mistake. That's one very costly mistake. Unfortunately this is how flashing a kernel that's interned for an entirely different device usually ends. If you know it's for the Nexus, why on earth would you flash it on your OnePlus One?
Transmitted via Bacon
Click to expand...
Click to collapse
By "here" I meant in xdadevelopers forums. I know it's a mistake. And at that time I didn't know it was ONLY for nexus. Any idea how to unbork it?

I just noticed that it's showing up as QHSUSB_BULK on your PC, you're bricked. I believe the only possible solution is to have a jtag repair done on it. But, you're probably gonna have a hard time finding someone that does jtag repairs on this phone.
All in all, you've learned a really important (and expensive) lesson here. XDA is made up of device-specific sections, when you own a device you absolutely must stay within your device's subforum.
Transmitted via Bacon

timmaaa said:
I just noticed that it's showing up as QHSUSB_BULK on your PC, you're bricked. I believe the only possible solution is to have a jtag repair done on it. But, you're probably gonna have a hard time finding someone that does jtag repairs on this phone.
All in all, you've learned a really important (and expensive) lesson here. XDA is made up of device-specific sections, when you own a device you absolutely must stay within your device's subforum.
Transmitted via Bacon
Click to expand...
Click to collapse
Maybe I could try push recovery.img from http://forum.xda-developers.com/showthread.php?t=2780894 ?

All the files you may need are in this zip :
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed-fastboot.zip

DSwissK said:
Maybe I could try push recovery.img from http://forum.xda-developers.com/showthread.php?t=2780894 ?
Click to expand...
Click to collapse
You could try but judging from experience I wouldn't get your hopes up too much.
Transmitted via Bacon

I tried to push recovery.img file and... no change. Still black screen, still no adb, no fastboot, no factory reset...

I think your time would be better spent tying to locate someone who does jtag repairs on this device. You can't push a recovery to a partition that doesn't exist anymore.
Transmitted via Bacon

timmaaa said:
I think your time would be better spent tying to locate someone who does jtag repairs on this device. You can't push a recovery to a partition that doesn't exist anymore.
Transmitted via Bacon
Click to expand...
Click to collapse
I think oneplus would repair his phone. At a cost though.
Sent from my One using Tapatalk

Yeah they would. But jtag would be cheaper. OnePlus will charge for a new main board.
Transmitted via Bacon

Unnecessary now.
Transmitted via Bacon

timmaaa said:
I think your time would be better spent tying to locate someone who does jtag repairs on this device. You can't push a recovery to a partition that doesn't exist anymore.
Transmitted via Bacon
Click to expand...
Click to collapse
Alright, thanks. I'll try to find someone in my country (Switzerland).

[Q] Bricked my One XL by flashing the wrong boot.img file

I was following Timmaaas 'How To' guide to a tee when I got to step #5 and and did the Reboot to find that my phone is now bricked. I was racking my brain trying to understand what I did wrong and I realize that I used the wrong Boot.img file when I flashed it!
I was having issues during the entire process and realized it was because I was using the CyanogenMod One X ROM instead of the XL. This was causing me to get an 'Error 7' until I switched to the XL and everything downloaded fine. However, I completely forgot to replace the Boot.img and ended up flashing my phone with the One X boot.img instead of the XL!
The phone is not responding at all. I did have it plugged into the computer and after it became bricked my computer downloaded the Qualcomm USB drivers for 9006 but its still not responding at all.
Is there anything I can do? It seems like all I need to do is change that one boot file and I would be golden. Please keep in mind this is my first Root so if you know of a way to fix I would really appreciate it if you can teach me in simple terms if possible.
Thanks so much! I really appreciate all you guys do at XDA you help an enormous amount of people. A donation from me is on the way! :good:
EDIT: I kept messing with the power button trying to boot it over and over and finally it launched to HTC one entry screen with the red text for a little less then 1 second but then shut back off. Maybe this gives some hope?

You're gonna need to get a jtag repair done. There's just no way for you to get the device to the bootloader in order to flash the right boot.img because it won't boot due to you borking the boot partition.
Transmitted via Bacon

BrickedAmbitions said:
EDIT: I kept messing with the power button trying to boot it over and over and finally it launched to HTC one entry screen with the red text for a little less then 1 second but then shut back off. Maybe this gives some hope?
Click to expand...
Click to collapse
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.

nem1yan said:
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.
Click to expand...
Click to collapse
No I can't issue any commands. I guess its toast, oh well. How do I get the jtag repairs done?

nem1yan said:
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.
Click to expand...
Click to collapse
There's no way the phone can get to the bootloader, it ain't gonna happen with a broken boot partition.
BrickedAmbitions said:
No I can't issue any commands. I guess its toast, oh well. How do I get the jtag repairs done?
Click to expand...
Click to collapse
You need to find a jtag repairer in your area.
Transmitted via Bacon

Super hard bricked Oneplus One.

Okay, so I was flashing full stock + unroot using WugFresh Bacon Root Toolkit.
It got up to flashing the RPM, completed that and then rebooted into bootloader.. It never rebooted it just shut down and didn't come back on.
Dead screen, can't reboot into bootloader, fastboot, normal reboot, nothing on screen at all ever, the charging LED doesn't even come on.
Device is not recognised on my computer at all, under any device name.
Took the back casing off, unhooked the battery and rehooked it back on again.. Nothing.
Thinking the phone is well and truly f*cked.
What are my options guys? Contact Oneplus customer service and play roulette to see if I actually get a response from them within a 3 month period and then have to face the gigantic cost of posting the phone back to them from Australia on the hopes of getting a new one? Or just buy a new phone, the S6 just came out so that's an option.

Lesson: don't use toolkits.
Anyway, give this a try:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If that doesn't revive your phone nothing will. There's no point in contacting OnePlus about this unless you're happy to pay for whatever repairs are needed, this doesn't fall under warranty.
Transmitted via Bacon

timmaaa said:
Lesson: don't use toolkits.
Anyway, give this a try:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If that doesn't revive your phone nothing will. There's no point in contacting OnePlus about this unless you're happy to pay for whatever repairs are needed, this doesn't fall under warranty.
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah like I said earlier.. It isn't recognised via USB at all. Thanks anyway.
It wasn't a fault of the toolkit, it was the fault of the phone itself. I use it because it saves me time, who can be arsed typing that manually when you have a .bat to do it for you?

Stevles said:
Yeah like I said earlier.. It isn't recognised via USB at all. Thanks anyway.
Click to expand...
Click to collapse
Yeah, and many of the people who have successfully revived their phones using that method weren't able to recognise their phone via usb to start with either. But hey, I guess it isn't worth trying.
Transmitted via Bacon

timmaaa said:
Yeah, and many of the people who have successfully revived their phones using that method weren't able to recognise their phone via usb to start with either. But hey, I guess it isn't worth trying.
Transmitted via Bacon
Click to expand...
Click to collapse
"A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB"
AS I SAID the device is not showing up on the computer, AT ALL. Under any device name.
It does not vibrate when I hold the power button for 20 seconds, it has no ADB, no fastboot, no nothing.
But hey, thanks for being an arsehole about it. Really appreciate it.

Stevles said:
"A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB"
AS I SAID the device is not showing up on the computer, AT ALL. Under any device name.
It does not vibrate when I hold the power button for 20 seconds, it has no ADB, no fastboot, no nothing.
But hey, thanks for being an arsehole about it. Really appreciate it.
Click to expand...
Click to collapse
I know what a hard brick is. And as I said, many people who thought they were hard-bricked have revived their phones with that method. It isn't your usual detect-by-fastboot fix. Isn't it worth a try? Others in your situation have had success with it.
Plus, if your phone is actually 100% hard-bricked, why are you posting here? If that's the case there's absolutely nothing that can be done. You came here looking for help, I'm giving you the link to the one thing that has a chance of saving your phone.
Transmitted via Bacon
---------- Post added at 12:40 ---------- Previous post was at 12:39 ----------
Jessooca said:
Wugfresh is the one of the most reputable and is the most downloaded developer on all of XDA look it up. So suggesting not to use toolkits is ridiculous.
Send me a PM of your issues and I'll see if I can't get you back up and running... Provide me all the details of what all your phone does and does not do, etc... I've read all that you've said above, so I suppose just tell me what it DOES so if anything, Thanks
- Jessooca
---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------
+1
Click to expand...
Click to collapse
It doesn't matter how reputable a toolkit is, they cause problems, this thread is a testament to that. You can find many threads just like this one in this very q&a section that describe very similar issues after using a toolkit.
Transmitted via Bacon

timmaaa said:
I know what a hard brick is. And as I said, many people who thought they were hard-bricked have revived their phones with that method. It isn't your usual detect-by-fastboot fix. Isn't it worth a try? Others in your situation have had success with it.
Plus, if your phone is actually 100% hard-bricked, why are you posting here? If that's the case there's absolutely nothing that can be done. You came here looking for help, I'm giving you the link to the one thing that has a chance of saving your phone.
Transmitted via Bacon
---------- Post added at 12:40 ---------- Previous post was at 12:39 ----------
It doesn't matter how reputable a toolkit is, they cause problems, this thread is a testament to that. You can find many threads just like this one in this very q&a section that describe very similar issues after using a toolkit.
Transmitted via Bacon
Click to expand...
Click to collapse
Actually in this case I'm almost 100% sure it was due to the fact I had just installed Oxygen OS and was reverting back to stock from it. Had nothing to do with the toolkit. Not to mention, I have never had any problems with this toolkit in the past and I would still recommend it to people who want to save them self from hassle and wasting time. Thanks anyway.
By the way, anyone reading this: Stay the hell away from OxygenOS. Nothing but dramas from it, it seems. Not forgetting to mention the fact it is literally just a stock version of Lollipop anyway! Better off with CM12S or BlissPop or any of the CFW's out there.

Stevles said:
Actually in this case I'm almost 100% sure it was due to the fact I had just installed Oxygen OS and was reverting back to stock from it. Had nothing to do with the toolkit. Not to mention, I have never had any problems with this toolkit in the past and I would still recommend it to people who want to save them self from hassle and wasting time. Thanks anyway.
By the way, anyone reading this: Stay the hell away from OxygenOS. Nothing but dramas from it, it seems. Not forgetting to mention the fact it is literally just a stock version of Lollipop anyway! Better off with CM12S or BlissPop or any of the CFW's out there.
Click to expand...
Click to collapse
I agree that there are better ROMs available for this phone, but that's just our opinion, heaps of people have been looking for a stock aosp experience on this phone and I think Oxygen is as close as you could get. As for the ROM itself causing problems, I don't think that's it. I flashed it to test it out and went back to my previous ROM without a single issue (as have many others). I think it's a matter of taking the care to flash the right firmware/modem before reverting back to whatever ROM was running previously, otherwise it's kinda asking for trouble.
So have you tried the unbrick method I linked you to? I'm not saying it's definitely going to fix your problem. What I'm saying is there have been several cases of this phone showing all the signs of being hard bricked, without it actually being hard bricked, and that's the fix that saved those phones. You might be hard bricked, or your phone might fall into the category that I just mentioned, but at this point anything has to be worth a try.
Transmitted via Bacon

timmaaa said:
I agree that there are better ROMs available for this phone, but that's just our opinion, heaps of people have been looking for a stock aosp experience on this phone and I think Oxygen is as close as you could get. As for the ROM itself causing problems, I don't think that's it. I flashed it to test it out and went back to my previous ROM without a single issue (as have many others). I think it's a matter of taking the care to flash the right firmware/modem before reverting back to whatever ROM was running previously, otherwise it's kinda asking for trouble.
So have you tried the unbrick method I linked you to? I'm not saying it's definitely going to fix your problem. What I'm saying is there have been several cases of this phone showing all the signs of being hard bricked, without it actually being hard bricked, and that's the fix that saved those phones. You might be hard bricked, or your phone might fall into the category that I just mentioned, but at this point anything has to be worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
Read through it and the sole problem of why it won't work is that there is no communication with my phone via my computer at all. The point of that tutorial is to unbrick your device by manipulating what your computer see's as the device (Qualcomm generic hardware ID being reported) unfortunately I can't even see that. I think it's just a lost cause unfortunately. But thank you for taking an interest.
UPDATE: Wow what do you know? After trying for an hour of powering on/off and trying to fastboot and flashmode and all that jazz and no luck, tried it on my laptop and sure enough it popped up with the Qualcomm generic driver ID. Whole bunch of screwing around and now it is booting into ColosOS. Thanks guys for the links and offers of help!

Stevles said:
Read through it and the sole problem of why it won't work is that there is no communication with my phone via my computer at all. The point of that tutorial is to unbrick your device by manipulating what your computer see's as the device (Qualcomm generic hardware ID being reported) unfortunately I can't even see that. I think it's just a lost cause unfortunately. But thank you for taking an interest.
UPDATE: Wow what do you know? After trying for an hour of powering on/off and trying to fastboot and flashmode and all that jazz and no luck, tried it on my laptop and sure enough it popped up with the Qualcomm generic driver ID. Whole bunch of screwing around and now it is booting into ColosOS. Thanks guys for the links and offers of help!
Click to expand...
Click to collapse
Lol, I knew that was going to get your phone up and running again [emoji14]
Very glad to see that your phone has been revived from the dead
Transmitted via Bacon

timmaaa said:
Lol, I knew that was going to get your phone up and running again [emoji14]
Very glad to see that your phone has been revived from the dead
Transmitted via Bacon
Click to expand...
Click to collapse
You earn a medal!
You can even help people who don't want to get helped
Way to go, Tim

Same thing happen to me whike swithing back to stoc. After using oxygen but i m flashing the factory images flashall.bat but after this hard brick my device after changing or trying able to connect my like bulkusb kind of in device manager and use one plus one recovery toolkit 1.0 it will brink my complete dead one plus one to life try buddy

rakesh595160 said:
Same thing happen to me whike swithing back to stoc. After using oxygen but i m flashing the factory images flashall.bat but after this hard brick my device after changing or trying able to connect my like bulkusb kind of in device manager and use one plus one recovery toolkit 1.0 it will brink my complete dead one plus one to life try buddy
Click to expand...
Click to collapse
Yeah, I'm just gonna wait for the CM12S OTA. Tried most every other ROM and was not impressed. This being said, I'm still buying an S6 in two days. Will be keeping my OPO to satisfy my ROM flashing/android manipulating needs and using the S6 for everything else a smart phone offers

Stevles said:
UPDATE: Wow what do you know? After trying for an hour of powering on/off and trying to fastboot and flashmode and all that jazz and no luck, tried it on my laptop and sure enough it popped up with the Qualcomm generic driver ID. Whole bunch of screwing around and now it is booting into ColosOS. Thanks guys for the links and offers of help!
Click to expand...
Click to collapse
How did u get it unbricked / ur PC to recognize ur OPO? Im having the same hard brick issue... my OPO is completely dead, doesnt even charge at all too. :crying:

MatLiamSousa said:
How did u get it unbricked / ur PC to recognize ur OPO? Im having the same hard brick issue... my OPO is completely dead, doesnt even charge at all too. :crying:
Click to expand...
Click to collapse
Try plugging it into a different computer.. That was what worked for me.
Don't know if it was necessary (in fact I am almost certain it isn't) but In my haste I took off the back cover and unscrewed a thousand small screws with my jewellers kit and unplugged the battery and plugged it back in. Like I said, not necessary.
Even if it doesn't look like it's charging.. If you can't see it on a computer at all then keep it on charge for a few hours anyway.. It can't hurt.
Best of luck!

Stevles said:
Okay, so I was flashing full stock + unroot using WugFresh Bacon Root Toolkit.
It got up to flashing the RPM, completed that and then rebooted into bootloader.. It never rebooted it just shut down and didn't come back on.
Dead screen, can't reboot into bootloader, fastboot, normal reboot, nothing on screen at all ever, the charging LED doesn't even come on.
Device is not recognised on my computer at all, under any device name.
Took the back casing off, unhooked the battery and rehooked it back on again.. Nothing.
Thinking the phone is well and truly f*cked.
What are my options guys? Contact Oneplus customer service and play roulette to see if I actually get a response from them within a 3 month period and then have to face the gigantic cost of posting the phone back to them from Australia on the hopes of getting a new one? Or just buy a new phone, the S6 just came out so that's an option.
Click to expand...
Click to collapse
hello buddy,
i got same situation like yours. but the only different thing is when i connect my opo to my laptop and press the power button with vol up key it connects to my laptop showing QHUSB_BULK. I update it with ANDROID ADB INTERFACE and it does but thats it nothing else. i cant go fastboot or adb.
CAN YOU PLEASE tell me how you fixed your super hard bricked opo like mine...
thank you.

dewan555 said:
hello buddy,
i got same situation like yours. but the only different thing is when i connect my opo to my laptop and press the power button with vol up key it connects to my laptop showing QHUSB_BULK. I update it with ANDROID ADB INTERFACE and it does but thats it nothing else. i cant go fastboot or adb.
CAN YOU PLEASE tell me how you fixed your super hard bricked opo like mine...
thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
From previous comment on thread.

dewan555 said:
hello buddy,
i got same situation like yours. but the only different thing is when i connect my opo to my laptop and press the power button with vol up key it connects to my laptop showing QHUSB_BULK. I update it with ANDROID ADB INTERFACE and it does but thats it nothing else. i cant go fastboot or adb.
CAN YOU PLEASE tell me how you fixed your super hard bricked opo like mine...
thank you.
Click to expand...
Click to collapse
No that is exactly like what happened to mine. Follow the guide to the letter and it'll fix it up if you did it right, it fixed mine.
Best of luck!

help plz
The step to install color fails every time. Suggestion plz....
Here is the log(both in windows 8.1 & xp) plz help...
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED

mobasser said:
The step to install color fails every time. Suggestion plz....
Here is the log(both in windows 8.1 & xp) plz help...
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
Click to expand...
Click to collapse
Instead of posting this multiple times in various threads (double posting is against the rules) you should ask this question in the unbrick thread.
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732

OnePlus One - stuck on Resurrection boot

Hello guys,
I apologize if this has been solved before but I wasn't able to find anything on it.
I have a oneplus one phone which I had running Ressurection Rom (I don't have the details as my father was using it for the last 2 years).
He dropped the phone and gave it to a shop for repairing of the screen. They repaired the screen but now they have somehow messed with the software where I am UNABLE TO BOOT TO FASTBOOT OR TRWP. The function of holding POWER + VOLUME DOWN or POWER + VOLUME UP doesn't work. When I attempt those two options, it still continues to boot as it normally would and then start optimizing apps. Does that for about 45 minutes and then just restarts and repeats the process.
I haven't messed around with android stuff for about a year now, so simplified instructions (rather step by step) would be extremely helpful.
Thank you so much for taking the time.

NSingh95 said:
Hello guys,
I apologize if this has been solved before but I wasn't able to find anything on it.
I have a oneplus one phone which I had running Ressurection Rom (I don't have the details as my father was using it for the last 2 years).
He dropped the phone and gave it to a shop for repairing of the screen. They repaired the screen but now they have somehow messed with the software where I am UNABLE TO BOOT TO FASTBOOT OR TRWP. The function of holding POWER + VOLUME DOWN or POWER + VOLUME UP doesn't work. When I attempt those two options, it still continues to boot as it normally would and then start optimizing apps. Does that for about 45 minutes and then just restarts and repeats the process.
I haven't messed around with android stuff for about a year now, so simplified instructions (rather step by step) would be extremely helpful.
Thank you so much for taking the time.
Click to expand...
Click to collapse
This condition is called hard brick.To fix this,
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
Use this tool on winXp or win7(don't use 8 or 10),run it as administrator.Make sure you install the drivers correctly,good luck!

Mr.Ak said:
This condition is called hard brick.To fix this,
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
Use this tool on winXp or win7(don't use 8 or 10),run it as administrator.Make sure you install the drivers correctly,good luck!
Click to expand...
Click to collapse
Hello, Thank you for your response.
I have tried the instructions that you provided and I am stuck in a place where the "Samsung" drivers for OPO are installed but the phone isn't detected by the computer when its plugged in. I assume that means the drivers aren't installed correctly. However, when I do open device manager and attempt to update or uninstall the drivers there isn't a device there that is representative of OPO.
How do I get to the point where the drivers can be installed without me having access to the phone. I can't really go into a bricked phone and turn on ADB etc.'
Thank you

NSingh95 said:
Hello, Thank you for your response.
I have tried the instructions that you provided and I am stuck in a place where the "Samsung" drivers for OPO are installed but the phone isn't detected by the computer when its plugged in. I assume that means the drivers aren't installed correctly. However, when I do open device manager and attempt to update or uninstall the drivers there isn't a device there that is representative of OPO.
How do I get to the point where the drivers can be installed without me having access to the phone. I can't really go into a bricked phone and turn on ADB etc.'
Thank you
Click to expand...
Click to collapse
Read the whole thread.
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Use Xp or win7(must).

Okay so I have attempted this a tiring number of times; initially the phone at least was going on to loading apps, now it just flashes on the Resurrection load screen and doesn't change at all. Also when I try to boot into recovery/fastboot, nothing happens.
I have also tried installing different drivers from like a samsung phone, nexus but to no avail.
Is there anyone who can perhaps TEAMVIEW me and help out or live chat?

NSingh95 said:
Okay so I have attempted this a tiring number of times; initially the phone at least was going on to loading apps, now it just flashes on the Resurrection load screen and doesn't change at all. Also when I try to boot into recovery/fastboot, nothing happens.
I have also tried installing different drivers from like a samsung phone, nexus but to no avail.
Is there anyone who can perhaps TEAMVIEW me and help out or live chat?
Click to expand...
Click to collapse
Device on Twrp works fine?

Mr.Ak said:
Device on Twrp works fine?
Click to expand...
Click to collapse
I'm not able to boot into twrp.

NSingh95 said:
I'm not able to boot into twrp.
Click to expand...
Click to collapse
@psxda97 ,can this be a battery issue?

Mr.Ak said:
@psxda97 ,can this be a battery issue?
Click to expand...
Click to collapse
I don't think so. If it is a battery issue he could go to fastboot since fastboot only uses a small amount of charge.
NSingh95 said:
I'm not able to boot into twrp.
Click to expand...
Click to collapse
Try turning on your phone while connected to a charger.

psxda97 said:
I don't think so. If it is a battery issue he could go to fastboot since fastboot only uses a small amount of charge.
Try turning on your phone while connected to a charger.
Click to expand...
Click to collapse
I have, its definitely not a battery issue, because i have seen the phone stay on for an hour just on the bootscreen without being plugged in or anything.

NSingh95 said:
I have, its definitely not a battery issue, because i have seen the phone stay on for an hour just on the bootscreen without being plugged in or anything.
Click to expand...
Click to collapse
Most probably your volume buttons were messed up during the repair. That's the only reason I can think of. There are some videos on YouTube about fixing the volume buttons.

I think I just totalled my H910...

So, I was trying to root my V20 I legit just purchased earlier today.
I followed the Dirty Santa guide, and it worked out great. I was in TWRP and I went to wipe the cache, and accidentally wiped the whole thing. While I was attempting to fix it, I was putting a MicroSD card back into the slot and knocked the battery out.
I know.
After messing with it for 5 hours, I finally got back to TWRP. In my state of exhaustion and frustration, I accidentally flashed an H918 ROM onto the phone in TWRP. It restarted, and now it's totally dead. Black screened. Won't turn on, can't use any button combinations to get it into fast boot nor recovery.
Any ideas?

aNGERY said:
So, I was trying to root my V20 I legit just purchased earlier today.
I followed the Dirty Santa guide, and it worked out great. I was in TWRP and I went to wipe the cache, and accidentally wiped the whole thing. While I was attempting to fix it, I was putting a MicroSD card back into the slot and knocked the battery out.
I know.
After messing with it for 5 hours, I finally got back to TWRP. In my state of exhaustion and frustration, I accidentally flashed an H918 ROM onto the phone in TWRP. It restarted, and now it's totally dead. Black screened. Won't turn on, can't use any button combinations to get it into fast boot nor recovery.
Any ideas?
Click to expand...
Click to collapse
Hehe... what happens when plugging to charger or connecting to your pc, which rom did you flashed

messi2050 said:
Hehe... what happens when plugging to charger or connecting to your pc, which rom did you flashed
Click to expand...
Click to collapse
nothing at all. and this:
https://forum.xda-developers.com/v20/how-to/h918-twrp-flashable-stock-firmwares-t3619671
I guess the 918 and 910 look TOO similar on a 1440P screen
sometimes you gotta laugh to keep from crying.
Luckily, it was only 240 dollars.

aNGERY said:
nothing at all. and this:
https://forum.xda-developers.com/v20/how-to/h918-twrp-flashable-stock-firmwares-t3619671
I guess the 918 and 910 look TOO similar on a 1440P screen
sometimes you gotta laugh to keep from crying.
Luckily, it was only 240 dollars.
Click to expand...
Click to collapse
Ouch unfortunately this is a complete rom that updates every partition on your device including bootloader... which killed your device..:crying: if you managed to get back into your device their maybe a chance.. sorry for that..

918 bootloader on 910=brick. no way round that.

If that were to happen to me i think i would be trying everything even if it doesnt make sense LOL! (Like..... puting the phone on the fridge, or disarming the whole phone and disconnecting the motherboard and then reconnecting it again and all) ... But... I've never flashed a rom not intended for my device. I've always been careful with that.

You're in luck, download your stock rom & try my method...
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222

Prowler_gr said:
You're in luck, download your stock rom & try my method...
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Click to expand...
Click to collapse
will this work even if i can't get a screen?

Yep, I restored a total brick (would only boot into firmware restore screen)
Just follow the thread about installing & setting LGUP, replace the files with the contents of the zip & off you go...

Prowler_gr said:
Yep, I restored a total brick (would only boot into firmware restore screen)
Just follow the thread about installing & setting LGUP, replace the files with the contents of the zip & off you go...
Click to expand...
Click to collapse
this won't even get into any screen. i press power and get nothing.

Pull battery & reinsert. Pressing the up-volume key insert your usb cable (connected to PC), to get into download mode

Prowler_gr said:
Pull battery & reinsert. Pressing the up-volume key insert your usb cable (connected to PC), to get into download mode
Click to expand...
Click to collapse
unfortunately, i still get nothing =(

Is your battery charged?

Prowler_gr said:
Is your battery charged?
Click to expand...
Click to collapse
it sure is

http://www.youtube.com/watch?v=76jVJXDYzkc

Prowler_gr said:
http://www.youtube.com/watch?v=76jVJXDYzkc
Click to expand...
Click to collapse
just tried it out, no go.
i DO hear windows detecting the USB connection, and in device manager i am getting QUSB_BULK

Different story then... You will need QPST tools to at least flash the aboot partition (which contains the download mode), then you should be able to restore with LGUP.

Prowler_gr said:
Different story then... You will need QPST tools to at least flash the aboot partition (which contains the download mode), then you should be able to restore with LGUP.
Click to expand...
Click to collapse
do you know how to do that stuff?

I'd probably be able to work it all out if it was my phone. Google is your friend. On the other hand it would be faster to go to a professional shop (with tools such as octoplus or z3x) to do it for you for a fee if warranty is not an option.

All phones SHOULD be covered LG's warranty. I'm not sure if they'lll ask for proof of a receipt, but i'm pretty sure they will considering they asked for it when I sent in my LG tone platinums. If that's the case, ask the og owner if they still have it. No one is really developing for the H910 model anyways so you saved yourself some frustration in the long-run.