Develop Bugs

Bricked My Nexus / Bad USB Connection

I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.

Sorry to hear that. This is something I learned (second hand, thank god) when I had my Galaxy S1. Odin can simultaneously be the best and worst tool you use.
Sent from my Galaxy Nexus

ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium

ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
rayiskon said:
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.

iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
I had a feeling that it wasn't truly bricked, but since my phone's USB driver (or whatever aspect of USB data transfer) was malfunctioning I couldn't do anything about it. I think of it this way: if in that state my phone had a 5% chance of being recognized by Odin, and if my phone already had less than a 20% chance of being recognized before the soft-brick, then I had a 1% chance or less that it would even show up in Odin and even lower odds at a successful flash. Regardless, Verizon agreed to send me a warranty replacement.

iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
Same here with the vibrant. IIRC there was a special way to get your phone to recognize Odin when it happened. Something like plugging in the phone to the computer and then pulling the battery. Odin even worked when I borked a flash and the screen wouldn't even turn on. I would think the nexus could be brought back similarly.
But if the USB port is on the fritz I'm not sure I would want to bring it back.

As far as I'm concerned Odin is the worst thing you can hook up to your devce. No single program has bricked more devices than Odin.
______________
Just Flash It !!!

on my old SGS1 there was chance get back bricked device by method called "JIG"..(its hardware way get back download mode) but i dont study it more...

I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?

try to use another cable to connect ur phone to pc
just flash stock via odin, it's not bricked.
My s2 sometimes has that problem when i flash stock

eksasol said:
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
Click to expand...
Click to collapse
I appreciate the advice but I no longer have that phone. My replacement should come today.
With regards to the drivers, I was referring to the drivers on the phone not on the computer. I honestly don't know if there are USB drivers on the phone (I would think there are) or even if those drivers were causing the malfunction.
The first thing I'm doing this afternoon is plugging my replacement phone into my computer. If the new one doesn't work right then I'll have to make a trip to the Apple store because the problem will almost certainly be my laptop. I'll also owe a big apology to Verizon.

USB and touch screen no longer working

A few days ago my phone was stuck on a bootloop at the doomkernel logo so i flashed the latest version of doomkernel on and it seemed to fix the problem. Then while copying the wi-fi modules to my memory card i got a weird popup about titanium update crashing so i closed it. Immediately after that my touchscreen stopped working. I didnt think much of it at the time so i just rebooted my phone into recovery and flashed the new wi-fi modules for doomkernel. When I booted the phone the touchscreen still wasnt working but now it wouldnt recognise the usb cable, whether plugged into the computer or charger. I thought it was the cable so I tried a few others but it still wouldnt pick up. When the battery died and i plugged it into the charger it charges while the phone is switched off but when the phone is switched on it wont charge at all. This led me to believe there was some sort of software/driver/kernel issue or something. I could still control most of the phone using the gamepad so i backed up all my important things and flashed stock 4.0.2.A.0.62 firmware back on the phone. Problem still persists and I cant flash the stock wi-fi modules back onto the phone because I cant gain access to the memory card via usb and i cant type on the phone so i cant download it using the phone. Does anybody have any suggestions? Has anybody else even been through something like this?

Stuck in "download mode" whenever i plug a usb

Hi i recently purchase a second hand LG-E971 (locked to rogers and not rooted).
The phone seem to be working at first but whenever
i connect the phone to the computer or charge it on the wall
it goes to "download mode" the only way to exit it is to hold pwr for 8sec.
i got all the driver installed properly in "download mode"
tried to factory reset it with E97110D_00.KDZ and E97110E_00.KDZ
with success but still having the same problem
whenever i plug a usb cable in
i installed the driver for PC
LGUnitedMobileDriver S4981MAN38AP22 ML WHQL Ver 3.8.1.exe
when i connect the phone the driver got installed automatically
but the phone doesnt connect to the PC (win7 i tried 2 different computer) in any mode it is only charging
Is there a KDZ that is already Root with CMW or TWRP that i can factory reset it?
Thank you.

I would contact rogers to get the device checker under waranty.
If you have flashed the original KDZ, you eliminate all software related issue that could've cause this. It must be an hardware issue.

i have same problem. since today whenever i plug the phone to charge it it goes to download mode.
any way to fix it? im on cm but didnt change anything recently

I would suggest to start with cleaning the USB pirt on the phone. Compressed air and a wooden toothpick will help. I had a similar problem with my old SGS2, when dirt in the socket was causing sime weird behaviour.
Worth trying before going to the service centre...

having the same issue as well..i hope there's a possible fix available.

