A couple of weeks ago my N4 decided that it didn't want connect to my computer. I tried windows xp, 7, and osx. I tried 5 different usb cables that worked with other android phones just fine. I tried all usb ports on said computers. I've uninstalled and re-installed all drivers, using all the known methods. Then I noticed that I was getting terrible battery life. Like 5% gone in 20 minutes with all radios turned off and leaving it in my pocket. I was on the latest verison of PA with the latest verion of franco.kernel and I've had no previous problems with my phone.
So I thought maybe I did something to it like a bad flash, so i downloaded a stock 4.2.2 zip and flashed it (with gapps). The problem persisted. So I proceeded to wipe the phone in cwm in an act of desperation, and lo and behole I was then stuck with the same problem as before, but this time with no working os to boot to, and no way of connecting it to fastboot or adb in order to put any files on the sdcard/ flash it back to stock. I am, however, still able to boot into cwm and the bootloader. Then, thinking it might be a problem with the usb daughter board as whenever I tried to plug my phone into a computer it gave me this:"windows has stopped this device because it has reported problems. (code 43)", I ordered a replacement. Replacement came, I swapped them out, and absolutely nothing has changed. I tried uninstalling/deleting drivers and re-installing them just to make sure, but same results as before. Also, the N4 DOES charge when plugged into a power source like normal.
So the way I see it, I can either keep trying to replace parts, or one of you wonderful people know some crazy fix to my problem. If not, then I could go the other way, and attempt to brick the N4 even further in order to get it replaced (I.e. it's not possible to see whether or not it's unlocked/has a custom recovery). Also, I can enter "download mode" by holding down the volume buttons and connecting a usb cable, but windows still doesn't recognize the device.
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.
So after getting around to installing the July security patch a couple days ago USB C charging stopped working on my Nexus 6P. If I use a USB A to USB C cable it will charge, but not if I use USB C to USB C. This persisted over multiple cable and chargers.
I tried to wipe the cache but had a problem getting into recovery - I could get to the boot loader but when i select Recovery i get a 'No Command' error screen. (eventually i found out i could power and volume up from this screen to get recovery, but the wipe cache didn't fix anything.)
Then I installed Oreo hoping that would take care of the issue but no luck. Any thoughts? Anybody else get this from the security patch?
Google support has not been particularly helpful.
Hi, i just started getting this issue today. I installed android O yesterday. My original charger which is C to C wont work but C to A will work fine. I've also had my 6p not recognized by my pc. It only charges when i plug it in. Tried different cables, different computers, but I think it might by my charging port. Google support tried, they didn't know what was going on.
But I'm stuck without a custom recovery right now and have lost root access. But phone is working fine. Messed up during flashing, didnt flash custom recovery thinking twrp would be intact but nope. And I cant use ADB to reflash anything cause my stupid 6p wont get recognized by my pc. haha
sonysingh1983 said:
Hi, i just started getting this issue today. I installed android O yesterday. My original charger which is C to C wont work but C to A will work fine. I've also had my 6p not recognized by my pc. It only charges when i plug it in. Tried different cables, different computers, but I think it might by my charging port. Google support tried, they didn't know what was going on.
But I'm stuck without a custom recovery right now and have lost root access. But phone is working fine. Messed up during flashing, didnt flash custom recovery thinking twrp would be intact but nope. And I cant use ADB to reflash anything cause my stupid 6p wont get recognized by my pc. haha
Click to expand...
Click to collapse
haha. use bootloader mode and fastboot flash the TWRP you overwrote when you flashed over recovery. ADB only works in Recovery, but fastboot works in bootloader mode which previously said you can access.
Hi, I really need help. three months ago, some weeks after my Mi 9T overheated on sun (don't know if that has some relation to the issue), it suddenly stopped charging while on, unless I rebooted or turned off. Also, it had difficulties to transfer files to PC and connect to a flash drive by OTG.
Then, I took it to a guy and he said I needed to replace the charging port, and so I did. But only now, after a serious issue. I was changing my rom from MiRoom (MIUI 12) to Evolution X, since the MiRoom's developer ended the rom's support. But It didn't work, It boots into Fastboot mode. I tried to connect to PC and OTG, on recovery mode, but neither worked. The PC doesn't recognize my phone, and the OTG flash drive isn't recognized by the phone.
I bought the charging connector online and paid that guy to replace it. The port feels better, the connector feels way steadier when pluged in, but I still can't know if it charges while on and file transfer to PC or OTG is still not working. So, I'm stuck on recovery mode, in a rom that doesn't boot and a USB port that doesn't work properly. If anyone has a clue of what part I might take to replace or a repair, or maybe a software solution, if that's the case, I would be really thankful.
Back in 2014 my device stopped charging with USB. I just happened to find it the other day and put it on a wireless charger and lo and behold my Nexus is alive again. Back then I used to do a lot of flashing ROMs but I'm very rusty now. It has a custom rom called Vanir on it and is rooted and has twrp. If I just download a custom rom to the device will I be able to go into recovery and install it? My laptop just died on me and I can't use it to flash the ROM. I just want to try something different for fun.
Thanks!
Edit: the USB won't work even if my laptop hadn't died.
Download custom recovery to internal memory. Make sure it's not saved in to system directory, but internal sdcard directory. Boot in to recovery mode, wipe cache, then chose install and find your custom ROM. Press install. Make sure custom ROM is definitely made for your device and was confirmed to work without any issues. USB stops working for few reasons. First and easiest to fix is damaged USB socket. You can replace it by buying a new or second hand one. Second reason is short on OTG activation pin. If its's shorted to GND, USB charging will not work and no communication with computer possible. There is a lot of possibilities where this short could have happened. On my 3G device this happened under main processor, and the only way I managed to revive it was injecting 1V to OTG activation pin, which somehow made short disappear.