Hi guys,
Im actually using samsung galaxy s GT-9001 and have recently ran into a serious problem. actually two
Problem 1 : Usb cable malfuction
Im unable to connect my phone to pc, windows reports unrecognised device (was able before, tried few PC, cables) , furthermore im unable to charge my device unless i remove the battery, connect the charger then put the battery back up. Also noticed if i just put the charger on turned off device it boots instantly (skiping the option to charged as turned off), it does charge over USB, but does not recognise it.
Problem 2 : How to return to stock recovery and rom without USB
In regards to my problem number 1 , i have decided to give a shot at warranty, unfortunately cannot get rid of my CWM and custom ROM without ODIN. Any ideas how i could go back to stock rom + stock recovery without USB cable?
ps: Only created this thread as my last resort, after countless hours of browsing and testing. Please help
furthermore im unable to charge my device unless i remove the battery, connect the charger then put the battery back up. [/QUOTE]
Have you tried cleaning the contacts on battery and phone?
MogiMogi said:
Problem 2 : How to return to stock recovery and rom without USB
Click to expand...
Click to collapse
You can try Mobile Odin and also these to resolve connection problems
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
Hello! Long story short I've tried to flash TWRP from Linux with a Windows VM using ODIN and ended up with a "hard-soft" bricked phone. Hard-soft because on the phone is just a brick with a fancy screen that displays only the logo. No recovery, no download mode, no $lsusb recognition by the PC. I'm hoping to be able to boot in download mode using a diy USB JIG that I am willing to create. Only small problem: I can't find any schematic or any guidance for the type-C connector. Does anybody know if the JIG method is still present, if so, where should I connect the resistor to? Also, if you have any suggestions on how I can bring my phone back, I would appreciate the help. Symptoms are as followed: The phone turns on, displays the Samsung logo and from there is an infinite bootloop. The key combos for recovery and download mode are not working. Can't even force reboot the phone. At this point I have opened up the device and removed the battery connector, reconnected the battery after ~12h and still the same problem. Also, there is no charging interface when I plug the phone into the charger. Now it's just a fancy brick. PS: It's the exynos version. Thank you!
EDIT: The volume rocker wasn't working. After securing the motherboard better the I was able to recover from download mode.
I have a note 3 that has always worked flawlessly until today. The phone has a stock ROM, is rooted and has a custom recovery. I am selling the phone so I wanted to go into recovery and clean the phone for sale.
When I tried to go into recovery, the phone looked like it was going in, but after a minute or so, the phone rebooted. The Samsung Galaxy Note 3 logo appears and on the upper left corner it says, "Recovery Booting, Set Warranty Bit: recovery", then it reboots.
I installed Samsung USB drivers, went into download mode to flash the original ROM, but Odin doesn't recognize the phone. There isn't any sim in the phone, but I doubt that makes a difference.
Any help would be great, thanks,
Ian
Tried using different usb cables and usb ports?
Where did you get the custom bootloader?
What model Note 3 ??
audit13 said:
Tried using different usb cables and usb ports?
Where did you get the custom bootloader?
Click to expand...
Click to collapse
Sorry, I meant to say the phone has a custom recovery (TWRP) and it's been on the phone a couple of years. I used the phone up until February when the screen cracked and I got a new digitizer for it. it's been sitting since. Yes, I tried 2 different cables and 2 different USB ports
JJEgan said:
What model Note 3 ??
Click to expand...
Click to collapse
SM-N900W8, the phone was bought from Telus, but has been unlocked.
Ian
If Odin doesn't recognize the phone, there is no way I know of to flash a stock ROM.
Is it possible the USB port is damaged?
audit13 said:
If Odin doesn't recognize the phone, there is no way I know of to flash a stock ROM.
Is it possible the USB port is damaged?
Click to expand...
Click to collapse
I replaced the USB port, just in case. I think it's the mainboard though. The phone will only turn on if I plug the USB cable in, then it goes through the recovery then shutoff routine again. The battery measures 4.3 volts, is this too low? Maybe the battery is too low and when it is plugged in it starts to boot, but shuts down due to a low battery? How can I charge the battery if when I plug the phone in it turns on and wont charge?
Ian
iskolnick said:
I replaced the USB port, just in case. I think it's the mainboard though. The phone will only turn on if I plug the USB cable in, then it goes through the recovery then shutoff routine again. The battery measures 4.3 volts, is this too low? Maybe the battery is too low and when it is plugged in it starts to boot, but shuts down due to a low battery? How can I charge the battery if when I plug the phone in it turns on and wont charge?
Ian
Click to expand...
Click to collapse
The phone will not charge in recovery mode or download mode so it could be a battery problem. The battery voltage may be too low. Do you have access to another battery to try?