Related
If you are having problems getting to download mode, Use the Stock Captivate Cable Only when trying to access Download mode!
Story:
I have struggled with 2 captivates now to get into download mode. I have read tons of arguments back and forth from people that say it is easy to get into download mode, and people who say that it is impossible with their phones.
Well, for some history...On my first captivate, I bricked it and it refused to go into download mode...PERIOD. I proceeded to exchange it(I was within my 30 days), and didn't think much more about it. Well, I installed Cognition 2.2 recently and in the process realized that my new phone would go into download mode just fine by doing the standard process of:
1)remove battery, sim, microsim
2)reinserting battery only
3)holding down both volume buttons
4)inserting usb cable
No problems right? Well, I ended up "bricking" my phone by accidentally deleting my framework-res.apk file(don't ask) and lo and behold, I suddenly could not get it to go back into download mode. I was really pissed at this point and spent all night trying everything all over again.
Well, I decided to give up for the night and go to bed. As I was laying in bed a thought crossed my mind. I had purchased a second usb cable(from ATT) to use with the captivate, and the one time that download mode had worked, I was using the standard captivate cable that came in the box. However, every time it wasn't working I was using my second USB cable. So I got up out of bed to try the stock cable and, lo and behold, it works flawlessly every time.
I would venture to guess that this is what the problem is with most everyone else that can not get their captivates to go into download mode. So, if you haven't tried it give it a shot. And certainly tell everyone you know to use the stock cable only.
I just want to reiterate that the spare cable that would NOT work was purchased from ATT and is the cable that they recommend you purchase as a spare. It wasn't like I got it from ebay or something.
Using a usb cable I got from ebay, monoprice, htc, motorola, and stock samsung cable, I was able to get into download mode everytime...
... also, shouldn't this be in general and not in development?
No USB Hubs or Extenders
RECOMMENDED: Use your stock USB cable that came with the phone.
IMPORTANT: Plug the USB cable into your computers native motherboard USB port (the back of your computer). Plugging the cable into USB switches, extenders or external ports, does not allow the phone to enter download mode correctly.
Aerimus said:
I just want to reiterate that the spare cable that would NOT work was purchased from ATT and is the cable that they recommend you purchase as a spare. It wasn't like I got it from ebay or something.
Click to expand...
Click to collapse
I can confirm, although i found this out a whilllllle ago, just didnt think much of it lol
Just so you know. I found that in some cases certain USB cables just will not work with some devices. This has to do with the quality of the cable. I would avoid overly thin or flat cables because they tend to be cheaply made and won't be able to provide a stable power flow. The shorter the cable the better.
shinji257 said:
The shorter the cable the better.
Click to expand...
Click to collapse
The cable he/I bought from AT&T is shorter the the cable that comes in the box, and doesnt work, so im not sure if shorter is better
kkeo said:
Using a usb cable I got from ebay, monoprice, htc, motorola, and stock samsung cable, I was able to get into download mode everytime...
... also, shouldn't this be in general and not in development?
Click to expand...
Click to collapse
I can recreate this over and over again. The reason I put this here and not in general is because I, like many others, have struggled over and over with odin, and people had the attitude of "it works every time, you're just doing something wrong." The reality is that you're trying to prove that I'm just "doing something wrong" because all your cables work. I can recreate this over and over again. What do you want me to do, make a video of it in order for you to believe that there is an actual issue?
I think it's important for people to see this when trying all the roms and mods that are in the development section. In fact, I think it would be REALLY helpful if designgears would add this to the "how to get to download mode" section on the Odin thread. I can't tell you the amount of hours I have spent trying to get into download mode. It is incredibly frustrating to do everything right, and have others telling you that you are not doing it right.
I searched google endlessly looking for a solution to get into download mode, and no where did I see this as a possible solution. Also, as an FYI, when I plug in the other cable, it just goes straight to the battery screen no matter what I press. I can hold down the power and volume buttons to go into recovery mode, but it's impossible to get to download mode.
I have plugged mine into a usb port in the front of my computer as well as in my monitor. I have never had a problem with download mode or anything else.
Aerimus said:
I can recreate this over and over again. The reason I put this here and not in general is because I, like many others, have struggled over and over with odin, and people had the attitude of "it works every time, you're just doing something wrong." The reality is that you're trying to prove that I'm just "doing something wrong" because all your cables work. I can recreate this over and over again. What do you want me to do, make a video of it in order for you to believe that there is an actual issue?
I think it's important for people to see this when trying all the roms and mods that are in the development section. In fact, I think it would be REALLY helpful if designgears would add this to the "how to get to download mode" section on the Odin thread. I can't tell you the amount of hours I have spent trying to get into download mode. It is incredibly frustrating to do everything right, and have others telling you that you are not doing it right.
I searched google endlessly looking for a solution to get into download mode, and no where did I see this as a possible solution. Also, as an FYI, when I plug in the other cable, it just goes straight to the battery screen no matter what I press. I can hold down the power and volume buttons to go into recovery mode, but it's impossible to get to download mode.
Click to expand...
Click to collapse
While this is good to know...It is quite possible you got a faulty second cable, and some of the cables that do come in the box are faulty as well..
It's always a good reminder to try changing out cables if your having an issues. Same for downloading different things that work for a-lot of people and not for you/me..same too for hooking into the back of the computer and bypassing the external hub....Sometimes you get lucky and find the problem right away..sometimes you don't....It's called a process of elimination...
FWIW..I've never trusted cheap ass cables..in anything. Never have..Never will..but..JSYK..expensive cables go bad from time to time too
Thanks for the reminder
Mac
jromney said:
RECOMMENDED: Use your stock USB cable that came with the phone.
IMPORTANT: Plug the USB cable into your computers native motherboard USB port (the back of your computer). Plugging the cable into USB switches, extenders or external ports, does not allow the phone to enter download mode correctly.
Click to expand...
Click to collapse
I use the external ports on the front of my case without a problem...
jromney said:
RECOMMENDED: Use your stock USB cable that came with the phone.
IMPORTANT: Plug the USB cable into your computers native motherboard USB port (the back of your computer). Plugging the cable into USB switches, extenders or external ports, does not allow the phone to enter download mode correctly.
Click to expand...
Click to collapse
I've also noticed that, on my PC at least, my front case USB ports don't always reliably work with this procedure. I've been plugging the USB cable since into the USB ports on the motherboard.
Mac11700 said:
While this is good to know...It is quite possible you got a faulty second cable, and some of the cables that do come in the box are faulty as well..
It's always a good reminder to try changing out cables if your having an issues. Same for downloading different things that work for a-lot of people and not for you/me..same too for hooking into the back of the computer and bypassing the external hub....Sometimes you get lucky and find the problem right away..sometimes you don't....It's called a process of elimination...
FWIW..I've never trusted cheap ass cables..in anything. Never have..Never will..but..JSYK..expensive cables go bad from time to time too
Thanks for the reminder
Mac
Click to expand...
Click to collapse
The thing that throws me off is that this cable works for EVERYTHING else. Data transfer, media syncing, recovery mode, charging, etc... There was never anything that would indicate any issue with the cable. I just want to make sure everyone knows this, because when I was struggling to get into download mode, I didn't see anyone suggest that it could be the cable, even though the cable worked for everything else.
OP - thanks for posting this! It is at least another thing to keep in mind when troubleshooting. I was actually considering getting another cable to keep at work.....
P.S. would we get in trouble for quoting Michael Scott's favorite joke in response to post #6? Yea, I know. Little too obvious right. I'll restrain. Already made myself chuckle anyways
terrigan said:
I've also noticed that, on my PC at least, my front case USB ports don't always reliably work with this procedure. I've been plugging the USB cable since into the USB ports on the motherboard.
Click to expand...
Click to collapse
Um.. not true - Although I did use the stock USB Cable - I was flashing the night away (trying to recover my bricked phone) on my Win7 box using a USB hub that had a few other devices hooked into it.
Never had an issue getting to D/L mode.. and it found the phone again and again and again and again.... (go on for infinity).
I think it has more to do with the hardware your connecting it to and how the USB drivers loaded (i.e. XP=****e) and what type of OS your running more than anything. I had terrible luck with my work's XP rig... but my Win7 x64 rig found the device while in d/l mode - found the drivers?!?! and I was good to go.
Although - it is always a good rule of thumb IF you can't get the device to recognize on your computer to use the original cable and hook to the best source of power for your USB which is the back of your computer.
So.. this isn't a [FIX] - just a good tip. If you can't get into D/L mode by holding the volume button and jamming in the USB or using ADB -> Reboot Download command.. your pretty much fux0red.
I need original USB cable
I just wanted to throw in my $0.02 I needed to use the original USB cable and a port directly on my motherboard. The usb cable I bought from newegg does not work with my MSI X58 motherboard and my capitavate. The original cable does not work if I use a front usb port on my Antec P183 case. Strangly an identical usb cable from newegg that I ordered at the same time does work with my work computer, Dell X38 motherboard.
Ive had the same problem... only way i get it to download mode is via Terminal:
su
reboot download
I really cant get it to work no other way :s
jromney said:
RECOMMENDED: Use your stock USB cable that came with the phone.
IMPORTANT: Plug the USB cable into your computers native motherboard USB port (the back of your computer). Plugging the cable into USB switches, extenders or external ports, does not allow the phone to enter download mode correctly.
Click to expand...
Click to collapse
honestly, i have my phone cord that came into the box, connected to an extender cable, that's connected into a usb port hub so i don't agree with what you're saying here
mine works every single time
This method has been known for some time now, reading really helps...
http://forum.xda-developers.com/showthread.php?t=731989
designgears said:
This method has been known for some time now, reading really helps...
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
I appreciate all your hard work on everything. I read through that post and tried to search it several times... Believe me, I spent hours pouring through the pages looking for something that would work.
No where did I see anyone say to make sure you were using the stock cable because other cables might not work? Feel free to correct me if I'm wrong...there are a lot of pages after all.
Furthermore...I'm sorry to be new to Android and to flashing roms, but we are all new at some point. No one is born an expert.
edit: I'm guessing you misunderstood the post? I wasn't posting about the method...just about the fact that many usb cables, including the micro usb cable that ATT sells, do not work for getting to download mode. If I'm wrong about what you were posting, feel free to correct me. If i'm correct, your post is quite ironic
The first captivate I had WOULD NOT GO INTO DOWNLOAD mode regardless of cable or usb port. I tried every port and every cable including the stock one that came with the phone.
The replacement captivate ALWAYS goes into download mode regardless of cable or port.
It's a tip and thank you for the. But if your phone is one of those that does not have 3 button recovery then it will likely not work with the 2 button download trick either.
USB debugging no longer activates on my phone. Activating it in settings/applications/development brings up the "Allow USB debugging?" permission window. However, no usb notifications appear, and the phone appears to be a dead device to any PC it is connected to.
This started when I accidently got into the download screen from the phone options popup. The display showed the yellow sign, android guy with shovel, and message warning not to turn target off. Phone was not connected to anything at the time.
Searching found a couple of threads indicating that a battery pull was safe to get out of it. Did same.
Since then, usb debugging (or usb anything) has been dead on this phone. Other methods of usb access (thru usb settings) have no effect either.
Tried the following...
(1) restore to my last backup rom.
(2) numerous reboots and battery pulls.
(3) mount/unmount sd card in cwm recovery
(4) clear caches
(5) changed pc's and cables (all worked before)
(6) reinstalled usb drivers on pc (worked before, didn't expect it to help since issue is at phone end)
As you can see, I'm running out of sticks to poke the horse with. Does anyone have any ideas?
Update: new kernel didn't help, either
Update2:
(a) Can't do a restore via odin, which won't detect the phone.
(b) Updated my adb (which I don't use much). adb devices command will not detect the phone via usb.
(c) Installed adbWireless which allowed me to push a stock nandroid backup to the phone. Restored that, usb is still dead.
(d) Restored back to my superdark rom, usb is still dead.
Head scratch: I'd blame hardware except that it seems to be between the settings and execution. If it was purely hardware, I'd expect to see the usual usb notifications. Regardless, it looks like I'll have to revert back to stock and let Verizon figure it out.
Update3:
(a) switched to the new AOSP rom. Nice, but no usb.
(b) switched back to superdark since I like my speakerphone and the AOSP seems to be on hold. Still no usb.
Resolution:
My apologies for not posting a resolution. My bad. After the first few days the post kind of fell off the radar and I stopped checking.
Short version...dirty usb port.
Details...after a week or so, I saw the usb icon flash in the notification bar for a few seconds when I plugged it in for a recharge. Hadn't seen that in a week, hope springs eternal!
A thorough cleaning of the usb port using a paper swab dampened with alcohol restored usb functionality. Not much dirt came out on the paper, but it must have been enough to probably bridge the contacts somehow.
At present the phone is fully functional. The original Verizon cable seems to be a little wonky. I have an aftermarket cable that works fine. It may be that the aftermarket cable did some physical harm to the contacts in the port, or the original cable is going bad (I had something very similar happen on my Omnia). Not sure.
I now use the original verizon cable only for charging at work and use the aftermarket cable for usb connecting at home.
Bottom line...if your usb goes dead as described in the op, carefully clean the port.
My thanks to all who responded...
Download screen shouldn't have harmed you.
You probably are well aware of this, but sometimes it's the simplest solution: Is your usb cable unplugged when you are trying to turn on USB debugging? It will not let you if you are plugged into a pc or mounted for some other reason. Make sure your file manager and any other rogue app is closed. Again, it does sound like you have tried all of this, just giving my best shot ar an answer.
Other then that... Has anyone else had this problem? I haven't seen it in this forum before.
The most general solution to any issue on these fascinates is to undo whatever you did to break it, it's just difficult sometimes to isolate what that event was.
Swyped w/ XDA App. When in doubt, mumble.
Thanks for the reply.
USB is unplugged when turning on debugging. I've also tried turning the phone on with usb plugged in.
The last thing I had done (before accidently activating the download screen) was to install SiMi Folder Widget. Needless to say, it went away with the rom restore.
Also used ATK to kill running processes before turning on usb debugging. Also verified that I still have root.
I've buggered the phone up before but have always been able to figure out a way back (with help from forum searches). This one's got me stuck.
Tonight I'll try to figure out if it can be odin'd back to stock and rebuild from there.
Again, thanks. All suggestions/advice are appreciated.
See op for steps taken to (unsuccessfully) solve this.
Can anyone advise how I can flash back to stock DI01 without using odin, since it won't detect the phone? I can push files to the phone via adbWireless but that's about it.
thanx in advance...
I dont know if you fixed it or not, but here is a stupid question. Are you using the cable that came with your phone? I have several cables that will only charge my phone and only the stock one enables data transfer. Hope this helps. Good luck
Sent from my SCH-I500 using XDA App
Have you tried a factory data reset?
Sent from my SCH-I500 using XDA App
Did this ever get resolved? I hate to see an open issue die like this.
My apologies for not posting a resolution. My bad. After the first few days the post kind of fell off the radar and I stopped checking.
Short version...dirty usb port.
Details...after a week or so, I saw the usb icon flash in the notification bar for a few seconds when I plugged it in for a recharge. Hadn't seen that in a week, hope springs eternal!
A thorough cleaning of the usb port using a paper swab dampened with alcohol restored usb functionality. Not much dirt came out on the paper, but it must have been enough to probably bridge the contacts somehow.
At present the phone is fully functional. The original Verizon cable seems to be a little wonky. I have an aftermarket cable that works fine. It may be that the aftermarket cable did some physical harm to the contacts in the port, or the original cable is going bad (I had something very similar happen on my Omnia). Not sure.
I now use the original verizon cable only for charging at work and use the aftermarket cable for usb connecting at home.
Bottom line...if your usb goes dead as described in the op, carefully clean the port.
My thanks to all who responded...
This may be my problem! I'm having the same similar effects. Although mine randomly shows the symbol but also says my usb is connected when it does. I've been trying to solve this for 2 weeks now! I hope this is the solution.
Sent from my SCH-I500 using Tapatalk
common problem
This must be a common problem because I've had the same issue. switched cables and viola, all good.
My exact problem solved:
USB debugging activated on phone but computer did not detect it at all, nothing what so ever. Not even on dial-up mode, or download-Odin (yellow triangle).
Drivers installed (Fascinated and Nexus for the hell of it).
Tried to ADB my into it both from windows 7 and MAC OS-X.
Hell I even tried a different USB cord.
I would get the USB debug icon in the status bar only when on windows7 machine.
I cleaned the phones USB port with the alcohol damped paper towel/tooth pick and the **** worked, first time.
Man I gotta thanks God for this site. I been ****ing with for 2 days.
Then this lil SOB acted as if nothing ever happen. I wanted to beat the hell out the lil ****er. But we are back friends now.
Thanks dude. This **** needs publicized more. I went through a few links before I found this.
I would and tell people to use something non-metallic and removed the battery beforehand. I did just to be safe.
When I plug my wife's phone in, most of the time it does not even recognize that anything is plugged in at all, but the phone charges. Sometimes in device manager the phone comes up with a yellow exclamation point and the error
Windows has stopped this device because it has reported problems. (Code 43)
I installed the Android SDK and USB driver.
I installed the Samsung Driver from the site.
I thought possibly it was a software issue, so I was going to try to set the phone to factory settings. When I go into recovery, there is an Android logo with a red exclamation point, then eventually it boots back into Android with no change.
I manually added the driver into android_winusb.inf as I saw on another post here, but no matter what it is not picking it up.
I want to just be able to connect so I can root the phone and put a ROM on it. The phone is pretty hosed and slow. Any suggestions?
I had this at one point. It was the device, I had to get a replacement.
Sent from my SCH-I815 using Tapatalk 2
esoh said:
I had this at one point. It was the device, I had to get a replacement.
Sent from my SCH-I815 using Tapatalk 2
Click to expand...
Click to collapse
Well I do have insurance on it, and I agree that is the easy way, but I really don't think the hardware is broken.
I mean it charges, so the USB port works. I think if I was able to reload Android from scratch onto it, it would work. However, every solution I see requires rooting and you can't root without USB. It is a frustrating catch 22. Any other possible solutions? If not, I guess we are screwed.
The most frustrating part is factory reset not working.
I am currently having similar problems like you, I have one USB port from memory card reader and on that port phone isn't even charging but a flash drive works without problems. On other ports (back of case and front) there is charging but computer can't recognize the device. Try uninstalling all phone related drivers or cleaning them with some sort of driver cleaner. Then reinstall driver, or let Windows update it automatically. Mine worked for a while, and in device manager it was recognized as Acer ADB.
EDIT: Hi, just to report reason of my problems, my USB cables started failing for no apparent reason, my original Samsung USB cable and one other no name have both failed. I'm currently using my old LG USB cable, wrapped up in insulating tape, but everything is working good. So try some other micro USB cable, it maybe the source of your problems.
Phone: AT&T SGS 4
Version: Recent OTA accepted, lost root, custom screen still present
Problem: USB port on the phone doesn't stay connected, sometimes says "USB Connected" but does nothing. Won't charge, and isn't recognized by my computer.
Steps taken to resolve: Tried different cables, wall power and computer USB plug ins, accepted the OTA, did a factory reset. No dice.
More details:
I picked up my AT&T SGS 4 in late April. It was made in Korea, and hasn't had much in the way of issues. I rooted it with moto chopper, and used TiBu to freeze the update processes; so I did not take the update from the ninth of this month.
Today my wife pointed out to me that my device was no longer charging. As usual, I had been charging it with the cable that came with the device. I have tried multiple chargers, all of them on wall current. Then I figured I'd give a computer USB connection a shot.
In short, it literally connects, then disconnects. I've already ruled out cables, and it doesn't seem like it's a battery issue. Right now I have my phone off, and plugged into the computer's USB. It keeps vibrating like I just plugged it in, even though I haven't touched it for quite some time.
Google searches have all come back saying the same thing; RMA the sucker. I accepted the OTA and did a factory reset just to be sure. With an unstable connection to my computer, I fear that my options for further modding my phone are slim. I am no longer rooted after the OTA, but I still have the custom boot screen. I presume this means that I won't get anything out of a warranty claim.
Gents, do we have any ideas on how to fix this thing? This phone is practically brand-new, and I've had a case and screen cover on it since I started using it as my daily driver. If this is truly a hardware failure, is there any chance that I could still ditch the custom unlock screen on boot?
61 views, and nary a reply?
Dannar said:
61 views, and nary a reply?
Click to expand...
Click to collapse
so are you on MF3? if you are, i think you are SOL.
I took the OTA in hopes that it would fix something, and turn my root off. I didn't realize the damn custom screen would remain.
I can't make any modifications from my computer because without the all-important USB port, you just can't do anything. I took a chance, the only one I could, with the OTA, and lost.
What the he'll Samsung? Guess I can't modify your devices in the future for fear of them breaking. My first device by them too. Guess I ought to have stuck with HTC.
Insurance.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
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.
Just to rule out the obvious, have you tried different cable and computer?
gabriwinter said:
Just to rule out the obvious, have you tried different cable and computer?
Click to expand...
Click to collapse
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.
godraistlin said:
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.
Click to expand...
Click to collapse
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.
How did you brick your OP in the first place? Does it still charge?
Z-Blade said:
How did you brick your OP in the first place? Does it still charge?
Click to expand...
Click to collapse
It bricked in the middle of using the unbrick tool. It literally doesn't do anything. No charging, no vibrations. Nothing.
gabriwinter said:
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.
Click to expand...
Click to collapse
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
The fact it does not even charge sounds like a hardware issue. Even when its bricked it should at least charge.
godraistlin said:
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
Click to expand...
Click to collapse
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.
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.
Did you try holding power button for >40 seconds?
godraistlin said:
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.
Click to expand...
Click to collapse
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
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.
dladz said:
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
Click to expand...
Click to collapse
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.
GAMIT PRUTHVI said:
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.
Click to expand...
Click to collapse
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.
gabriwinter said:
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.
Click to expand...
Click to collapse
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.
jhs39 said:
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.
Click to expand...
Click to collapse
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.