Hello!
Around Nov. 11th, I followed on-screen prompts for firmware update (I believe the fall One UI 5.0) on my Galaxy S22. Put in the password I've used since I activated the phone in July to "complete the update" after system restart, but device won't take it and I have only a few "attempts" remaining.
Phone is Verizon, no luck with Samsung Find My Mobile; Google's Android Device Manager won't even _ring_ the phone (it showed the correct GPS location at first, but not after I let the phone die and charged it up again ... tried resetting password from here, but even several soft resets later, it now reads device cannot be reached and shows a generic map with no pin).
I've heard of people soft-resetting until it works, but I don't want to waste more attempts with the only password I've ever used (definitely used the eyeball icon to make make sure I'm typing it in right!). No way to roll back the update or reinstall it? So much data since my last backup :-/
Any ideas for last attempts into the phone before factory reset? Willing to keep trying.
-J
P.S. Was advised to move this post, hopefully I'm in the right channel now. I have pics / video to suppplement post if needed.
P.P.S. Noticing that Airplane mode looks to be enabled, but I seem able to hit WiFi icon and "connect" to home network over it.
This started happening to me today too, I have a galaxy a51 though. I recently updated as well a few days ago.
My pattern unlock worked fine earlier in the day. I put it on the charger and walked away for a while, when I came back the pattern that I've used for a long time no longer works. I've tried so many times it keeps locking me out in increasing increments of times... now it's counting down from an hour.
Soft resets did nothing, I tried many times. I don't have find my phone enabled or a samsung account linked, my google account is linked but unfortunately google forced me to set up 2FA a while ago so now I need my phone to get into that too!
The only other thing I've seen mentioned as a fix is to let the phone die completely then recharge it and see if it will accept the pattern. Mine is at 60% right now so it's going to take a while. I also don't want to factory reset as none of my data is backed up, unfortunately.
I feel like the update has to be related to this problem too. I've had several problems since doing that update and never had any of these issues prior. Did you ever figure anything out with yours?
Related
My tablet recently began entering a locked blue screen state devoid of text or icon. It holds there for one to three seconds and then reboots.
Prior to the start of this rebooting sequence trend I downloaded and installed the stock ROM listed on my signature, hoping that it would alleviate some issues with delay in screen tap response, some occasional heating during gaming along with what I perceived to be a little bit of driver related lag.
I haven't figured out when, why, or how it decides to reboot. But as far as I can tell it seems to be related to [behind the scenes machinery of] Google Play (GP). I suspect this because it has happened when I've launched GP or GP tried to do some updates or software installation.
Incidentally, though possibly unrelated, when I try to add an account via settings, at the sign in page, the device returns unable to sign-in message citing connectivity issues. I am in China, so I suspect this could all be related. To get around this issue, I log into a VPN service. This allows me to sign in and add the account to the device. However, in order to play any games, I must log off the VPN. But once the account has been added to the device, it more-or-less is able to access some of the Google services (at least the ones not outright blocked -such as drive and YouTube).
In my troubleshooting attempts, I have thus far done a cache wipe and factory reset from the boot menu. All to no avail.
At this point I need to live in constant fear of a sudden reboot, for I know not when it will strike next.
I would appreciate some suggestions on either what the issue might be, how to determine the cause, or how to solve it.
Thanks
Funny story...
So Kitkat has been released, for the TGY country code.. Yay!
P605ZSUCNE3_P605OZSCNE3_P605ZSUCNE1_HOME.tar
Is the md5 file to be put into the AP slot of Odin 3.09, for my tablet.
I was excited thinking this would address the issue.
Prior to flashing the ROM I factory reset from within the settings, then I went into the recovery boot menu and there I wiped the cache and did a factory reset once more.
Then I proceeded to setup and sign into my Google account, after flashing the ROM.
Naturally the tablet went ahead and started downloading and installing apps and updates from Google Play.
I was happy to see that it was progressing along swimmingly.
The screen dimmed down and then shutdown after period of inactivity (while downloading and installing apps in the background).
Occasionally, I'd click the home button to see tat everything was going as it ought.
I then noticed the screen turned black somewhat suddenly, without dimming first.
I thought little of it.But I went to check by pressing the home button... I figured maybe there's a little lag or the tablet is too busy installing, so I clicked the power button. Nothing; no response.
The tablet is deader than dead.
Now I don't know what to do.
After waiting a while, under the advisement of another user who apparently has also been having issues with his note 10.1 2014, I decided to try to long press the power button. The tablet came back on, and resumed downloading and updating from Google.
But now the tablet is going into this sudden blank blue screen and most of the time rebooting on its own (occasionally it needs a little help, by the pressing and holding of the power button to induce the reboot) ever so randomly. I have found absolutely nor rhyme nor reason for when or how it decides it's going to reboot itself. It tends to happen often if/when I launch some apps that require logging into Google services; but at times it happens without provocation -at all.
Recently it's been boot-looping -without the launching of any app... just from turning on, sitting idle, and then rebooting. But I'm no closer to figuring out how to consistently induce the reboot, either.
My tablet has never been rooted (and for obvious reasons, never will be), no custom ROM, no ROM from another region. Nothing that would give Samsung the excuse to void my warranty (not that it's worth much, here in China).
And yet, it still reboots at random intervals for no immediately apparent reason.
In any event, if anyone has any ideas on how to proceed, any suggestions on what to do with this POS, I'm open to suggestions.
I'm interested in general ideas such as take it to the Samsung shop (something I'm loathe to do because Samsung has terrible service -especially in China- and at best I'm looking at a month or something like that before I get it back), so some ideas on how to discover when/why/how this rebooting sequence is being triggered -and maybe troubleshoot it is slightly preferable.
Hi gang, got a bit of a strange one here. had my G3 for about 15 months so far, and save for having to send it back after a few months for something i cant remember, its been a great phone until tonight when for some reason, it has decided to not connect to wifi or bluetooth. I have tried rebooting numerous times, and still the same. I have ran a factory data reset and still the same. When i factory reset the device, i tried to connect to the wifi however the phone simply rebooted and carried on rebooting until i took the battery out. If i get into the OS on the phone, and try to turn wifi or bluetooth on they simply say turning on, but never complete the turn on and seem to get stuck. My phone is an unrooted phone as i need it for banking apps that wont work due to the root.
I have searched on the net and have noticed numerous pages about this yet nobody appears to have a solution for it. i am going to give Three a ring tomorrow and organise the phone to be returned, but im just curious why this has happened? any ideas?
Same here, waiting for marshmallow official update, hope will work
Hi everyone,
I'm having serious problems with my Wi-Fi on my Samsung Galaxy Note 3 Neo (SM-N7505). Whenever I click the button to activate the Wi-Fi, the icon goes from grey to a dull green (darker than the bright green which signals that a function is turned on), as it does when it's trying to turn itself on. Problem is, instead of turning on, it just stays in that state for a few minutes before reverting to grey. This has gone on for a while, and I've already tried several possible solutions which I found after online searches. I don't think it's a hardware issue (see point 1 for the reason), and I really hope it isn't, because my warranty has been voided due to rooting, so I can't have my phone replaced or repaired unless I pay for it (which I can't at the moment). So, I'm basically ignoring the possibility of hardware failure and trying every possible software solution, hoping one of them will work, otherwise I'm just stuck with no Wi-Fi. These are the fixes I've tried:
1) Take out the battery while the phone is on, wait a few seconds, then put it back in and boot the phone up. This used to work when the problem first presented itself a few months ago (which is why I don't think it's a hardware issue), and I've been since using this method to fix it whenever it happened again. But a few days ago, this method stopped working for whatever reason, so I was back to square one.
2) I tried renaming the data/misc/wifi/wpa_supplicant.conf file, which seems to have worked for some people, but not for me.
3) I tried updating the version from Kitkat to the recent Lollipop, hoping that would fix it, but nope.
4) I tried deleting practically every single app one by one, hoping that one of them was interfering with the Wi-Fi somehow, but nope.
5) As a last resort, I tried a factory reset, but not even that worked.
This is basically the long and short of what I've tried to fix this... I might've skipped a few of the simpler fixes I tried (for example, I just remember I tried disabling "Smart Network Switch", which seemed to do it for some people), but the big stuff is all there.
I'd really like to get my Wi-Fi back, so if anyone could help me fix this thing I'd be really grateful!
Thanks in advance to anyone who will bother to reply.
same problem dude
Same problem...wifi and bluetooth not working...pls help us
Same Problem for me, Initally it works fine even after updating Official Lollipop update (OTA), but after few months now wifi & bluetooth are not working for me. And finally faced battery drain issue for past few days. Battery goes down upto 20% per hour even in idle condition. Then i rooted & installed Note Rom & even after i face the same problem. Is there any way to fix?
I received my lightly used LG G7 G710ULM a few hours ago. (purchased from eBay)
Went out and took a bunch of pictures with it without a sim card in it. Came home and powered the phone off before throwing my sim card in.
Booted the phone back up and it seems to have factory reset itself; Was thrown back into the initial setup screen and of course, after going through all that again, all the photos I took today are gone.
Needless to say I'm furious and now have trust issues with this thing.
Any idea as to what might have happened, if it's possible to recover my lost photos, or what I should do right now?
I haven't been able to replicate this issue yet (tried powering off and removing sim again) so it's not a consistent thing, but now I'm scared that it might randomly happen to me again.
Thanks.
Thaifight-R said:
I received my lightly used LG G7 G710ULM a few hours ago. (purchased from eBay)
Went out and took a bunch of pictures with it without a sim card in it. Came home and powered the phone off before throwing my sim card in.
Booted the phone back up and it seems to have factory reset itself; Was thrown back into the initial setup screen and of course, after going through all that again, all the photos I took today are gone.
Needless to say I'm furious and now have trust issues with this thing.
Any idea as to what might have happened, if it's possible to recover my lost photos, or what I should do right now?
I haven't been able to replicate this issue yet (tried powering off and removing sim again) so it's not a consistent thing, but now I'm scared that it might randomly happen to me again.
Thanks.
Click to expand...
Click to collapse
Are you sure that the previous owner account wasn't still logged in? If it was the previous owner could have launched a remote factory reset (yep it's a feature).
LameMonster82 said:
Are you sure that the previous owner account wasn't still logged in? If it was the previous owner could have launched a remote factory reset (yep it's a feature).
Click to expand...
Click to collapse
Pretty sure it wasn't as I had to do the whole Google setup when I first turned the phone on.
My friend postulates that this might be similar to the "security feature" found in newer Samsung Galaxy phones in which whenever a new SIM card from another country (more specifically from Canada) is used, when one switches to a U.S. SIM after having been on a Canadian SIM, the phone will do a factory wipe.
Man that just happened to me, I have been using this phone for like 3 days... I fully charged it and I don't know sometimes I like to make a restar so I hold power button to show the restart menu so I clicked on power off and restart, went to the bathroom took a shower and came back to find my phone reset.. No one's is in home so is no like someone tried to type pass codes and after several attempts go to factory reset so no that didn't happen, so yes my LG G7 reset itself... Sorry my bad English
I've been having an issue since at least January. I was hoping either the Feb or March update would fix it, but it hasn't. My Pixel 2 XL has been acting strangely, but only when driving. When I drive, the device will either soft boot (states that PIN is required after restart, but opening terminal and checking uptime shows it hasn't physically booted) or soft lock (black screen that won't come on until hard booted). When it happens, my music will stop and my car's screen will go black. After a period of time, it'll ask me to reconnect the phone, either due to the device being encrypted until the PIN is entered after the soft boot or because it's simple no longer responding in the case of a soft lock. I've tried:
Removing the bluetooth connection for the car
Removing all known cars from Android Auto
Clearing cache
Uninstalling a few driving-specific apps
I was hoping maybe someone had an idea of anything to try besides a factory reset. I really hate reconfiguring my device from scratch (or even from TiBu backups).
I ended up trying multiple different kernels (Elixir and Evira) with the same results, so I broke down and did a factory reset. I reloaded apps and data from Titanium Backup. I'm no longer having the soft boot issue, but a different one instead. Now, randomly, my phone seems to disconnect from Bluetooth, audio it was playing plays through the phone speaker, and my car's display blanks out. I noticed my watch also shows that it has been disconnected from my phone. After a few moments, Android Auto returns to my car's display, but upon selecting anything (for instance, the music I had been listening to), it shows that the device is not compatible.
If I check the phone at this point, every app that had been running has been stopped. My notification bar is empty, and it usually has a few permanent notifications. The phone hasn't hard or soft booted, as it doesn't request the "PIN after restart". It just killed literally everything that was running. I have set both Android Auto and my music apps to not be battery optimized, as I assumed that might have been a problem, but with no better results. If I unplug and plug back in the USB cable, the phone operates normally. I haven't had any especially long trips to see if the issue occurs a second time. I'm lucky enough that my trips to work take 8-10 minutes.
Has anyone seen this or have any suggestions on things to try?
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
cliff6056 said:
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
Click to expand...
Click to collapse
It was similar, but I wasn't using Adguard. I had been using 1.1.1.1 for DNS, but when I stumbled on that post, I removed custom DNS settings without success. Thanks for the thought, though!
In all my years with Android, I haven't had such an infuriating issue. It's almost enough to make someone go to *gasp* iPhone! ... Not really.
For what it's worth, while you mention bluetooth audio and your watch disconnecting, of which I don't use either, I did have somewhat similar issues with Android Auto which it sounds like you also used as you mentioned plugging in. Sometimes AA was disconnecting, sometimes the phone not being recognised when plugged in. It's been a year so can't remember all the symptoms, but at the end of the day, it was the charging port that was malfunctioning, and which Google nicely replaced for me. This also caused adb and fastboot to be intermittent, and not see "devices" which also confirmed the charging/data port. Again, just another shot in the dark for you to consider.
Well, I went on vacation a few hundred miles away last week. On the way up, the phone freaked out repeatedly. I had my wife try to disable WiFi. Same issue. I had her try to disable Bluetooth. Same issue. Both disabled. Same issue. While at our resort, the phone freaked out a few times on the drive to breakfast (literally a 2 minute drive).
On the way back, I decided to disable Location services and revoke all Location permissions. I drove 50 miles with no problems. I had my wife enable Location and drove 30 miles. No problem. I had her tick on apps that I felt needed Location permission, one by one, every 10 miles. No problems at all. I ended up with all of the apps that I feel need Location turned on and haven't had a problem since. So something was choking on Location data, but unfortunately, I have no idea what app it was. I think it might have been Action Services, but I can't be sure. I'm just glad it's fixed, frankly.
I know this is an older post, but I wanted to get my "fix" posted, just in case someone else runs across a similar issue. At least they'd have something to try.