Database Users

Screen gets black/gray/white and then gets back to itself

Hi guys,
I would really appreciate your help if you ever ran into such an issue.
This thing started happening on Android 4.3 and it continued on Kitkat after I unlocked my device, unlocked, wiped and installed factory image of Kitkat.
The thing is that while working the screen suddenly turns either black/gray/ image dims/ only half image appears.
It mostly happens when using Chrome.
after a few minutes of dimming just leting it on with the screen off, it all go back to normal.
The only thing I noticed is that the region of the back camera gets a little warm, but besides that everything's OK.
Have anyone ever ran into such a thing? What could be the problem?
I'd appreciate your response,
Fabian

anyone??
Please?
Thanks,
Fabian

screen constantly switching between lockscreen and stock homescreen

Okay, so yesterday I was out with friends and my battery was low.When I had to use my phone, shortly after the battery died.I came home, started charging it and when it had about 20% i turned it on.Ever since that, my phone is constantly switchung between my lockscreen and stock homescreen, with me not being able to do anything(go to the settings or something like that).So I hard reset the phone and when it booted up and I was going through the basics, one message popped up every few seconds: "The UI has stopped working." So it was difficult to go through all that stuff, but I made it only to see the problem is still the same.I also tried to take it apart and blow the dust off the MB hoping it would work, but unsuccesfully.I also have to mention the screen is cracked very bad and you can see inside the phone down where the LG logo is, but the phone was working absolutely fine in that state for over a year.Any help? :crying:

I'm guessing that you didn't have a lot of storage left on your phone, right ? A similar thing once happened to me, rebooted while storage was completely full. Refused to work until I reflashed it.

jonixas said:
I'm guessing that you didn't have a lot of storage left on your phone, right ? A similar thing once happened to me, rebooted while storage was completely full. Refused to work until I reflashed it.
Click to expand...
Click to collapse
So I should do a CSE flash, right?I'm flashing my phone for the first time now and waiting to complete the download of the .kdz file(slow internet )

Nexus 6P Bootloop after 4core

I applied the 4core fix for my N6P back in September of last year, and stopped using it around December because of the battery life. Around July/August I purchased a battery and installed it and things were going well. Now my phone is freezing and booting to the Google Logo and... Crash again. No Nexus animation; Google, crash. Sometimes it will attempt to boot and bootloop and sometimes it turns on and works fine. Sometimes if it turns back on it freezes and boom. Google logo.
I guess the remaining 4 cores in this phone are done completely from the looks of it? I know the patch wasn't meant to be permanen, only temporary because the remaining 4cores would eventually die.

snappycg1996 said:
I applied the 4core fix for my N6P back in September of last year, and stopped using it around December because of the battery life. Around July/August I purchased a battery and installed it and things were going well. Now my phone is freezing and booting to the Google Logo and... Crash again. No Nexus animation; Google, crash. Sometimes it will attempt to boot and bootloop and sometimes it turns on and works fine. Sometimes if it turns back on it freezes and boom. Google logo.
I guess the remaining 4 cores in this phone are done completely from the looks of it? I know the patch wasn't meant to be permanen, only temporary because the remaining 4cores would eventually die.
Click to expand...
Click to collapse
My 6p also started bootlooping again today and this time fix didn't help me. I think it's gone for good.

maxguncel said:
My 6p also started bootlooping again today and this time fix didn't help me. I think it's gone for good.
Click to expand...
Click to collapse
Is yours booting to the Google logo and crashing? Or simply bootlooping? Mine goes to the logo, crashes about 10-15 times and then eventually attempts to boot.
It's a shame, got a baby on the way and simply can't afford another phone right now

snappycg1996 said:
Is yours booting to the Google logo and crashing? Or simply bootlooping? Mine goes to the logo, crashes about 10-15 times and then eventually attempts to boot.
It's a shame, got a baby on the way and simply can't afford another phone right now
Click to expand...
Click to collapse
Displays Google logo about 20-30 sec and restarts. Before I could see the animation but this time no luck.
Congratulations! I also have a newborn, we'll see what the future holds

maxguncel said:
Displays Google logo about 20-30 sec and restarts. Before I could see the animation but this time no luck.
Congratulations! I also have a newborn, we'll see what the future holds
Click to expand...
Click to collapse
Thank you You too! Day of Thanksgiving he is supposed to get here, but my wife isn't doing too well lol do you know of any way for us to pull data? Adb is failing to see my device when it's in the bootloader, fastboot is working though. I tried once more to flash twrp 4 core and boot it with no luck. Those small cores gave out I guess. I left my phone on overnight bootlooping with no luck. I got most things off, just my actual camera fder I couldn't get and apps which aren't a huge deal.

