Unable to Connect Via USB - XPERIA X1 Q&A, Help & Troubleshooting

My Xperia suddenly developed an issue last week. Upon connecting to my pc for sync, the USB device not recognised popped up and refused to leave. I turned my phone off and turned it back on, and i suddenly have the bootloader screen pop up! After multiple retries, i discovered that connecting it via USB to the pc before turning it on was the only way to get it to turn on normally. It also shows the USB device not recognised when in bootloader mode.
Is there any possible cause and solution to this issue? I have tried a hard reset to no effect, and i cannot flash cos i dont have Hard-Spl
Help
BR

Related

[Q] phone not recognized (either download mode or MTP mode)

Hi,
first off, i have searched the forums and i have googled my problem, but i think this is a real specific problem,
my phone boots just fine. but my bottom three buttons aren't working whie in software. i CAN go into recovery using the three button method. (using the home button, so it workes just fine) but as soon as i enter recovery the homebutton (and menu and back button) wouldn't work anymore.
so i thought; it is an software problem so a new rom should do the trick. at least it is a good guess.
problem being, the phone isn't recognized by my, and others, pc. whenever i connect the phone (phone "on", at homescreen) the phone starts to charge but the pc does nothing. it doesn't even show "unknown device". Also in download mode no luck. not recognizable.
Strangest part? if i start to connect, disconnect, connect, disconnect (etc.) the phone 20-30 times, there is a chance it will be recognized. this is only not the case in download mode.
i replaced the cable and reinstalled (and redownloaded) the drivers numbers of times, also i used different USB ports (USB3.0 and 2.0)
Hope you guys can help me out.
Thumbnail
have you tried to toggle the usb debugging mode ?
Yes, tried that already. any other ideas?
bump, nobody an idea what to do?
tbh it sounds like the microusb port on the phone itself is dodgy. possible that the solder needs to be reflowed.
sounds logical, would it be possible to do this on my own? i have got a good bit of experience soldering. and is there anything i should know beforehand?
and the buttons, is it possibly in the software? or is there something else going on?
edit; it would be strange if the connector is dodgy, because every time i plug in the cable it starts charging, so atleast 2 pins are properly connecting
did u try to connect another phone ? or try to coonect it to another pc, maybe problem is in ur pc ?
klimeque said:
did u try to connect another phone ? or try to coonect it to another pc, maybe problem is in ur pc ?
Click to expand...
Click to collapse
my own phone is working just fine (xperia s), my brothers sgs2 works fine, and an i9001 also works good. tried it on a other pc and works just fine
bump, any other ideas? see above posts

[Q] Bootloader gone?

I have a standard SM-N700 Galaxy Gear and had it running null. All seemed fine until one night after a notification tried to come to the watch, the screen flashed white and the watch appeared to shut down. Since then, it hasn't been able to turn on for anything. Below is the steps I've taken to try to recover my smartwatch...
Tried using multiple power supplies, no response (one power supply even caused the charging dock to become a little warm)
Tried holding power for 10 seconds, no response.
Tried repeatedly holding/pressing power (I heard sometimes this can help clear a softlocked device), no response.
Opened the watch and disconnected the battery. When the watch was reconnected, it vibrated once as if it was going to turn on, but didn't do anything further. Repeated attempts at removing the battery had no response, not even a vibrate.
Tried connecting the watch to my PC, the computer beeped that a device was connected and reported that there was no driver for "sec s5pc210 test b/d". I checked and the standard Samsung USB Drivers are installed. Tried other USB cables and USB ports, either the computer gives the beep of a malfunctioning USB device, or beeps as if something connected, but then the device seems to disappear.
I've read some resources that suggest that either the watch is completely fried, or somehow during an update to Gear Manager, it corrupted or damaged the bootloader of the watch, and after the watch attempted to reboot, it failed and got stuck in the condition it is in now. Based on these resources, there's supposed to be a way using Odin to flash a proper bootloader to the device, but since it does not appear to stay connected for more than an instant, and when it does connect it appears as this "sec s5pc210 test b/d" device, the tools I've tried to flash the bootloader have failed.
I really don't want to have to replace this device. Having a Samsung watch that still runs plain Android is not something I want to give up.

SOLVED: SP Gravely Ill: Suffered heart attack (vibrates 3 times)

