Yesterday I was listening to a podcast when it suddenly stopped and my earbuds disconnected. The phone appeared to be dead - nothing happened when pressing or long-pressing the power button, and the screen would not turn on. After getting home, I found out it's not completely dead because my PC recognizes it if I plug it in. However, some of the settings seem to have been reset since I no longer have ADB access or bluetooth pairings. It seems to be connected to wifi tho.
So... what are my options? I would like to recover what I can from the storage. The only thing I can think to do right now is let the battery run out (it's not like I can turn it off anyway) and see if anything changes.
Stock ROM, T-Mobile version reflashed to International + Magisk 24.3
Well, today I plugged it into my PC, pressed the power button for a few seconds, and it booted up normally. No idea what happened.
I just had a similar thing happen to me as well. One minute everything was working, then bluetooth started being really weird (connecting and then disconnecting). I told the phone to restart and then nothing. Didn't respond to the power button. Finally, I was able to get into Fastboot and then recovery. From there it was then able to restart normally and I haven't had any issues since.
Related
ok so here is the rundown
Device: HTC one on vzw
Rom: Slimbean 2.x
Gapps: Slim AIO gapps
had a weird problem with the display today if anyone has had this or know someone who has i would greatly appreciate the help. I just flashed Slimbean 2.x last night and all was good. no problems what so ever, got everything setup and was working fine. this morning around 10am i opened snapchat to view a video. i clicked on the video and as soon as it started the screen went blank and would not turn on. i tried holding the power button down for at least a minute and nothing. also tried power and volume down, power and both volume buttons, power and volume up and still nothing seems to work. when i plug it into the wall charger the red LED light does not turn on and screen does not wake. when i plug it into the computer the computer does not ever read the device and noting pops up letting me browse the files on the phone. i have no clue why this happened it has been working fine for the 3 months that i've had it. took it to verizon about an hour ago and they didn't know either but they are sending me a replacement htc one. all i really want now are my photos that i have on the phone.
does anyone have any ideas about what i could do?
thanks
I had something similar and think it was conflict related. After installing the "advanced power menu" with xposed, I had an issue when trying to use it to boot into recovery. Basically it had timed out and then went away without rebooting. The next time I tried it locked up and my screen went black. My keys would light up if I clicked on the power button (it was dark in the room so the sensor was still working), but nothing else. Nothing I did would make the screen turn on at all and holding down the power key to reboot did not work. I just planned on letting the battery die out. After about 45 minutes, the phone just rebooted and everything was back to normal. I really think it locked up due to a conflict similar to what a PC might do.
I was getting a notice on boot that said "Your device is corrupted and cannot be trusted," so I held down the power and volume down buttons to get it to fastboot mode. However, I couldn't get it to be recognized in fastboot on my laptop. At one point I selected "reboot bootloader" and the phone promptly shut off, black screen and completely unresponsive.
From that point on, I can't get it to do anything. I've tried holding power + volume down for 20 seconds and then plugging it in (as noted in another thread) as well as taking it apart and disconnecting the battery to see if that would reset it somehow. No dice.
Any other suggestions before I give up? Thanks very much in advance...
olm3ca said:
I was getting a notice on boot that said "Your device is corrupted and cannot be trusted," so I held down the power and volume down buttons to get it to fastboot mode. However, I couldn't get it to be recognized in fastboot on my laptop. At one point I selected "reboot bootloader" and the phone promptly shut off, black screen and completely unresponsive.
From that point on, I can't get it to do anything. I've tried holding power + volume down for 20 seconds and then plugging it in (as noted in another thread) as well as taking it apart and disconnecting the battery to see if that would reset it somehow. No dice.
Any other suggestions before I give up? Thanks very much in advance...
Click to expand...
Click to collapse
my device is for the most part of the time in qualcomm mode, but I managed to have access to the phone 3 days ago, installing apps & stuff, worked perfectly well until I had
the bad idea to try to charge it through the charger instead of charging it through my computer...
how I've done it?
I used the power reboot technic :
1) pressing the power button for 1 minute
2) doing nothing for some seconds
3) pressing the power button again for 1 minute
4) connecting the phone to the charger, the red light flashed
5) the battery icon appeared soon after
6) waiting for complete charge, phone rebooting
it worked once, so I suppose it can work again. fingers crossed.
I have a Samsung I9250 which I've unlocked, rooted and loaded with Lineage. The Lineage version is 13.0-20171126-NIGHTLY-maguro. The recovery is TWRP and the root is through SuperSU FREE (CM) v2.79-SR3. The On/Off button doesn't usually work. If the phone is off then pressing On/Off has no effect. Occasionally it works for no reason I can see, it seems to be random, but for the most part it simply doesn't have any effect. If the phone is on then the same is true. Turning it off from the On/Off button is usually impossible. I get round this through Settings>Display & lights>Wake on plug. This means I can activate the phone by connecting it to a PC using its USB cable. This will activate the phone immediately if it is off. It doesn't help with turning it off and I am usually reduced to taking the battery out. The phone is effectively useless although it is clearly NOT bricked. When I can turn it on it works fine.
I don't know if this is a hardware or software problem. If it's a software problem I don't know if the fault is in Lineage or TWRP or SuperSU. I noticed that the problem existed before I installed SuperSU. Has anyone else come across this problem? I'm reluctant to bin the phone because I spent such a long time getting Lineage on to it, but, if I can't turn it on or off it's not really a phone. Any help would be greatly appreciated.
@erich_vogt it's more a hardware problem, you can buy a new button (find link of online stores in accessories section or google.it).
for easyness you don't need to plug charge/usb everytime, you can set volume button waker, find in settings > button (don't remember where correctly, it will be somewhere there) then use volume switches to wake it.
erich_vogt said:
If the phone is off then pressing On/Off has no effect.
Click to expand...
Click to collapse
There have been power button bugs, but only in the OS. If it's not turning on from off, then I think the switch is broken! A common failure in old phones, which is why "volume button to wake" is important, to reduce load on the power button.
Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.
erich_vogt said:
Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.
Click to expand...
Click to collapse
3rd dec nightly has problem with booting, get back to older than it.
Reset volume button waker, if it stopped working. I never had problems with volume buttons.
I'd second the idea of it being software. I've had problems with all builds after 20171112. I get the impression there was something overlooked when the developers unified the builds for different GNex variants.
If you still have the phone, try that 20171112 build.
I don't know how to roll back to an earlier build. The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.
erich_vogt said:
The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.
Click to expand...
Click to collapse
Ah, ok. Sorry, I thought you could still do more than that, but it was rebooting and unusable in that sense.
That's well beyond any help I can offer you. I hope you got any data off it.
My VS985 has 2 problems, which may be related to each other. The first is that, when the phone is fully turned off, turning it back on again is difficult. When I press the power button, the phone just vibrates at me and then refuses to turn on. Screen doesn't light up or anything. Pressing the power button again does nothing at that point. What I have to do, sometimes up to 7-8 times before it turns on, is remove the battery, wait a few seconds, put it back in, then press the power button again. It'll vibrate every time, and eventually one of those times it will turn on and boot up.
The second issue is that I've found it impossible to get into recovery mode using the buttons. I can get in just fine using the quick boot app, but that's not much use if I ever end up in a state where I can't boot into the OS. Apparently it's supposed to work by turning the phone off, then pressing and holding the power + volume down buttons and waiting for the LG logo to show up. I've tried this many times, it never works, possibly because of the first problem.
I bought this phone used, immediately used ODIN to downgrade it to the original stock OS, then towel rooted it and installed CM (LOS 14.1 now), so I've no idea if this phone has always had this problem or if I caused it. It's not a big deal since I always keep my phone on but makes trying new ROMs scary. Has anyone heard of this before, or have any idea how to fix it?
Well a few days ago, like 2 weeks ago, I thougt I lost my SW3 (I use it w / o leash because it broke and there's no replacement for the stainless steel one) but actually it was lost on my travel bag xD
After plug in again it started to charge, but when I tried to turn on (after reach 100%), after the sony and SW3 logo, it turns off, like it has a problem at boot. I tried to repair via Xperia Companion and the process was succesful, but the watch just gets stuck on the same SW3 logo.
Now I think is the battery, but I'm really hoping is not, there are any suggestion guys about what could be happening?
Is it stuck at the 4 dots spinning? If So I have the same problem, I have tried a factory reset, updating the rom via push commands etc I have brought a new SWR50 thats working with ADB debugging enabled this time (Didn't do it on the last one) my question hopefully will help the OP as well can I take a complete clone/rom backup from the working watch then push that to the broken watch (Bare in mind no debugging enabled on the broken one) Also to the OP have you held down the power button to get to the fastboot menu and factory reset/recovery settings? if not then you turn off the watch, press and hold the power button until the "insert usb now" shows, you then press the power button quickly twice to access the recovery menus
The Watergod said:
Is it stuck at the 4 dots spinning? If So I have the same problem, I have tried a factory reset, updating the rom via push commands etc I have brought a new SWR50 thats working with ADB debugging enabled this time (Didn't do it on the last one) my question hopefully will help the OP as well can I take a complete clone/rom backup from the working watch then push that to the broken watch (Bare in mind no debugging enabled on the broken one) Also to the OP have you held down the power button to get to the fastboot menu and factory reset/recovery settings? if not then you turn off the watch, press and hold the power button until the "insert usb now" shows, you then press the power button quickly twice to access the recovery menus
Click to expand...
Click to collapse
I forgot about this thread lol
thanks dude!, A couple times it reached the spinning dots, but not always, sometimes it turned off on the SW3 logo before the dots appear, and actually I tried all those things you mentioned, but it didn't work, also I think my watch is (even more) screwed now xD...
Trying to do a second repair on Xperia Companion, the watch got turned off in mid repair, lending obviously on an error, and also losing the ability of do offline charge so once the battery reach 0, is over...
now when I plug in just stays on the SW3 logo, I still can go to connect USB screen and go to the two clicks menu (and stays on), but every time I try a repair, in the middle of the process disconnects and turns off, I don't know exactly why only when is plugged on the repair process it turns off, even pluged in the PC w/o repair stays connected all the time... bad thing is I don't know if is charging or not, so could stop working anytime
Have you tried to push the update through adb recovery mode?
The Watergod said:
Have you tried to push the update through adb recovery mode?
Click to expand...
Click to collapse
every day I'm more convinced the watch is screwed
If I turn on the watch stays on the SW3 logo all the time (it seems offline charge works after all), I even can go to the "insert USB" screen and stays on all the time, but when I try to push something to the watch, always disconnects, turns off and the process obvioulsy gets interrumpted, I'm losing my hopes xD
I'm using the original charging wire, but tried with other working ones
my sister bought me this smart watch , it came on long enough to program a few this after I charge it and then 10 minutes later it shut off and now it won't come back on or power up , what should I do ?
I have a weird problem with my sw3. When I plugin my watch to a charger nothing shows up but the watch gets heated up. But when I connect it to PC it just keeps turning on and off. Tried various methods available on this site but none of them worked.