I've been having a weird occurrence with my Z5 and I'm wondering if anyone can enlighten me as to whether I should be panicking or not.
I unlocked my bootloader, rooted on android 6, installed xposed and a few modules and then installed all of my apps from backups from my old Z2. The phone was working great, restarting perfectly, and I've been adding software to the phone.
I mount a lot of software on my phone and have a 200GB SD card, so I have a ridiculous amount of apps on it(~300 non system apps after debloating).
Recently when my phone has been rebooting it will load to the wavy screen, dim the screen to my brightness setting after it's nearly ready, un-dim itself back to the first brightness setting, then after a moment crash and go black screen. The LED flashes red a few times, then stays solid for a moment before the phone bootloops and begins trying again.
On the second attempt it will usually load correctly though it still does the bright-dim-bright which did not used to occur. If I kill the phone using power + vol up and load again, it doesn't load successfully on the second shot.
What does this LED pattern mean? Anyone with some expertise able to shed light on any of this? Anything would be hugely appreciated!
Related
I have rooted my desire z (about a half year ago) and now I am having a problem.
When I boot my phone my screen stays black during the phase that normally would show that htc logo and white background. And after that colors are weirdly blueish (it goes back to normal after I put my phone to sleep and wake it). Also bootloader is black (I know that it boots to bootloader because when I push vol- and the power it goes to clockworkmod). And clockworkmod is also weirdly blueish. I got this problem when I was trying that unofficial CM9 rom and I have used superwipe, tried several other roms and backups of other roms, but the problem don't go away. Any ideas how to fix this?
It seems that my screen problems change when I open/ close keyboard. So could the cable be a bit broken?
Most probably the cable. If you are still in warranty, take it to be serviced. If not, I'm sure that wouldn't cost much.
Either way, sounds like a hardware problem.
Hi i have this supper anoying problem after 5.0.2 update! So basicaly What it does is when ever i will pick up the phone it would turn off like the screen would dim (not rebbot or shut down) and after a little tapping on a screen it would turn on again and sometimes when it does that it would glitch a little. While typing this it happened twice its sooooo anoying idk what to do now if i wont find any solutions i will just buy samsung galaxy or something like that. Also my carrier is Virgin Mobile thanks
Same problem, same phone.
Definitely annoying! Seems random but especially while rotating for me. I have not been able to dig up any solutions thus far.
Check out your proximity sensor settings in the HTC testing app, or try Gravity screen. Mine did the same thing a couple times, also clean off your screen at the very top left, if you look real good you can see the sensor just under the front camera hole in the glass, also sometimes a screen saver will mess with this sensor. One more thing is the stock lock screen can cause an issue similar to what you are talking about, hope one of these help yo out, cane0716
Sent from my 710C using XDA Free mobile app
hi
thanks for information i already gave that phone to my friend and i think he fixed it by actually having different lock screen i currently have samsung galaxy s5 its wayyyy better lol
Phone turns off during use and will not complete boot unless plugged to charger even when the battery is almost full.
This error started last night after I did factory reset because of observed phone lag. I did mistakenly "wiped internal storage" but got the alert of "no OS during reboot", so I restored from my backup from SD.
the phone started properly but went off during initial setup and will go back off each time I tried turning it back on. I thought it was battery so I plugged it to power.
it did boot but will go back off once I have few touches on the screen.
I had to leave it plugged to setup my accounts else it will go off.
I'm using its Wi-Fi to send this message via my PC because any 2 - 3 touches will switch the phone off.
once it does that, it won’t even boot to bootloader before it goes off again unless plugged to power.
what I do to solve this please??
Hey guys,
After replacing my broken screen and reflashing my M8 from GPe to the original Sense, my screen is behaving a bit erratically.
When booting up, everything works fine. The backlight (if set to auto) will dim and light up accordingly, it can be manually set to different brightnesses, et cetera. Phone is working fine.
Then, when the phone is locked and unlocked using the power button, there is a good chance that it will 'bug out', only lighting up the backlight without displaying the screen. After one or more lock/unlocks, the normal screen will come on and I can use my phone as usual. However, at this point the phone is no longer able to change brightness other than the maximum, and the unlocking bug will still occur most of the time.
I've tried flashing different ROMs, both Sense and GPe, but all exhibit the same problem. Changing the setting in the menus successfully changes the values in the system files, but the screen brightness doesn't change.
I suspect something went wrong with the firmware itself, so I'm trying to downgrade the phone to an official build, and work my way up from there.
- Does anyone recognise these issues or have any idea what may be causing this?
- What is the best way to ensure firmware files are re-flashed on a S-ON phone?
I tried logging the console from boot to the moment the error occurs, but haven't been able to make much sense of it (or even find the breaking point, it spits out log rules too fast!). Can add it if anyone is interested.
Thanks in advance!
There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Gnatcatcher said:
There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Click to expand...
Click to collapse
Maybe replace battery?
Hi there! I am not sure if your problem was fixed yet. But my Pixel XL died yesterday and did the same exact thing. It went into an infinire boot-loop, and after trying many times to power off and reboot, some weird artifacts appeared.
I think I messed up the phone, because at first the phone booted and then restarted, but now it just restarts and never ends....
EDIT: After some hours of rebooting, and more artifacts, the Pixel finally booted on android. Battery was at 4% so I guess that helped. It keeps rebooting from time to time, but at least I can copy my photos now haha.
Hello,
My wife's Sony Xperia XZ2 Compact with model number H8324 has an issue with booting or maybe the launcher getting stuck in a loop after getting to the lock screen for a split second.
The phone seems to boot like normal and gets to the lock screen, we are even able to punch in one or two digits of the 4 digit pass code. Then it goes into a loop of the notification bar and back button flickering. From then on the phone is not responding except for the power button which brings up the normal "Turn off, Reboot, and Lockdown" menu. The issue just started out of nowhere yesterday morning and we haven't been able to fix it yet. We haven't done any rooting or custom rom flashing, it's running the official Sony software but it's out of warranty.
Here's a video showing the issue. The video shows the whole boot process but the link takes you to the last part after the logos.
We would love to get some files off it so if there is a way anyone can help us with that we'd prefer it over a hard reset.
Things we've already tried
Turning the phone off and on again
Unlocking the phone in the split second the lock screen works, this is just too short to swipe up and then put in four digits.
Rebooting the phone
Booting while charging
Booting into safe mode (this has the same issue)
Connecting the phone with USB to a pc, the phone is recognized by Windows, but it doesn't share it's filesystem with Windows.
Connecting the ADB to it, alas usb debugging is not yet enabled on the phone
Trying to get into recovery mode, we haven't been able to get into the recovery menu. Googling seems to indicate it might be holding volume up + power button when the phone is off but then it doesn't seem to do anything at all.
We're currently trying to run out the battery of the phone to see if that will resolve the issue on it's own.
If anyone has any idea, we would love to hear it.
no solution from me. But I have exact same problem and tried same things. Yesterday I did not used the phone. Day before shut down, today tunred it on and it starts with the issue. Strange it happens to both of us at the same time frame. removing sims did not help either.
By holding down "volume down+power" I was able to boot in safe mode but the same issue occur; no way to get into the phone.
Yeah that's weird. Draining the battery did nothing for us. There was not much data that we wanted to extract from the phone. Most of it was contacts and an emulated Pokémon game save file. So my wife eventually reflashed the OS with Xperia companion which did actually resolve the issue of not being able to use the phone.
I faced the same problem today ,i have xz2 , yesterday it was 24% and today i found it 0% so I put it in the charger ,but I faced this problem