Hey guys, I've searched for the same problem and it seems that nobody had the same problem.
So like many of us the usb port only charge while off.. but I can go into bootloader and use fastboot which means non-sense...
Does someone have an idea of what I can do before I buy a replacement?
EDIT: I've done the *#*#4636#*#* secret code, went under battery info and it doesn't detect the charging plug.
Thanks
Cordially,
baskwo
*1 week Bump*
Grab a paperclip and scrape the dust from the bottom of the micro usb plug. They look like they are clean, in reality they are not.
Are you running stock 4.3? Try if the charger gets detected in recovery mode (e.g. TWRP).
Does USB work in Android (PC connection)
Before I post my problem I had change the micro usb part so it's brand new :/ (I tried to clean it tho)
It is not stock because as it was not working I tried CM with its custom kernel and no luck.
Usb does not work in recovery mode but it works in bootloader as fastboot device!
THanks for your answer your help is appreciate!
USB only works in fastboot mode
Hi everybody,
I have a problem with my meizu m2 mini.
It's Charging only when it's off. It's Not recognize by the PC except in fastboot mode.
I have download lot of roms but it 's not resolve my problem.
In the engineering menu, I can active the charge icon when i play with the IF TEST in Hardware USB menu.
I have Android 5.1..1
Related
I've been searching the web, but cannot find help. Have i9250, but cannot get it to be detected by a PC. I can't even get a device with no drivers installed to show up. Not in fastboot, not in download mode, nothing. I had a working, barely, phone, but the battery was draining and I couldn't detect the phone with any PC/USB cable combination. I replaced the USB daughterboard and still had the same issues. After that, I tried flashing stock recovery and stock rom, so I could maybe get Google to fix it, but it's stuck on boot loops. Also, no Omap 4440 detected, if I plug in without battery, like in this thread http://forum.xda-developers.com/showthread.php?p=28038226
Thanks in advance for any advice.
sgtkwol said:
I've been searching the web, but cannot find help. Have i9250, but cannot get it to be detected by a PC. I can't even get a device with no drivers installed to show up. Not in fastboot, not in download mode, nothing. I had a working, barely, phone, but the battery was draining and I couldn't detect the phone with any PC/USB cable combination. I replaced the USB daughterboard and still had the same issues. After that, I tried flashing stock recovery and stock rom, so I could maybe get Google to fix it, but it's stuck on boot loops. Also, no Omap 4440 detected, if I plug in without battery, like in this thread http://forum.xda-developers.com/showthread.php?p=28038226
Thanks in advance for any advice.
Click to expand...
Click to collapse
after my usb port started restarting my phone due to a short circuit i got by with a usb cable that i cut and attached the wires to the pogo pin connectors and charge it that way. Really not a good way, buy yourself a pogo pin charger dock if possible, sounds like a usb replacement is needed (same for me, but getting an extra couple of batteries, just got an external charger)
I was able to charge, but now I'm stuck with bootloops and can't get a data connection to a computer with fasboot or odin.
sgtkwol said:
I was able to charge, but now I'm stuck with bootloops and can't get a data connection to a computer with fasboot or odin.
Click to expand...
Click to collapse
cant boot into recovery? i've managed to get by with adb over wifi where it was needed, thankfully nothing that has required an actual usb connection.
at what point is the reboot occurring? would safe mode possibly help?
Recovery just shows the android open with red exclamation.
OS bootloops on Nexus logo.
Neither Odin nor bootloader are recognized by any PC/usb cable combination. Even after changing the USB daughterboard http://phonepartsusa.com/samsung-ga...onnector-flex-cable-0000824?filter_name=i9250
Hey guys,
Now, my Galaxy Note 2 was rooted. When I connected it with the USB cable to my PC the PC didn't recognize it (it used too, but then suddenly it stopped connecting). It still charges but no new device is detected. No Kies, no MTP, no Odin.
I didn't worry too much, because being rooted I could still do everything using the external sd card.
However then the ROM for Android 4.3 was leaked I stupidly installed the stock version. So, no root, and no capability to mess around with the phone.. I also have no viewable option in Settings to set the device connection to MTP, or PTP mode as usual, but maybe that's because of Android 4.3
I have bought a new USB flex part, opened it and replaced it but it still didn't work.
I download a version of phoneutils.apk and installed (because the one on Android 4.3 didn't have Qualcomm USB settings option) and choose the correct options, but still nothing.
Do you have any idea what may have gone wrong? Or what I can try to do?
I desperately want to root the thing.
Thank you very much! I appreciate any suggestion and reply.
Hi!
This might sound stupid but... have you tried a different USB cable? Or USB port? Sometimes this can solve these kind of issues. Take a look in your computer's Device Manager and see if you have any problems with the USB hub driver. Also try to connect using a different PC and see if that works.
You can try and boot in Download mode (Vol down + Home + Power) and see if ODIN sees the phone. If so, you can flash another stock firmware and see if your USB works then.
Yea tried all that! No success. /:
Phone goes into download mode but Odin does not recognize it..
Ruwin said:
Hi!
This might sound stupid but... have you tried a different USB cable? Or USB port? Sometimes this can solve these kind of issues. Take a look in your computer's Device Manager and see if you have any problems with the USB hub driver. Also try to connect using a different PC and see if that works.
You can try and boot in Download mode (Vol down + Home + Power) and see if ODIN sees the phone. If so, you can flash another stock firmware and see if your USB works then.
Click to expand...
Click to collapse
Hi,
So I got fairly sick of HTC's Android 6 update (Crazy amount of bugs) and decided to install CM-13.
A problem arose then when I tried to unlock my bootloader, the computer wouldn't detect my the one m8 in fastboot mode even with android studio and usb drivers installed or standard mode.
I installed HTC sync manager and still no good.
I tried different cables and different computers (one win 10 the other win 7).
When the phone is in standard mode and connected to the computer the usb symbol comes up and says charging only,
if i click on this and select file transfer mode the screen just greys out and stays like that until i click home/back.
This option comes up only once (I need to reboot to get it again).
I found another thread that says to install "AndroidHtcsync2.apk" I tried this and it didn't work.
Thanks
Maybe, like me, you have a broken USB port that will still allow charging but no data connection
assetttt said:
Maybe, like me, you have a broken USB port that will still allow charging but no data connection
Click to expand...
Click to collapse
That might be it, only thing is i was able to send files no problem a month or two ago before the update.
You need to be in bootloader-fastboot mode for fastboot commands; they won't work booted in OS or in bootloader (I think one of those is what you mean by "standard mode"?).
Other than that, Win7 is more reliable. And USB 3.0 is known to cause issues with USB connectivity on this phone, as well.
Sorry that wasn't clear. I was actually in fastboot mode when sending the commands.
The windows 7 computer I tried it in had USB 3.0 ports as well so that might be it.
However I wiped the phone after failing to flash CM and it fixed most of the bugs I was having trouble with so I might just leave it this way.
Thanks for the help
Hi Everyone,
I seem to have bricked a nexus 2013 wifi. At first, it was having movie playback issues so I restored it to lollipop using factory image on the google site. I decided to get OTA up to the latest MM. So far so good. But I though about putting a custom rom to it. So I installed TWRP 3.02 for flo and flashed PN MM with the recommended GAPPS. Kernel was what came with it. It worked fine until this morning when I realized that the touchscreen was not responding. I went to BL mode and into recovery. TWRP came up but touch was not responding as well.
So, I connected the device to my PC. It now shows unrecognized device. It still charges and all that but It is now stuck on the google logo. when I go to TWRP, touch wont work. I have tried another cable, still the same. My N6 is detected without issues using the same PC and cable. Since there are no drivers, I cannot reflash anything...
Any thoughts? Or am I just lucky to have bricked it? Appreciate any inputs that will be thrown in this direction. Cheers!
Hi, N7 motherboard gets touch, USB, accelerometer and compass data via the wide silver cable which often suffers from poor contact. Please try this first. If it is still not fixed, then in fastboot mode run and post the output of the following commands:
Code:
fastboot getvar all
fastboot oem gpt-info
fastboot format cache
Thanks for the help. hmm.. i pressed that part and it booted up to PN, touch is working as well. Not sure if that fixed it but if it happens again im gonna try to press that area. however, its still not detecting the device. I see it in Device manager, it says unknown device and will not take any driver, so fastboot is not an option for me atm.
so just an update. when I was able to boot up, it will not go landscape no matter what. I downloaded check my android and it the tests for compass and sensors were not responding. I decided to open the back cover, it was fairly easy. The thing is I have not the right tools to reseat the silver flex cable and I fear I might damage it, so I tried putting folded paper on to where it connects to on both ends. Now the thing works with landscape and so far, have not experienced touch issues or no boot issues.
I still do not have access to fastboot, though, as it still isnt detected by my computer. so I may have to stick to putting stuff to it over the air. Or should I just reseat that cable? Does it just slide out?
welxiii said:
I still do not have access to fastboot... should I just reseat that cable?
Click to expand...
Click to collapse
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
noahvt said:
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
Click to expand...
Click to collapse
The next step:
disconnect the ribbon cable from both the mobo AND daughterboard
spray the cable's and PCB connectors' contacts with Electronic Cleaner
reconnect and relock
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
Hi,
I really appreciate the assistance. Well, here's what I found.
[*]What's the VID/PID of the non-detected device? USB\VID_0000&PID_0002\6&688A3B8&0&2
[*]Does ADB work if you start TWRP? I don't think it does. In TWRP, I still get a message on my computer that the device has failed. DM shows the device as unknown usb device (device descriptor request failed)
[*]Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it? no it doesnt. same error as above.
[*]Is an OTG flash drive recognized? yes it does.
[*]Maybe Windows has a driver problem - does it work from live Linux? I'm still working on this. btw the same setup works on my phones and they are detected just fine.
update:
Suddenly its now detected by my pc. I connected my usb otg. At first,. It wasnt detected so I tried the usb on my nex6 and it worked. I connected it back to the 7 and voila! No error and DM now shows it as an android device. Whew!
But I have one question, is it safe to leave the folded papers i placed on both ends of the silver connector?
welxiii said:
Suddenly its now detected by my pc...
...is it safe to leave the folded papers i placed on both ends of the silver connector?
Click to expand...
Click to collapse
Yes.
As I mentioned earlier, the silver cable also connects USB data, so if you experience USB detection problems again, then do full re-seating with clean-up.
Cheers :highfive:
Thanks again for the assistance. Hopefully, it doesn't come to that.
unbricked my google nexus 7 tablet
if anyone has bricked there nexus 7 wifi tablet.....you can now unbrick it with the skipsoft toolkit. my tablet was bricked for awhile (it was stuck on the google logo and when I tried to boot into the twrp recovery it showed the android bot with an exclamation point so I was screwed big time) so I just brought another one (different version). after awhile I gave up hope, but today I decided to unbrick it (or atleast try to). at first I was using the nexus toolkit like I did before and I was having problems with it being recognized via adb and it wouldn't flash the stock recovery.img. than I remembered that I also had the skipsoft toolkit installed on my computer and the nexus 7 tablet was also supported on that toolkit so I decided to give it a try. at first, since I had it plugged in, it wouldn't recognize that it was plugged in not realizing that I had to download all the images and recoveries it needed to be able to root it and return it to stock if necessary so I did that and when I finished installing everything it detected that my device was in fastboot mode. I flashed the stock recovery image and it booted up like it was suppose to. I'm writing this just incase so one has bricked there device and has lost all hope in fixing there mistake. I love android and recently have a lg nexus 5x that's rooted with a custom rom on android 7.0 nougat. android is awesome
who ever developed the skipsoft toolkit....your awesome and thankyou for making this possible.
i am trying to connect my device with pc when i connect it select usb option is not appear on my device i have tried with every cable original third party but same issue i have tried installing adb all the drivers turn on my device in fastboot connect with pc run this command fastboot oem device-info its just show waiting, one more issue i am facing is when i connect with original charger and cable my phone charging is not increasing i have tried with original samsung s9 cable and charger same issue not able to charge with quick charger but when i connect it with ordinary 5v/1.5A charger my phone charging is increasing slowly but increasing i don't know what's going on can anybody help me on this :crying::crying::crying:
i also do have the same issues on my Mi Mix 2, after flashing havoc 3.0 custom rom USB not functioning but charging is okay. also all sensors suddenly are not working. I want to reflash it to stock rom but i cant because PC wont recognise the Mix 2 even in fastboot mode
any one with same issues?