Hello,
I've a big issue, if I try to connect the phone, via usb, to the pc windows none of the devices recognize the connection.
Nothing appear on the Defy. On the Pc, sometimes appear the "new device windows" but if I try to install drivers it show me an alert saying that the device is not installed correctly.
I've tried all the motorola drivers available but nothing happen. I've also tried 2 other pc and 2 other usb cable
Fortunally, the device is rooted and I can install a nandroid backup but I don't know how I can resolve this issue, someone can help me?
Thanks
nickee said:
Hello,
I've a big issue, if I try to connect the phone, via usb, to the pc windows none of the devices recognize the connection.
Nothing appear on the Defy. On the Pc, sometimes appear the "new device windows" but if I try to install drivers it show me an alert saying that the device is not installed correctly.
I've tried all the motorola drivers available but nothing happen. I've also tried 2 other pc and 2 other usb cable
Fortunally, the device is rooted and I can install a nandroid backup but I don't know how I can resolve this issue, someone can help me?
Thanks
Click to expand...
Click to collapse
Enable / disable USB debugging maybe? But normally there should be a prompt on the phone when you plug it in (pulling down the status bar usually asks you what to do, give memory card access, charge only...). Btw, does the Defy charge when plugged in or does the LED light up?
Arjoma said:
Enable / disable USB debugging maybe? But normally there should be a prompt on the phone when you plug it in (pulling down the status bar usually asks you what to do, give memory card access, charge only...). Btw, does the Defy charge when plugged in or does the LED light up?
Click to expand...
Click to collapse
Tried but nothing change. The phone doesn't charge correctly and no prompt message if I connect it to the pc.
And it is definitely not the cable and / or the USB port? Then it has to be a hardware problem on the phone's side I think.
Arjoma said:
And it is definitely not the cable and / or the USB port? Then it has to be a hardware problem on the phone's side I think.
Click to expand...
Click to collapse
Not the cable and not the USB
There's a way to reinstall all the Defy driver without the cable?
Try installing new moto drivers.
http://forum.xda-developers.com/showthread.php?t=1100585&highlight=rsd
Installed but no improvement on the situation. I think that's an hardware problem...
nickee said:
Installed but no improvement on the situation. I think that's an hardware problem...
Click to expand...
Click to collapse
Almost seems so : But charging works?
Arjoma said:
Almost seems so : But charging works?
Click to expand...
Click to collapse
Charging didn't work if I connect the phone to the pc, it's strange because if I connect to the electrical power it works.
I also think that I've had an issue when I've installed the custom firmware
Huhu,
i have issue with my usb connection.
If i connect it to the laptop it say Unknow Device (error code 43). Then it only charge.
I looking up the internet for 2 days now.
Someone said Unknow device is always a driver problem.
Found some driver called samsung/sgs2 driver. But that wasnt working.
Debugging modus also not help me.
Maybe someone have an other idea?
Try this
1. Turn off phone while still plugged in to your computer
2. Press Volume Button Up and then Power button to turn it on in bootloader/or recoverymode
3. You should hear a typical usb connecting sound. (if not you can unplug and plug the usb until you hear it)
4. Unplug it to hear the usb disconnecting sound.
4. Restart your phone and then allow it to turn on as usual, allow it to load everything before.. doing #5
5. Try plugging it in and test.
i tested it but not get a sound.
bootloader say waiting for usb ;/
Uninstall any previous drivers you installed and install these. http://forum.xda-developers.com/showthread.php?t=961956
They worked for me.
These are the drivers i already tried.
But they not work for me ;/
If you're laptop is Windows:
-install Samsung Kies....after that, plug your Glide, there should be a prompt "Installing device drivers" and/or "Searching Windows update..." Wait for that to be done and you should be able to connect.
Same thing with MAC,
I tried that befor but not work ;(
Does i have a chance to flash the phone without usb?
can i install CWM withouth odin?
huhu1312 said:
I tried that befor but not work ;(
Does i have a chance to flash the phone without usb?
can i install CWM withouth odin?
Click to expand...
Click to collapse
There might be a cwm flashable via rom manager soon if we get some testers with stock recovery to join #utkanos on freenode irc.
and someone know how to root without usb?
is there a functionally apk?
huhu1312 said:
and someone know how to root without usb?
is there a functionally apk?
Click to expand...
Click to collapse
So far, only way is through Odin on windows PC
because CPrisic
huhu1312 said:
Huhu,
i have issue with my usb connection.
If i connect it to the laptop it say Unknow Device (error code 43). Then it only charge.
I looking up the internet for 2 days now.
Someone said Unknow device is always a driver problem.
Found some driver called samsung/sgs2 driver. But that wasnt working.
Debugging modus also not help me.
Maybe someone have an other idea?
Click to expand...
Click to collapse
I have the same situation with my glide. But the problem was miserable. Once i've changed USB cable, everything became OK for me (other phones work good with old cable).
Try this. Maybe it could help
Hi guys,
i wanted flash some new kernel, i have currently Rush kernel. So i opened freshly installed FlashTool (0.90.10.1) with installed drivers from /drivers folder, take out battery and press "menu" and connect cabel....just like million times before. But now the LED just blinked blue and phone bootloops until i pull the cable out. And just the same happens when i want to go into flashmode (green LED) it just blinks and get bootloop. Can someone give me some advise? I am using original SE cable that comes with it.
edit: i am not using USB controller, i am using USB that comes right from motherboard
edit 2: even if i try "reboot into fastboot mode (via ADB)" in flashtool, it reboots into CWM...
Lord5619
And what happens when you try an older version or manual fastboot?
XperienceD said:
And what happens when you try an older version or manual fastboot?
Click to expand...
Click to collapse
just the same...
hmmm, but now the weird part, when i put the cable, just the cable without phone connected to it, windows told me, that "some of devices was not recognized" and drivers was not installed for unknown device. What the hell does this mean? drivers for cable?! btw: the cable is barely used i flashed with it two Arc S just week ago.
lord5619 said:
just the same...
hmmm, but now the weird part, when i put the cable, just the cable without phone connected to it, windows told me, that "some of devices was not recognized" and drivers was not installed for unknown device. What the hell does this mean? drivers for cable?! btw: the cable is barely used i flashed with it two Arc S just week ago.
Click to expand...
Click to collapse
Sounds like a PC issue to me.
nope it was that cable...i don´t get it, but with another one, it just works. I am using sometimes that "non-working" cable for file transfer or charge battery and it works normally. Strange...
I was flashing my phone as normal in the process of rooting it, then my brother turned my computer off...now i can't seem to get my phone into Download Mode, but it will go into recovery mode to hard reset the phone, but nothing happens*. When plugged into my computer, it doesn't come up in Device Manager.
Plugging it in with no battery makes the computer recognise it as "Unknown USB Device (Device Descriptor Request Failed)"
* I can get to "Factory data reset" but after selecting yes, the Bootloop continues
Anyone help ?
LukeIMG19 said:
I was flashing my phone as normal in the process of rooting it, then my brother turned my computer off...now i can't seem to get my phone into Download Mode, but it will go into recovery mode to hard reset the phone, but nothing happens*. When plugged into my computer, it doesn't come up in Device Manager.
Plugging it in with no battery makes the computer recognise it as "Unknown USB Device (Device Descriptor Request Failed)"
* I can get to "Factory data reset" but after selecting yes, the Bootloop continues
Anyone help ?
Click to expand...
Click to collapse
Seriously no idea, my computer can't seem to detect it at all
Can anyone at least recommend another place to look ?
Or are any of these links a good path to follow ?
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
http://www.reddit.com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/
http://forums.androidcentral.com/lg...-cm-11-update-can-t-get-phone-recognized.html
LukeIMG19 said:
Seriously no idea, my computer can't seem to detect it at all
Can anyone at least recommend another place to look ?
Or are any of these links a good path to follow ?
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
http://www.reddit.com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/
http://forums.androidcentral.com/lg...-cm-11-update-can-t-get-phone-recognized.html
Click to expand...
Click to collapse
I could do this:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
for the LG G3 D858HK, but from the problem described, would it be better to just take it back ?
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.
slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.
slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
Post SS of the device manager after connecting the phone to the PC
150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.
@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...
Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722
slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode
150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.
nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?
nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.
150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.
Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?