Hello,
I'm facing a weird problem, that after booting into Mi A1,
Status bar & Background wallpaper, would disappear & appear every 3 seconds.
& this continues in a loop.
I even tried flashing "Full stock October build" to both slots a & b (while selecting "save user data").
but the MiFlash Tool, gives an error "Flash modem_a error".
I will appreciate, if someone can help me out here.
As i can't use my phone.
Boot into safe mode and disable Lock and Ambient display
[email protected] said:
Boot into safe mode and disable Lock and Ambient display
Click to expand...
Click to collapse
I disabled lock screen & Ambient display,
as well as flashed stock boot images of September & August builds on their slots.
After doing all this, i could straight away go to homescreen.
But still the background of homescreen keeps on switching between black & the status bar also disappears,
then suddenly, wallpaper & status bar appears.
When i click search bar, to type something, keyboard appears. But immediately disappears due this background+status bar flickering/resetting.
Can anybody help me in fixing this.
First post edited.
It seems like constant system UI crashing. I experienced it once with Nexus 5X after doing some system modifications, the only way how to solve it was to perform factory reset. Reflashing of system only strangely didn't help at all.
Had to clean flash stock rom via MiFlash Tool.
Took me 5 hours, to copy files & setup phone again.
Even i had this problem
I some how managed and went into settings and performed a factory reset
The problem vanished
It's WhatsApp Causing Problem
Hi,
I have Reset the phone thrice, But Noticed All work Well till I Install WhatsApp, As soon As Whats app Data Restore Complete it Again Start Flashing and Not Able to Work.
Thanks
Amit
---------- Post added at 03:25 AM ---------- Previous post was at 03:00 AM ----------
Same problem here, it was Causing because of whatsApp, Solution Turn off Ambient Display,
I Did Hard Reset, By Power off and Volume keys,
If You can Reach to the ambient Display settings without Reset try to turn it off, as phone works for few seconds after re-start.
Mine is Working fine after since I turned Off Ambient Display,
Got this Solution from Other Thread, Thought to Help others.
osrox said:
Hello,
I'm facing a weird problem, that after booting into Mi A1,
Status bar & Background wallpaper, would disappear & appear every 3 seconds.
& this continues in a loop.
I even tried flashing "Full stock October build" to both slots a & b (while selecting "save user data").
but the MiFlash Tool, gives an error "Flash modem_a error".
I will appreciate, if someone can help me out here.
As i can't use my phone.
Click to expand...
Click to collapse
Related
Hi There,
Shortly after updating my Nexus 4 to 4.2.2 OTA today the screen went blank and I've been unable to get it to function correctly again.
The phone is still showing some signs of life, I am getting notification LEDs and I am unable to unlock the phone with facial recognition even though the screen remains blank - I can tell from the vibration and the LED stopping that it has unlocked. Pressing the power button to lock it starts the notification LED again.
I have tried a hard boot (Volume Down + Power) and the screen did come on to display the google logo followed by the X but as soon as they had been shown it returned to a blank screen.
Does anybody have any ideas of what this could be or how to solve it or should I contact Google in regards to this issue?
Thanks in advance for any help
seems like the OTA update has corrupted somewhere. You should reboot into bootloader and use fastboot to flash the stock 4.2.2
Is there anything else worth trying before doing that? I wouldn't have a clue where to start as this is my first android device
Ok so I got it working but did lose all my data. If anyone else comes across this issue I had to boot into recovery mode and do a full wipe/factory reset. The first time i did this the phone started up with no problems but during configuration when I entered my Google account the blank screen strangely returned so I again did a full wipe in recovery mode, skipped the 'set-up google account' step and then entered it manually later in settings once the device had started up.
No idea what caused this and if its a bug in 4.2.2 or an issue with some settings in my google account that are being backed up and restored to the phone but either way I had no problems until 4.2.2 update installed and the issue occuring even after first data wipe rules out any third party apps being the cause.
I had a similar problem after updaing that the screen stay blank and it wo'nt unlock
As soon as i disable the bluetooth the problem solved.
It's happened when i paired it with my pc
I rooted my Note and all was good for a while, but i think i must have changed a setting in Wanam Xposed, but i can't put my finger on what...Whenever I restart my Note, I go through the boot animation and then the lockscreen shows for a brief second before it goes into a second boot. The animation is the same both times (I have changed my boot animation in the system folder). I'm not sure why it started doing this. Any help would be appreciated.
bilichjl said:
I rooted my Note and all was good for a while, but i think i must have changed a setting in Wanam Xposed, but i can't put my finger on what...Whenever I restart my Note, I go through the boot animation and then the lockscreen shows for a brief second before it goes into a second boot. The animation is the same both times (I have changed my boot animation in the system folder). I'm not sure why it started doing this. Any help would be appreciated.
Click to expand...
Click to collapse
I started having the same issue on a 100% stock phone. Found resolution here (not enough posts for a link yet): androidforums.com/samsung-galaxy-note-3/791631-note-3-booting-boot-so-nice-does-twice.html. Turning off "Always allow scanning" from the advanced wifi menu stopped mine from booting. It almost seems like the first time it boots it crashes and has to reload TouchWiz or something. Not sure how the wifi scanning affects booting, but it worked for me.
Hi. My nexus 4 is on 5.1.1 unrooted. Once or twice every day, the screen goes black. But on screen nav buttons and notification drawer works. Have to reboot to get it working again. Any solution? Cant post youtube link. Please watch at /watch?v=oQfLmX-EYvU
Quite strange, looks like some kind of "partial" systemUI crash.
Have you tried wiping the cache partition in your stock recovery?
Hi guys,
Something strange is happening to my zenfone. When I want to switch it off, and I click the "power off" option my phone activates offline mode, then the screen just dimms instead of going full black. When I try to switch it on again, everything is okay except that my phone doesn't vibrate and goes straight to boot animation, there is no loading system circle, phone boots up in 3 seconds. I don't need to enter pin too. When I choose restart option everything goes as normal. Any help is appreciated
Zf5
Not rooted
Android 4.4 kitkat
Gumak11 said:
Hi guys,
Something strange is happening to my zenfone. When I want to switch it off, and I click the "power off" option my phone activates offline mode, then the screen just dimms instead of going full black. When I try to switch it on again, everything is okay except that my phone doesn't vibrate and goes straight to boot animation, there is no loading system circle, phone boots up in 3 seconds. I don't need to enter pin too. When I choose restart option everything goes as normal. Any help is appreciated
Zf5
Not rooted
Android 4.4 kitkat
Click to expand...
Click to collapse
Its a common issue.
Just wipe everything from bootloader, like system, data,cache, then flash recovery.img from .44 update and then reboot to recovery and sideload the .54/.540 update.
everything will be fixed.
Me and my friend faced the same issue about a year and a half ago,and this fixed the issue.
What does 'sideload' mean? Sorry I am new here :v
Hello,
So today I woke up today to find my device stuck in the google text bootloop, did a quick search on how to fix it and found this guide : https://www.xda-developers.com/nexus-6p-bootloop-fix/
I did everything and I guess it worked correctly, except the fact that now my bootloader being unlocked I stumble upon the "your device can't be checked for corruption" error, and so I'm stuck on another different bootloop. Locking the bootloader fixes the corruption error but I'm back to my previous google bootloop (even if I flashed the image that was in the guide).
So whether the bootloader is locked or not I'm stuck on one of the two bootloops (by the way I tried flashing a factory image after that but didn't fix the google loop).
Is there any way I can fix it?
Thanks!
Keagghan said:
Hello,
So today I woke up today to find my device stuck in the google text bootloop, did a quick search on how to fix it and found this guide : https://www.xda-developers.com/nexus-6p-bootloop-fix/
I did everything and I guess it worked correctly, except the fact that now my bootloader being unlocked I stumble upon the "your device can't be checked for corruption" error, and so I'm stuck on another different bootloop. Locking the bootloader fixes the corruption error but I'm back to my previous google bootloop (even if I flashed the image that was in the guide).
So whether the bootloader is locked or not I'm stuck on one of the two bootloops (by the way I tried flashing a factory image after that but didn't fix the google loop).
Is there any way I can fix it?
Thanks!
Click to expand...
Click to collapse
The corruption error you get from unlocked bootloader is nothing to worry about. It should resume after the message is displayed. Unless it pauses then you can resume by pressing the power button .
Exodusche said:
The corruption error you get from unlocked bootloader is nothing to worry about. It should resume after the message is displayed. Unless it pauses then you can resume by pressing the power button .
Click to expand...
Click to collapse
Well the problem is just that it goes into a loop, this message into google text into this message into google text etc
I'm still stuck in a bootloop except that instead of only having google text switching into black screen it's now google text switching into corruption error :/
Keagghan said:
Well the problem is just that it goes into a loop, this message into google text into this message into google text etc
I'm still stuck in a bootloop except that instead of only having google text switching into black screen it's now google text switching into corruption error :/
Click to expand...
Click to collapse
You will just have to try the bootloop threads an hopefully something will get it working. However even if you do phone will be slower maybe time for upgrade.