Hi everyone. I know this has been covered many times. But I have a a pixel 3 stuck in edl mode. Has anybody found a working fix? Without having to search through many previous posts.
jwc08 said:
Hi everyone. I know this has been covered many times. But I have a a pixel 3 stuck in edl mode. Has anybody found a working fix? Without having to search through many previous posts.
Click to expand...
Click to collapse
This is the main thread on that subject, and there is no fix. It is an unrecoverable hardware failure.
[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting...
forum.xda-developers.com
Related
Hello guys,
when I woke up, my S6 was just flashing blue, while I charged it.
But it won´t turn on. I tried many different ways of holding the power buttons but nothing works.
I also can´t get a connection through ADB and fastboot.
A few seconds ago, I tried to reach the phone with the Anrdroid device manager of Google, but there is also nothing. It just says, that there is no connection, and the phone was last online yesteday(min. 7h ago).
Does anyone of you know, how to fix this?
Regards,
_v0id
Have you tried volume down and power button
_v0id said:
Hello guys,
when I woke up, my S6 was just flashing blue, while I charged it.
But it won´t turn on. I tried many different ways of holding the power buttons but nothing works.
I also can´t get a connection through ADB and fastboot.
A few seconds ago, I tried to reach the phone with the Anrdroid device manager of Google, but there is also nothing. It just says, that there is no connection, and the phone was last online yesteday(min. 7h ago).
Does anyone of you know, how to fix this?
Regards,
_v0id
Click to expand...
Click to collapse
This is how my phone got softbricked/getting bootloop.
Give us more info about your phone. Root or no root? Version?
Immoblize said:
This is how my phone got softbricked/getting bootloop.
Give us more info about your phone. Root or no root? Version?
Click to expand...
Click to collapse
It has no root atm and there was never a bootloop or something else.
It´s just off and it seems, that it´s pretty much broken. I tried again every button combination - nothing worked.
never mind, i just came from work, and the phone was a bit warm when I touched it. that is a bit confusing, because i thought it made no reaction.
Thread closed per OP request.
Solution: it was a manufacturing issue (some burned parts).
Hi, my daughters Poco X3 (two months old from new, no issues thus far whatsover) decided today go into the main menu of Poco Recovery 3.0
thus far i have tried to reboot which just switches the phone off and on back to the same menu. I have also tried the connect with MiAssistent but as i never used that software before it doesn't recognise the device.
I have NOT tried wipe data yet, as i hope one of you has a solution that's avoiding that.
I'm currently trying to run the battery completely dead in the hope the phone then forgets this nonsense but i would assume there are more technical solutions to the problem than sheer luck.
thanks in advance for any help
Hello,
I got a very strange problem with my Pixel 4a I recently got for repair and I need some help.
The failure I experience is that it boots and after a few seconds just reboots again.
So I thought I should put the device into Fastboot or adb and get a new Fimware flashed. Strange enough it shows the same behavior in this modes means I cannot flash anything at all onto this device.
A further defect are 3 vertical green Bars but else it is basically new.
Hope someone has some clue on what's going on.
Hi - wondered if anyone can help.
As above ive got a blackscreened phone - ive got cart blanche with this phone...(its a workmates phone, hes bought a new one) so i can do anything i want (if anyones got any drastic options im up for that!). Apparently the history is that the phone was behaving as if the battery was faulty to the point it died. Ive replaced the battery but the phone is still dead. Plugging the phone in the laptop i see the bulk usb driver popping up. Some time ago i did recover a oneplus phone in the same state using a gui tool that reloaded the image back on loading on the separate images one by one....can something like that be done for this.
Cheers to anyone that has a go!
ComfySofa said:
Hi - wondered if anyone can help.
As above ive got a blackscreened phone - ive got cart blanche with this phone...(its a workmates phone, hes bought a new one) so i can do anything i want (if anyones got any drastic options im up for that!). Apparently the history is that the phone was behaving as if the battery was faulty to the point it died. Ive replaced the battery but the phone is still dead. Plugging the phone in the laptop i see the bulk usb driver popping up. Some time ago i did recover a oneplus phone in the same state using a gui tool that reloaded the image back on loading on the separate images one by one....can something like that be done for this.
Cheers to anyone that has a go!
Click to expand...
Click to collapse
If by "bulk usb driver" you mean QUSB_BULK_CID:xxxx_SN:xxxxxxxx, the phone has an unrecoverable hardware failure. See the thread below.
[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting...
forum.xda-developers.com
dcarvil said:
If by "bulk usb driver" you mean QUSB_BULK_CID:xxxx_SN:xxxxxxxx, the phone has an unrecoverable hardware failure. See the thread below.
[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah - its that...! well, never mind....i thought i could as the OnePlus phone i had, was in the same state and i managed to recover that....thanks for the reply.
So, i've been flashing custom ROMS on my android phones for many many years. Never really screwed up... Except now. Let me explain;
I was going to flash LineageOS on my OnePlus 8 phone. Nothing I haven't done before. I follow the guide as the maintainer described (for your reference, https://wiki.lineageos.org/devices/instantnoodlep/install).
Towards the end of the process when I got to Installing LineageOS from recovery I'm asked to format data. Here something went horribly wrong. As the process of formatting finished. All that's left to do is reboot. And so I reboot. This was the last time I ever got any sign of life from my phone. Because after shutting down, it never started back up. No sign of life at all. No fastboot, no adb, not even a splash screen. I've tried to boot it with any combination of keys. But no matter which one (reset, boot to recovery, even boot to EDL). nothing. Not even a buzz or a battery indicator when I plug it into the charger either. Bricked beyond anything I've ever seen.
In the 3 days since it happened I've:
- Charged my phone for 20+ hours
- attempted rescue using fastboot/ adb
- followed the steps from about every comment in this thread: https://forum.xda-developers.com/t/cannot-unbrick-cannot-enter-edl-mode.4148589/ (on USB3 and USB2, with the oneplus official cable and 3rd party cables)
- followed the steps this friendly youtuber explained:
- pressed any button and any combination of buttons on my phone for at least multiple minutes
- screamed at the phone really loud
Obviously none of these steps did the trick. My computer (I tried 3 computers actually, and both in Windows and Linux) just does not recognize the phone anymore. Nothing in device manager. Not even when i'm attempting to EDL.
Quite honestly I'm just stumped. It's not even recognized by device manager. If I didn't know any better I'd suspect the hardware itself failed at the exact same time as the software. I hope any of you can help me out.
One option you can try is getting an EDL cable.
Xryphon said:
One option you can try is getting an EDL cable.
Click to expand...
Click to collapse
Hi Xryphon,
That's interesting actually. I didn't know there were specialized cables for this. I was just using regular USB C. I'll look into getting one.