Strange, I had to get a replacement Pixel therefore I had to reset my watch. When I tried to reconnect the watch would not generate the patient code. So I factory reset again and same issue. So I flashed the stock image and same issue. So then I flashed the preview image and finally got connected.
Now it won't charge when the OS is booked all the way. As soon as it goes up one percentage it just stops charging. Now here is the most strange part... It will charge while it's being factory reset and booting for the first time.
Has anyone seen any of these issues?
Never heard of anything like that Does it charge when Powered Off? Maybe try Neg's custom ROM...
Charging it causes it to turn on.
Strange, I flashed back to the factory stock image and its working fine again.
Related
My friend has a completely unrooted, stock Evo. I'm not sure about the hardware version, and I hope it doesn't matter.
They were texting and using navigation with the phone plugged into a car charger, when it turned itself off and now won't turn back on. After a battery pull, it'll boot to the splash screen, but then shuts off again. After that, it doesn't boot at all.
I've tried getting it into fastboot, but I'm not incredibly familiar with the Evo. So far, no luck.
I have a rooted Incredible, so I've tried all the little tricks I've used to fix my phone.
So, any ideas? Bad hardware, bad software? Get it replaced?
My last Evo (I'm on my third one) was unrooted & would do something similar. At first it would just reboot itself, but then the screen would freeze & flicker and I would have to pull the battery then try to boot it up. Sometimes it would take 10 or so tries, but after it would boot up it would eventually do the same thing. At first doing a factory reset would fix it but then that stopped working.
If it's similar to my issue then it will have to be replaced. If your friend has insurance then they'll replace it for free since it isn't user damage. Until they get a replacement, try booting into fastboot & selecting reboot from there instead of just powering it on. That worked for me a few times.
I had tried the fastboot reboot, but it wouldn't even get that far.
Turns out, the navigation and texting had drained the battery faster than the car charger could charge it. After a full charge overnight, it's booting up fine. So it was fortunately a very simple problem.
Thanks for the reply, though.
Sent from my ADR6300 using XDA App
I have read the other posts regarding the rebooting issues of the Sprint Galaxy S3 variant, but I seem to have a touch more difficult problem. My phone constantly resets and seems to be getting worse. It now will reset in the middle of recovery. I was able to wipe the cache and dalvik and then it started resetting even more frequently in recovery and made reloading the rom impossible. It even resets in the download screen. So it makes it impossible to use Odin and other applications. If anyone has any ideas let me know. I have a few possible options that I am pondering. The following is what led up to this if you need some background:
A week ago, I noticed that my battery suddenly was not charging when wifi was on. I turned it off thinking it was some glitch and reset the phone and plugged it in to charge. It said it was at 100 % some hours later. then I turned it back on again and within a couple minutes, it said it was at 22%. So I hard reset and then plugged it into the wall, but it was still not charging. I had go somewhere,so I plugged it into the car charger and enabled fast charge. I turned on my data and all the sudden it rebooted, lost my wifi password, but when it came back on, it was charging properly. So I thought it was just some odd glitch. Charged properly for days.
Then I noticed the phone starting to randomly reset maybe once very other day when texting. I was actually going to put on a new rom tomorrow thinking maybe my old one had become corrupt. Then it suddenly increased drastically tonight to where it was starting to reset constantly. I thought maybe the button was stuck, and pulled off my otter case to make sure it wasnt being pressed down oddly, but it continued. Then I went into recovery and was able to wipe the cache and dalvik before it got really bad and now it won't even let me stay in recovery for any length of time. I almost got a rom loaded when it reset and its been resetting faster than ever. Becoming unresponsive to button presses as well. Even when I could get into the recovery, it would keep showing "swipe screen to open," as the power button was apparently continuing to activate or the phone was trying to reset itself. And yes, I have tried a battery pull several times and then tried to get into recovery, only to be booted out right as I see the recovery screen if I get there.
So that is my problem. I can't flash odin or anything else as the phone just keeps resetting. Part of me thinks to get a new battery and try to see if that doesn't solve my issue, as maybe the battery is causing the phone to reset? But part me is also thinking maybe the power button has gone sticky suddenly? It won't charge it seems as the red light will not come on and it keeps resetting before the battery charging icon can even come up. Any help or advice would be appreciated. I am leaning towards the battery going bad suddenly and shorting out the phone. I now have the battery, which last I saw was at 48% (It was charging when this happened), out of the phone and am waiting till morning to hopefully pick up a new battery. But I would appreciate any insights into this issue.
Thank you very much
Same issue
I'm having the same issue described above with the S3 constantly rebooting. I can get into download mode but it restarts a few seconds into the flash. I have tried a different battery but that did not solve the problem - I am also thinking it's a power button issue... any suggestions?
mawamd said:
I'm having the same issue described above with the S3 constantly rebooting. I can get into download mode but it restarts a few seconds into the flash. I have tried a different battery but that did not solve the problem - I am also thinking it's a power button issue... any suggestions?
Click to expand...
Click to collapse
I just had my phone replaced for same reason ( Thank god for insurance) Download mode would last about 5 seconds, Recovery would do the same. I managed to get a stock restore with flash counter reset to boot as i was walking into the Sprint store for the techs to look at this lol.. Same exact thing happened on my S2. Power button is done. If you have INS call and get it replaced (Took me about a week for new phone)
I read some post on possibly using Samsung Kies to flash a new ROM, but that was for the international version. I would be curious if anyone has ever tried this or if its possible to replace the power button with a part replacement? I have ordered an S4 but this time I will make sure to use the home and left touch pad more often to unlock the phone and save wear on the power button. I wold still be interested f anyone has found a fix for this.
mawamd said:
I'm having the same issue described above with the S3 constantly rebooting. I can get into download mode but it restarts a few seconds into the flash. I have tried a different battery but that did not solve the problem - I am also thinking it's a power button issue... any suggestions?
Click to expand...
Click to collapse
So after looking around, I am pretty convinced this the power button,as people describe on this question. If you don't have insurance, I see there are selling replacements or you can pay someone to replace and fix the power button fairly affordably on ebay. I might go the second route, as I want it fine right and the man had a 100 percent rating positive, and I dont really know what I am doing lol. Thanks everyone for your answers.
Having issues with factory reset on my watch. When I go to the unpair option and say yes to factory reset, it acts like it's going to do the reset but then just kind of shuts off or goes unresponsive. Throw it back on the charger and it boots up like it was just powered off. What am I missing?
agentfazexx said:
Having issues with factory reset on my watch. When I go to the unpair option and say yes to factory reset, it acts like it's going to do the reset but then just kind of shuts off or goes unresponsive. Throw it back on the charger and it boots up like it was just powered off. What am I missing?
Click to expand...
Click to collapse
I have the same problem too!
I've tried the reset multiple times, battery is always at 100% when trying. Getting very frustrating. Any ideas? Google has not been helpful.
Just says "Resetting, please wait" then "Restarting" then goes black until I dock it again, at which point it boots back up like all I did was reboot it.
Any help at all here?
I was having this problem... so I fully charged it and while it was turning off, I threw it on the charge also and it worked..
gd6noob said:
I was having this problem... so I fully charged it and while it was turning off, I threw it on the charge also and it worked..
Click to expand...
Click to collapse
None of that is working for me. It just turns off when trying to reset while at 100% battery.
I think this watch is just broken. I had it off the charger and when I re-docked it and it turned on with 54% battery. 5 mins later, it was at 100%.
I have the exact same issue :/
Still unable to factory reset this..
So, finally got this reset to happen...now ~30 minutes after the initial setup has finished, the watch battery is dying while on the charger. Thoughts?
It's (kinda) charging now. I just have no watch faces to pick from. Not really syncing.
I had the same problem - after multiple tries it worked.
After several days of waiting, I still have no ability to pick watch faces from the Android Wear app. Thoughts?
Moto 360 first gen. reset
The trick is to un-pair and reset it while is charging. good luck!
RD
Hi,
I'm wondering if there's anyone else who is facing this problem or I'm just unlucky.
On last Sunday, when I was listening to YouTube Music at a low battery (around 15%), after a while the phone shut itself off. I guess it was just the phone ran out of battery so I tried to charge it. But the moment I plugged in the charger, the hidden emergency flash light in the front turned on (the one on top right). When the phone successfully booted up, an application called CQATest appeared with a notification. The phone won't charge and take SIM card anymore since then.
I've done some research and tried many methods to fix it, including reboot in the recovery, factory reset, using adb to change boot mode, reflash the rom, disabling the CQATest app. None of them could solve my problem. Disabling the CQATest app does let me to have signal again, but I still cannot get the phone charge. It shows Turbo Power connected, but not charging.
Is there anybody facing the same issue, or even better, have a solution?
Thank you.
Update: I found a solution for this. I put my phone to fastboot mode and charge it from there, overnight. Next morning, it's working normal again.
You can always try a custom ROM. And make sure to format every partition in TWRP before - format, not just wipe.
If that works you can try other stuff. If not you have a hardware issue is guess and only a phone repair could fix that.
PS: try a different charger. If it's only not charging it might be an issue there. And have you tried to charge it while the device is shut down?
Artim_96 said:
You can always try a custom ROM. And make sure to format every partition in TWRP before - format, not just wipe.
If that works you can try other stuff. If not you have a hardware issue is guess and only a phone repair could fix that.
PS: try a different charger. If it's only not charging it might be an issue there. And have you tried to charge it while the device is shut down?
Click to expand...
Click to collapse
Thank you for your reply. Yes I did try another charger. However I'm using a Qualcomm qualified charger so I don't think that's an issue. I brought it to UbreakIfix and they told me it's a motherboard problem so the only way to fix it is to change the motherboard. It'll cost a phone to do that. I'm just wandering if there's any body else who is having the same issue. Because my problem appeared out of no where.
That's normal. Hardware problems often appear out of nowhere all the sudden. And it's always hard the really on them down to a source.
And yes, repairs for not typical phones are always expensive. On my first Z Play the screen cracked. Seeing the price of a repair and realising I could get an unused Z2 Play for the same money you can guess what I did. Can't say I regret it too much.
The last two times I allowed my phone to charge fully, the phone locked up (would not come on when the power button was pressed) and I had to do a soft reset (hold the power button for 30 seconds). This happened on two different chargers with two different cables (one of which is the factory set). Thus, the issue is almost certainly not hardware related.
There have been no changes to my phone, no newly installed apps, etc. There have been a number of app updates, including several Google/Android core apps, and I am wondering if one of those could be the problem. (After the first time the phone locked, I updated the kernel to the latest version, i.e., PQ3A.190801.022. Note also that the phone is rooted with Magisk.)
Has anyone else experienced this problem? If so, what did you do to resolve it? What can I do to try to figure out why this is happening?
groston said:
...What can I do to try to figure out why this is happening?
Click to expand...
Click to collapse
Try replicating it in safe mode to rule out 3rd party apps.
I'm having the same issue the last 2 weeks. I haven't updated any apps and I have auto updates off. No changes to my phone since the end of august and it just started doing this.
Were you able to figure out what was causing it? My issues occur using a 5W Qi charger. So it is definitely not cable/charger related.
Sorry to report, but I have no idea. Since having posted my question, my phone has been behaving properly.
I've got the same issue on 10. I put my phone on a pixel stand at night and when I wake up I have to do a soft reboot to get the screen to turn on. Reverted back to Pie and the issue went away. Flashed the Oct factory image for 10 including wiping data and the issue returned. Booted into safe mode last night. Woke up this morning and had to force a reboot to get the screen to turn on.
darkstar73 said:
I've got the same issue on 10. I put my phone on a pixel stand at night and when I wake up I have to do a soft reboot to get the screen to turn on. Reverted back to Pie and the issue went away. Flashed the Oct factory image for 10 including wiping data and the issue returned. Booted into safe mode last night. Woke up this morning and had to force a reboot to get the screen to turn on.
Click to expand...
Click to collapse
Weird. I'm still on 9 that was working fine and no update that I know of.
I confirmed the issue with both QI charging and cable charging on my phone.
I've taken to making sure my phone is charged before bed and just pulling it off the charger before going to sleep. Since my phone is also my alarm and having it go unresponsive is no good. Only looses about 3% battery overnight.
Well, not sure what happened but the day before yesterday my phone did it's usual lock up while charging requiring a reboot. Unusually after reboot if I logged on too fast it would immediately shutdown. But for some reason this time it took me 7-8 tries to get in. I haven't updated any apps, changed any modules in Magisk or anything. It just went to almost boot looping.
As soon as I got it stable I popped into Magisk and looked at what modules were there. I noticed I had added Substratum previously, to try and do a dark theme, but apparently I never removed or disabled it. I disabled all the modules and suddenly no more problems. Reboots without shutting down after log in and no longer locking up on the charger.
I removed two audio mods (audio compatibility patch and audio modification library), as well as substratum. Three of 5 mods I had downloaded.
I am currently only have Active Edge Mod and V4A legacy FX for mods and my phone is now working fine. If it changes I'll let you guys know.