Related
Alright, so i sat down and did my first ROM flash (the clean update based off the DI01), then immediately downloaded ROM manager, and flashed the voodoo v0.2 with stock clock and voltage. Now every time I plug in the USB cable, I get the "battery is not connected" error. I have tried:
turning off phone, unplugging cable, pulling batt. then turning on, then plugging in cable
unplugging cable, pulling batt. while on, putting batt. in, turning on, then plugging in cable
... and every other possible configuration. I have left the battery out for 10 minutes now, and still no luck when I put it in.
suggestions?
EDIT:
waited a while longer, and it randomly worked. mods, feel welcome to delete this thread
It's been known to be related to phone being too hot.
hey..
That's what exactly what happened to me, so i actually flashed back to the stock rom
through the odin and wipe everything and started all over man..
I don't know..
Something is gotta be wrong with Voodoo kernel..
But in this way, i fixed it..
So i think im gonna stick with the lagfix for now..
and i guess when Dev comes out a different fixed verison, i'll take it again..
Good luck man
My phone was running at a fine temp to the touch, and I think the Battstat widget said it was at 30c, which should be fine. I think today i will flash over to a 1.1 or 1.2 Ghz voodoo kernel
Aidman...try this unplug the usb cord and shutdown pull the battery , then replace battery fire it up and charge....
post back results....
Voodoo busted my phone too. I could get the battery disconnected message to go away if I took the battery out and let it sit for a few minutes, but then it would come back later. It's a pain in the ass getting the message every time I try to charge my phone. Went back to stock until a fix can be found. My battery is nowhere near being hot when this happens, and I have only seen the message when using voodoo. I think I'll just wait for a later release. Too buggy for now...
Alright: for those of you who never read the full first post: THE PROBLEM IS SOLVED, thanks for everyone who decided to chip in. I had to try the battery pull about 10 times before it worked
Edit: I feel like an asshole after rereading my own post. I am sincerely sorry for my incredible stupidity.
aidman said:
Alright: for those of you who never read the full first post: THE PROBLEM IS SOLVED, thanks for everyone who decided to chip in. I had to try the battery pull about 10 times before it worked
Click to expand...
Click to collapse
I did read your post and understand the the problem wa solved for you, but not for me. I wanted to include my experience in case others are having the same issue. I was unable to fix the problem.
SnrSuave said:
Voodoo busted my phone too. I could get the battery disconnected message to go away if I took the battery out and let it sit for a few minutes, but then it would come back later. It's a pain in the ass getting the message every time I try to charge my phone. Went back to stock until a fix can be found. My battery is nowhere near being hot when this happens, and I have only seen the message when using voodoo. I think I'll just wait for a later release. Too buggy for now...
Click to expand...
Click to collapse
Not a lot of people get that error. I never did. And it never appeared either.
I had this issue too with the "no battery" indicator, and so did another individual in the lagfix release thread. No our phones were not hot, my own battery was nowhere near being hot, and we tried battery pulls, but that never worked. What worked for me was reflashing the voodoo 0.2 kernel on top of itself, the other guy tried that and had success with that too. You may give that a try, but I must say, that was only a temporary fix because after a while I got that annoying message back again.
I seem to have gotten rid of it for good, backed up all my apps in titanium, re-removed voodoo (be sure to get rid of "remove_lagfix" file when it's no longer needed), did a factory wipe, reflashed the stock Odin Kernel, did another factory wipe for the heck of it, then applied Voodoo, then reinstalled my data + app data using titanium backup (keep in mind I never wiped, restored, or returned system back to stock). Been running for a while, and I have yet to have the "no battery" annoyance and to be honest my phone boots quicker. So up to you, worked for me if you wanna give it a try.
Just wanted to update this thread. I have noticed that after flashing the voodoo kernel I too am getting the battery not connected error. However, I ONLY get this error when I have the usb cable plugged in when shutting down and starting back up again. If there is no usb cable plugged in when powering the device on, I have no problems with battery errors.
2 things stick out for me...
1. I had USB debugging on when doing the fix.
2. I removed the battery to go into initial Odin flash...PDA, etc.
The guide said my phone would reboot on its own, but it just sat at a blank screen. I had to unplug the cord and turn the power on. So do we have a fix for this yet?
i know earlier today my battery reading according tot he widget for setCPU said 66 degrees F.......which is kinda hard to believe seeing as the outside air temp is 80 degrees F outside and the inside air temp is 73 degrees F and my phone, although it had been sitting untouched for hours pluggen in inside, it was still on.....i cant believe the battery was running the best part of 10 degrees below ambient...even in idle state
Just flash the 1200 voodoo kernal u won't have that problem
Sent from my SCH-I500 using XDA App
I have had three Mytouch 4gs replaced because every one of them I get turns itself off and wont turn back on until the battery is pulled out and put back in. This happens about 6 times a day.
I have tried a new SIM card, new sd card, new battery, factory reset, factory reset with a format of the sd, and they still turned off even without any apps installed and not signed into google.
I am baffled. Does anyone here know what could be wrong here?
i dont know why this has happened to you so many times but it happened to me this morning and immediately after the battery was pulled and reinserted i went to rom manager and fixed permissions. took a while to finish cause i have buku apps but hasnt happened since.
hope it helps ya!
I was running completely stock when this happened, but I've since upgraded to virtuous fusion. Is it better to boot into recovery using CWM to fix permissions or am I fine doing this from the app?
Well I fixed permissions through CWM and it just turned off on me again. Ugh. I'm guessing its not a problem with the rom but with my hardware. Should I try flashing the latest radio?
Does anyone else here have this problem? Wtf is going on?
idk if its the same problem you're having but mine has recently started turning the screen off, the buttons still turn on as well as the led blinking if i have a notification but the screen wont come back on until i do a battery pull
so i'm also wondering what the problem is, fyi i'm using the kernel that came with cm7 and the latest radio
Hmm not sure. When my screen wont turn on I get no lights at all.
One of the causes can be the battery going bad.
I had the same issue until they sent me a new battery.
Sfkn2 said:
One of the causes can be the battery going bad.
I had the same issue until they sent me a new battery.
Click to expand...
Click to collapse
I have tried many different batteries with no effect.
I have noticed however that if it goes unresponsive and I plug it in the charging light comes on and I am able to boot the phone. It will turn off rather quickly though. Like in 20 minutes as opposed to 2 hours. Very weird.
Wow has anyone found a solution for this Problem? I can go into recovery and flash roms with no problem but as soon as it boots to the home screen its just automatically shuts off. Only twice have I gotten it to actually stay on for an hour or so. Also while charging it flashes green then orange, I have two different batteries, any ideas?
Well mine is the same it started after a small six to eight inch drop on the floor and it randomly freezes and when i boot it up just goes into boot loader and after a while of it being off it will go into OS any ideas anybody I am thinking it has something to do with bad chip but what do i know lol tel me know if anybody finds anything out thanks in advance
I've begun encountering the same problem after flashing MIUI 2.3.30 ROM. And I've also noticed that my phone started to get hot. It never did this before. I know my battery is fine, I also re-calibrated my battery and everything. I am even also thinking that for some reason my phone is bricked. It holds charge for about 10 minutes before it dies, even on the new battery, which I have tested on another MT4G and works perfectly. The other phone is my nephews. I wonder if this has to do anything with the bad EMMC chip?
Any input for solving this will greatly help.
Reboots
drunk21 said:
I've begun encountering the same problem after flashing MIUI 2.3.30 ROM. And I've also noticed that my phone to get hot. It never did this before. I know my battery is fine, I also re-calibrated my battery and everything. I am even also thinking that for some reason my phone is bricked. It holds charge for about 10 minutes before it dies, even on the new battery, which I have tested on another MT4G and works perfectly. The other phone is my nephews. I wonder if this has to do anything with the bad EMMC chip?
Any input for solving this will greatly help.
Click to expand...
Click to collapse
You might have already looked at this but have seen in some other roms I have been working with is to make sure to check the md5 sum before flashing just because it flashed doesent
mean it was right it takes is slight hickup in a download and a bit of garbage where it don't belong. Better to check it do the full wipes even a couple times or maybe even mounting and format the boot n system partitions so if on a particular rom ask in its section.
Hope that helps, wish ya well
I would agree with the above post making a clean wipe, and even the format does help. I have been trying out almost all of the newest ICS roms avaliable and I notice it helps when wiping everything/format system and boot. Even the newer ICS rom Awesomev2.1 suggest doing so for the system partition.
As others have stated, you might not have performed a FULL wipe.
Reflash, but do the wipe (I did also wipe battery stats..seemed to help in my case)
Random restarts and won't load
Had the same issue when I switched to Virtuous Unity... battery wouldn't hold a charge and would randomly restart.
After basically nuking my phone (full wipe, cache/battery wipes, etc.), as well as installing Creamed Glacier, the battery life is better but the random restarts are not. Plugging the phone in is the only way to keep it from restarting constantly, where it will load the T-Mobile splash screen but turn off either immediately after or as the home screen loads. But the battery is always at least 50% when I plug it in and it stays on. It also seems to take forever to recharge (plugged into laptop).
I want to think it's a battery issue, but the fact that it's not dead when I plug it in makes me think it's a hardware issue. I can't send it in to T-Mobile (shipping charges and time would be huge, as I'm in a foreign country and I rely on it so much for communication), and I'm loathe to buy a new phone.
Anyone have any ideas?
ivioi3ius said:
Had the same issue when I switched to Virtuous Unity... battery wouldn't hold a charge and would randomly restart.
After basically nuking my phone (full wipe, cache/battery wipes, etc.), as well as installing Creamed Glacier, the battery life is better but the random restarts are not. Plugging the phone in is the only way to keep it from restarting constantly, where it will load the T-Mobile splash screen but turn off either immediately after or as the home screen loads. But the battery is always at least 50% when I plug it in and it stays on. It also seems to take forever to recharge (plugged into laptop).
I want to think it's a battery issue, but the fact that it's not dead when I plug it in makes me think it's a hardware issue. I can't send it in to T-Mobile (shipping charges and time would be huge, as I'm in a foreign country and I rely on it so much for communication), and I'm loathe to buy a new phone.
Anyone have any ideas?
Click to expand...
Click to collapse
I really hate to be redundant, but you formatted /system and data? System gets missed a lot and you didn't specifically mention it.
Sent from my HTC Glacier using XDA
I have had the same problem with ics zips 4.01 all of a sudden the phone stops responding to the power button and have to take out the battery and boot up the phone but as of yesterday with the 4.02 I have had the problem. I don't know if it due to the heat cause where I live it hot and its just the beginning of summer too?
HELP,
yesterday, I was using my nexus 7 for normal use, wasn't playing game, just browsing with chrome. the battery was 8 percent when I last saw it. I then proceed to charge it, but the thing suddenly just shut down itself. I thought I misread the battery percentage, so I charge it anyway. about an hour later, i checked on my nexus 7, turn it on, got to the boot screen, got to the home screen, use it for about 15 minutes, and suddenly, the screen black out, it was flickering like crazy, and making some white noise ish sound. I panicked so I hold down the power button and turn it off. I turn it on again, and after about 30 seconds, the same thing happened again. I was using motley's kernel with 520 GPU, and I thought, maybe my nexus 7 cant handle the GPU OC. So I went to recovery, tried playing with recovery for about a minute or so, but the screen didn't flicker at all on the recovery. So I flashed the 484 GPU version of motley's kernel. When I reboot to system, the same thing happened again. So I thought, maybe if I restore to my old backup, it would not be like this any more. so I wipe the data, dalvik, and cache, and I restore my old backup. But the same thing happened again, only this time, after I turn it off, it make a high pitched sound.
I waited for about 6 hours, and now when I turn my nexus 7 on again, it works normally.
So, what has happened to my nexus 7?
bump
I'd say it is the overclock. Graphic cards do some weird stuff when overclocked. You can burn up your GPU doing that and cause it to forever freak out. I always shied away from GPU overclocks.
Sent from my Nexus 7 using xda premium
would that cause any permanent damage?
keni.mardira said:
would that cause any permanent damage?
Click to expand...
Click to collapse
It should be ok if you reflash back to stock rom to make all the hardware back to reset mode. A warning always given when we try to flash rom with oc created.
i also experienced this one, also received a battery warning and then suddenly screen went blank. then same weird thing happened as the one above. I'm on paranoid android rom and i'm quite sure it's not overclocked or something. Was only able to get back to normal by holding the power button for around 15-20 seconds...
Happens to me
This will happen to me a lot when my nexus 7s battery dies, I plug the tablet in and then immediately try to start it up. It will work for around 30 seconds then look like an old TV without a signal. I am on stock everything, no rooting or custom Roms (yet). I always thought it had something to do with battery calibration being off and the tablet not having enough power to run, because it always works fine when I charge it before attempting to boot.
I have also noticed that every once in a while the screen will have a vertical line of pixels flicker.
Same thing happened to me yesterday...
I got the "low battery" warning and after some time the screen started flickering in many colors and there was a weird static noise.
I pushed the on/off button, but it wouldn't turn on again. After a few minutes of charging, I could turn it on again.
This isn't normal behaviour, is it? Shouldn't the N7 perform a regular shut-down when the battery has no juice left?
I'm on the rooted stock rom btw.
androidswagz said:
This will happen to me a lot when my nexus 7s battery dies, I plug the tablet in and then immediately try to start it up. It will work for around 30 seconds then look like an old TV without a signal. I am on stock everything, no rooting or custom Roms (yet). I always thought it had something to do with battery calibration being off and the tablet not having enough power to run, because it always works fine when I charge it before attempting to boot.
I have also noticed that every once in a while the screen will have a vertical line of pixels flicker.
Click to expand...
Click to collapse
+1 bro. I am having the same problem. what do we need to do ? it is same with all nexus 7's . should we claim the warranty or just neglect it ? wat say ?
Aditya88 said:
+1 bro. I am having the same problem. what do we need to do ? it is same with all nexus 7's . should we claim the warranty or just neglect it ? wat say ?
Click to expand...
Click to collapse
I faced the same problem. I dont know when the battery might have drained out, but on starting the tab on low battery, it suddenly started showing black screen with little grains and suddenly stopped with a noise. I charged, started the tab again while charging, and the battery reading stuck at 21% even after charging for 20 mins. Within 5 mins, it happened again. Now after 35 mins of charging, I start it again, it boots normal, and now its reading the battery percentage in an incremental value (started with 22%) and now its again stuck at 23%
Is this a HW related issue? Or do you think it is more of SW related issue? If it is more towards the HW side, we better have it replaced. Mine is C70 model.
bump
just happened to me... it may have run out of juice... didn't turn on when I tried, so I guess it did... then I put it on the charger, tried booting it, went away for a sec and when I came back I also got this black screen with some flicker and a static noise...
will now try to charge it over night before trying again...
Nexus 7/Google problems
I received my Nexus 7 on Aug 21 after hearing the rave reviews. It didn't come with app for a camera, so I downloaded one.
The camera didn't work. I re-booted it & it worked this time. Downloaded Skype - whole reason for getting the tablet - to stay in touch with family that is far away. Tried to Skype - camera wouldn't work. Rebooted - worked this time again (getting tired of having to reboot for something I want to use to work). On Sept 2, sent message to Google inquiring about camera & app I downloaded. Only response - "thank you for contacting...blah, blah, blah - check out Q&A." All along, the tablet would shut itself down & reboot randomly (battery fully charged sometimes). On Sept 13, I shut it down & charged it. After a full charge, I tried to power it back on. Tried again several times that night & then the next morning. Called Google (who I bought it from). Told them I didn't want a piece of junk that wouldn't work. He told me it was past my remorse period. (The only remorse I have is buying their piece of crap instead of a reputable one.) I finally did get it to come back on, but camera hasn’t work since even after a complete factory reset. Any way – in order to get this one fixed, I have to “buy” a new one, then send back the old one & be reimbursed. Is this a legitimate business practice?
hi,
since today i have the same issue. did nothing special, just swichting from g currents to chrome. stock rom, no modifications, not rooted, everything original
n7 suddenly had a black screen(battery was at 28%). nothing worked, no powerswitch(10-30 secs). when connected to original power supply and cable, it boots up.. google logo .. glowing X.. lockscreen. then, approx. 30 sec later it turns off again(screen black). usb cable still connected. after some time it comes up again.. and repeats the procedure. after some cycles it stops, and when i reconnect the usb calbe it starts over again. sometimes, before it turns black, it shows a flickering screen and sometimes fizzling sound.
any suggestions?
I had this same issue right after the 4.2 ota update, after leaving it on charge overnight it seems fine now after a couple of discharge / charge cycles
Its like after the update it was over estimating the battery level
Sent from my Nexus 7 using xda premium
Same thing!
I have a completely stock Nexus 7, and the EXACT same problems are happening to me too! The first couple of times it happened my tablet would reboot normaly. But now, my tablet won't boot up at all. Any suggestions on what I should do? Also, remember, I have no mods installed.
Happening to me too.My N7 shut itself down because of low battery a couple hours ago and I haven't been able to get it to boot since. When I plug it into the charger it shows a flickering screen like a tv with no signal but with less white flickers. I've tried multiple chargers and cables but I could only get it to boot up a couple times and both times it did not show that it was charging even though it was plugged in and the battery was at 0% so as soon as it boots up it shuts itself down again because of low battery.
So now I've got it on the charger, screen all a'flicker, waiting for it to get a charge but I've got a feeling its not even charging because, like I said, the few times it has booted it showed the battery at 0% and not charging.
I guess I'll try to leave it alone for a while and see if it will start up after being plugged in for a bit.
EDIT: I let it sit there and charge for about an hour or so (with the screen flickering) and I was finally able to get it booted. It said it only had 3% battery but now it seems to be charging as fast as usual.
devhen said:
EDIT: I let it sit there and charge for about an hour or so (with the screen flickering) and I was finally able to get it booted. It said it only had 3% battery but now it seems to be charging as fast as usual.
Click to expand...
Click to collapse
Yup... I've let mine sit there turned off and charging over night... helped!
Just had a problem with the Nexus 7 not charging when battery was likely fully depleted. Putting a charge cable in was automatically booting the Nexus 7 up and wouldn't charge shutting down right after. Loops going on and off. What I did was plug a charge cable in and hold power+both volumes and now I believe I am charging at the bootloader screen. It stays on so I will leave it like this and if it doesn't resolve the issue I will try recovery once it is charged.
I've just started having the same issue. Has happened twice when battery gets to 8%, suddenly jumps to 0, shuts down, then after a few seconds restarts itself. Gets to home screen for a few seconds, battery showing 8, then jumps to zero, switches off and has flickering blocks on screen with static noise. This keeps repeating, only way I have found to solve it is to load into bootloader, then select power off. Device charges normally then and once charged works fine. I am unlocked and rooted but running stock 4.2.1, think I'll just have to return it for a warranty claim.
Based on what you experienced, the lesson here is your device can't handle the GPU over clock of more than 446mhz or it will do some crazy stuff.
Sent from my Nexus 7 using xda app-developers app
Here is my problem. I have a Nexus 4 that constantly powers off. And by power off, I mean as soon as the Nexus 4 boots up into the OS, the phone starts the power off sequence.
What I've tried so far was:
- in recovery did a factory reset, wiped both the data and cache partition.
- tried reloading the official nexus 4 firmware. Tried the 4.4.4 and 4.4.3 image
- used fastboot to load up a custom recover only to realize there is no rom on the phone itself to install from so that's out of the question pretty much.
- I tried the adb sideload but the computer doesn't see the nexus 4. the computer however sees the phone when it boots into the OS but the phone starts the shutdown operation as soon as it loads the start screen.
If it's hardware issue, then I guess there's no point in trying to fix it. But if it's only software related I want to at least try to see if it can be saved. lol
Any suggestions?
Well I know this happens when you have 0% battery
maybe your battery isn't charging?
Try booting with your N4 plugged and leave it plugged so 5 minutes, check your battery status and if it's ok unplug it and cross your fingers.
Roastmeat said:
Well I know this happens when you have 0% battery
maybe your battery isn't charging?
Click to expand...
Click to collapse
I thought about that at first. but according to twrp the battery life was above 70% and can run on battery perfectly fine. The phone doesn't actually belong to me. She gave up trying to fix her problem and got a new phone. I just got curious and want to find out what is causing the issue.
danmen2 said:
Try booting with your N4 plugged and leave it plugged so 5 minutes, check your battery status and if it's ok unplug it and cross your fingers.
Click to expand...
Click to collapse
I left the battery charging all of last night just to try it regardless of what the status said. It was hovering at around 70-80% according to TWRP before I plugged it in. It actually made progress today. The phone booted up. So I put in LPV just for the fun of it. The first time it booted up into LPV, it was doing the shut down process as well. Plugged it back into the wall for 5 mins, unplugged it and turned on like normal. Went through the set up process.
Left it sitting there for about an hour. Then decided to shut down the phone and restart it to see if that issue would return. Didn't return until Play Store started doing updates. The phone shut down. Powered it back up and it was fine. lol. Battery life right now is sitting at 78% and battery widget reborn is saying the temperature is 39C. So it coule very well be the battery. But my friend said the guy she brought the phone for repairs supposedly changed the battery. lol. So I don't know.
Espada04 said:
I left the battery charging all of last night just to try it regardless of what the status said. It was hovering at around 70-80% according to TWRP before I plugged it in. It actually made progress today. The phone booted up. So I put in LPV just for the fun of it. The first time it booted up into LPV, it was doing the shut down process as well. Plugged it back into the wall for 5 mins, unplugged it and turned on like normal. Went through the set up process.
Left it sitting there for about an hour. Then decided to shut down the phone and restart it to see if that issue would return. Didn't return until Play Store started doing updates. The phone shut down. Powered it back up and it was fine. lol. Battery life right now is sitting at 78% and battery widget reborn is saying the temperature is 39C. So it coule very well be the battery. But my friend said the guy she brought the phone for repairs supposedly changed the battery. lol. So I don't know.
Click to expand...
Click to collapse
Yeah, sounds like a possible bad repair. Try another thing, flash a kernel not based on stock, like hell's doctor or hell's core. After 4.4.4 there are several issues like boot loops and shutdowns with kernels based on stock.
danmen2 said:
Yeah, sounds like a possible bad repair. Try another thing, flash a kernel not based on stock, like hell's doctor or hell's core. After 4.4.4 there are several issues like boot loops and shutdowns with kernels based on stock.
Click to expand...
Click to collapse
Well it's running Android L Preview port so it's not running 4.4.4 based rom. At least to my knowledge. I'm going to see how long this last. I suspect they didn't really replace the battery or it could be an issue on the motherboard side not detecting the proper charge level on the battery? But battery life so far on the phone seems pretty crappy. 13% in the last 45 minutes on airplane mode with wifi on.
Everyone, please help me. I don't know what else to do. I am desperate here!!!
So, I've had my Galaxy Note 4 since the day they came out (October 24th, 2014), and I baby my phone.
Anyway, I've never dropped it, got it wet - nothing.
Last week, out of nowhere (I don't recall downloading anything out of the ordinary), my phone started getting extremely sluggish. I wiped the cache partition, but that didn't solve my issues.
Then, the phone was shutting down (abruptly, not powering down) out of nowhere. So, I pulled the battery, and did so many other recommended things.
Now, I cannot turn on my phone without first pulling the battery. Every so often, the phone shuts down (abruptly) and I have to pull the battery to start it up again.
I've changed batteries to back to my original battery, but that didn't help.
Then, every so often a screen comes on with the Android character saying, "Downloading. Do Not Turn Off Target !!"
Please help me!!! What can I do? What should I do?
I love this phone and it's gonna be a long time before the Galaxy Note 8 comes out!
Dankees said:
Everyone, please help me. I don't know what else to do. I am desperate here!!!
So, I've had my Galaxy Note 4 since the day they came out (October 24th, 2014), and I baby my phone.
Anyway, I've never dropped it, got it wet - nothing.
Last week, out of nowhere (I don't recall downloading anything out of the ordinary), my phone started getting extremely sluggish. I wiped the cache partition, but that didn't solve my issues.
Then, the phone was shutting down (abruptly, not powering down) out of nowhere. So, I pulled the battery, and did so many other recommended things.
Now, I cannot turn on my phone without first pulling the battery. Every so often, the phone shuts down (abruptly) and I have to pull the battery to start it up again.
I've changed batteries to back to my original battery, but that didn't help.
Then, every so often a screen comes on with the Android character saying, "Downloading. Do Not Turn Off Target !!"
Please help me!!! What can I do? What should I do?
I love this phone and it's gonna be a long time before the Galaxy Note 8 comes out!
Click to expand...
Click to collapse
Could be a faulty battery because the symptoms sounds similar to mine.
What happened to me was :
Phone would shut down randomly and would only switch on when plugged and charging.
Phone would shut down randomly and would only switch on after pulling out the battery.
Phone would randomly reboot.
Phone would discharge at a very quick pace. 20% for 5-20 minutes of usage.
Phone would only switch on when plugged into a power source but would bootloop when unplugged, even at 100%.
I managed to remedy the situation by buying a new battery. Although you did mentioned that you replaced it with the original battery, I suspect that there might be some sort of batch issue or something when it comes to the Note 4 battery. This current battery that I'm using is the third battery I bought for my Note 4 (because Samsung did not honour their warranty) and the only one that did not came from a Samsung authorised dealer and so far the issues seems to be gone. My phone stopped shutting down randomly and now I'm able to get 4 hour SOT with 12 hours of battery. Not that I'm suggesting you to get a fake battery but it's worth a try to see that it's not a motherboard issue.
My first two battery that came from Samsung and an authorised dealer both had issues within one year respectively and if you bring it to Samsung they will claim it's a motherboard issue and will charge you a few hundreds for a replacement so a new battery is worth a try.
So, I replaced my OEM battery with an Anker battery over a year ago. When this issue started, I put the OEM battery back in. The same issues occurred and the battery drained faster, so I put the Anker one back in.
Did adding a new battery fix your issues? It seems like you might have had the same issues as me.
Did that boot screen with the big Android guy come up on your phone as well?
Did you do a factory reset upon loading the new battery in?
I really love this phone, as you do, and I really want it to work and last!
Dankees said:
So, I replaced my OEM battery with an Anker battery over a year ago. When this issue started, I put the OEM battery back in. The same issues occurred and the battery drained faster, so I put the Anker one back in.
Did adding a new battery fix your issues? It seems like you might have had the same issues as me.
Did that boot screen with the big Android guy come up on your phone as well?
Did you do a factory reset upon loading the new battery in?
I really love this phone, as you do, and I really want it to work and last!
Click to expand...
Click to collapse
Hi there,
I had exact the same problems. I think it is your flashmemory that is causing the problem. When the phone suddenly reboots into downloadmode you normally will see an error message in red saying "emmc read failure". This is your flashmemory. I ordered a new motherboard via alieexpress and replaced it myself, which is not difficult. You can find tutorial on youtube.
My phone is working perfect now.
Dankees said:
Everyone, please help me. I don't know what else to do. I am desperate here!!!
So, I've had my Galaxy Note 4 since the day they came out (October 24th, 2014), and I baby my phone.
Anyway, I've never dropped it, got it wet - nothing.
Last week, out of nowhere (I don't recall downloading anything out of the ordinary), my phone started getting extremely sluggish. I wiped the cache partition, but that didn't solve my issues.
Then, the phone was shutting down (abruptly, not powering down) out of nowhere. So, I pulled the battery, and did so many other recommended things.
Now, I cannot turn on my phone without first pulling the battery. Every so often, the phone shuts down (abruptly) and I have to pull the battery to start it up again.
I've changed batteries to back to my original battery, but that didn't help.
Then, every so often a screen comes on with the Android character saying, "Downloading. Do Not Turn Off Target !!"
Please help me!!! What can I do? What should I do?
I love this phone and it's gonna be a long time before the Galaxy Note 8 comes out!
Click to expand...
Click to collapse
Same issue here, started over a week ago, I have tried so many things, no results, you can't do anything, just gotta change the motherboard.
Same issues for me also. I replaced the battery,with no positive effect. The only thing to help is installing the app wake lock. Phone now works, but this does not solve the poor ram handling.