Hello!
Had my N9 for almost 4 years now! About a year in, I started experiencing the white-static-screen-high-pitched-screech issue that many of you have described, but disconnecting and reconnecting the battery connector solved the issue. As of late, I have been running stock Android N.
Recently, I have been starting to experience the issue again, as well as trouble booting up. The problem has gotten much worse over the past two weeks or so, to the point where I cannot fully start up -- the Google logo shows, the start-up animation starts playing, but usually doesn't make it very far before the animation freezes and the screen goes black. I can access the boot menu and Recovery mode though. Going into Recovery mode and explicitly "powering down," letting it sit for a bit, and then starting up sometimes makes it all the way to the OS, but it shuts down by itself shortly after. I cleaned and reconnected the battery connector, but that did not help. I just tried a factory reset, but that doesn't seem to have fixed the issue -- my device is wiped, but if I can get into the OS, it just shuts down as before. If I don't explicitly "power down" and let it sit, the battery does run down, which makes me think that rather than crashing when it freezes, it's still running, or trying to.
Any suggestions? Thanks!
weirdo16 said:
Hello!
Had my N9 for almost 4 years now! About a year in, I started experiencing the white-static-screen-high-pitched-screech issue that many of you have described, but disconnecting and reconnecting the battery connector solved the issue. As of late, I have been running stock Android N.
Recently, I have been starting to experience the issue again, as well as trouble booting up. The problem has gotten much worse over the past two weeks or so, to the point where I cannot fully start up -- the Google logo shows, the start-up animation starts playing, but usually doesn't make it very far before the animation freezes and the screen goes black. I can access the boot menu and Recovery mode though. Going into Recovery mode and explicitly "powering down," letting it sit for a bit, and then starting up sometimes makes it all the way to the OS, but it shuts down by itself shortly after. I cleaned and reconnected the battery connector, but that did not help. I just tried a factory reset, but that doesn't seem to have fixed the issue -- my device is wiped, but if I can get into the OS, it just shuts down as before. If I don't explicitly "power down" and let it sit, the battery does run down, which makes me think that rather than crashing when it freezes, it's still running, or trying to.
Any suggestions? Thanks!
Click to expand...
Click to collapse
Have you tried replacing the battery with a new one?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Have you tried replacing the battery with a new one?
Click to expand...
Click to collapse
Thanks! I've considered it, but the battery seems like it's OK -- it holds a charge when powered off, and the voltage still seems pretty high (~4.1v) Are there any other ways to tell if the battery might be bad, how do you tell? Has anyone determined if the white-screen-screeching issue is caused by the battery itself, or the battery connector?
weirdo16 said:
Thanks! I've considered it, but the battery seems like it's OK -- it holds a charge when powered off, and the voltage still seems pretty high (~4.1v) Are there any other ways to tell if the battery might be bad, how do you tell? Has anyone determined if the white-screen-screeching issue is caused by the battery itself, or the battery connector?
Click to expand...
Click to collapse
I have the same issue on my n9 but put it out to pasture so I never tried to replace it. I have seen others on here who have and it seemed to work. But, it also seemed that they couldn't find a real good replacement and the replacement battery didn't last that long.
Sent from my [device_name] using XDA-Developers Legacy app
I'm having the exact same problem. No matter what I flash it always get stuck at the bootanimation. Sometimes it doesn't even get past the initial Google logo bootscreen. I can never fully boot to the OS, though.
redsmith said:
I'm having the exact same problem. No matter what I flash it always get stuck at the bootanimation. Sometimes it doesn't even get past the initial Google logo bootscreen. I can never fully boot to the OS, though.
Click to expand...
Click to collapse
Have you tried updating to the lastest factory images from Google? They include additional pieces of firmware than just the OS and many ROMs are built with certain factory builds in mind. The firmware and ROM need to match. The kernel also needs to match. And if you're going to a completely different ROM, you need to factory reset. Or at least, it's a good idea to. Not all ROMs will boot without a factory reset.
gk1984 said:
Have you tried updating to the lastest factory images from Google? They include additional pieces of firmware than just the OS and many ROMs are built with certain factory builds in mind. The firmware and ROM need to match. The kernel also needs to match. And if you're going to a completely different ROM, you need to factory reset. Or at least, it's a good idea to. Not all ROMs will boot without a factory reset.
Click to expand...
Click to collapse
Yes, I flashed the latest factory image. I even flashed the first one (5.0). No matter what I try, it always get stuck at the bootanimation. Same thing with custom ROMs. I suspect something's wrong with the data partition, but not even wiping and formatting does the trick.
Related
So, my Atrix is doing something quite strange, and possibly unique.
Just about every 5 to 10 minutes, my phone will randomly reboot. This seems like something a forum search would fix. But it gets significantly more... weird...
More than half the time, it will come up to the Motorola logo, and just sit there... doing nothing. No errors, no messages, no nothing. Just logo. Pull battery, repeat. Sometimes it boots, mostly, it just does it again. Motorola logo. Big. Red. Cylon-like.
However, sometimes it seems that if I give the body of the phone a bit of a twist, flex it a little bit, SOMETIMES, this will prompt it to boot. I tried the because I have had to do this twist and flex trick to get the USB port to connect and charge for some weeks now.
If I can get it to boot, it will sometimes boot normally. Run for a while. And then I lock the screen. Sometimes, the lock button will wake it up like normal. More often though, it shows no response. I attempted to press the button while doing the same twist and flex trick, and this occasionally works. It will unlock the screen, and I can keep going. But usually, it just decided to reboot, and back to that darn Motorola logo.
I thought maybe because I was running JokerSax CM9 beta, it was a rom issue. So back to CM7 I went. No dice. Same thing. I kept a Nandroid backup of the stock ROM even, so I rolled back to that. Again, no change. Same results.
Some inconsistent symptoms are that sometimes when it boots up, the wifi will not come on. Other times it dose fine.
And one time, just one single time, it gave me a "Could not connect to modem" error on that red Motorola logo screen. I haven't gotten it to do that again.
So, is this a Radio issue? A ROM issue? Or has my logic board gone kaput? I am at a loss. I ordered a shattered Atrix from ebay for a logic board swap in case that would fix it, but it won't be here for another week. If anyone has some alternate ideas, I am open to suggestions!
does your wifi work properly when the phone is functioning?
How warm does the phone feel? Almost sounds like an overheating issue.
dLo GSR said:
does your wifi work properly when the phone is functioning?
Click to expand...
Click to collapse
Sometimes it works, sometimes not. Its really pretty random.
xcguy said:
How warm does the phone feel? Almost sounds like an overheating issue.
Click to expand...
Click to collapse
The phone gets quite warm once it starts having its fits. I usually pull the battery to let it cool down before trying again. I was running an overclocked kernel, but have since flashed back to a normal 1ghz kernel. It seems to get hot only when it is trying to boot. It only started doing this recently though. I never had an overheating problem before.
Reboot into recover and flush both cache and dalvik-cache.
Still sounds like an overheating issue...
xcguy said:
Reboot into recover and flush both cache and dalvik-cache.
Still sounds like an overheating issue...
Click to expand...
Click to collapse
Tried that already...
Well apparently, after flashing the latest AOKP for my phone, it keeps on rebooting itself at random time, and at other times, doesent boot at all. When I put it on charge, it shows the battery for a few seconds. I am unable to get in to recovery as it basically reboots there as well. In Download mode, I restored stock 2.1 FW and bootloaders carefully, but nothing, its still giving me an issue? Any advice, might just move on to the Galaxy Nexus
Did you do any flagrant battery pulls lately? Maybe check the contacts or that the battery fits snugly. Doubt that flashing caused it, but maybe something with the kernel power source.
I got it to boot into stock recovery, but after that nothing. Is there a way to fix it, i even tried a replacement battery but no cigar. Phone has plenty of potential.
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
jt.61 said:
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
122ninjas said:
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
Click to expand...
Click to collapse
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
mistabeo said:
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
Click to expand...
Click to collapse
Try to go to stock and see if the problem persists. If it does obviously a hardware issue
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
mistabeo said:
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
Click to expand...
Click to collapse
you know samsung has factory warranty for that kind of stuff.
i got my phone refurbished, about 9 or so months ago.. it only came with 3 months for the warranty. i guess getting a returned phone ended up biting me in the ass.
now the phone is overheating when im charging it.. looks like it's going to crap out on me soon.
Download the stock 2.3.4 firmware from the download repository. Do a full wipe including system data cache and dalvik. Boot into download mode hook up Odin and flash the stock firmware. If its a hardware issue your problems will persist in which case u could sell it on eBay for parts. If its a software issue that will fix it.
Sent from my SGH-I777 using xda premium
that's what i'll probably have to do tomorrow. if i remember correct, rooting the phone on 2.3.4 wasn't that straight forward, so i'd have to read up on how to do that again. but im just gonna leave it as is right now.
the phone acts really weird. when i took out the battery and replaced it with another one, it would keep doing the same thing. so then i plugged the phone into the USB charger and tried turning it on - that worked.
if it's a hardware thing, it's got to be something to do with the battery sensor. the phone is simple to remove, so i wonder if i can replace it myself.
i believe my phone is now semi-FUBAR.. it still runs, but seems like the battery sensor issue is a hardware one. i just tried doing a stock flash/odin thingy, and it still has the same issues... also, the phone is now permanently showing as MTP connected. i am also seeing decreased battery life.. only lasts about 1/2 a day now.
i guess i learned my lesson.. don't switch out the batteries too often, or your phone will die.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
Click to expand...
Click to collapse
is this a big deal? i'm also having samsung i9100? im using ucle5 AJ's rom/kernel.
i'm also having issues with charging the phone. it seems to charge forever, i have to unplug and plug the charger again to properly charge it.
When it says i9100 it means you tripped the flash counter. If you want to reset it use a triangle away app.
Sent from my SGH-I777
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
bubuty said:
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
Click to expand...
Click to collapse
No the same principle does not apply. Battery state wiping has no effect on this phone.
Sent from team Pirate! Using Tapatalk 2
Hello all,
My Note has been acting funny as of late. I am running Flapjaxx Cyanogenmod build. Earlier today, the device went into a boot loop fit and wouldn't get past the Samsung logo. On first notice, I thought that the power button may be stuck, causing the device to constantly restart. Upon further investigation, I noticed that:
On plugging in my device to a charger, the charging screen says that the battery is almost full, but on booting into team win recovery, it says that the batter is at 5 percent.
The battery seems to have gotten a tad bit fatter. When I take the back cover off, the battery just falls out when the phone is battery side down. It may be worth noting that I can't seem to get the back cover on all the way the past few weeks.
But the reason I am posting instead of just fixing the battery is because this started out of nowhere and my phone has been on this rom for many weeks now. Could the battery be causing all of this?
I have wiped the caches and I can get it to power on now but it keeps saying that "android is updating, optimizing x out of 60", which means that it is rebuilding the dalvik cache. Any help on this would be appreciated as I use this device a lot.
Back up and try another rom ....
••••changes with every flash••••
shayneflashindaily said:
Back up and try another rom ....
••••changes with every flash••••
Click to expand...
Click to collapse
I did want to avoid data loss if at all possible. I would take the latest unbloated ATT ROM.
I guess this what I get for developing on the Apple platform instead of android
I recently had a 6 month old Anker battery fail. It would cause my phone to boot to the samsung screen and hang. Had to install a backup each time it happened as no matter what I did the ROM would not load. After replacing the battery I had no more issues.
My phone has been working fine for the last year and a half regarding hardware and battery. The device itself has never given me any issues and the hardware is in pristine condition. Roughly three months ago I bought a ZeroLemon battery and case and have been using that since. The battery is also in great condition (no warping or expanding) and the case still looks brand new. BUT today when I went to use my phone (about 20 minutes after I unplugged it) I noticed it was off, and it will not turn back on at all. It will load the splash screen (it's rooted and has Xposed framework installed) but after one or two seconds it shuts of immediately. Somehow I did get it to boot into TWRP and I was able to make a quick backup, disable Xposed, run a quick factory reset and fix permissions. I flashed Cyanogen M12 and I thought everything was working fine (I was running M12 before and have been running Cyanogen for as long as I can remember.) but after 5-10 minutes the phone randomly shut off again. I have looked into this issue all day now and everyone that has had a similar problem has had battery issues. I have tried 4 different STOCK batteries today, as well as my ZeroLemon one and nothing has gotten it past the splash screen again. I am almost certain this is NOT a hardware issue but I have no idea what would cause it in the terms of software, since I haven't changed anything recently. If anyone has any suggestions please feel free to let me know. I'm looking for immediate fixes right now, so sending it back in or getting a new phone are secondary options. If you have advice just let me know in a comment or PM me, thanks guys!
Edit: At this point I can't do anything, ie: enter recovery, get the splash screen, enter odin (anything) it's like the battery is dead but the same exact battery works just fine in my friends phone.
Have you tried downloading the MDK full wipe tar, flashing it with odin, and using loki to root and bypass bootloader again?
So it turns out - after I took it apart - it has a defective power button. The actual piece that is soldered on. I don't know how to go about fixing it from here
Kind of strange but my device did the same thing today. I have tried multiple batteries with no luck. Will boot but then turn off before it reaches the boot animation. When I try to enter recovery or download mode it does the same thing.
Have either of y'all found a fix yet? My phone has the same issue (turning itself off after about 2-3 seconds after the boot animation begins).
Post number 7
Post number 8
Post number 9
Post number 10 finally
Any luck with getting the phone fixed?
ajgonzales said:
Any luck with getting the phone fixed?
Click to expand...
Click to collapse
I think he said it was an issue with his power button.