Develop Bugs

HTC Desire HD not starting after unsuccessful rooting. please help. i am scared :/

i Couldn't find my problem in the forums im sorry if im repeating it, seriously... im sorry. its about my HTC Desire HD.
i was using Advanced Ace Hack Kit and everything was fine, i downloaded the ROM as the cmd asked me to, installed it, rebooted it twice accroding to the cmd, but then it said something about pressing power button once this step finishes, and thats when my phone got stuck, the volume keys werent working and neither was the power key, just then my power went out and everything crashed!!
now when i turn on my HTC DESIRE HD, it starts but stucks at "HTC" white splash screen; not even "quietly brilliant" comes up, it just stucks on the white screen with HTC... i dont know what to do, please help me someone? did i brick it? can it be repaired if i send it into HTC for repair? please help me!!
once again please guys im extremly sorry if im repeating a thread with this one, im new but i still searched for half an hour over the internet but with no vain. PLEASE REPLY!
its my first expensive phone, and its only been with me for 2 weeks, if this is ruined then my parents wont buy me any other phone.
*fingers-crossed*

Ok man don't panic, just re run the hack kit from the white screen. If it is not working just let me know....
Sent from my Inspire 4G using xda app-developers app

still nothing :/
glevitan said:
Ok man don't panic, just re run the hack kit from the white screen. If it is not working just let me know....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
tried that just now with the phone off and plugged in (constant orange light) and with the phone on and plugged in(white screen only, no LEDs) and the hack kit just shows the message :
***ERROR ERROR ERROR***
Phone not plugged in
OR
Driver not installed
OR
USB Debugging not enabled.
***ERROR ERROR ERROR***
the pressing vol up button+power button also doesnt do anything, and the screen sticks to the white part for hours :/

I can't help much since my phone is "away" in the insurance company.
But have tried reflash of RUU
Sent from my Desire HD using XDA Premium App

trying that :|
XDA_h3n said:
I can't help much since my phone is "away" in the insurance company.
But have tried reflash of RUU
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
im downloading the custom ROM i found a link to online, which said that i should just connected the switched off phone and run the executable file. fingers scrossed and hoping it works.
believe me buddy; im craving for the one X or even the one S.
but i will get that only if i make through with the DESIRE HD for at-least a year lol, doesn't seem quite possible as of the situation right now.

Ashjerk said:
tried that just now with the phone off and plugged in (constant orange light) and with the phone on and plugged in(white screen only, no LEDs) and the hack kit just shows the message :
***ERROR ERROR ERROR***
Phone not plugged in
OR
Driver not installed
OR
USB Debugging not enabled.
***ERROR ERROR ERROR***
the pressing vol up button+power button also doesnt do anything, and the screen sticks to the white part for hours :/
Click to expand...
Click to collapse
Ok...You Need to reflash the Ruu....do You know how to Get the Cid number

RE:
glevitan said:
Ok...You Need to reflash the Ruu....do You know how to Get the Cid number
Click to expand...
Click to collapse
sorry my network was down. back on now, i dont know what the CiD number is, so yeah i dont know how to get it. sorry :/

Ashjerk said:
sorry my network was down. back on now, i dont know what the CiD number is, so yeah i dont know how to get it. sorry :/
Click to expand...
Click to collapse
Man are u online?? I am sending u a PM...
---------- Post added at 03:31 AM ---------- Previous post was at 03:15 AM ----------
Ashjerk said:
tried that just now with the phone off and plugged in (constant orange light) and with the phone on and plugged in(white screen only, no LEDs) and the hack kit just shows the message :
***ERROR ERROR ERROR***
Phone not plugged in
OR
Driver not installed
OR
USB Debugging not enabled.
***ERROR ERROR ERROR***
the pressing vol up button+power button also doesnt do anything, and the screen sticks to the white part for hours :/
Click to expand...
Click to collapse
ok...if you press power + volume up you will never get to hboot...it's volume + power down.
To get the cid number, just boot in hboot, choose fastboot and plug the phone until you see fastboot usb in red. Then open a cmd in the pc and type fastboot getvar all. INFOcidnum is the information u need to get the ruu,

