Posting here because gflex and g2 are almost exactly the same, and I figured this forum would be way more active.
When I boot my phone the boot led never goes off. The phone is fully funcional otherwise. I had been uninstalling services and rebooting to make sure that I did not break anything, but the last batch was: unused themes, hangouts, livewallpaperpicker, wirelessstorage, and printspooler, none of which would cause this. I have also cleaned out the startup apps so nothing starts on boot, was there something in there that terminated the boot light? I know I rebooted after that though. I was only deleting things that I could find info for, and nothing else is broken. I tried googling for "android led service" and similar searches to see if I could find a service that controlled the led with no luck. Any Ideas? I really Don't want to reflash
Edit: And also all of the vibrations quit.
Related
Hi,
I tried to change my file system from Dalvik to ART and when my phone was optimizing apps after reboot, my phone suddenly shut off and it wouldn't turn on. If I try to turn it on, it will show a solid red LED for 3 seconds or so and then start showing a blinking red LED.
I did manage to get into the bootloader and I flashed the whole factory image for Kitkat and erased my data through fastboot, but it didn't fix anything. Anyone know if there's anything else I can do? My phone is outside warranty because I bought it on release date last year :/
Look what this guy had: http://forum.xda-developers.com/showthread.php?p=47968382
Spoiler: it's the exact same issue, and he resolved it. Wouldn't it have been great if you just searched the forums for a similar thread before posting this? I can answer that. Yes, yes it would have been great. It would have saved you time waiting for an answer here. And it would have saved me time writing this rant. So next time, use search.
Sent from my Nexus 4 using Tapatalk
Oh thank you. What great luck that he had the same problem. Does anyone actually know why disconnecting the battery cable would solve the problem? It seems odd that this is caused by a software problem, but a physical fix returned it back to normal.
Problem solved, so i suppose we can close this thread now
Hi there, I never thought I would ever need to register onto a forum like this one and have to seek help directly, but it seems I have little other choice.
Anyway, I have a Nexus 7 (2012 model), and it has been working fine and dandy ever since I got it used back in June of this year. Only problems I had up until yesterday were occasional touchscreen jitters and unresponsiveness that I managed to fix with the guidance of a Youtube video. Moving along, I started to have odd problems occur yesterday that seemed to be quite the chain reaction and avalanche of even more problems that are making me awfully suspicious and paranoid.
The device kept on booting off after leaving it for a while. Turning it back on would sometimes result in the screen freezing up, prompting me to go in there and physically disconnect the battery. An antivirus scan showed no bad files of any sort. After some Google searching about the problem, I decided to go into fastboot and wipe cache partition. All seemed to be going fine until it freezes up in the process. Ok, time to forcefully remove the battery again. This time around, right before entering recovery menu, I see something a bit different. The red warning triangle still appears over the little Android mascot, but the words "No command" no longer appear. (I would provide a link, but I have not made enough posts yet.) I tried to wipe cache partition again. No avail. Ok, screw it, let's try formatting. Same result. Booting it up normally had resulted in the dreaded infinite Google logo loop.
That being said, is there any hope of me salvaging this device? I can still go into fastboot if that's any indication of hope!
Over the weekend Lightflow was being wonky. Showing I had notifications when I had none.
So I uninstalled it, and hit restart to let the phone refresh..
Upon doing so, it bootlooped.... I think. After 3-4 minutes it came up with a Force Close window and said "System is Not Responding would you like to close? [Wait][OK]"
Has anyone else seen this or experienced it first hand?
As a fix, I removed the battery and let it set for a minute or so. Re-assembled, powered on, and it took a minute or so to boot fully after the removal of Lightflow and the bootloop, I think...
As the system hadn't loaded, I was unable to get SS's.. But does anyone have any insight on this?
Question: Do you have a Developer edition ? How are you on 5.0.1?
But the system not responding issue has also happened to me. Fixed it with a battery pull.
Not sure what causes the problem though. Maybe check logs?
I've been having some problems with my Galaxy S5 recently after ~2 years and some change of owning it. I'm stock rooted on the original ANCG KitKat version.
The problem: If I power off my phone, it will cause it to go into a bootloop, not going past the first screen (Samsung Galaxy S5, powered by android). I haven't found a reliable way to fix it from the loop, but I usually just remove the battery, wait, and try again until somehow it just works and boots up. This is extremely problematic because sometimes my battery runs out and after charging I'll have to go through this game of chance again until my phone works.
The next problem also adds to this frustration as well. When I attempt to pick up a call, my phone will sometimes just not work and restart itself. This leads to lots of confusion and I can't call them back for some time because the phone is stuck in a bootloop.
In the few times that I do get my phone to actually boot up, everything works fine except sometimes my Wifi just doesn't work. It gets stuck on "turning on" where the notification drawer quick setting icon is dim green and never gets to the turned on full green state, eventually just turning itself off (no green color).
I haven't done a factory reset or any real troubleshooting yet, as I'm a bit worried I won't even be able to boot up the phone and I don't have the time yet to spend a full day fixing it. Any help would be appreciated, thanks!
The calling problem may be caused by the google dialer app not being set as the the default phone app but as for the other issues i have no idea a factory reset is a good start though
unfortunately I had the same problem but I have marshmallow but the factory reset helped with the not booting up and see a big difference with the battery
Hey guys, I have had my Note 4 for about 3 years now and it has never done me wrong. However, things have taken a turn for the worse... I started noticing a few days ago that it was slowing down on me, I mean, really slowing down. Big lag times when it comes to swiping to open the screen, or changing between apps, and the occasional self-shut down when the battery got down to about 15-20%. I had been putting off doing a self-update for a while, and when I finally had time to do one tonight, in hopes of cleaning it up, it is now lying on its death bed
I do not think the update ever finished (my phone is not rooted) but I was desperate enough to even do a factory reset and that has not fixed the issue.
Here are the symptoms:
As I go to boot the phone, I get past the Samsung Note logo and it looks like it is about to load properly, but then I get a popup that says "Unfortunately, the process com.android.phone has stopped" I hit ok and it keeps popping up again. I can't bypass it.. Then after I get passed that for a split second, another popup comes up that says "unfortunately system UI has stopped" It prevents me from getting to the home screen, in fact the screen behind it is black.
I have tried the following:
Clearing the cache partition from the recovery screen
I have done numerous hard restarts
I have gone through with a factory restart
That is where I have left off, and lost most hope, was with the factory restart. Now when I turn it on, I get past the logos and I can see in the background the page you would get as if it was a brand new phone (it says "Welcome! Preparing you device for first time use.." etc. But I can't do anything about it because I am still getting the same two popups that prevent me from doing absolutely everything!!!)
I have read about this happening and people seem to be able to fix this by accessing certain app setting and either resetting them, or clearing their cache. However, that is not an option for me because I can't get that far. I think something must have went wrong during the update...
Please help with any advice you can think of. I have been putting off rooting this phone pretty much because I was afraid of royally f****** it up, but at this point I am willing to try anything.
Thanks,
Eric
Hey guys, does anyone have any suggestions for my issue?? I am about to go out and buy a new phone, I have no idea what I can do to fix this. I have rooted it using Odin, but the popups are still occurring. I can't get the popups to stop, and they are preventing me from doing absolutely everything.
Is there anyway I can get it to go back to complete scratch? Again, I have done a factory reset, cleared the cache, rooted using Odin. I have done everything I can think of/what I have read I can do. I am willing to try anything at this point.
UPDATE: At this point my phone is on, and the only error message/popup I am getting is "Unfortunately, System UI has stopped." Behind that popup is a blank, black screen. The only option I have is to click ok, and the screen remains black.
Temporary solution that might work- Try logging in safe mode: Switch off the phone. Power it on and as soon as Samsung logo appears, release the power button and press and hold the volume down button. Release button when you see Safe Mode on the lower left corner of the screen. Try uninstalling all user apps in safe mode. To get back to the normal mode you can drag down from notification and disable safe mode.
You could also download the latest software for your model from samfirm and flash it via odin after factory reset. Could be a permanent solution.
why you just flash last frimware from sammobile,it will solve all your problems
SOLVED!!!
Alright guys, I was able to solve my problem, all thanks to this thread:
https://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3250864
I had already tried flashing a fresh stock rom, but to no prevail. I saw this thread and thought, hey why not give it a shot, and bingo! After downloading the .tar file for marshmellow and launching it through odin, she was good as new! So if anyone seems to have a problem with the system ui or the process phone.android popup, I suggest that thread.