Okay, here's the problem. Right now whenever I try to charge my phone Via the wall plug it freezes up and I have to reboot, sometimes it gets stuck in a loop showing the battery level saying Sidekick 4G and going back to battery till I pull the plug and let it set. Or sometimes the phone just locks up completely until a battery pull. What's wrong with this and how could I possibly fix this problem?
Note: It seems to be fine when I plug it into my computer via USB.
what ROM are you running, and when did the problem start? and are you using third-party batteries?
this might not be that much help, but i had this problem when using replacement batteries that i bought off Ebay. the batteries work fine when charged with the external charger that they came with, but when i plug the phone in via charger or USB, the phone immediately shuts down completely, and i have to pull the battery to get it working again.
I am using Generic Ginger 4.1 (though in about it says 3.8 for some reason) For a while now, I can't really pinpoint when. And it's what came with the phone.
ah ok, have you tried a different ROM to see if the issue persists? and/or posted the issue in that ROM's thread?
I haven't gotten my 10 posts in yet, and it happened when i was on Glorious Overdose V2
that definitely does seem to be a software issue. maybe try to ODIN/Heimdall it back to stock, then see if the problem happens again. if it doesnt, then maybe just try going through the steps again to try and flash whatever ROM you want again. if it DOES do it while on the Stock ROM, then you have a major problem that Tmobile will probably replace.
somebody correct me if i'm wrong here.
I'm not sure if tmobile will replace it with another sidekick since we have been officially discontinued :-(
Sent from my SGH-T839 using XDA
They will if its under warranty or if you have insurance...just don't expect a phone different than a sidekick.
Nope, can't return it :/ traded my sister some stuff and cash for it from her friend who bought it from craigs list I think? So...... yeah no warranty possibilities, already found that out when my imei was corrupted. So nothing I can do to fix this then?
Sent from my SGH-T839 using XDA
Related
My device shut itself off last night while charging. I had to do a battery pull to get it to turn back on. Anyone else experience this? My first droid, is this normal? I'm withing the 14 day grace period on my THIRD device.
No it's not normal. It is however a bug that some are experiencing and is usually fixed by doing a factory data reset and making sure you font skip over the Google setup when your device turns on for the first time after doing your reset. There is about 50 threads regarding this issue in this forum so your best bet would be searching for them and see what ers are doing to eleviate the situation. Worst comes to worst just exchange it for another.
Sent from my LG-P999 using XDA App
I think this problem was associated to the first few build batches of the device. After replacing for a new batch I have not seen this problem.
Update: Was told it's an issue with the battery. T-Mobile is overnighting a replacement battery free of charge. Was told if it does it again to replace through warranty as I am tired of taking up my time going to the store to replace.
I dunno. I think it is more drivers. Some people reported the phone turning off while stock during a charging session. They've rooted and moved on to the leaked Gingerbread or CM7 and haven't had any issues.
Me, I haven't had any issues with Stock 2.2 or CM, but the leaked Gingerbread does the same thing as described. It locks up and turns off while charging over night but also will just randomly do it throughout the day.
I don't think it is a hardware issue at all. I think it is some kind of driver/kernel issue.
Some reports state that the phone won't do this while charging over a PC-USB connection but does on a standard wall charger.
One thing to think about is which wall adapter are you using? The included on or another USB charger? I'm using my Nexus One wall plug, which some said could be the issue. I also use a wall plug from a MS Zune I found somewhere.
It could be the charging methods but that doesn't explain how it still does it while just being in my pocket. Now this is ONLY with the leaked Gingerbread/variants (EaglesBlood). Stock 2.2 and CM based roms I have no issues with. When I flashed the leaked build I found it powered off 3 times that night (after 5pm) by just laying around, and powered off in the morning just laying there on a charge.
The phone was at 100% when I turned it on. So maybe it is charging to 100% and turning off to prevent it from "over-charging"? I dunno but it still doesn't explain why it died 3 times without being connected to anything.
I say it is software. Try the latest CM7 #11 and report back. I think there is something fishy with the stock roms.
I am going to wait for the gingerbread update then move on to CM7. I will let you guys know if the new battery helps.
I rooted to cm7 and 2.3.3 update and this still happens... it definitely happens when charging towards full charge...
With that I also think the battery was bad since it happened 90% at charging ...
Im going to get a new one soon and see what happens..
Sucks for me though since I bought this phone from CL
Try CM7. There aren't any reports of the lockups. I'm actually running one of the later KANGs right now, which is a nightly created at a different time of the day.
CM7 #11 is available too. It isn't perfect but between the Theme app, Battery%, and Notification menu toggles... it is easy to deal with.
My problem with it now is the Sound will go out randomly and requires a reboot, but at least I'm not missing calls and notifications because it was off.
I have an non rotted G2x that I bought directly from A Tmobile store April 20th. I had random rebooted and almost daily my phone would lock up over night while charging. I was lucky I woke by myslef or I might have been very late for work. Amway... I was using my Nexus Ones charger, so I swapped it out and used the one that came from LG with the G2x. And I did not get anymore lockups after full charges overnight.
The other thing I did was every morning...I turn my phone off and then back on again.... right after I take it off the charger. And since I started doing that I got no more ghost restarts. Maybe it is coincidental....but it works for me. So far so good...watch as soon as I am done with this post....blame...reboot LOL. Anyway...try what I did. I thought I saw a reference tonight to rebooting the phone daily as a possible fix....in another post somewhere.
WTH my post disappeared.
I was coming back to edit it to say CM has a new #13 nightly:
http://download.cyanogenmod.com/?device=p999
My original post said to try CM7 before doing anything dramatic. CM uses their own Kernels which is what I suspect the problem is with the stock roms.
The official Gingerbread update should come with a new kernel update, as it did with other phones.
I did search, both here and google, and have not come across a similar problem.
I picked up a nexus s 4g recently and unlocked the bootloader using fastboot oem unlock, flashed clockwork mod recovery on, and installed cyanogen 7. I then found out I'm a complete idiot because that rom was made for the GSM phone, and the radio doesn't work.
Tried to use fastboot to load an original rom back on, which failed, so found a windows machine and installed Odin, followed a tutorial on how to flash back to stock, Odin reported a pass, but the phone will no longer turn on.
No amount of taking the battery out, button combos, or charging has changed this.
I had about 70% battery when I tried to flash with Odin, so I'm fairly sure it's not a battery issue.
I also tried to adb devices with the phone hooked up, and nothing was found, so it shouldnt be an unresponsive screen.
Help?
did you make a nand?
I did not. Not sure if it would help, because I can probably download someone elses nand but I don't know how to do anything with it with my phone not powering on
I could be completely wrong about that, not very familiar with nandroid.
You can't get it into download mode?
Correct.
Essentially the phone is dead, it will not respond to anything.
Very similar to the battery not being installed, but I know for certain the battery has a charge.
I just checked the battery, and I retract my previous statements. 560mAh and 3.08 volts. Would that be low to the point of it not taking a charge through the charger?
I have it on a special charger directly on the terminals right now, I will post results once its through.
Read in the fascinate forum that a guy purposely flash a rom from a different device ans used Odin to revert back, also he gave a tip that one should keep trying to use Odin if the first try didn't work. Not sure if this will help never happened to me...
Sent from my Nexus S 4G using XDA App
Fully charged battery did not help
Try what they used to suggest with the epic when it was stubborn. Remove the battery. Plug the usb cable into the phone then into the computer. Try to put it into download mode. If that doesn't work, I can't think of anything else. If you have insurance, maybe they'll swap it when they see it's dead for a refurb. Be nice and play dumb. Tell them something like it froze one time and you pulled the battery and after that it wouldn't turn back on.
I could use my insurance, but its $100 bucks now. Sprint really changed their policy on that.
I also don't really want a refurb phone, when mine was NIB 3 days ago. I realize it's my fault but still.
I'm trying to figure out if this problem is just my phone or an actual issue. I just got this phone 2 days ago from craigslist after being with the evo for almost a year. As soon as I got it, I rooted it n tried flashing ics roms themed and original leaked update. On every rom I flashed, the phone wouldn't recognize the charger or usb or it would tell me its charging but it would take 6 hours to gain 6% more battery? I also tried turning the phone off to charge but that didn't work either. Anyone know anything about this n what I did wrong or didn't do?
Sent from my Nexus S 4G using xda premium
I've had the exact same problem, i bought a NS4g from craigslist that wouldn't charge or turn on without a charger being plugged in. Long story short, i eventually got it back from Samsung with the warranty being voided due to water damage. So i opened it up and found some oxidation resudue and cleaned it off by scrapping it off. Luckily it worked!!. For you it might just be the battery since it actually says 6%, try to replace with another battery or place the battery in the freezer for 5 mins and try it again.
I flashed the unofficial leak rom again n it charges now but it doesn't say its charging on the lock screen or on the battery icon, but in the system info it says its charging? I have never ran into this type of issue before?
Sent from my Nexus S 4G using xda premium
Exact Same Problem
I was given ICS 4.0.4 via OTA update by google... It worked fine for like 2 months then exactly the same problem arises with my Nexus S i9023 (unrooted).
1. It's doesn't indicate on the lock screen that it's charging nor it indicates on the battery icon, however it does tells me that the battery is charging when I check the battery in the settings. This issue exists on both wall chargers and usb cable.
2. It doesn't asks me to mount mass memory of my Nexus S and my windows 7 machine says it cannot recognize the device..
I strongly suspects it's a bug in the ICS...
I would appreciate any help that I can get on this issue... but to be honest I read many threads here and I can't understand half of what people are trying to say, so I request to keep things a bit simple because I know nothing about how to root or flash or doing any other super geeky stuff ...
thanks
Some people have had luck just cleaning the USB port with a dry toothbrush and a can of compressed air. Might just be dirt. Worth a shot.
thanks mate,
Yeah, tried cleaning it with a brush... still no luck..
:crying: any ideas ?
everything was working perfectly and i didn't do anything , just when my first battery ran out , i shut it down and switch second battery then it just doesn't boot up anymore ... even with data cable connect with charger or PC, because usually it will show a charging animation when system isn't booted up ...
and one thing strange is that when i plug in my battery , phone doesn't boot up but it still heat up like i am using it ...
a little help please ...
qtwrk said:
:crying: any ideas ?
everything was working perfectly and i didn't do anything , just when my first battery ran out , i shut it down and switch second battery then it just doesn't boot up anymore ... even with data cable connect with charger or PC, because usually it will show a charging animation when system isn't booted up ...
and one thing strange is that when i plug in my battery , phone doesn't boot up but it still heat up like i am using it ...
a little help please ...
Click to expand...
Click to collapse
the same happen to me week ago! i think its jellybean...
Cascabreu said:
the same happen to me week ago! i think its jellybean...
Click to expand...
Click to collapse
how did you fix it?
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
qtwrk said:
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
Click to expand...
Click to collapse
Same issue with mine. Yesterday, 8/20/12, I broke a sim card connector pin and Nexus S wouldn't recognize sim card after a reboot. Rebooted the device again after the warning message: Sim card not detected/found.
Now Nexus S won't boot. Computers (Windows & OSX) can't recognize it's connected and 5 different charges won't show that the battery is charging. Battery still has a charge as I tested it in another Nexus S. When the battery is in, the device heats up. When connected to a power source, the device heats up.
Used Unbrickable resurrector with no success. UR shows: Device not found, No device detected.
Finally, I was running Jelly Bean from OTA update and not rooted. I noticed that in the past week or two the stock Andoird keyboard would cause force closing of apps or exceed processor threshold of 35% even if there was no program running. Google Now was also sucking the battery after the JB update. Turned that battery drain off on the other Nexus. Also, the Android Media process was taking a drain on the processor. Usually running at 40-50%.
Bought this used from CowBoom and hoping the extended warranty will replace or fix the broken sim card connector and unbrick the phone.
Luckily I have an iPhone 4S and a 2 yr old HTC Desire to turn to.
I've read on another thread, perhaps?, that two other users in the past week or so have had this same problem.
nexus s GT-I9020T Bricked after JellyBean
qtwrk said:
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
Click to expand...
Click to collapse
Same happened to me. The Unbrickable resurrector also didnt detect the phone. so i made the Unbrickable Hardware Mod (httpxx://forum.xda-developers.com/showthread.php?t=1566475) remove the xx from httpxx. now my phone is being detected and the tool is able to load its files. but still the phone is dead, no thing happens and the tool shows no device found after it loads the files. but when i picked GALAXY S from the drop down menu. the tool loads the files and now both the tool and the phone shows download mode with an android shoveling dirt. heimdall now detects the phone but it doesnt work caz its not a GALAXY S. So let us know what happens if u try this mod. cheers
The exact same thing happened to me. Strangely, it's happening with JB roms. And yeah, i told my problem in a very educated way on the ROM topic and they simply deleted the post, how nice.
Anyway, i just sent the phone to the warranty almost three weeks ago, i'm waiting for them to fix it or give me a new one.
djdeepblue said:
The exact same thing happened to me. Strangely, it's happening with JB roms. And yeah, i told my problem in a very educated way on the ROM topic and they simply deleted the post, how nice.
Anyway, i just sent the phone to the warranty almost three weeks ago, i'm waiting for them to fix it or give me a new one.
Click to expand...
Click to collapse
no , i was running 4.0.4 , AOKP M6 , as matter fact , it seems to be a problem of latest BOOTLOADER
dokugan ryu said:
Same happened to me. The Unbrickable resurrector also didnt detect the phone. so i made the Unbrickable Hardware Mod (httpxx://forum.xda-developers.com/showthread.php?t=1566475) remove the xx from httpxx. now my phone is being detected and the tool is able to load its files. but still the phone is dead, no thing happens and the tool shows no device found after it loads the files. but when i picked GALAXY S from the drop down menu. the tool loads the files and now both the tool and the phone shows download mode with an android shoveling dirt. heimdall now detects the phone but it doesnt work caz its not a GALAXY S. So let us know what happens if u try this mod. cheers
Click to expand...
Click to collapse
well ... i don't have these tools to do hardware level of modifications ...
anyway , i just send to repair , i think , the motherborad or something should be replaced ...
i was thinking about buying a new phone such as Galaxy Nexus if my Nexus S can not be repaired or way too expensive to repair...
i had same issue a few days after upgrading to JB JRO03E. i got the main board replaced under warranty. took about 2 and half weeks.
the phone came back with GB installed but OTA'd to ICS then JB JRO03L.
I had the same issue running cm10-0823. Screen froze while sitting idle. Pulled and replaced battery, and phone won't come back.
Looks like cm10/jb is causing some burn-out in circuit board; cpu, memory...?
_android_ said:
I had the same issue running cm10-0823. Screen froze while sitting idle. Pulled and replaced battery, and phone won't come back.
Looks like cm10/jb is causing some burn-out in circuit board; cpu, memory...?
Click to expand...
Click to collapse
as i have heard is that new bootloader messes with hummingbird CPU ...
I have exactly the same problem I flashed Codename Android ROM 3.4.1, done some overclocking (only 1200 MHz) and the device crashed. Well, nothing unusual. But I removed the battery, I think it was just when the device was rebooting - I think display turned on, I noticed some flash when the battery was already removed.
I tried to turn on the device, but it's dead. Display doesn't turn on, UnBrickable Resurrector says device not found.
I can send the phone to the warranty, but it's unlocked. Do you think they will find out it's unlocked? Even if the download mod doesn't work etc?
What should I do?
Well, I happened to end up with the same problem. Installed latest cm 10 nightly, started rebooting my phone. The moment I restarted it from CWM I realised that I forgot to flash some mod in CWM so I pulled the battery to go into recovery. Phone bricked, no input at all. Sent my phone on warranty, I hope they won't mind it had unlocked bootloader and cm10 on it ;P
That's just a bit stupid to be honest, pulling the battery while booting why not just wait?
Sent from my Nexus S
Now I know it's stupid. Do you think they will repair it even though it's cm flashed and unlocked?
i sent mine to repair and they fixed without paying a dime!
Cascabreu, you just made my day Well, I just have to wait now
nexususer1 said:
Now I know it's stupid. Do you think they will repair it even though it's cm flashed and unlocked?
Click to expand...
Click to collapse
The mainboard is fried. No way of knowing previous state of your phone. They will just replace the board.
Sent from my Nexus S using XDA Premium HD app
_android_ said:
The mainboard is fried. No way of knowing previous state of your phone. They will just replace the board.
Click to expand...
Click to collapse
I had the same issue back in August just after I flashed 4.1.1/JRO03E. It just died one day while listening to music. Took about 3 weeks to get the mainboard replaced under warranty. It came back bootloader unlocked and with Gingerbread 2.3.3 installed.
So I have a Stock Non-Rooted year old Galaxy s 4g that just turned off on me one day. I have tried everything to get it turned on. It does not bring up the battery charging screen when plugged in, and it refuses to boot into download mode. I suspect a hard brick, but I don't know what would cause it. Not only did it just turn off, it was at exactly 60% battery life and it shut down when I was trying to email my friend.
Take the battery out of the phone and put it on a flat surface like a kitchen counter. See if you can rock the battery back and forth and see if there is a bulge in the center, it shouldn't rock. Mine did this to me a year after I bought it and replacing the battery solved it.
Sent from my Galaxy Nexus using xda app-developers app
I would jump on amazon.com and buy a battery....you can find them for $5-7.00 all day long there.
You can even buy the battery for the vibrant at that price or lower and they work just fine.
I have 4 vibrant batteries i use with an external charger.
I know that the battery works, because i tried it in my friends galaxy, and his worked fine.
Tried his in yours?
How's your cable? Try a different one. I've got a handful that won't charge my phone, but, will work on my wife's Samsung (and some that will/will not charge my company phone)...
Sent from my SGH-T959V
Yeah, I did try his in mine, and it still wouldn't charge. I did try with another cable, still no results
Power it up and root the darn thing. Then install an ics rom. Hopefully your problem will resolve.
Sent from my SGH-T959V using xda premium
nicky89107 said:
Yeah, I did try his in mine, and it still wouldn't charge. I did try with another cable, still no results
Click to expand...
Click to collapse
And it won't boot up correct?
Yes, and it wont go into recovery or download mode
Man that sucks. Best advice I can give you is to call Samsung. If it's under a year they will warranty it. If it's over a year they may charge you. There a pretty good company when it comes to honoring their warranty so it's worth a shot. Sounds like critical hardware failure to me.