RE:
glevitan said:
Man are u online?? I am sending u a PM...
---------- Post added at 03:31 AM ---------- Previous post was at 03:15 AM ----------
ok...if you press power + volume up you will never get to hboot...it's volume + power down.
To get the cid number, just boot in hboot, choose fastboot and plug the phone until you see fastboot usb in red. Then open a cmd in the pc and type fastboot getvar all. INFOcidnum is the information u need to get the ruu,
Click to expand...
Click to collapse
yo if you're still there; i tried running the RUU executable file and after trying to read from my android phone, it says "error[170]: USB connection error".

Hopefully you get everything figured out dude

Ashjerk said:
yo if you're still there; i tried running the RUU executable file and after trying to read from my android phone, it says "error[170]: USB connection error".
Click to expand...
Click to collapse
Be patient, he'll sort things out.
@glevitan - lol..... second time I see you giving the instructions with the volume + power. You gotta remember it's volume down + power button
Sent from a dream.

I have exactly the same problem.
I cannot run a RUU as my computer won't detect the phone is connected via USB.
Any ideas? I've literally spent the past 4 hours trying to fix it.

klawsterfobik said:
I have exactly the same problem.
I cannot run a RUU as my computer won't detect the phone is connected via USB.
Any ideas? I've literally spent the past 4 hours trying to fix it.
Click to expand...
Click to collapse
Try installing the htc drivers/sync on your computer.
Sent from a dream.

Teichopsia said:
Try installing the htc drivers/sync on your computer.
Sent from a dream.
Click to expand...
Click to collapse
Done, but with no luck. The computer recognizes that the phone has been connected (it beeps and shows "Android Phone - Android Bootloader Interface") but I can't access it like a disk drive.
When I try to run the RUU I get an error saying it can't connect to the USB port...
** I un-installed, then re-installed HTC Sync and it picked the phone up and installed the drivers. So i'm doing the RUU at the moment and all seems to be running sweet. Its just finished and re-starting for the first time in a couple of hours! **
I'll try this rooting thing again eh!

Dont install HTC sync and disconnect ur computer from interner
klawsterfobik said:
Done, but with no luck. The computer recognizes that the phone has been connected (it beeps and shows "Android Phone - Android Bootloader Interface") but I can't access it like a disk drive.
When I try to run the RUU I get an error saying it can't connect to the USB port...
** I un-installed, then re-installed HTC Sync and it picked the phone up and installed the drivers. So i'm doing the RUU at the moment and all seems to be running sweet. Its just finished and re-starting for the first time in a couple of hours! **
I'll try this rooting thing again eh!
Click to expand...
Click to collapse
While using the ace hack dont install HTC sync use the drivers given in "*\tools\windrivers" folder
Most importantly Do not connect your computer to the internet As the driver manager checks for the latest drivers in microsoft website.. I was stuck there for a long time but nothing happened..
when ur not connected to internet it will take the drivers of "Android 1" which is already installed by installing "HTCDriver3.0.0.007.exe" from "*\tools\windrivers" folder.
Comin back the boot screen. Only HTC was visible on the screen after rooting but started the Ace hack again which removed this problem

You'll have a more successful ROOT if you use Ubuntu or a Ubuntu Live CD as I assume your using Windows right ? I used Ubuntu and rooted first time with no problems.

Thanks very

Ashjerk said:
i Couldn't find my problem in the forums im sorry if im repeating it, seriously... im sorry. its about my HTC Desire HD.
i was using Advanced Ace Hack Kit and everything was fine, i downloaded the ROM as the cmd asked me to, installed it, rebooted it twice accroding to the cmd, but then it said something about pressing power button once this step finishes, and thats when my phone got stuck, the volume keys werent working and neither was the power key, just then my power went out and everything crashed!!
now when i turn on my HTC DESIRE HD, it starts but stucks at "HTC" white splash screen; not even "quietly brilliant" comes up, it just stucks on the white screen with HTC... i dont know what to do, please help me someone? did i brick it? can it be repaired if i send it into HTC for repair? please help me!!
once again please guys im extremly sorry if im repeating a thread with this one, im new but i still searched for half an hour over the internet but with no vain. PLEASE REPLY!
its my first expensive phone, and its only been with me for 2 weeks, if this is ruined then my parents wont buy me any other phone.
*fingers-crossed*
Click to expand...
Click to collapse
i was in the exact same situation. All you have to do is connect your phone to your pc while its stuck on ''HTC'' boot screen. Wait for like a minute then use cmd and write 'adb reboot bootloader'. You should be able to fix it yourself from there
EDIT: doesnt work once bootloader is unlocked T_T im stuck on the white screen again...

