I know there are a million threads out there on bricking and odin and download mode and I have gone through almost all of them in the past 2 hours but I havent been able to find the solution to my problem.
I was odining back from trigger redux to JFD when the phone got stuck at flashing factoryfs.rfs. I hadnt checked repartition before flashing. After 20 mins of being stuck i disconnected the phone from my laptop and rebooted it.
It booted up to the pc and phone download mode screen. Since then my laptop running windows 7 64 bit is unable to recognize it. I have uninstalled and reinstalled the drivers and restarted the machine a couple of times.
I have done multiple battery pulls to try to recognize the phone on windows and tried all 4 USB ports but it wont be recognized at all. As soon as I connect the phone to the laptop, it boots up to the pc and phone screen which means the phone can detect the pc but the pc cant detect the phone.
I've tried using the original samsung micro usb cable as well as a nokia micro usb cable which i usually use for charging the phone.
Any help will be greatly appreciated. I do not have access to other windows machines at the moment.
i just noticed that if i pull the battery while the phone is connected to the laptop, the phone and pc download screen stays on.
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.
Ok so i had a Nexus 7 2012 installed into my car dashboard.
Some time ago the tablet stopped charging. I assumed the usb port was broken (had to jiggle it to charge sometimes) so i went ahead an tryied to clean it with a niddle while it was still on (stupid, i know). It still didnt charged and i tryied to power it off. It powered off and then it came back on. By itself. It was strange. I tought i short circuit it so i pulled out the battery and went to buy another daughter board for the usb charging port. The daughterboard came and i replaced it. Same problems.
Then i assumed it was a software error (the tablet had an unofficial lineage os installed). I booted into recovery and whiped cache + factory reset. Then the tablet went into bootloop. Powered back into recovery and plugged in the usb to the laptop. Surprisingly the laptop recognised it. I used Nexus Tool Rootkit to go back to stock rom but even after going back to stock rom, the tablet still wont charge.
Any ideeas on what might it happen ? How to fix it ?
Flagsterino said:
Ok so i had a Nexus 7 2012 installed into my car dashboard.
Some time ago the tablet stopped charging. I assumed the usb port was broken (had to jiggle it to charge sometimes) so i went ahead an tryied to clean it with a niddle while it was still on (stupid, i know). It still didnt charged and i tryied to power it off. It powered off and then it came back on. By itself. It was strange. I tought i short circuit it so i pulled out the battery and went to buy another daughter board for the usb charging port. The daughterboard came and i replaced it. Same problems.
Then i assumed it was a software error (the tablet had an unofficial lineage os installed). I booted into recovery and whiped cache + factory reset. Then the tablet went into bootloop. Powered back into recovery and plugged in the usb to the laptop. Surprisingly the laptop recognised it. I used Nexus Tool Rootkit to go back to stock rom but even after going back to stock rom, the tablet still wont charge.
Any ideeas on what might it happen ? How to fix it ?
Click to expand...
Click to collapse
Hello there have you been able to fix this?i am currently in similar state
Okay so I f****ed up my phone bad.
Everything was working fine. I had a custom rom installed. One day the charging jack stopped working. The phone wasn't charging or connecting to PC. So I replaced the jack from a cheap shop and the mobile was charging once again but wasnt connecting to PC. I didn't mind it. Now after a few weeks the screen cracked and I replaced it again from a cheap shop. I booted the mobile and everything worked fine for 5 minutes and then the phone automatically restarted. This kept happening and then I opened twrp. the screen was working fine now and it wasn't restarting. So I knew the screen was fine the software was faulty. So after a few F**k ups I managed to remove TWRP as well as the Rom. Now the phone is only opening to fastboot mode and I cant put it back to Stock Firmware because it is not discoverable on my PC. I know I can replace the charging jack from official moto store but please help if it is possible without that.
TLDR
no rom or recovery in phone
only boots into fastboot mode
cant connect to PC.
harshill_only stock said:
Okay so I f****ed up my phone bad.
Everything was working fine. I had a custom rom installed. One day the charging jack stopped working. The phone wasn't charging or connecting to PC. So I replaced the jack from a cheap shop and the mobile was charging once again but wasnt connecting to PC. I didn't mind it. Now after a few weeks the screen cracked and I replaced it again from a cheap shop. I booted the mobile and everything worked fine for 5 minutes and then the phone automatically restarted. This kept happening and then I opened twrp. the screen was working fine now and it wasn't restarting. So I knew the screen was fine the software was faulty. So after a few F**k ups I managed to remove TWRP as well as the Rom. Now the phone is only opening to fastboot mode and I cant put it back to Stock Firmware because it is not discoverable on my PC. I know I can replace the charging jack from official moto store but please help if it is possible without that.
TLDR
no rom or recovery in phone
only boots into fastboot mode
cant connect to PC.
Click to expand...
Click to collapse
If the USB socked isn't working, there's no other connection to transfer any file to the device.
It's impossible without repairing the USB socket.