I am posting this update in aid of future Xperia owners:
Problem: I seemed to have experienced the infamous Xperia "Red Light of Death". Phone vibrated 3 times continuously when charged. Screen never came on. Led was only ever RED, and only came on sometimes, sometimes solid, sometimes blinking twice. Computers were not recognizing the Xperia. Neither volume UP or DOWN button presses were ever recognized by any software on either the Win 7 or Win XP installations. However, on a couple of occasions, both computers recognized there was a device on the USB when doing a reset (reset + power). This caused them to try to install drivers. But the drivers, if installed, did not successfully allow any of the software tools to recognize the phone. Nor was the phone recognized in Device Manager, when connected, even when the UP or other buttons were pressed at connection time.
I asked for assistance on 4 or 5 of the net's biggest android forums on this... none came. So I was quickly giving up hope on the Xperia, since it seemed like there was nothing else to do. It might have taken water for all I know, when it was not in my hands, and the mobo might be quiched.
Solution: The phone is charging right now, the screen and color LEDs work fine, the original system is fully intact, and I did not need to reflash a new ROM or anything. However, I'm not exactly sure how I resolved the problem. I'll go through *some* of the steps that preceded this breakthrough. The breakthrough may (or may not) be due Sony's "PC Companion". This is an older version of what Sony now calls "Xperia Companion" (which did nothing good for me, so I went with the older software). "PC Companion" was also useless to me, since it kept insisting on not working unless you allow a connection for it to update itself. But the update always failed, with no clue as to why, despite a/v & firewall disabled. I found a comment where one user said he was able to do a bit more with PCC, once internet was disabled. So I tried that, and yeah, I could at least convince PC Companion to see if it could recognize the phone once the internet was disabled. But just like Flashtools, adb, the Sony Xperia SP drivers and all the other tools, it didn't recognize the phone was plugged in. At least, not the first few times I tried it, using various button combinations. (Up, Down & Reset/Power). Finally, I got a blue light and the PC (Win XP install) started loading drivers for the device.
I'm just not sure what triggered the change. Was it a reset/power combo operation? Was it a slight shift in the motherboard or USB connector that did it? Was it due to (the THIRD install of) PC Companion, or it would have happened with other software eventually? Its hard to say. I think these things contributed to the solution: PC Companion, the reset/power combo press, and just a lot of perseverance, most importantly. (3 days working at it in my case!). If you get this same problem with your Xperia, good luck to you.
(Trust me. You'll need it).
Lent my Sony Xperia SP (C5306) to someone, and it came back in a state where it vibrates 3 times when powering on or charging (it stops vibrating after a while, then starts again). And it won't boot or show anything on the screen, and only a RED led light comes on occasionally. So now I'm stuck on trying to flash a stock ROM on a Win7 system, using Flashtool 0.9.18.6, after installing the Flashtool drivers for "Flashmode" and the SP model, and PC Companion (PC Companion didn't fully install, because it demands updating, and fails on the update -- despite no antivirus installed, and the Windows firewall set to "enable all'). So now my problem is Flashtool won't recognize the phone on the "Please connect your device into flashmode" step, when I press Volume Down before reconnecting the USB cable. I've even tried taking the battery out for a few minutes, no dice.
At a certain point, after hitting the reset button and other buttons, Windows finally recognized there was a phone connected, and automatically installed USB drivers. Yet despite this, Flashtool still wouldn't flash the ROM. I do get 1 error in red saying "ROOT: THIS BUNDLE IS NOT VALID". Presuming this refers to the ROM, I made sure it specified it was for my model (C5306) and its even from the original carrier (Bell). In any case, it still goes beyond that error and proceeds to prepare the files for flashing.
So I'm not entirely sure what's preventing Flashtool from recognizing the phone, since it could be many things. My best guess is the soft or hard brick condition its in: since you can't power down the phone properly, and removing the battery is apparently not the same thing, its not getting to the trigger point that activates Flashtool's flashing. I'm right now trying the "rubberband trick". The idea is to keep the Volume down button depressed with a rubber band, and eventually, the battery wears down and maybe Flashtool recognizes it when it bootloops. I don't get that though, since Flashtool requires you plug the phone in via USB. And if its plugged in via USB, the battery should not ever run down, since its being charged by the USB port.
The phone was rooted, and IIRC, I think my bootloader is locked, so let's assume that. Can anyone help me along on this?
A few days ago, my Sony Xperia SP also could not start up and would keep on vibrating when connected to mains powered charger or USB port of PC. I just wish to record here my experience, hoping it will help some Xperia SP owners facing similar problems.
I tried various suggestions found in various forums but without success, gave up and bought a new phone. The very next day I did a final try. I charged it for around an hour just before I sleep and disconnected it when it was still vibrating. Next morning (yesterday), I pressed the Reset button (marked "OFF" on the back of the set with back cover removed), each lasting about 8-10 seconds. I did not felt any vibration. Anyway, I proceeded to press the power button on the side. And the set turned on! The battery status was shown as 100%. I connected it to my PC just in case drained down battery would cause it to shutdown. I saw a message indicating update was available and proceeded with update which was completed successfully. I downloaded an app and transferred my contacts to my SIM card. (Doing a backup with Xperia Companion will take many hours and I am not sure my contacts could be moved to a non-Sony phone if the Xperia SP fails again later). It has been 24 hours after my SP had revived and it has behaved normally so far.
My thought on this incident is that the problem was not due to battery or some hardware inside the phone. The problem was very likely due to incomplete software updating.

Phone killed by connecting to pc

Hello, today my phone was hard bricked by connecting to pc...I wanted to boot it up to download mode, but because my mistake i hold power down button and no power up button...then pc starts installing qualcomm_qdload driver or something...but it wasnt installed...i disconnect phone from pc and it wont turn on...its totally killed, it wont power on on charger, or something, only when i connect it to pc i see qdload driver...its that possible?
kiosk123 said:
Hello, today my phone was hard bricked by connecting to pc...I wanted to boot it up to download mode, but because my mistake i hold power down button and no power up button...then pc starts installing qualcomm_qdload driver or something...but it wasnt installed...i disconnect phone from pc and it wont turn on...its totally killed, it wont power on on charger, or something, only when i connect it to pc i see qdload driver...its that possible?
Click to expand...
Click to collapse
Try this hard reset https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429

Need help with possible bricked device !

Hi, yesterday my phone hangs on using apps and won't react to anything. So i have done a hard power off with power+vol up. Next i tried to start the device again and nothing The device won't start into any mode (system/bootloader/flash) and no lights etc. So i checked some threads in net and tried to plug in charger over night. Today behaviour has changed a little bit. When connecting to pc device is detected as usb device with error in getting description. This is the only reaction of the device. Again doing a hard power off etc. won't work (also no vibration).
Has anybody had same behaviour and could fix it ?
System is unlocked and was running with cm12.1.
Before you ask: pcc etc. also won't wark cause usb-connect won't work corectly.

Categories

Resources