IBeKay said:
i was in the exact same situation. All you have to do is connect your phone to your pc while its stuck on ''HTC'' boot screen. Wait for like a minute then use cmd and write 'adb reboot bootloader'. You should be able to fix it yourself from there
EDIT: doesnt work once bootloader is unlocked T_T im stuck on the white screen again...
Click to expand...
Click to collapse
Reflash a stock rooted rom and it's boot.img (found in the zip) and it will work.Or any custom.

Steam. said:
Reflash a stock rooted rom and it's boot.img (found in the zip) and it will work.Or any custom.
Click to expand...
Click to collapse
I would but there is no way of me getting to bootloader or recovery unless I force it into them, which I cant because I unlocked bootloader...

[Q]how to enter to recovery or download mode without side buttons?

My side buttons is not working for me.(the volume keys)
Any one know any way to boot to recovery?
i have a logo loop now.so i can't enter to the system.
help:crying:

ilia333 said:
My side buttons is not working for me.(the volume keys)
Any one know any way to boot to recovery?
i have a logo loop now.so i can't enter to the system.
help:crying:
Click to expand...
Click to collapse
Use adb from bootlooping screen. The command is "adb reboot recovery". Adb is part of android SDK. There are plenty of guides on how to set up adb out there and its easy.
Sent from my Inspire 4G using xda premium

Gizmoe said:
Use adb from bootlooping screen. The command is "adb reboot recovery". Adb is part of android SDK. There are plenty of guides on how to set up adb out there and its easy.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
"device not found"
i hjave to enter to fastboot mod but i can't.

ilia333 said:
My side buttons is not working for me.(the volume keys)
Any one know any way to boot to recovery?
i have a logo loop now.so i can't enter to the system.
help:crying:
Click to expand...
Click to collapse
As Gizmoe told you..use adb commands to achive that. Use the guide in my signature to see how that is done. :good:
---------- Post added at 11:53 AM ---------- Previous post was at 11:52 AM ----------
ilia333 said:
"device not found"
i hjave to enter to fastboot mod but i can't.
Click to expand...
Click to collapse
Make sure that you have usb debugging enabled and the driver is installed correctly (with the phone unplugged)

glevitan said:
Make sure that you have usb debugging enabled and the driver is installed correctly (with the phone unplugged)
Click to expand...
Click to collapse
It is but i have to be in Hboot to apply the adb commands

ilia333 said:
It is but i have to be in Hboot to apply the adb commands
Click to expand...
Click to collapse
You can run adb from pretty much anywhere. Even if you were stuck in the splashscreen or in the rom.
Sent from a dream.

Teichopsia said:
You can run adb from pretty much anywhere. Even if you were stuck in the splashscreen or in the rom.
Sent from a dream.
Click to expand...
Click to collapse
but how can i check that usb debugging enabled?
if i cant accese the system?

ilia333 said:
but how can i check that usb debugging enabled?
if i cant accese the system?
Click to expand...
Click to collapse
You don´t to have be in hboot to use adb. You have to be with the phone on normally or from the splash screen itself. If you are in hboot then choose fastboot and try from there but using fastboot devices command instead.
As long as you have not factory reseted the phone the usb debugging drivers will stay in the phone.

ilia333 said:
but how can i check that usb debugging enabled?
if i cant accese the system?
Click to expand...
Click to collapse
USB debugging should always be enabled by default in any custom Rom. The thing that will disable it is doing factory reset from hboot screen. But you can't get there anyways so it should be enabled. Start the phone as normal and let it go to splash screen. Plug into pc and be sure to check that pc sees the phone. If not, unplug phone. Uninstall drivers. Re install drivers and then plug phone back in. From adb type "adb devices". You should see your device. After that run the "adb reboot recovery". If it still doesn't see it plug phone into different port. Preferably one that goes straight into mother board and remove any other USB devices that are plugged in.
Sent from my Inspire 4G using xda premium