Sadly this morning I had the same problem. Bootlooping, I even cannot enter into Recovery. Then, suddently, it restarted, but I wasn't home, so I hadn't the chance to save the data. Then, about 3 hours later, it restarted bootlooping and, since then, it's stucked into this bootloop. Even reflashing the modified boot won't work.
Anybody knows how to at least recover the data inside? Even if I have to break the phone (I'm going to buy onther one soon)

hey guys, me too. but you know something? my initial assessment was that it was a result of an update. Now looking here annd seeing so many others with the same problem at the SAME TIME?? mine happened out of the blue on about October 4th or 5th. Ive had this phone for two years and never had aproblem with it at all. right out of the blue (in the morning) i get the bootloop. I cleared the cache and it booted up again. it was just fine for two days and now it is down black and out. When i push the power button i get a red light. one blink. if i hold down pwr and vol i get 8 blinks. tried on stock charger and other charger. like was previously mentioned when i tried it on a different charger it worked. the first time. now its dead. any solutions?

Marxmellow said:
hey guys, me too. but you know something? my initial assessment was that it was a result of an update. Now looking here annd seeing so many others with the same problem at the SAME TIME?? mine happened out of the blue on about October 4th or 5th. Ive had this phone for two years and never had aproblem with it at all. right out of the blue (in the morning) i get the bootloop. I cleared the cache and it booted up again. it was just fine for two days and now it is down black and out. When i push the power button i get a red light. one blink. if i hold down pwr and vol i get 8 blinks. tried on stock charger and other charger. like was previously mentioned when i tried it on a different charger it worked. the first time. now its dead. any solutions?
Click to expand...
Click to collapse
It simply means that the battery is fully discharged. Keep it connected to the current and maybe it restarts working.
I'm in the same situation since yesterday, hoping that at some point it returns working for some time, just to backup some data. I have like 10GB of photos not backupped in it.

When I replaced my battery I reinstalled factory. Start from scratch.
I had the same issue and that's all I did. Booted fine after that. I used the ifixit battery tho, cause if you got a lower cost one it could be the battery itself too

Galaxy S5 with Lineage OS stuck in a bootloop

Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Might Be A Malicious OTA Uptade , My Advice For You , Install Stock Rom

Try installing a different rom and if that works, retry installing LOS. Two years ago i became unable to update/install LOS. RR was an instant success and i kept using that till becoming somewhat instable one year ago, so back to LOS, w/o difficulties(probably a clean install of RR would have solved the problems i had, but i didn' t want to do this two times, if really RR and only that was the culprit).
Of course you can start by reinstalling stock rom in Download Mode, as this will be the last attempt if all previous measures may fail. Then re-root, re-install TWRP etc.

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
I Heard That The Last Uptade For Lineage Doesn't Work So Download A New ROM In Your Computer And Put It On A SD-CARD And Boot To Recovery And Clean-Flash It
Oh If You Want To Know My ROM I'm Using : Resurrection Remix.

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.

yerrag said:
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.
Click to expand...
Click to collapse
Well, this worked for a while. Then, bootloop became more stubborn.
By then, I had already bought a phone to replace it, so I was in no hurry to fix this issue but still, I hate to see a good phone go. Still has a screen that stood the test of time, and at high res, and I love the size of the phone.
So, another Hail Mary. And it worked!
I put the phone, worked in tissue paper, then enclosed in bubble wrap, in the freezer overnight, surrounded by grains of rice in a plastic container, that had been vacuumed by a FoodSaver machine.
The following morning, removed the phone from the freezer and laid it bare, separating the battery from it, and wiped it clear of moisture, and let it sit to evaporate any more moisture from the temperature gradient.
Then started the phone, and the bootloop once again gone.
So, phone saved. But since it's no longer that reliable due to the recurring bootloop problem, it would be my phone to watch streaming movies from Amazon Prime or Netflix, but not my phone for receiving calls and text messages, or for Waze and all.
The lesson I got from this is that with this phone, the circuitry inside has become finicky. To open it up and fix it would be too bothersome, especially with the circuitry being composed of embedded modules. Probably somewhere inside there is a capacitor that has reached its reliable end of life, but still breathing and needing an occasional handholding. So, I just gotta learn to live with this quirk, and this quirk is tolerable for the use I have it for.
So, if you run across this problem, I hope I gave you a workaround for you to remain loyal to a workhorse that served you long enough.

Black Shark 2 - Stuck in bootloop

Hi all!!
Unfortunately my first post here starts with something not quite fun.
My BS2 has just randomly decided to go into a bootloop (I think it's called.). It doesn't even get past the logo screen and it's totally unresponsive to all buttons. So, not quite sure what to call this.
I have NOT EVER rooted my device or flashed any firmware or messed with it in any way.
I was just using it normally when it suddenly started flashing and turned off, never to turn on again.
The phone is running the latest version of the Global from. Nothing else to describe really except that the phone is bone stock with nothing ever done to it.
Would really appreciate any insight anyone would have on this!

Same problem