I have an S4 GPE and had a rooted 4.4.2 I9505GUEUCML4 with no issues. In order to flash the 4.4.3 update, I installed TWRP 2.6.0.0 (big mistake - since it saw an empty file system and that's where the problem started) and then replaced it with philz touch 6.15.6 and flashed the zip file. Everything worked fine, but the battery stopped charging. In connecting charger to phone (I tried 3 different chargers with 3 different batteries) lightening bolt appears, LED flashed red - but no charge happens. I tried:
- Multiple clean wipes/fact. resets with a full firmware odin flash, followed by a factory reset (actually tried flashing a couple of variants)
- Went to the lab and had the phone usb checked - no issue
- charged batteries in external chargers - all charged without an issue
The phone is still not charging.
I'd appreciate any and all suggestions.
Thanks!
Cap302 said:
I have an S4 GPE and had a rooted 4.4.2 I9505GUEUCML4 with no issues. In order to flash the 4.4.3 update, I installed TWRP 2.6.0.0 (big mistake - since it saw an empty file system and that's where the problem started) and then replaced it with philz touch 6.15.6 and flashed the zip file. Everything worked fine, but the battery stopped charging. In connecting charger to phone (I tried 3 different chargers with 3 different batteries) lightening bolt appears, LED flashed red - but no charge happens. I tried:
- Multiple clean wipes/fact. resets with a full firmware odin flash, followed by a factory reset (actually tried flashing a couple of variants)
- Went to the lab and had the phone usb checked - no issue
- charged batteries in external chargers - all charged without an issue
The phone is still not charging.
I'd appreciate any and all suggestions.
Thanks!
Click to expand...
Click to collapse
Did you used any OTG devices ? Sometimes they may affect battery charge.
petrusconsult said:
Did you used any OTG devices ? Sometimes they may affect battery charge.
Click to expand...
Click to collapse
No OTG device involved. Thanks
Related
Hello-
My friend is having an issue with his Samsung Galaxy Y phone he purchased a couple of months ago. The device will not charge. I've advised him to perform the following, but with no luck:
1. Verify working outlet
2. Ensure USB port contacts are clear of any interference
3. Verified working charging cable
4. Verified known good replacement battery
5. Reset device to factory settings
I suspect infant mortality and a defective charging port or something hardware related. Should I have him try anything else before proceeding with the RMA process given the device is only a couple of months old?
Thanks for your advice!
Is is not charging. Or is it not showing that it is being charged.??
If its 2nd case then ask him if he is on a custom rom.. If he is then tell him to change it or revert back to stock..
** rooting is new for me,
nd i am a noob to root....**
Thanks for the reply menewtoroot, completely stock and it's not charging at all.
If You WIPE battery stats present you install custom rom, you cant see showing the battery charge...
FIX: replaced with the completly stock ROM
But if you connect to pc not with battery in your phone is still on, I think you must check the connector with amperemeter for electrical technic is the same case with my friend....
Sent from my GT-S5360 using Tapatalk 2
Hello guys
2 1/2 years with my D802 and in october i change rom because i have bootloop problem (Zip "kernel" for CM12 on CM13...) And... Slow charging appears (Actualy: Latest CM 13 Nightly )
Problem:
Not charging when boot in android in 99% of times, and randomly 10-1500mA charging when i have luck
Charging slow phone Off and in TWRP but it's random, sometimes nice charging ( 200mA-1500mA )
No USB connection when Android is on ( No MTP, ADB, Charge, no Windows sound ) (i use ADB wifi) but USB is okey in TWRP ( No adb but MTP ok and charging ok sometimes )
What i tried:
Other AC Power
Other USB Cable
Other Rom ( Newest CM 13 Nightly with System/Dalvik/Cache Wipe )
Other Kernel ( Lambda Infinito Stable and Beta N9 with "Fast charge" like Dorimanx Stock Kernel )
New battery ( 20euro in my a*s lol )
Clean the gnat in the usb port
What i don't try:
Go back to Stock Firmware
Change USB plug
If you have same problem solved, tell me please !
Thanks
I thinks i solved the problem...
I found a gnat in the usb port after cleaning it .-.
Phone charging... Nice solution
Edit: Big luck, the gnat don't was the solution
riwan15 said:
I found a gnat in the usb port after cleaning it .-.
Click to expand...
Click to collapse
Dafuq. Funny experience. How the hell does a gnat fit into this tiny hole. I Germany the gnats are up to 10mm long. I would have to mummify or dry it to decrease size. But nice that your phone is back in business.
Lol, phone at 100%, i disconnect the usb cable, wait for 99% and... Not charging again... Now i'm at 37% and crying x)
The solution don't was the gnat x) Only big luck lol
Maybe solution:
In TWRP (phone at 0% and plugged) the battery don't appear in the top (normal) but i disabled the MTP and the battery show up and charging ! I retry when the phone is a 0% and confirm this fix !
(Sorry if i alone or something but a pass 1week to search for fix and there is no fix in google, only "hardware" problem but i don't thinks the hardware problem exist if the phone don't touch water or has fallen)
I hope this thread is gonna help somebody
Maybe change TWRP version can fix the problem ? I'm gonna try it after looking if disable the MTP is a fix
Edit: TWRP from 2.8.6.1 to 3.0.2-1 (Blastagator's TWRP) fixed half of the problem, now 1/2 charging phone off and always in recovery, left phone with android on and the problem is fix :3
Problem "fixed"
The only way for charging is to plug when the phone is booting ( on lg screen, before recovery or android ) In recovery the charging is safe, in android boot i need sometimes to plug/unplug after boot to start charging
The problem is now not really one for me, just a gesture to do ( Phone working, new battery = 2days phone on !! I'm happy like 2years ago)
For USB Data, no fix found, but Airdroid and ADB Wi-fi are in the party
I hope this thread can help
Info:
D802 - TWRP 3.0.2-1 - CM13 Nightly Dec 03 2016 - No kernel - Xposed V87
Edit: flashed most recent stock firmware (Android 5.0 based, dated back in early 2017) and charging/file transfer is possible again. So I'd speculate that it comes down to incompatible kernel from the later version of ROM.
I would still love to have Lineage OS 16 on this though, so any help/pointer is still appreciated.
--------- Original Situation Below ---------
I recently took a very old Galaxy Note 3 (N9002), and successfully flashed TWRP (N9005/HLTE) build, and the equivalent Lineage OS 16 build (official nightly).
I was very pleased to see that the 6-yr old device runs the Android 9 based ROM very smoothly, and had all the fun getting re-acquainted with Android in general, until the moment I plugged in the charging cable and Samsung official adapter -- nothing.
I reconfirmed this by turning on Developer Mode - ADB debugging, and connected to the computer that I used to flash in the recovery earlier, with 3 different working USB cables. No charging, no file transfer, no devices attached when doing
Code:
adb devices
.
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around camera) gets mildly heated.
Turned the phone back on in Download Mode, and confirmed that it's still detected by Odin3 (and even flashed an HLTECHN TWRP and back to HLTE one successfully). Both prove that the cable, the charging, and the transfer mechanism should work.
This becomes pretty inconvenient in terms of day-to-day use, so any help and suggestion would be greatly appreciated.
Thanks.
Exactly the same issue
woozyking said:
Edit: flashed most recent stock firmware (Android 5.0 based, dated back in early 2017) and charging/file transfer is possible again. So I'd speculate that it comes down to incompatible kernel from the later version of ROM.
I would still love to have Lineage OS 16 on this though, so any help/pointer is still appreciated.
--------- Original Situation Below ---------
I recently took a very old Galaxy Note 3 (N9002), and successfully flashed TWRP (N9005/HLTE) build, and the equivalent Lineage OS 16 build (official nightly).
I was very pleased to see that the 6-yr old device runs the Android 9 based ROM very smoothly, and had all the fun getting re-acquainted with Android in general, until the moment I plugged in the charging cable and Samsung official adapter -- nothing.
I reconfirmed this by turning on Developer Mode - ADB debugging, and connected to the computer that I used to flash in the recovery earlier, with 3 different working USB cables. No charging, no file transfer, no devices attached when doing
Code:
adb devices
.
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around camera) gets mildly heated.
Turned the phone back on in Download Mode, and confirmed that it's still detected by Odin3 (and even flashed an HLTECHN TWRP and back to HLTE one successfully). Both prove that the cable, the charging, and the transfer mechanism should work.
This becomes pretty inconvenient in terms of day-to-day use, so any help and suggestion would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
I'm facing exactly the same issue after flashing with the same Lineage OS 16 on the mobile model Galaxy Note sm-n9002 HLTECHN
No charging, no file transfer, no devices attached when doing
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around the camera) gets mildly heated.
Will greatly appreciate if someone can help
Thanks
valteg said:
I'm facing exactly the same issue after flashing with the same Lineage OS 16 on the mobile model Galaxy Note sm-n9002 HLTECHN
No charging, no file transfer, no devices attached when doing
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around the camera) gets mildly heated.
Will greatly appreciate if someone can help
Thanks
Click to expand...
Click to collapse
here's the script that can fix the usb problem for n9002 on oreo or pie rom: just flash it without wipe the cache; but unfortunatly it doesn‘t work on android 10 and im looking for solution
https://drive.google.com/open?id=1G1...K7y1HwQbd4LN20
sm-n9002
pigliang said:
here's the script that can fix the usb problem for n9002 on oreo or pie rom: just flash it without wipe the cache; but unfortunatly it doesn‘t work on android 10 and im looking for solution
Thanks, Pigliang for the quick help
But I can't open the link, I keep receiving the following ERROR message from Google.
"404. That’s an error.
The requested URL was not found on this server. That’s all we know."
Please can you check and send the script again
Thanks
Click to expand...
Click to collapse
pigliang said:
here's the script that can fix the usb problem for n9002 on oreo or pie rom: just flash it without wipe the cache; but unfortunatly it doesn‘t work on android 10 and im looking for solution
https://drive.google.com/open?id=1G1...K7y1HwQbd4LN20
Click to expand...
Click to collapse
The link is not working, can you uplode it again?
Recently I've been to coolapk and find a one seemed to be working right (not tested yet):
Google Drive
Hi Everyone!
I have an XT1641, which previously had a charging pin problem.
At the Last week, it started to reboot only many times until it suddenly shut down and didn't light anymore.
When plugged into a charger, the white light flickered.
Since I thought it was still a charging pin problem, make the change.
The cellphone works seemed to restart, but it continues with the same problem.
Sometimes the bootloader works ( Power + Vol -) and sometimes No.
I already tried everything. Install ROM STOCK, I made it blankflash (none worked "waiting for firehose to get ready" ).
It seems to be a firmware or similar problem, but I can't find the solution.
Previously, you never had a custom ROM installed, or root, or anything; at this cellphone
Thank you!
PD: SORRY FOR MY ENGLISH
How did you try for installing stock rom? Check usb drivers installed in your pc
przvlj said:
How did you try for installing stock rom? Check usb drivers installed in your pc
Click to expand...
Click to collapse
By Fast Boot (when it worked).
Now, after a week of turning it off, the cell phone turned on again without problems.
Hey all! First of all, I hope this is the right board.
A while ago I got a Samsung Galaxy Tab A (2016), model SM-T858, the one with LTE, and yesterday I tried to charge it, but it didn't want to charge, at all, it looked like the charger was not working, so I left it alone and went to do other stuff, when I came back, the battery was at 30%, the screen was totally black (No battery indicator), and it let me turn it on. But it still said that it wasn't charging, tried connecting it to a few different PCs, nothing, recovery, nothing, it wasn't being detected, BUT it gets detected in ODIN/Download mode. Anyway, I tried using a "Adaptive fast charging" Samsung AC plug (Supposedly the one that came with the tablet), and it wouldn't charge.
After that I just left it like that, and went to Root it, I first installed TWRP from the official website, it worked. I rebooted into recovery, still not working, but in TWRP's file manager I can see a "charger" file in the root of the nand, not in /system/, not in /etc/, just laying there in the root. It seems to be a binary file, could this be the cause the tablet is not charging/being detected by computers.
Thanks. Th3F4ult.
Hello @th3f4ult
Welcome to XDA. If you have not already, please read the Forum Rules linked in my signature, especially:
Use our search function to find the best forum for your device.
Click to expand...
Click to collapse
As a courtesy, we will move this post to the correct section.
th3f4ult said:
Spoiler: Post
Hey all! First of all, I hope this is the right board.
A while ago I got a Samsung Galaxy Tab A (2016), model SM-T858, the one with LTE, and yesterday I tried to charge it, but it didn't want to charge, at all, it looked like the charger was not working, so I left it alone and went to do other stuff, when I came back, the battery was at 30%, the screen was totally black (No battery indicator), and it let me turn it on. But it still said that it wasn't charging, tried connecting it to a few different PCs, nothing, recovery, nothing, it wasn't being detected, BUT it gets detected in ODIN/Download mode. Anyway, I tried using a "Adaptive fast charging" Samsung AC plug (Supposedly the one that came with the tablet), and it wouldn't charge.
After that I just left it like that, and went to Root it, I first installed TWRP from the official website, it worked. I rebooted into recovery, still not working, but in TWRP's file manager I can see a "charger" file in the root of the nand, not in /system/, not in /etc/, just laying there in the root. It seems to be a binary file, could this be the cause the tablet is not charging/being detected by computers.
Thanks. Th3F4ult.
Click to expand...
Click to collapse
Flash the tablet with 4-file firmware. You will read the firmware version thanks to twrp, in the /system/build.prop file, after mounting the system partition.
ze7zez said:
Flash the tablet with 4-file firmware. You will read the firmware version thanks to twrp, in the /system/build.prop file, after mounting the system partition.
Click to expand...
Click to collapse
I've already flashed it with the stock rom, the 4 files, BL, AP, CP and CSC (Tried both, CSC and HOME_CSC), tried the roms from a few different carrier.
Clean/blow the USB socket and try on other usb cables.