glevitan said:
You don´t to have be in hboot to use adb. You have to be with the phone on normally or from the splash screen itself. If you are in hboot then choose fastboot and try from there but using fastboot devices command instead.
As long as you have not factory reseted the phone the usb debugging drivers will stay in the phone.
Click to expand...
Click to collapse
any other way to enable it ?
I did a factory reset.
i just installed a new rom.
thank you for trying to help any way/

Go to settings>Applications>development and check USB debugging.
If you're still getting device not recognized, you should reinstall HTC drivers by reinstalling HTC sync. ( if you haven't installed those in the first place, then you won't be able to use adb unless you do)

ilia333 said:
any other way to enable it ?
I did a factory reset.
i just installed a new rom.
thank you for trying to help any way/
Click to expand...
Click to collapse
When you say "factory reset," do you mean that you ran a RUU? Or that you chose "factory reset" in recovery, so you still have a custom ROM installed? If the answer is the latter, you probably have USB Debugging enabled. Just give ADB a try.

bananagranola said:
When you say "factory reset," do you mean that you ran a RUU? Or that you chose "factory reset" in recovery, so you still have a custom ROM installed? If the answer is the latter, you probably have USB Debugging enabled. Just give ADB a try.
Click to expand...
Click to collapse
I have a custom ROM.i did a factory reset from the recovery.
But i have message that "device not found".

ilia333 said:
I have a custom ROM.i did a factory reset from the recovery.
But i have message that "device not found".
Click to expand...
Click to collapse
Do you have the HTC sync drivers installed? If not, you should be able to find guides for it, like glevitan said.

bananagranola said:
Do you have the HTC sync drivers installed? If not, you should be able to find guides for it, like glevitan said.
Click to expand...
Click to collapse
Thank You guys !!!!
I did it.
From fuly turned off phone.

Weird, but hey. Whatever works. Glad you got it.
Sent from my Inspire 4G using xda premium

Bump Bump Bump!!!
I have the same problem with HTC Desire HD!
And guess what? It belongs to my wife!!! And I have to give it back to her or I should stay several nights
in the street.... and instead of a pillow I should put a cat or something under my head!
Problem.... Stuck at htc boot screen... not able to enter recovery
I installed 4ext recovery ages ago....
the main problem is that the volume keys ( both up and down ) are broken and neither of them work!
adb restart recovery doesn't work
no device find!
yes I installed all the drivers, and I can boot other phones into recovery
What should I do?
Please help!
tanx!

hrkh83 said:
Bump Bump Bump!!!
I have the same problem with HTC Desire HD!
And guess what? It belongs to my wife!!! And I have to give it back to her or I should stay several nights
in the street.... and instead of a pillow I should put a cat or something under my head!
Problem.... Stuck at htc boot screen... not able to enter recovery
I installed 4ext recovery ages ago....
adb restart recovery doesn't work
no device find!
yes I installed all the drivers, and I can boot other phones into recovery
What should I do?
Please help!
tanx!
Click to expand...
Click to collapse
How did you end like this? can you access hboot?

glevitan said:
How did you end like this? can you access hboot?
Click to expand...
Click to collapse
How?
I installed the R26.2 successfully, the JB Rom I mean..
Then installed all the tweaks in PIMP my ride successfully again ( I am not a noob.... )
That didn't triggered it...
At the end I was trying to install Int2ext+ and it happened....! I don't know why!
I had done this before on various phones.... I don't know what happened!
The only thing I was able to access so far was HTC BOOT SCREEN! :laugh: and I also
can access a choke hold from my wife soon I guess!
I don't know why these things always happen to her phone... other friends phones are fine when
I change their roms bla bla bla!

hrkh83 said:
How?
I installed the R26.2 successfully, the JB Rom I mean..
Then installed all the tweaks in PIMP my ride successfully again ( I am not a noob.... )
That didn't triggered it...
At the end I was trying to install Int2ext+ and it happened....! I don't know why!
I had done this before on various phones.... I don't know what happened!
The only thing I was able to access so far was HTC BOOT SCREEN! :laugh: and I also
can access a choke hold from my wife soon I guess!
I don't know why these things always happen to her phone... other friends phones are fine when
I change their roms bla bla bla!
Click to expand...
Click to collapse
Pull the battery and then put it back. And try to boot, pressing power + volume down until you get hboot.
Sent from my GT-N7000 using xda app-developers app

