Okay. Hi guys.
I'm having some horrible USB connection problems and I've no idea whether they are hardware/software. I'm leaning towards the former.
About a month ago I noticed while plugged into my charger, my phone wasn't charging. Wiggling the cable did little, if anything to help. But it only happened that one day, and after a few beeps and boops of connections coming and going, it had seemed to have fixed itself.
Yesterday I decided to upgrade from XtreStoLite KitKat to XtreStoLite Lollipop. I made a bit of a mess of it and accidentally wiped my entire OS/cache/data before even putting the ROM on the sdcard directory. Fortunately I had already upgraded the modem/bootloader and was able to sideload the ROM.
I say I was able to sideload the ROM successfully, but this is really where the issues started to resurface. The first dozen or so times I tried to sideload I got "ADB not recognized" errors in CMD. I tried all sorts of USB driver re-installations, and installing google USB drivers from the Android SDK etc and nothing was working. Lots of beeps and boops of drivers installing and USB connections being made. In a last ditch attempt, I went back to CMD and once again typed "sideload adb rom.exe" and by some random miracle it worked. But that was the LAST time. I tried again later and got the same error as previously.
Anyway... new ROM installed. I ran through the set-up process and plugged my phone in to transfer over the add-on pack so I could re-activate Samsung Kies connections in order to restore my apps/photos etc.
*B-beep-b-b-b-eep-boop-b-beep* The phone was wildly connecting and disconnecting. I unplug it, blow into the USB connector - try to see any bent pins, but can't see anything. After a few tries I get it to connect long enough for me to transfer the file. Kies reinstalled. Throughout this WHOLE process there has been FAR too many disconnects.
If I DO get my phone to connect - Kies is stuck eternally on "connecting". I have a feeling MTP mode is just broken - as NOTHING shows up in My Computer when in that mode. Odin 3.09 no longer sees my phone at all, and when I connect in Camera mode NONE of the .zip files I placed in the sdcard directory show in Windows at all. But they ARE there, as I can still install from .zip in recovery.
The phone seems to work fine. But I want to restore my Kies backup, add/remove the .zips in the main sdcard directory, and see my phone in Odin.
Please help me. I am scared.
Okay, so i have a Samsung S4 (i9505) running cm12 (5.1.1). The problem I'm facing is that it won't connect to my laptop (or multiple other computers i've tried, also tried downloading and deleting stuff of windows which didnt work either) via the usb cable, i've also tried mounting multiple USB's (Through an otg adapter), which also didn't work.
I've tried turnign debugging on and off, ADB on and off, developer options on and off. I came to my last resort today, resetting it. I reset it, the samsung boot logo came up it then went into TWRP, though the TWRP logo just kept flashing on and off (i read somewhere this means that its corrupt but im not sure). The only way i could get the phone to boot was by pressing the: home + volume down & power buttons and then pressing down (cancel) on the custom OS warning screen.
The problem now that im facing is, i cant reset my phone, mount anything via the usb or connect it to any computer. If someone could help me, that'd be greatly appreciated.
I need some help guys.
My Nexus 7 all of a sudden stopped sending data through usb OTG and i tried to erase cache through TRWP but ended up deleting the OS. Now I am stuck with a device with no OS. I cannot mount the USB for my computer to recognise it so that I can restore it. I tried ADB sideload but it doesnt load and gets stuck on starting...
If I click on Mount, I cannot click on the USB-OTG box. My computer does have the correct drivers for the USB as it used to work on it before but since the OTG stopped responding to data I am now stuck and cannot push a restore image to the device.
Any help would really be appreciated.
Many thanks.
I've tried almost everything I can think off. I tried different OTG cables, different computers. None of the computers even detect a device as plugged in. Whether I boot into bootloader or recovery I just cannot get the PC to even acknowledge the fact that something is plugged in. As a result I am just not able to flash it at all. I tried NRT with the soft-brick option but that fails too because it says no adb connectivity.
any help please?
Hello XDA, my virtual phone heros, i appreciate your good work, i am reading here for a few years as a ghost and today i signed up because i am lost with a serious problem on my Note4 N910C (English is not my native language)
THE CONDITIONS AND ENVIRONMENT:
My Phone was first running on stock Lollipop 5.1.1 when i rooted it over ODIN 3.10.6 with space X kernel and CF Autoroot, SuperSU then i flashed the latest TWRP...
After that i flashed a Custom Rom: Sweet_ROM_V17.1_COJ2_N910C...
Everything was running flawlessly for about 2 weeks...I installed Titanium Backup, Xposed, Xprivacy Pro, Busybox and a lot more and made a complete TWRP Backup then, it was running like a charme...The backup is fine because when i messed up my phone through trying harder xprivacy parameters and other tweaking i needed to set it back by TWRP into the old state...
Nothing happened after that, it was running 100% for over a week of heavy usage...
THE PROBLEM:
The one morning i took it from the charger with 100% Battery and went to work...
Before the error occured I did some searching on the internet, used chats. movies, nothing special this day, USB Debugging was On, i remembered something messed up my chrome browser like this ad hijackers, i set it back by erasing data,cache of chrome in the app menu, then there was nothing else strange i remembered, my AF Firewall was closed, only Whatsapp and Browser were allowed to going through...
The same day in the afternoon i tried to use my car charger to recharge my Note 4 as usual, but this time it wasnt recognizing the charger and my first thought was that the charger is faulty or the cable, so i turned off the phone by the androids power menu...I retried loading my battery In the phones off state but when i plug in the charger, the battery symbol came up for short and then it remained dead, it s the same scenario until today, so i used my powerbank to try charging, because the powerbank has an indicator to show the loading state and everytime i plugged it in, it came up for short, battery symbol shows up for a few seconds, but no percentage or animation is showing as usual and no red LED, then its switching off, the powerbank LED indicator stops the loading state after a few seconds, so the loading current stops...
At home i tried the stock charger and it remained the same, since that, i have to charge the battery outside the phone...
The strange thing is:
The Rom is still booting fine, TWRP is booting, but its not going into download mode from Androids Power Menu like before, its always just rebooting back into android if i choose download mode and i have to take the battery out and back in and hit the download mode pattern Vol- Home Power, to enter Download Mode and even the booting into Download mode from TWRP gives the same strange results:
On my Laptop i started the device manager to see the USB hardware string parameters after a windows popup was telling me something like "Device not recognized"
The USB Driver ID dont fit the old right driver ID, it seems to be empty and the port is not communicating anymore
since the charging bug occured,( Everything worked fine the day before.)
I tried my Laptop to narrow down the bug with the same driver i used for flashing phones (S6,910F,910C) over ODIN and my Lappy has USB 2.0 and USB 3.0 ports.
I always used the same USB 2.0 port for ODIN and other MTP stuff, but since the bug showed up the 910C is not recognized at the USB 2.0 Port anymore, seems to be dead in the devices manager table, only the USB 3.0 Port shows it as unknown device with a strange empty ID --> I tried the other devices like the N910F and G920F that are still recognized by ODIN on the same USB2.0 and 3.0 Ports both with the same USB hardware strings, its just the N910C that isnt recognized anymore, in no mode, no ADB, MTP, no download mode, everywhere the same, USB is bricked! Windows finds no driver and says its no info avaiable on this device so I tried to force the right driver to run with the wrong buggy driver ID but its not communicating, ODIN indicator and log remains unchanged...So it seems to be the same situation like other people getting from killing the bootloader by bad flashing, the only difference is that my phone is still booting fine into recovery and even Android but with no charging. My USB Port is totally useless now, its like if Samsung or Google OTA update has overwritten my bootloader or something hidden in the rom that woke up to kill my mods i dont know and now.
PS: Things i tried so far with no results on fixing my issue....
1. Complete fresh reinstall of Sweetrom, 2. Flashing another kernel...
3. Roll back to my TWRP Backup of perfect running ROM but with no USB support anymore:
The Phone remains in unknown state, not affecting ODIN to switch into flash mode
I am sure its the bootloader, since its battery bug is still occuring while the phone is in off state...
Unable to tell the charger the right ID without USB communication...
i was wondering if there is a solution to make a bootloader hotflash from out of Android or something like getting me back on stock first with download mode, forcing the USB ID or communication with a tool out of android, SD card boot image like on note 3 whatever, please tell me! I cant find something related to my USB and Charging ISSUE
PLEASE HELP ME, I am lost
Still the same. It's booting fine, USB2.0 no reaction on the laptop in Fastboot/Adb/Mtp ... On USB 3.0 Device remains unknown with strange Device ID String in windows 10 hardware Manager... Forced the old formerly working driver, but Odin can't find it anymore... Adb, Mtp, fastboot don't work, no communication... USB Cid is hard bricked, Charging never works in no state, just showing up for a few seconds in off state while plugging it in for short.... Bootloader must be damaged, fastboot and twrp can be started with dead USB... So is there a way to run a boot image to fix my bootloader from SD card, Aroma, or like OTA Updates are flashing? If Samsung and Google apply bootloader updates over OTA and simply restart, why we can't do that??? I need a new bootloader, is there any way without USB?
Greetings,
Thank you for using XDA Assist.
I have moved your question to your device's Q&A forum. You'll receive expert advice here. Good luck!
Fixed!
The problem is the USB Connector Port itself, figured it out after bending the inner contacts up with a flat screwdriver and cleaned them. Before that i always tried the same gently with no change, but please do it at your own risk only. After searching for many hours about possible reasons for the problem, I came to the conclusion to even compromise the Port and heavy bending it up, now it's charging! I will exchange the port soon and change the frame too to have it back like as new... OK, if anyone in the future have problems with the bootloader or USB hardbrick n910c, feel free to ask me, I upgraded my knowledge on many causes now
Thank you very much
My 2cents stick to one charger. Do not share that charger with others.
The worst culprit are the cheap china car chargers.
I went thru two USB ports on my first phone to figure this out.
Ever since I have adopted the policy of using only one cable. Never had this issue.
Hi All
I am looking for an update.zip file I can use to flash the stock 6.0.1 rom again over my existing version to fix a USB connection issue. I need a Samsung OTA update.zip which can be flashed from the stock recovery via an sd card.
This has come to light as I've recently tried to update my note 4 to nougat but came across an issue where the phone will not connect with my PC via USB. I have tried all the usual tricks on the phone (dev options, usb debugging, MTP+ADB etc) but nothing was working. In the end I have replaced the micro usb daughter board on the phone thinking there must be an issue with the data pins but the phone still refuses to connect but charges fine. Strangely the phone thinks it's connected fine but the PC says it is not getting a device descriptor response. I have checked drivers etc and also tried 3 other PCs all of which connect to my old S4 without issue. I have also tried various USB cables including a new genuine samsung one.
Due to not being able to connect to a PC in any mode (such as odin download mode or recovery) and having the stock recovery without root my only hope is that a new update.zip will sort out corruption from the last OTA update. I believe this may be the reason as I was able to connect fine until the most recent update a couple of weeks ago. I have tried using a zip from the samfirm downloader but the recovery failed immediately with 'unable to map file'
Any help you guys can give would be greatly appreciated as I really don't want to be stuck on Marshmallow now Samsung will no longer be updating the Note 4.
I have tried connecting in MTP mode, odin download and recovery mode with usb debug both on and off
Many Thanks
Luke