Database Info

[Help] Google Nexus 5 might be bricked

Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead (Edit: For a strange reason, it didn't update to the latest version available.)
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3

Almogpas said:
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Click to expand...
Click to collapse
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom

bitdomo said:
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
Click to expand...
Click to collapse
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)

Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
hmmm... try lg flashtool. Link in my signature.

Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
http://developer.android.com/sdk/win-usb.html

doctor_droid said:
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
Click to expand...
Click to collapse
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.

Almogpas said:
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Click to expand...
Click to collapse
Yup if the pc is not detecting the phone best is to try wid another usb cable and a different pc... let us knw tomorrow

Did you install those libraries properly?
Freshly baked from my Nexus 5

This universal ADB driver + this ADB and Fastboot pack always does the trick for me.
When you get either ADB or Fastboot working we can help you recover the device.

Dead M2, recognized as SOMC Flash Device

Dear XDA Community,
I'm trying to revive an M2. The user of it told me it just suddenly stopped working while watching a YouTube video, and she couldn't turn it on since then. The phone literally looks dead. No signs at all, except one: The phone was first seen in Device Manager as "QHSUSB_BULK" (with an exclamation mark), then I installed the Flashtool drivers and it's now recognized as a "SOMC Flash Device". That's all.
I have tried to recognize the phone with Sony PC Companion, Emma, and the Sony Mobile Flasher by Androxyde (found the program as "flashtool-0.9.19.8"). None of them could detect the phone as a phone, except the last one mentioned (flashtool-0.9.19.8), but it just kinda detects it halfway.
Here's the log it gives:
30/040/2016 18:40:01 - INFO - Device connected with USB debugging off
30/040/2016 18:40:01 - INFO - For 2011 devices line, be sure you are not in MTP mode
When I try to access it with fastboot mode, and press the "Check current device status" button, I get this:
30/040/2016 18:40:33 - INFO - Device Status: NOT FOUND
I also tried booting the phone into fastboot mode (holding volume up and power button, but nothing happens at all).
Is there any hope to fix it?
Thank you in advance!

If it's recognised as a somc flash device it should be salvageable, leave it charging overnight(at least this way you know the battery should be fully charged) and try unistalling then reinstalling Sony pcc and connect the M2(this should install the drivers) if you can get it to recognise the device a software repair should be possible if it's a stock device. Try having a read through this thread it may be of some help...
http://forum.xda-developers.com/showthread.php?t=1849170

I've tried the things you mentioned, but it's still the same. Sony PCC just tries to detect the phone and says I need a newer version of PCC, but when I check the updates, it says the latest version is installed. Perhaps I have to drain the battery to zero so the chips will be reset?

I'm done with unplugging the battery from it's mainboard, but nothing happens. The led isn't lighting up in any case at all.

Any update on this issue? I have also the same problem.
Στάλθηκε από το SM-G920F μου χρησιμοποιώντας Tapatalk

Have you solved it?
If not, have you tried normal fastboot using CMD?
- Download ADB with Fastboot files (there are somewhere on forum or search for it in google)
- Connect the device while holding volume up button
- If the blue light goes on, it should work (otherwise try in console "fastboot devices")
Sent from my Xperia M2 using Tapatalk

@Th3 Ant I tried also this. It doesn't detect my device for any reason. If you uninstall the Somc driver it detects it as qhsusb_bulk. I think the problem is with the boot partition - maybe it is corrupted. But there is no way to do this since I am not able to get either to fastboot or flash mode
Στάλθηκε από το SM-G920F μου χρησιμοποιώντας Tapatalk

Is there update on this . Help me to fix my Xperia S . Same problem .

If fastboot and flash mode aren't working, there's no hope.

Can the Jtag riffbox can fix this ?

pynix124 said:
Can the Jtag riffbox can fix this ?
Click to expand...
Click to collapse
Try these steps, but first without opening your device.
http://forum.xda-developers.com/showthread.php?t=2646405
I could save my Bricked Z1 (detected with Code 43 and yellow warning sign) like this:
1. Press and hold Vol UP + Power with USB connected for more than 1min.
2. If device is detected as SOMC Flash Device i followed the unbrick steps frome the Thread above
3. Repair with PC Companion

Oneplus 6 unable to be unbricked

Hi everyone,
A couple of days ago I rooted my Op6 and then decide to flash No limits rom via recovery (blu spark), as I was used to do with my last android phone, the Samsung Galaxy Note II.
Unfortunately I missed something and now it is stuck in the bootloader screen. Nothing works from the phone and I couldn’t revive it. I use a Mac but I tried all tools that are adviced here on XDA with my friend’s Sony Vaio but without success.
I managed to update drivers but I cannot run a flash-all.bat and I cannot use MSMdownload tool.
How can I do? Thanks to anyone who will manage to help me!!

EDIT: Sorry, just noticed you say you cant use the MSM tool. This one worked for me.
You could try this
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
Worked for me.

Check the guide about unbricking and if You are unable to use flash-all.bat so you Have to flash commands One by One. It's worked for me a few of months ago.

It doesn’t work either that way. I updated my drivers, but no computer is recognizing the phone.
I tried from changing usb cable or port to changing computer, to change methods.
I didn’t found any solution here on XDA, I tried everything!!

Make sure u use the cable included with the phone. Some cables doesn't work

Neither. I tried with the original and two others that I have.

if possible do you have windows? the flash-all.bat works for windows and is better to use(i was unable to use it normally in linux). What happens when you show flash.bat?

I tried Mac and Windows. On Windows it always shows in terminal "waiting for any device", even if I uploaded the drivers and made everything possible.

Did you put your OP6 into fastboot mode in correct way? I mean you might be doing the wrong procedure when entering fastboot mode.
It happened to me for the first time, I came from Samsung and I thought the phone needs to be stayed on the fastboot menu screen just like Samsung but no.
You need to turn it off and reboot it while pressing home and vol down button simultaneously until the PC recognize.
Good luck unbricking~

I always powered it on via power+volume up before connecting to the usb cable, because connecting it while powered off always resulted to power it on automatically on bootloader screen

Phone unrecognized in download/recovery

So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.

chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.

While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.

Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.

bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.

Stuck on drivers

Hey so like i have a problem. It\s seems to be to simply impossible to get any drivers to work, i tried everything google drivers, sdk ,drivers that come on phone and drivers from some random websites. Nothing works, tried both w10 and linux ubuntu. On my older pc i had 0 issueas other than simply doing something dumb.
Im out of ideas, help? Also tried with sony z5 premium instead of my nokia 7 plus but same thing -_-
Sidenote:fastboot device from phone drivers kinda works(?) But still im not able to do anything because im stuck on waitig on devices when i want to flash

To manage an Android phone from PC you at least need
1. ADB - provided by Google
2. FastBoot - provided by Google
3. Android-USB-driver provided by OEM/Carrier matching your phone
and nothing else.

Have all of those and im stuck on waiting on devices after i reboot to bootloader. Seriously annoying maybe i will try on other pc and see what happens but its not really a solution

If your phone supports Fastboot - take note that not all phones do - then when Fastboot returns "Waiting for device" it's a driver problem: Install correct driver.

True but as i wrote official drivers don't work it's on the phone after all. Rest doesn't work too then . Heh