Need to return to stock w/out functioning power button

OK here's the quick version of what happened.
Last night, before leaving work, I was playing a game (dice w/buddies) and when I was finished I put the phone to sleep. Picked it up after my 45 min drive home and the screen wouldn't turn on at all. Pulled the battery and as soon as I put it back in the phone vibrated and started the boot process. I didn't even hit the power button. I let it do it's thing and just watched. The screen was all kinds of jacked!! Vertical banding and discoloration to say the least. Well it took about 10 min to boot but when it did the touchscreen was unresponsive. After about 10 min of batt pulls to reboot and check the screen, I called VZW for a replacement.. (They overnighted one and it will be here this morning) So after that call, I just put the phone down and fed my daughter and did a few things around the house. Went back about 2 hrs later and pulled the battery and rebooted the phone to find that the screen now works! BUT the power button does not. It won't wake the phone up,put it to sleep, nothing. It's dead. So I thought I would unroot/relock and take it back to stock so I can send it back. Here is the problem with that; with the power button broken, fastboot won't recognize the phone. I can get into the bootloader via rom toolbox lite (JRummy app) and that works fine. But whether I try it thru adb or WugFresh's toolkit, as soon as the phone hits "Checking fastboot status", it fails. When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
So how can I return to stock without a working power button? Even if I was to get it back to stock somehow, I can't relock it as I would have to hit the power button to accept the warning. Is there any other way?

I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.

eqjunkie829 said:
I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.
Click to expand...
Click to collapse
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."

cubsfan187 said:
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."
Click to expand...
Click to collapse
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.

cupfulloflol said:
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.
Click to expand...
Click to collapse
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.

cubsfan187 said:
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.
Click to expand...
Click to collapse
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.

cubsfan187 said:
When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
cupfulloflol said:
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.
Click to expand...
Click to collapse
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

cubsfan187 said:
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.

cupfulloflol said:
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.
Click to expand...
Click to collapse
This is exactly what I am gonna try after getting the new phone set up. :good:

Bootloop of horror

So I'm currently stuck in a horrible bootloop without the possibility of going in to hboot or recovery.
Was on ViperX 3.6.0 and on XM Kernel 300 when just out of the blue my phone restarted it self and went into a bootloop that i just don't seem to be able to get out of..
When I go in to hboot, it automatically goes to fastboot, then back to hboot, then bootloop (again).
Any suggestions?

How much time do you have to perform a command in the bootloader ?
When the phone hits the bootloader/fastboot usb you hit enter to clear the cache
Fastboot erase cache
Hopefully that solves the loop. Or try to power down

For some magical, mysterious reason, it booted normally - again, out of the blue!
Wth?!
Trying to get a last_kmsg, but ADB won't find my device - but fastboot does!

HoffaLompen said:
For some magical, mysterious reason, it booted normally - again, out of the blue!
Wth?!
Trying to get a last_kmsg, but ADB won't find my device - but fastboot does!
Click to expand...
Click to collapse
if you're using windows probably you're missing the drivers

Weird ! When the viper rom is booted you need to enable usb debugging......

matt95 said:
if you're using windows probably you're missing the drivers
Click to expand...
Click to collapse
Mr Hofs said:
Weird ! When the viper rom is booted you need to enable usb debugging......
Click to expand...
Click to collapse
Drivers are installed, trying to update them.
USB debugging is enabled.
Edit: Managed to get a last_kmsg, Here

Hmm i have no idea what to look at

Mr Hofs said:
Hmm i have no idea what to look at
Click to expand...
Click to collapse
That makes two of us!
Maybe I should post it in Xmister's thread?

Good idea. I may find something odd when i have loads of time. But i haven't

I cant boot my oneplus 3 at all

i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?

There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM

i tried that method but the device doesnt even show up on my pc

envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.

I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification

Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon

No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.

you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867

Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...

rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again

Then use unbrick method 2..

rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all

Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?

I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.

I jeep getting the sahara communication failed error

envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!

Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk

Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?