Bricked beyond repair?

[godraistlin]

So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.

 

[gabriwinter]

Just to rule out the obvious, have you tried different cable and computer?

 

[godraistlin]

Just to rule out the obvious, have you tried different cable and computer?

Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.

 

[gabriwinter]

Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.

I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.

 

[Z-Blade]

How did you brick your OP in the first place? Does it still charge?

 

[godraistlin]

How did you brick your OP in the first place? Does it still charge?

It bricked in the middle of using the unbrick tool. It literally doesn't do anything. No charging, no vibrations. Nothing.

 

[godraistlin]

I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.

device descriptor read/64, error -32

That's the error I got. Problems with USB communication.

 

[Z-Blade]

The fact it does not even charge sounds like a hardware issue. Even when its bricked it should at least charge.

 

[gabriwinter]

device descriptor read/64, error -32

That's the error I got. Problems with USB communication.

This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.

 

[jhs39]

Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.

I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.

There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.

Good luck.

 

[gyedema]

Did you try holding power button for >40 seconds?

 

[dladz]

So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.

If it's totalled then one plus will have no idea what is wrong either, send it back mate.

 

[GAMIT PRUTHVI]

After reviewing all the replies, which won't work for you.

Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.

 

[godraistlin]

If it's totalled then one plus will have no idea what is wrong either, send it back mate.

I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

 

[godraistlin]

After reviewing all the replies, which won't work for you.

Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.

I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

 

[godraistlin]

This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.

I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

 

[godraistlin]

Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.

I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.

There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.

Good luck.

I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.