Hi, I started having the strangest issue 2 days ago. Phone model is Samsung Galaxy A50.
I have been unable to unlock my phone once I pressed the lock button or if it went to sleep (screen off).
The only way out of the issue is to restart it by pressing volume down and power for 5 seconds. I put the screen timeout to 10mins (which is the maximum). But no long term solution. Whenever the screen turns dark it stays dark. If a call comes in, the phone vibrates (or ring) but any interaction with the phone is impossible. If I play music, the music continues once the screen is off. The sound can be turned up or down, but it's the only thing that can be done.
While the screen is on, changing the volume via the buttons affects the actual volume of the music, but there is no UI indication that the volume changes, no popup nothing.
So all physical buttons are working correctly.
I have trie "reset parameters", I have tried "reset all data" (backed up everything through Smart Switch). It doesn't change a thing. The phone is reset (still on android 11 though, although I bought it on android 10...) but the issue remains.
Now something very interesting :
Just now, I setup Phone Link for windows 10, so that I am able to see and answer texts and phone calls while at the office. Which works, it sort of defeats the purpose of a "cellular" phone but well...
HOWEVER : while my phone is connected to my desktop through Phone Link. I can lock and unlock at will, change volume and see the UI pop up (via the windows interface or directly on the phone, same behaviour) It's basically fixed. I thought it was fixed for good, so I disconnected my phone from Phone Link. The screen went black as before and there was nothing I could do except reconnect it via Windows 10 (then it immediately starts behaving as usual again...).
My guess is it's definitely software. I just don't understand why a factory reset didn't do the trick...
I wanted to try and reset through the bootloader, but I never managed to effectively get into the bootloader (through volume up and power while the phone is off).
I do not recall making any updates or installing anything just before these symptoms occured. I did install a firmware update that was available after these symptoms started but to no avail
Has anybody seen this before ? Thanks in advance
Related
So I've had my fuze a little over a year now, no major issues. Used mostly energyroms, but about December time I switched back to a simple non-bloated stock rom for the stability.
Anyway today at work I was texting, and I press the power button to put the phone in standby. And the screen remains on and usable. I tried again and it would not go into standby (power button physically feels normal, it does not feel loose or abnormal.) So i let it sit for a few minutes, then i look at it and a message poped up asking if i wanted to turn the phone off (like as if i was holding the power button)so i press no, then it comes up again a few seconds later and aagain and again. So I soft reset the phone.
The phone resets but takes a LOT longer at the att/htc splashscreen, then it hangs at the htc screen and does not make it to the wimo screen, but instead an error screen saying:
"The device is unable to boot because you have either turned off the device incorrectly or tried to install an applicationa from an untrusted source, press SEND to reset your device or press any other button to cancel..."
I think it went through the hard reset this time because when it restarted it asked to calibrate the screen and install stuff. it resets again sometime after that, still takes forever at the splash screen and comes back up to the error, only this time no matter what button i press it wont go away and boot into wimo. It seems like none of my buttons work (they wont light up now) when i slide out the keyboard, it is not lit up like normally.
And heres the kicker, my only way to turn on/off the phone is to take out/put in the battery. As soon as I pop the battery back in the fuze turns on. Is my phone toast? Ive tried to hard reset and the phone does not reach the bootloader, it goes straight to the splash screen. Same with trying to reflash it from my comp, raphealwrapper cannot find my phone.
I've only recently encountered the exact same problem on my Touch Pro, but stock ROM and everything. As far as I can tell, our power buttons are busted and probably need to be serviced. One of the contacts must be stuck in the 'on' position somewhere inside :\ As a temporary fix, I've been using AEButton Plus and remapped double tap end call key to turn the screen off, and removing the stylus to turn it on.
Device: HTC One M8 running Liquid Smooth from may 13th.
This is rather odd - All day, my phone was working just fine. As I was listening to some music (through the speaker... or should i say speakers boomsoundhighfive:highfive, I pushed the power button to unlock the phone to text somebody, except all I could see was the music app (apollo) in the background with a dialogue saying that android system UI has stopped. Every time I hit "ok", it popped right back up. I'm assuming that that was because it was trying to restart, and it just kept crashing.
A bit later, it was still doing the same thing when all of a sudden I could no longer turn on the screen. However, my music is still playing, and I can control the volume with the vol buttons. The only other thing I can do is double tap the screen to get a bit of hepatic feedback from double tap to wake. Also, the low battery notification LED is now flashing, as it was at fairly low battery when this started (around 30, it's been about 45 minutes since this started).
I can't reboot through ADB as usb debugging isn't on, and I tried holding down the power button for about a minute with no luck.
Anybody got any advice? My current plan is to wait for it to die and hope it reboot normally... Otherwise I might boot straight into recovery and restore a nandroid...
Alright, sorry for creating this thread - it died, I plugged it in and turned it on. It appears to be completely working. Anybody know why this would happen? It seems a bit odd.
Suspected problem: Bootloop
It all started when I connect my phone (Garmin-Asus A10 (v5.0.82 (updated with GarminAsusPhoneUpdater_Telenor_v2.0.3.exe of denmark))) on laptop through USB cable, the USB slot looks slightly damaged already upon looking at it, after connecting the expected to be happen is that the back-light will turn on, but what happen is that the phone has no response from it, I try to press the power button still no response, I removed the battery and bring it back and try to turn on again the logo appears (without vibrate which is supposed to be present in turning on my phone) then disappear after 7-10 secs.
It's already stock on the logo as I turn it on, the moment I pressed the power button the logo appears for about 7-10 secs then it disappear, also when I removed the battery and put it back the logo appears without pressing anything and disappear again after 7-10 secs.
I try to wipe the data through Volume Up + Volume Down + Power Button the ** WIPE USERDATA ** appears but then after a few secs it disappear again which is supposed to last for about a minutes.
And also I still can go to the **USB POLLING MODE ** through Volume Up + Power Button but seems like there is nothing to do with that thing.
I know it will be easy to fix this with the use of Garmin-Asus phone updater but it requires the phone storage which is so impossible to access at this point.
Hope you guys can help me with this, I badly need that phone.
----
Updates:
I can already open the phone and go to the home screen and menus... etc., but only when I close/cover the 1st metal/copper of the battery (back view (- to +))., but then I get an error saying that "The installed battery is not compatible with this device"
Upon doing this the phone is keep on rebooting, even if I already turn it off it keeps on turning on by itself, also I can't use any network at this point.
I already formatted the phone using master clear & **WIPE USERDATE** (Volume up + power button) still got the same problem.
And also updated with 006-B1243-00.update (The last .update file I used to update my phone (V5.0.82 DN)), upon rebooting after verifying the .update file it just blink twice then the update stops already at that point.
Updates 2:
Physically there is nothing wrong with the phone, I can still use the phone but as I mention already "only when I close/cover the 1st metal/copper of the battery (back view (- to +))." everything works fine except for the error "The installed battery is not compatible with this device" the red with "X" battery (Screenshot-1434948958913)
Also I notice something from my storage the "System Volume Information" (Screenshot-1434949331146, Screenshot-1434949336619, & Screenshot-1434949345666), I'm pretty sure that I haven't seen yet that before, I deleted the folder still it comes back.
Also once I connected my garmin phone to my computer the USB connected thing (Screenshot-1434949876071) don't disappear just until I restarted the phone.
Thanks in Advance.
Pixel 2, unrooted, stock, locked bootloader.
I was providing power to another pixel 2 far from a power outlet. After ~15 minutes, the phones were behaving fine. After I ate (about 45 minutes later), I unplugged the phones and my phone (the one providing power) had a black screen that would not turn on (there is no screen cover; i've heard of those causing issues with the head sensor and turning the screen off)
At first I thought the device had been drained, but the fingerprint sensor responds with the normal haptic blip. If I press the power button right afterward, the fingerprint sensor used to also flash the screen veeeeery slightly, as though it were off and being turned back on, but it no longer does that.
Troubleshooting steps so far performed:
held power button for >30 seconds: causes a long haptic blip that repeats itself every 30 seconds. No other response, and the phone acts like it's off; it no longer does the short blip on fingerprint sensor use (how I get it "on" again is a bit of a mystery, as there's no haptic feedback to represent turning on; probably something I do "boots" it silently and it starts haptic blipping once that's done)
held power button and vol.down at the same time: results vary based on whether it's "off" (after 30 sec power press). If off, nothing happens. If on, after 30 seconds I get the long and the short haptic blips in sequence.
tried to connect pixel buds to it to see if assistant would talk to me. pixel buds wouldn't connect.
charged for 20 minutes and then performed the steps above.
did NOT try calling it before I switched my sim to an older back-up device and now I can't re-activate it on the dead phone to try that.
Still no dice. Dead-seeming phone. One thing I was wondering about... I've noticed when these 2 phones are touching (stacked), they prompt some kind of linking or sharing (well, they don't NOW but they did when they were both alive). Is it possible that my phone offered to cast to the other phone and my leg confirmed while it was in my pocket? Surely it wouldn't continue to cast after being restarted? (this is a reach but it's all I can think of)
Recently discovered the alarm is still set. It went off at 7:15 this morning (correct time), but NOT with the alarm ringtone I have set. So either some settings are wonky or... maybe it's unable to mount the storage filesystem? I can either turn it off by holding the power for 30 seconds or by turning the volume down (volume keys still work)
I'm traveling with a mac right now but when I get back to a PC, is there any chance I could get somewhere with something like ADB (without wiping the device)? I might need some specific steps as I usually only tinker with scripts like wugfresh's.
Google wants to send me a refurb but the device is only 19 days old and I'd rather have a new device when I paid for a new device.
Thanks!
Don't want to quote all of that, so I'll just say that you can download the Mac version of the tools, download the latest factory image, edit the flash-all.sh to remove the -w, so you don't wipe userdata, and then just run the newly saved script. But, you do have to unlock the bootloader first.
DuckRuckus said:
you do have to unlock the bootloader first.
Click to expand...
Click to collapse
Thanks for the reply. I'm back home so I can use my PC now... but I haven't unlocked the bootloader, so I gather I'll lose all my data if I unlock it? Is there any way to extract data without being able to enable data transfer mode on the device?
Also, if I can't get a screen, I can't boot to fastboot or recovery... Will I be able to actually do anything at all?
Hi, I am facing with a very weird issue. If I locked phone by pressing power button or waiting until time out, the phone can not be unlocked. The phone it self not freezen. If I turn on music, it plays even after screen is locked, I can volune down and up. But the screen is not back on. I have to hold power button to force phone restart. The phone is working fine until screen is off. No application is installed and I have tried to do factory reset. Also, I have tried to enter in safe mode and nothing helps, the result is the same. Maybe somebody had same issue and fixed it. Or could direct me on the right path where should I look. Thanks in advance.