Related
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
First of all - yes, I know that this problem is (allegedly) a common one, but mine differs from every case I found on XDA (and on other forums). I have tried every fix I found related to similar issues, to no effect.
I am S-OFF, rooted, and have the latest JellyTime release installed (R9). I am on JellyTime since R7, and no issues were observed whatsoever until now. I use EXT4 recovery (the latest stable build), and have installed no kernels or radios. Phone was fully wiped before flashing R9.
For the past week or so, my Desire is having troubles charging. It would sometimes show as charging, and turn the red LED on, but in fact the battery is discharging - and much more quickly than when plugged off the charger. Also, the LED is often wrong about it's status. It would turn green when on less than 100%, once even at about 80% - pretty far from 100%, if you ask me. I tried to calibrate the battery three times (using battery calibrator), and the problem came back a day after the calibration (at most).
Yesterday, as I went to sleep, I left my phone connected to the charger, and the same thing happened. When I woke up, the battery was depleted (about 4% when I woke it from hibernation). I changed the cable and the charger and when to class, returning to the same situation.
Later that day, I bought a Sandisk Ultra 64GB MicroSDXC memory card. I partitioned it using GParted, creating both EXT4 and SWAP partitions next to the main FAT32 one. I transferred a few apps to the EXT4 partition using AppMgrIII (only those without the little grey warning sign).
Everything seemed to be in order, but a few hours later my screen went black (it was still on, though), and nothing I did fixed the situation. Naturally, I removed and inserted my battery. Since then, my device is completely dead. I won't turn on, and won't charge. A list of thing I tried:
1. Just connecting to charger: no effect, even after a few hours. No LED light. Same when changing cable/charger/connecting to PC.
2. Connecting to charger when battery is removed: No LED light, unless I play with the cable - then there's a flash of red LED every now and then. The LED flashes only once every time - when I stop fidgeting with the cable at the angle in which the light flashed, nothing else happens until I resume the fidgeting.
3. Pressing the power button - I tried that for 10 seconds and 30 second, both had no effect.
4. Covering the middle bars on the battery, and leaving the phone connected to charger (then removing tape and turning on) - no effect.
5. Putting the battery in the fridge for 10 minutes and trying again - no effect.
6. Charging the battery outside device, with a cut-down USB-MicroUSB cable (proven working in the past, BTW).
As you can see, I searched for solutions quite a lot - and even though it seems like the same problem every one, it is different in that the LED is not working on any condition. Anyway, no solution I found fix the problem.
Does anyone have any idea what the hell is going on with my phone?
Not a fix but a roundabout solution would be to buy a second battery and battery charger, then you wouldnt need to charge the phone at all!
Check out this item I found on eBay: http://pages.ebay.com/link/?nav=item.view&id=400471194202
Edit: I get the impression it may be the charging port on the phone that could be to blame
Not a charge level issue
tonylee000 said:
Not a fix but a roundabout solution would be to buy a second battery and battery charger, then you wouldnt need to charge the phone at all!
Click to expand...
Click to collapse
My battery was at least 60% charged when the phone died. Besides, I charged it outside the phone earlier, and saw no change at all...
Do you have access to another battery you could use to test with? Could be the battery thats died
tonylee000 said:
Do you have access to another battery you could use to test with? Could be the battery thats died
Click to expand...
Click to collapse
No, I don't have a second battery. Are there popular smartphones whose batteries are compatible with the Desire HD? I'm at school, shouldn't be too hard to find another smartphone...
ClaymanTE said:
No, I don't have a second battery. Are there popular smartphones whose batteries are compatible with the Desire HD? I'm at school, shouldn't be too hard to find another smartphone...
Click to expand...
Click to collapse
Im not aware of any other phone that uses the same type of battery as the dhd unfortunatly. Good for them though the dhd battery is pretty damn poor. Just to buy a battery off ebay can be 99p free delivery so not a big cost but there *might* be someone with a dhd at school you could askto help, it was a flagship phone once upon a time afterall
tonylee000 said:
Im not aware of any other phone that uses the same type of battery as the dhd unfortunatly. Good for them though the dhd battery is pretty damn poor. Just to buy a battery off ebay can be 99p free delivery so not a big cost but there *might* be someone with a dhd at school you could askto help, it was a flagship phone once upon a time afterall
Click to expand...
Click to collapse
OK, but I really don't think this is the problem - for example, what I understood from other threads is that when connected to charger, with battery removed, my DHD's LED is supposed to flash in green and red. Like I mentioned above, that is not what happens with my phone. Do you have another idea?
ClaymanTE said:
OK, but I really don't think this is the problem - for example, what I understood from other threads is that when connected to charger, with battery removed, my DHD's LED is supposed to flash in green and red. Like I mentioned above, that is not what happens with my phone. Do you have another idea?
Click to expand...
Click to collapse
I dont have me dhd with me to test, but I have connected it without a battery to see if it would power on, im sure it didnt flash green and red, it either light up red or didnt light at all
---------- Post added at 09:54 PM ---------- Previous post was at 09:51 PM ----------
From what I gather, either the phone (the phone itself, or just the usb port), the battery or the charger is at fault and you've got to narrow that down. That will be loads easier if you find someone with a dhd that could help you.
tonylee000 said:
I dont have me dhd with me to test, but I have connected it without a battery to see if it would power on, im sure it didnt flash green and red, it either light up red or didnt light at all
---------- Post added at 09:54 PM ---------- Previous post was at 09:51 PM ----------
From what I gather, either the phone (the phone itself, or just the usb port), the battery or the charger is at fault and you've got to narrow that down. That will be loads easier if you find someone with a dhd that could help you.
Click to expand...
Click to collapse
Didn't found anyone. Problem. Is there another way to check the battery, outside the phone?
ClaymanTE said:
Didn't found anyone. Problem. Is there another way to check the battery, outside the phone?
Click to expand...
Click to collapse
Without another phone, or desktop battery charger cradle, your left with a voltmeter option, but you need to be able to charge it first lol (I really dont recommend cutting a usb cable and just using that, that could cause more problems! - id really want you to get the cradle for £4 including battery, then you have a new battery that you can assume works properly, a charging cradle that again you can assume work properly so only leave the phone at fault if it doesnt work. Potentially a waste of money if the phones dead but also potentially the best £4 you ever spent! Nb if you do opt for the cradle it maybe woth looking for an option that dispatched from your own country for speed in the post but that will increase the cost by a little bit)
ClaymanTE said:
OK, but I really don't think this is the problem - for example, what I understood from other threads is that when connected to charger, with battery removed, my DHD's LED is supposed to flash in green and red. Like I mentioned above, that is not what happens with my phone. Do you have another idea?
Click to expand...
Click to collapse
A dhd, plugged in to the mains, without a battery inserted but with the battery cover fitted in place - the phone wont boot, no leds are lit up - nothing, no life whatsoever
tonylee000 said:
A dhd, plugged in to the mains, without a battery inserted but with the battery cover fitted in place - the phone wont boot, no leds are lit up - nothing, no life whatsoever
Click to expand...
Click to collapse
However, when I connect it the LED does lights up - just not in the way I though it's supposed to. It blinks red once every time I connect it, like it's protesting against it.
ClaymanTE said:
However, when I connect it the LED does lights up - just not in the way I though it's supposed to. It blinks red once every time I connect it, like it's protesting against it.
Click to expand...
Click to collapse
With a battery inserted? - lke it attempt to sta charging but stops because of some sort of error maybe. A new battery maybe in order :/
tonylee000 said:
With a battery inserted? - lke it attempt to sta charging but stops because of some sort of error maybe. A new battery maybe in order :/
Click to expand...
Click to collapse
no, when the battery is inserted the LED won't blink. When it's removed, it blinks red once when I connect the phone.
ClaymanTE said:
no, when the battery is inserted the LED won't blink. When it's removed, it blinks red once when I connect the phone.
Click to expand...
Click to collapse
Well then get a new battery, you can find people with HTC Sensations and EVO 3Ds, the batterys have the same widths, and they are proven to be working in the desire HD, with the battery door off that is.
Sent from my Desire HD using Tapatalk 2
I bought a note 10.1 2014 Ed a couple of weeks ago on eBay. Not refurb and sealed in the box.
Devastated to find tonight, after completely discharged and shut down, that it seemed not to charge at all.
It becomes stuck on either the battery symbol, where nothing happens, arrow doesn't spin and no animation, or goes to the device model name. All the while the brightness flickers.
Have tried various chargers, I've taken all the cards out but nothing is working
I think it may be a loose connection with the battery (but open to other theories).
If anyone has had this problem, how have you fixed it? Is it worth disassembling and trying to fix it myself (as I'm sure you can tell I don't have a lot of knowledge about this)? Being an eBay purchase is it still under warranty with Samsung? How much would a fix be if it was a loose battery?
Thanks in advance
shining08 said:
I bought a note 10.1 2014 Ed a couple of weeks ago on eBay. Not refurb and sealed in the box.
Devastated to find tonight, after completely discharged and shut down, that it seemed not to charge at all.
It becomes stuck on either the battery symbol, where nothing happens, arrow doesn't spin and no animation, or goes to the device model name. All the while the brightness flickers.
Have tried various chargers, I've taken all the cards out but nothing is working
I think it may be a loose connection with the battery (but open to other theories).
If anyone has had this problem, how have you fixed it? Is it worth disassembling and trying to fix it myself (as I'm sure you can tell I don't have a lot of knowledge about this)? Being an eBay purchase is it still under warranty with Samsung? How much would a fix be if it was a loose battery?
Thanks in advance
Click to expand...
Click to collapse
As far as I am aware items from ebay are not covered under warrenty.
Even with the screen off and nothing happening, leave it on charge for few hours then unplug and try to put it on.
Also have a look into the charger port of the tablet at the bottom to make sure nothing looks bent or out of the ordinary.
Sent from Galaxy Note 10.1 2014 Edition via Tapatalk.
samsung sm-p605 dead not starting
havig the same error mentioned above.. got the device new from amazon, shipped to chile where i live.. recieved it and tried switching on and didnt switch on.. tried connecting wall charger for couple of hours no progress not even battery symbol coming up.. tried usb to laptop battery image comes up with no animation.. and screen flickers... boots in odin mode... when tried booting in recovery mode stucks in screen where the model name appears...
plz help since i have 0 hrs of usage completely new.. chile samsung doesn't accept becos its purchased in usa.. any email of samsung will also help
shame i always liked samsung over apple.. and bought a product with no support.. apple atleast accepts product bought anywhere in the world and even replaced battery for my frnds iphone 5s when in warranty...
I have not had this issue with my Note, but my Nook did the same thing once. I disconnected the battery for a few minutes and everything reset. No idea if this will help, or if you are adventurous enough to try it.
Here are some pictures of the Note tear down. http://forum.xda-developers.com/showthread.php?p=49595697
samsung sm-p605 dead not starting, screen flickers
i am going to try removing the battery as u said.. lets see..
anyother ideas plz let me know..
but shld i do this quite often?? is this an known error of note???.. do we have this problem when complety drained????
samsung sm-p605 dead not starting, screen flickers
no luck.. i removed the battery from the board, then plugged in back after couple of minutes..
still in same state..
the screen flickers a lot.. is that normal when the note is completely drained..???
It is very bad for the battery to go completely down. I don't let it happen on my devices, so I cannot say if the flicker is normal.
My experience with the Nook was actually a friend's device. He had let it run down, and it was not charging. He left it on the charger for a few days, and it was still not showing a charge. He gave it to me to check out. I disconnected and reconnected the battery. It was probably half an hour or so, because I was interrupted. When I reconnected the battery, the Nook popped on and reported a full battery. Apparently it was charging but not registering anything, and the disconnect allowed things to reset.
If you do not any other ideas, I would suggest leaving on the charger overnight (or longer) and trying the disconnect again. Maybe leave it disconnected longer too.
shining08 said:
I bought a note 10.1 2014 Ed a couple of weeks ago on eBay. Not refurb and sealed in the box.
Devastated to find tonight, after completely discharged and shut down, that it seemed not to charge at all.
It becomes stuck on either the battery symbol, where nothing happens, arrow doesn't spin and no animation, or goes to the device model name. All the while the brightness flickers.
Have tried various chargers, I've taken all the cards out but nothing is working
I think it may be a loose connection with the battery (but open to other theories).
If anyone has had this problem, how have you fixed it? Is it worth disassembling and trying to fix it myself (as I'm sure you can tell I don't have a lot of knowledge about this)? Being an eBay purchase is it still under warranty with Samsung? How much would a fix be if it was a loose battery?
Thanks in advance
Click to expand...
Click to collapse
I have the same exact issue right now! But mine is a refurbished unit. I tried the battery unplug, tried leaving it charging overnight, letting it discharge, flashing new roms, new kernels, etc. Nothing. THe only thing that did work a little bit was changing the kernel. Other than that, even flashing stock ODIN roms wasn't working.
When you charge yours, does it charge up to 75% but won't go any further? And does it take an extremely long time to get there? Because mine does. Reading about other devices that have the same issue, it seems to be the battery. But the other devices were phones. This is a tablet. The battery costs $65 :/
shining08 said:
I bought a note 10.1 2014 Ed a couple of weeks ago on eBay. Not refurb and sealed in the box.
Devastated to find tonight, after completely discharged and shut down, that it seemed not to charge at all.
It becomes stuck on either the battery symbol, where nothing happens, arrow doesn't spin and no animation, or goes to the device model name. All the while the brightness flickers.
Have tried various chargers, I've taken all the cards out but nothing is working
I think it may be a loose connection with the battery (but open to other theories).
If anyone has had this problem, how have you fixed it? Is it worth disassembling and trying to fix it myself (as I'm sure you can tell I don't have a lot of knowledge about this)? Being an eBay purchase is it still under warranty with Samsung? How much would a fix be if it was a loose battery?
Thanks in advance
Click to expand...
Click to collapse
I know this is a very late reply and you have probably solved your problem by now, but for future readers with this problem:
I currently have the exact same problem, and just found out what it was. Either my charging cable (official Samsung cable) is faulty. I plugged it into another microUSB cable, and it is now charging again. No more battery symbol that doesn't have the spinning animation or flickering, and now it turns on.
StandardLeopard said:
I know this is a very late reply and you have probably solved your problem by now, but for future readers with this problem:
I currently have the exact same problem, and just found out what it was. Either my charging cable (official Samsung cable) is faulty. I plugged it into another microUSB cable, and it is now charging again. No more battery symbol that doesn't have the spinning animation or flickering, and now it turns on.
Click to expand...
Click to collapse
Thanks for this information. Exactly this was the issue. Great!
Charging works and screen stops flickering with Samsung charger if you let it charge in Recovery mode. Mine is still charging as of now, so I don't have any news further yet, but it went from 0% -> 3% after around 30min.
Other than that, I only managed to get charging working with a Motorola's turbo charger.
Okay, gonna try and explain this as best I can, bear with me.
2.5 years ago or something I got a Gnex from Verizon, brand new. The phone would act like a ghost was using it, like someone was interacting with the touchscreen. It'd randomly call contacts, send texts (random letters/numbers), all kinds of weird stuff. Video of it on day 1 HERE doing this. Took it into Verizon, got a new replacement. Never had the problem again. 2 or so years go by, not a single problem, unlocked, flash, all that, never had the problem again.
About a month ago, I upgraded to a Moto X and passed this phone on to a family member. At the time was running the latest stable Cyanogenmod ROM, the last for JB. 10.2 maybe? Anyway, that's what ROM was on it, again, no problems. Factory reset the phone to wipe my stuff, left it rooted and unlocked. I gave them the phone, battery, extended battery, and a few cases as well, no charger cause I know they'd twist up and destroy the factory cable. Setting the phone up for them battery starts going low, used their charger. Cable had shorts and crap, scavenged around looking for good charger. Get phone set up for them, and I'm done, handed off.
A day later, they're complaining that the phone is going crazy, like a ghost is using it, and it's randomly calling people, sending texts, opening menus, not charging, etc. Sounds like EXACT same issue I had with my very first Gnex that I exchanged. Figured that was really strange, maybe it was the software. Factory reset to latest factory image 4.2.2, lock BL back up, completely bone stock. Re-setup phone and all that jazz. Phone's acting fine. Decided this time that'd I'd let them have the original stock charger, thinking maybe that'd help with the charging issues too. All seems well....
However, during the reset and all, and after re-setting up the phone, battery is low.... plug it in with a known good charger of mine, but not stock original, and all the sudden the phone's freaking out again. Turn screen off, turns itself back on. Dialing people, opening apps on its own, etc. Figure maybe this Gnex just won't take any charger except it's original. Pull battery, reboot, phone's fine, fine for 10+ minutes. Plug in OEM charger this time, wait a few seconds, unplug, phone goes crazy.
Also interesting, they brought another charger of theirs with a little red LED on, plug it into wall, red LED comes on. Interestingly, if the charger is unplugged from wall with red LED off and I plug it into the phone.... the red LED on the wall charger turns on... that's not right. So.... here's where I'm at now. If I pull battery, reboot, and never attach a charger, the phone acts perfectly fine. The instant I plug in ANY charger, it'll start going wacko and continue to until I pull battery and reboot. At first I thought this was a charger issue, but now... I'm thinking it's battery related. This little experiment of getting the phone to go crazy after plugging in a charger applies to both the OEM and extended battery, regardless of what charger I use.
When I owned the phone, I almost exclusively used the OEM charger, occasionally another charger I had that I know works fine. Gave Gnex to family member WITHOUT a charger, so they were forced to use who know what condition phone charger. I'm wondering if maybe some rogue jacked up phone charger with shorts in it and crap somehow killed the extended battery. Then, they switched to the OEM battery, and again, unknowingly killed that battery too with the same crap charger. So maybe buying a new battery would fix the issue and only using the OEM charger from now on or the other one that was mine that I know works? Or maybe the phone is just broken now? It just doesn't seem right that plugging a phone into the micro-USB should turn ON the red LED on the charger when it's not plugged into the wall, like the power is coming out of phone and going into the LED...
I just refuse to believe that on the exact same day and within hours of me upgrading to a Moto X and passing on my Gnex that had worked perfectly for 2 years in my possession somehow just happens to "break" or "go bad" on its own. Thought it was software glitch/bug in CM, no. Thought it was incompatible charger, no. Maybe the batteries are bad? Maybe the phone's circuitry got jacked up too? Just seems weird that, as far as I can tell, pulling the battery and rebooting fixes it for good until the battery dies. Within 30 seconds of connecting a charger, the phone goes bonkers.
Any ideas? Feel bad, family member probably thinks I dumped a bad phone on them!
Thanks!
What kind of sorcery was that? I honestly don't know what to say about this other than bad timing? I highly doubt a ghost is possessing the phone.
I know a ghost isn't possessing the phone, I just, that's how I best described it when it was going wacko by itself. Plus, interesting topic title, maybe get a few more people to read it and maybe offer some advice or info or something :laugh:
However, I do have a ghost in my house, or a spirit or something. I've seen him, sitting on my couch before. He died in a fire, smoke inhalation, no smoke alarms in the house. House was sold, completely rebuilt, and I am first to live in it since then. Crazy story for a different forum lol
From what I can see, it's just that the screen isn't working properly because of leaked currents from the battery or the charger... Just get the whole screen replaced (it's hard to only replace the glass layer) and should be fine.
Sent from Google Nexus 4 @ CM11
Leaking currents, had it happen to me before from a bad charger. I doubt it's the battery, try an outlet in a different house, they may have bad power.
Sent from my Galaxy Nexus using Tapatalk
So this "leaking currents" problem, it's a problem with the battery? A problem with the phone, in particular, the screen? It definitely sounds like a rogue bad charger could have done this based on the feedback so far. The "damage" or whatever happened at their house. Just the other night, they brought the chargers and phone and stuff to my house, a different house, problem persisted. So I'm not thinking it's a dirty power issue or anything.
...and so you should have the screen replaced. I've had Motorola and HTC phones with issues responding to touches when charging, and replacing the screen largely eased the problem (although I still ended up getting a new charger because I don't want it to also damage the newly replaced screen).
Sent from Google Nexus 4 @ CM11
Op may also want to consider relocating... ghost home and ghost phone, that's too much!
LOL
Mike7143 said:
So this "leaking currents" problem, it's a problem with the battery? A problem with the phone, in particular, the screen? It definitely sounds like a rogue bad charger could have done this based on the feedback so far. The "damage" or whatever happened at their house. Just the other night, they brought the chargers and phone and stuff to my house, a different house, problem persisted. So I'm not thinking it's a dirty power issue or anything.
Click to expand...
Click to collapse
Could be the battery, could be the USB cables or chargers, could be the USB port on the device, could be the screen. The fact that it only happens when plugged in but with more than one charger and battery makes me suspect the USB port on the device. From my understanding you can buy a replacement. A temporary fix would be to use a charger that charges the battery outside of the phone.
Sent from my Galaxy Nexus using Tapatalk
No ghost... i think
I think its because the charger you use....
I had the same problem, but not with gnx... before gnx I used galaxy i5801...
when I put my mobile in charge, my mobile did some crazy things, like operating itself,...I figured out that the charger I used is not the one I shouldn't use.
every mobile has a charging limits, like voltage restriction..
little difference in voltage could make big difference.
so I changed the charger. problem solved for me.
other than charger.. there are some things can do this, I don't know about all.
I doubt it may caused by your digitizer...maybe is has too much sensitivity, caused by water, dust, pressure, etc....
digitizer and display are not the same.
I faced this one too ( galaxy i5801) before charging problem, but not with gnx.
A digitizer is the part of a touch screen that senses your touch and "digitizes" your gestures into impulses that the phone can understand as commands.
if it continues my last suggestion.... call the priest
Well, I borrowed an OEM standard and extended battery from a friend, neither fixed the problem. My friend did say that similar to my first Gnex, when he first got his, it did the same exact thing, but after a while it stopped and it hasn't done it ever since. I also narrowed it down, or, widened the issue, in that it's not just AC chargers, the exact same stuff happens with a brand new 12V car charger.
Dirty power on the fifth rail of a USB wire. Its either the charger not supplying enough power or a damaged cable.
Sent from my Galaxy Nexus using Tapatalk
My vote is on the screen, due to the digitiser. Replacing the touchscreen could help solve the problem. I was in your family's position when I got a used Motorola Cliq from a friend and the battery was all good, no leaks. Ghosts just started touching it everywhere like a crazed groupie when it went into my possession. No explanation as to why it happened and I didn't look into it that much but replacing the screen is the most likely solution.
Hey guys,
first of - sorry if this is oftopic.
I notice heavy charging issues on my g4 intl. The phone just won't charge probably.
I'm running on the latest cyanogenmod nightly, everything else works fine.
Cyanogen says "slow charging" even when I plug in the original cable, or a quick charge wallplug. With all micro USB cables everything is fine for a week or two, but after that everything repeats again.
It seems like the phone cuts down the input power to 300 milli amps or so, while "charging" the battery percentage is going down sometimes, too.
When the phone is off and plugged in, the charging is slow too.
But sometimes everything is fine for a charge or two.
Does anyone have the same issue or have a solution?
Greetings from germany
Okay I found some guys talking about this here, but is there any final solution for this?
radrian said:
Okay I found some guys talking about this here, but is there any final solution for this?
Click to expand...
Click to collapse
It happens to me too, stock ROM, cm13, aosp, no difference.
I have tried changing USB cable (only cable) and device begin charging normally again.
I don't think it's something software related..
But if you have already tried with another charger and problem is still there..
I'm really frustrated. I don't know what is happening to my g4, since 2 month's I noticed heavy red screen ghosting, too. The phone was already repaired once from lg, there the problem was that it won't boot up anymore.. Next time I won't buy lg..
radrian said:
I'm really frustrated. I don't know what is happening to my g4, since 2 month's I noticed heavy red screen ghosting, too. The phone was already repaired once from lg, there the problem was that it won't boot up anymore.. Next time I won't buy lg..
Click to expand...
Click to collapse
I got problems with display too..
Both lateral sides are brighter than the rest of the screen.
Especially with dark images it is absolutely horrible.
Will never ever buy LG anymore.
same problem here with the ghosting and the super slow charge some times battery goes down even while plugged to original charger, had a G2 before this, love the phone was almost flawless, this one I had it for almost a year now, piece of **** full of problems, now after the lates OTA the unlocking is retardedly slow, I double tap for unlocking the screen wakes up but dimmed and unresponsive and after a second it fully wakes up, I'm so frustrated with this piece of ****, the only good thing is the camera. Btw regarding the slow charging problem, I tried with different batteries and chargers and same results (I'm fully stock, no root no nothing)
Sent from my LG-H815 using XDA-Developers mobile app
my problem is that sometimes it just doesn't charge at all the led blinks and i wake up for 0%