dead thread i know but i have SOME valuable information if you have this phone lying around "dead"ish. i went through a lot of crap trying to revive my dead battery phone and i remembered, i just by chance stumbled upon a "solution" of sorts. it basically is taking out the sim card, turning on the phone WITHOUT the cable, and once it's on i can connect it again. the moment i put in a sim, the damn thing starts flaking out. i'm currently using solidkernel 1.95 gproj with cm 12.0 official nightly 10/16(2015). this had happened to me like a month and a half ago or so as well. ANYWAY, it's either a radio thing, a kernel thing, a rom thing, or a combination of the three. that would NOT explain why the phone assumes download mode has been invoked, especially given it should only happen through a special pre-boot procedure using buttons (two no less). still, it is possible that my sim slot is too dirty, or my sim itself is problematic? i don't know. what do you guys think?

Phone won't connect to PC or charge from a wall charger.

For some reason my phone will either not connect or connect and disconnect constantly to either one of my pc's and sometimes won't charge from a wall or car charger. I tried every cable I have so the cable is not the problem. I can turn the phone off and on several times, factory reset, flash the ruu via sdcard and then maybe I can get my phone to connect to my PC. I was able to connect my phone to my PC after trying for 45 minutes and flashed the developer ruu. My phone rebooted after a successful flash and now the problem is back again. Does anyone know what could be wrong?
One more thing...HTC car mode starts up on its own sometimes and sometimes when I plug the phone into my PC.
Edit...I called HTC and they told me that because I unlocked the bootloader, I can use my uh-oh warranty and get a free replacement. So that is what I'll do. My phone was always acting goofy anyways.

lyall29 said:
For some reason my phone will either not connect or connect and disconnect constantly to either one of my pc's and sometimes won't charge from a wall or car charger. I tried every cable I have so the cable is not the problem. I can turn the phone off and on several times, factory reset, flash the ruu via sdcard and then maybe I can get my phone to connect to my PC. I was able to connect my phone to my PC after trying for 45 minutes and flashed the developer ruu. My phone rebooted after a successful flash and now the problem is back again. Does anyone know what could be wrong?
One more thing...HTC car mode starts up on its own sometimes and sometimes when I plug the phone into my PC.
Edit...I called HTC and they told me that because I unlocked the bootloader, I can use my uh-oh warranty and get a free replacement. So that is what I'll do. My phone was always acting goofy anyways.
Click to expand...
Click to collapse
looks like a hardware issue, replace

Exactly the same thing is happening to me and I have no clue what to do.. Any ideas ?

Try cleaning the usb port with a pin.

shivadow said:
Try cleaning the usb port with a pin.
Click to expand...
Click to collapse
I have replaced the port with another one and its the same thing.

can i get some help???

ok, so here's what's going on:
Google nexus 2013 wont start up. It was previously Dead Dead, but its been charging, so it can start up now. However, i shuts down when i take it off the charger, but thats bc its not fully charged yet.
now for the real issue:
It seriously wont start up, it gets to the google logo, but it just shuts right back off after that. and sometimes, when i power it on, the google logo flashes on screen for less than a second, and then shut off immediately afterward, and i can't get to the bootloader when that happens.
when i AM able to get into the bootloader, i've tried everything. i wasn't going to factory reset, but when all failed, i tried it. But even THEN it didn't work. instead of bringing me to the next page, it just shut off again. can I get some help pls? (BTW it isn't charging with the cable it came with, its charging with a samsung j7 charger, but i made sure that its working)

If it turns on at all, then it isn't completely broken I believe. Have you tried the re-stock method shown in the forum? You just run the .bat file inside it and it'll flash you back to the latest stock firmware. It is supposed to fix any soft-brick issue.

gman88667733 said:
If it turns on at all, then it isn't completely broken I believe. Have you tried the re-stock method shown in the forum? You just run the .bat file inside it and it'll flash you back to the latest stock firmware. It is supposed to fix any soft-brick issue.
Click to expand...
Click to collapse
How? i can't get it to connect to my pc via USB because USB debugging is off. I also need to get the official nexus 7 charger because it's not charging at all and i can't get it on.

Ah, you didn't mention usb debugging wasn't enabled... Hopefully someone will be along asap with a better solution

Justneedsomehelp said:
How? i can't get it to connect to my pc via USB because USB debugging is off. I also need to get the official nexus 7 charger because it's not charging at all and i can't get it on.
Click to expand...
Click to collapse
You don't need official charger. Any is suitable.

Any microusb in good working order should work. Check the charging port is free of lint and other dirt so the connection is good. Is the device showing that it is charging? Even off it should show that it is taking a charge. If not, and you are certain the charger is in good condition and seated properly then it may be a faulty or failed battery. I know mine is going, just won't hold a charge very long. If you can get into the bootloader, you can fastboot the factory packages regardless of adb debugging being enabled. You just can't flash non signed images unless you are bootloader unlocked. If you can boot into bootloader then fastboot back to stock would be my suggestion to start.