Hello everyone,
having major USB issues on my GNex. It's not charging anymore, but when the phone is off, it displays a charging animation. I could get it to charge once since this occurred, I left it plugged in overnight on my Mac (phone turned off). Did the same thing last night, no charge at all.
Mac OSX does not recognize the device, my Windows machine keeps telling me something like "the connected device is not working properly and can't be used... ". This message pops up every few seconds, so I guess it's constantly connecting and disconnecting. I can't access the internal storage on both systems.
My first guess was a hardware defect. But when I try to boot into recovery mode, a screen instantly pops up that shows Andy and displays a message: "Downloading. Do not turn off target.". In the upper left corner it displays " ODIN MODE" in small red letters.
When I press the power button in this screen (there is a big arrow pointing to the button with "start" written in it) the phone just normally reboots.
I can't get into fastboot mode because of this. I can get into CWM Recovery when i use the reboot into recovery option built in the ROM.
I dunno much about Odin (next to nothing). Has it something to do with Samsungs Kies? Could it be that something has put my phone in this "ODIN MODE" and it constantly tries to download something, making the USB port unusable? The port is not completely broken, as the phone displays a charging animation when it's turned off... so there is some connectivity left!
Thoughts coming up that this could be some kind of software issue. If there is a possibility to get out of the Odin Mode, it may solve the problem.
The phone is unlocked and rooted, running AOKP Milestone 5 and franco kernel.
I tried to restore an older nandroid, but it did not change anything.
Would send it in for exchange, but not able to relock the bootloader due to no fastboot access. If it can be confirmed that this is a hardware problem, I have to pay for the repair, I'm fine with that.
Has anybody any ideas that could be helpful? Any help is much appreciated, thank you in advance!
Do a search and you will find at least 30 helpful threads. Basically you only need to replace your USB charging board and it works again. Should be a warranty issue, but Samsung has really been an ass on handling this issue lately and claiming water damage.
I have mentioned it many times here: this problem can be probably solved by thoroughly cleaning your USB with soft toothbrush.
True, I also cleaned my port but it only fixed it temporarily.
Thanks guys. Tried to clean the port, nothing changed.
Ordered an OEM charging board off ebay, hope changing it will fix the issue.
Only thing I'm wondering about is, that the phone is stuck in Odin Mode when I boot it up with Vol. - and the Power Switch. So I downloaded Odin but it does not recognize the phone...
I am also facing the same problem. I am currently using the phone by charging the battery externally. Can someone confirm that changing the USB flex cable is the solution ?
Just posted in another thread but it is definitely the USB port for me. Using an HTC Vision (Google g2)
Related
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
Please try to enter the bootloader mode in a bright room as it is very difficult to see in poorly lit environment. Till you enter the bootloader mode your device will not be recognised. Perhaps one of the three keys is getting released..the light button is the usual culprit. Once you are in the bootloader you can reflash.
Thank d_ranade for your answer.
I am sure the screen is 'all black' and I've tried to press the buttons several times.
I think the main problem now is how to enter the Bootloader.
I sometimes find it takes several goes to get into Bootloader mode. If not, have you tried a hard reset?
I've tried whatever i can do. Hard reset is useless too.
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
I have sent you a pm, it should help you.
-Jwrightmcps
Thank Jwrightmcps for your help, but i can not enter the Bootloader ,so can not use mtty to do more.
Unable to start/see bootloader
I seem to have the same problem with my upgraded universal which was working fine for about ten days. Then I installed TomTom on it and again it was all working that evening.
Then, when I turned it on the screen went blank (white), so I re-flashed it, but, part way through the screen went black, so I left it connected for further hour and nothing. I have since been unable to get it to do anything, it is not recognised by activesynch, it will not charge (either from the mains or the USB on either of the batteries) nor will it turn on or respond in any way.
I have unset ‘allow usb connections’. I have tried solidly for +/-10 minutes doing the backlight + on/off button and reset bit - repeatedly, with my wife helping to ensure all buttons were being pressed. All I got was a message from MicroSoft telling me that ‘One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it’. The only positive thing is that every time I do it and depress the reset, the red LED flashes (provided I leave the USB cable in) but at no point have either of us been able to see any writing on the screen.
Any guidance (apart from where to take it for recycling) would be welcome…
It happened to me several times too. Even in the old ROMS. But had learned many things out of it. I removed the battery. Wait for several seconds or maybe minute before placing it back. And after placing it back wait again for some time before doing the "power + light + reset" (bootloader). At some point when I am in the bootloader mode already and reflashing, connected to the PC already, the screen went blank again. So I'm sure that something went wrong again. I repeated the procedure again (removing battery, placing it back etc...) and the reflashing continued. It takes patience (maybe).
After having experienced this so many times, I'm beginning to assume that it is not because the battery is "bad" or there is a problem on the ROM being reflashed. It is on how it (the battery) is connected to the unit. The reason why it does not turn on, charge even if connected to the charger, does not hard reset, does not react to anything... I just don't know.
One thing more, the procedure I said above sometimes does not work at once. But at least I managed to "resurrect" my device several times.
This I am sure, it is not in the ROM that is being flashed or the update...
Hope this helps,
Lelen
lelen, Thanks for your assistance. I tried last night, but it still could not enter the bootloader mode...
I have the same problem =( and i don't know what to do, someone told me that i have to change motherbord to resolve this problem, i hope there are some other solutions.
Dead Uni
I too had this problem. With the device not responding at all and not able to enter bootloader stops mtty from working.
Only way i could get it to work was to take it to an O2 shop to send it away for repair (luckily the O2 XDA range has a 2 year warranty and because its completely dead they cant tell the OS has been modified).
Unfortunatly like the previous post i think it can only be fixed by replacing the mainboard.
Hi all, i found this thread http://forum.xda-developers.com/showthread.php?t=291097&page=6
so many people have the same problem , and nobody found a solution? i can't believe that on all this universals died motherboard, and there is no way to fix it with some special cable or some programm.
yes,i post the last reply of the thread you mentioned above, but nobody can resolve it.
I recommend you remove the battery and leave it over night. Put the battery back on, ensure it is properly mouted and try booting it.
It worked for some, no idea why though. I'm actually suspecting a bad battery mounting, which results in the motherboard unable to detect a battery is iserted, thus refusing to boot.
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
coolbeans252 said:
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
Click to expand...
Click to collapse
i guess thats what i will have to end up doing
anyone goten repairs done in north america?
( i live in western canada)
got the same problem
sofene said:
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
Click to expand...
Click to collapse
hi..please let me know if your device is fixed and how you managed to fix it. my email id is [email protected]
http://forum.xda-developers.com/show...6&postcount=52
I've been trying to fix my T889 note 2 with this two annoying problems.
the phone won't turn off every time I shutdown it down it turn it self back on, its like its just restarting it, I downloaded this app called "shutdown" to test if it will shut the phone off but still no after pressing it there's a command line in the bottom left corner of the screen "reboot -p", I also tried downgrading it back to 4.1.1 because I thought it was just a firmware bug but not luck and even tried to take the battery out and leave if for few minutes but after inserting the battery back in it will turn itself on without pressing the power button.
(FIXED) => for the detecting issue I read some thread here most of them said to replace the cable which I also tried. re-installing the drivers many times and the *#7284# method didn't work as well and I'm running windows 7 64bit fully updated. I have other galaxy devices and they all can be detected. (I REPLACED THE WHOLE CHARGER PORT FIXED THE PROBLEM)
hope someone can help me with other solutions
thanks.
I left my perfectly fine i-9505 s4 to charge overnight to find out it did not respond to anything, holding down the power button or power+voldown+home did not result in any sound image or vibration.
Removing the battery and re-inserting it makes the s4 respond to the power button, but the phone shuts down seconds after powering on. This also happens when I try to enter recovery, download mode or insert the charger.
It even happens when I use my usb JIG, the downloading screen appears for a second, after that the screen blacks out again. Tried removing the SD / SIM cards.
The only way I can connect it to Odin for a second (at least as far as I know), is by:
1) removing battery,
2) inserting Jtag
3) inserting battery
4) remove JIG (very quickly)
5) insert USB to PC (very quickly)
Yay! Windows makes the "USB connection" sound, before making the "USB connection lost" sound a second later and the screen blacking out..
What could cause this? Is it my battery? Connector? Software (jamals 4.4v6, faux123, mj5 modem)?
Have you tried directly plugging it into the charger or your computer without the battery?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Thanks for your reply.
Yes, I did try that, the screen does not turn on if I plug my charger / USB cable from PC into my S4 when the battery is removed.
What could cause shutdowns after 2 seconds from booting? I hope this is fixable!
It sounds like there is a physical defect in the device. If it was software related (this can be caused by a borked up ROM or Kernel) you wouldn't see the same behaivor in Download mode and that doesnt' use either the ROM or Kernel.
You could have something physically broken inside the unit that is causing an electrical short once something common to the system and download mode is activated, which would cause the reboot. That could be the USB port that both the system and Download mode will constantly poll the USB port looking for a connection, but only after a second or two. It won't look at the USB port immediately when teh GALAXY S4 splash screen pops up so that's why you get a second of it working. There are 100 other things internally that it could be too.
I'd say make sure the charing port is cleared of any debris. If that doesn't work, I'd say it's broken and needs to be repaired. Without knowing exactly what is causing the issue I wouldn't suggest trying to fix it because you'll cancel the warrenty by doign so and might not find the problem. It could even be a faulty memory chip on teh circuit board that wouldn't look broken to the eye.
Since you can use Download mode for more than a second, you obviously can't try to restore to stock, which is the prefered go to method to fix things like this.
joepsz said:
Thanks for your reply.
Yes, I did try that, the screen does not turn on if I plug my charger / USB cable from PC into my S4 when the battery is removed.
What could cause shutdowns after 2 seconds from booting? I hope this is fixable!
Click to expand...
Click to collapse
Sounds very much like a hardware malfunction. Without having the device on hand, I can be of no help, unfortunately. If it's under warranty, I suggest you try to get a replacement.
Thanks for the replies. You have convinced me that this is a hardware issue. I have no clue as to what might have caused this defect.
I will soon try a different battery, and if that fails I will contact Samsung.
Unfortunately though, my firmware is custom and this may void warranty, which would suck since the cause of the issue is probably not related to the software.
A day later, the problem appears to have solved itself. I'll keep you updated.
My S4 was working for some time, but the problem returned, the phone shuts down seconds after booting (normal boot / recovery / download mode / USB-Jig induced download mode..)
HOWEVER:
Sometimes, when I connect my S4 to a charger, it turns itself on (first displaying the charging icon) and then starts booting, showing the Google boot animation (since I'm running GPE). This animation keeps going for minutes, and then the phone shuts down again (black screen, does not respond to anything.
joepsz said:
My S4 was working for some time, but the problem returned, the phone shuts down seconds after booting (normal boot / recovery / download mode / USB-Jig induced download mode..)
HOWEVER:
Sometimes, when I connect my S4 to a charger, it turns itself on (first displaying the charging icon) and then starts booting, showing the Google boot animation (since I'm running GPE). This animation keeps going for minutes, and then the phone shuts down again (black screen, does not respond to anything.
Click to expand...
Click to collapse
You're just delaying the (possibly inevitable) death of your phone. Use your warranty while you still have it. At least I would in your situation.
joepsz said:
A day later, the problem appears to have solved itself. I'll keep you updated.
Click to expand...
Click to collapse
The symptoms that you have described are those of a bad power button. This happens quite often.
tronac said:
The symptoms that you have described are those of a bad power button. This happens quite often.
Click to expand...
Click to collapse
I think you are right! It would explain the inconsistency and the fact that my phone sometimes turned on by itself.
Thanks!
tronac said:
The symptoms that you have described are those of a bad power button. This happens quite often.
Click to expand...
Click to collapse
I had to send my S4 back to Samsung THREE TIMES before they realised it was a hardware error. The first two times, all I got was a factory reset.. Which of course, didn't help.
I'm pretty sure you were right, it was a bad power button.
Hi everyone,
first off, I've spend days now trying to find a fix. If I've missed anything, I'm sorry, it wasn't for lack of trying.
Here's the situation: I have acquired an HTC One X earlier this year which has worked quite flawlessly. I went ahead and unlocked the bootloader and installed a custom recovery. However, since I handed the phone off to my not-so-techy sister I did not use a custom ROM, and after the HTC update failed with the custom recovery I reversed that as well. The device should now be stock everything with unlocked bootloader.
After a few months my sister encountered heavy problems, though. She described them as battery related (wouldn't turn on correctly) and eventually she moved to a new phone. Now I have gotten the device back and I am trying to fix it. After charging it I managed to have it boot once. However, I but it to the side and wanted it to load some more. Ever since then the screen doesn't come on. The charging LED seems to work fine (eventually switched from red to green, too, indicating that the device is fully charged) and the button backlight still works, too. Most significantly though, the device is recognized as MTP device in Windows: I can access all the data in the storage without problems.
I have read that there is an issue with the HTC One X and the display connector so eventually I went ahead and took the device apart. It's lying in front of me now in pieces, but I still couldn't get the screen to come alive. The obvious conclusion would be to buy a new screen but the device doesn't feel like it's worth the investment. Besides, I would like to know for sure that it's the screen before I do anything.
So I turn to you guys and ask if you have any idea how I could access the phone via my computer. I tried to boot it up in bootloader mode but due to the strange standby methods HTC is using and not seeing anything on the screen I haven't been able to do that yet: Whenever I connect my USB cable it's recognized as MTP device, not ADB. Debugging seems to be deactivated so that doesn't seem to be an option. Does anyone have any idea how I could get the phone to talk to my computer (i.e. get into the bootloader or ADB screencast for sure)? With my Galaxy S I could simply plug in this dummy micro USB and would be sure to end up in download mode.
Any help is appreciated!
tl;dr: HTC One X screen is dead but LEDs work, is recognized as MTP device. How to make it talk to the computer?
Thanks,
rien
Alright, sometimes just posting stuff like this helps already. I was now finally able to get the phone into fastboot (apparently) and it's reacting to the fastboot commands. I suppose the next step is to load CWM and connect via adb. This way I can at least do a factory reset.
Does anyone have any ideas regarding the original issue with the screen? Especially since it does seem to work occasionally. And doesn't show any fragments...
Can I enable USB debug mode from within the recovery to work in the system?
Hello everyone. My brother has the SM-T320. It doesn't power on at all. But if I plug the tablet directly into an outlet or laptop, it turns on but immediately goes to "recovery booting" and looping and not actually turning on. I can press the Power+Volume Down buttons to go to Download mode. I have three laptops at my disposal. I installed the Samsung USB drivers on two, and just Samsung Kies on the other. I have also tried different Odin versions (3.07 and 3.09) and it still won't connect. I also bought a different battery, and even if I leave it charging (aka bootlooping), if I disconnect it, it turns off. Essentially, I think the firmware is messed up and simply doesn't recognize the battery. So that's why I wanted to flash a stock recovery. Any ideas what I can try? Thanks a lot for the help!
I should also mention that I tested battery connection (tablet plugged into an outlet with the battery removed) with a volt meter and I gut 4.45V, which I think is fine?
mark1995n said:
Hello everyone. My brother has the SM-T320. It doesn't power on at all. But if I plug the tablet directly into an outlet or laptop, it turns on but immediately goes to "recovery booting" and looping and not actually turning on. I can press the Power+Volume Down buttons to go to Download mode. I have three laptops at my disposal. I installed the Samsung USB drivers on two, and just Samsung Kies on the other. I have also tried different Odin versions (3.07 and 3.09) and it still won't connect. I also bought a different battery, and even if I leave it charging (aka bootlooping), if I disconnect it, it turns off. Essentially, I think the firmware is messed up and simply doesn't recognize the battery. So that's why I wanted to flash a stock recovery. Any ideas what I can try? Thanks a lot for the help!
Click to expand...
Click to collapse
OK so it is in download mode when you connect it to Odin?
Hey everyone, I got the problem partly fixed. I was able to reset it to original firmware by using the Samsung kies3 software. It somehow was able to recognize the device even though Odin couldn't. However, turns out, the reason tablet would turn on only when plugged in is because the battery wasn't connected completely. The battery connector on the motherboard itself is separating and so the pins are not touching the board completely. My ghetto temporary fixed was to cut and stick part of a bobby pin over it to clamp it in place. However, this will probably damage the connector/board in the long term. I'm not very good with soldering parts/pins that are this small, and nor do I have special equipment besides solder and soldering iron, so I'm trying to figure another clever way of holding it strongly in place. If anyone has any idea how to go about that, it would be appreciated.