I have installed Italian OTA Nougat for about a week with clean install (no root).
The phone have suffered 3 random reboots in 5 days. I can't find the culprit of it. It's bizarre that after every random reboot there is a completely white screen after I insert the sim code and unlock the phone. I must press home button in order for the phone to be usable again and go to home screen.
I guess that the obvious answer is factory reset it again, but i really don't have the time to set it up again from scratch. Any ideas or suggestions? It's there a log of the phone that I can use to find the culprit? Thank you for your time
Block this app causes the issue with the white screen. I have uninstalled it and i how Random reboots stop too.
So I was just doing some hardware tuning using Kernel Adiutor to save battery, restarted, and it booted up (I was using apply on boot obviously) and was running very slowly. I tried to change the settings, but the phone froze. "No problem", I thought as I rebooted via adb command. It reboots and I cancel the apply on boot, and it freezes after five minutes. I reboot again, freezes again. Reboot, freeze. This happens about 6 or 7 times , each time freezing sooner than the last. Then, it freezes one last time, then the screen goes black. I try reboot and reboot to bootloader/recovery with hardware buttons with no success. So I assume it powered off, but I should check adb first. I ran the devices command and it showed up as active. I ran all basic reboot commands and those just sit there and never complete (I sat here for 20 minutes waiting for it).
I also thought it may be stuck in Android with no display, which I've had happen before on another S7, but it doesn't respond to touch or hardware buttons, and doesn't show up in file explorer (I have screen lock off so it shows up even when off normally).
So then I thought it may be stuck in bootloader with no display. I open up Odin and it recognizes the device, but won't flash anything at all.
Also, this device has never been dropped to my knowledge, and has no cracks, so I doubt it's hardware damage.
I've tried everything I can think of, and Google yielded no results thus far
TL;DR
Messed up with Kernel Adiutor and the screen went black after multiple reboots and freezes
Tried hardware reboots and adb reboots
The device shows up in adb and Odin, but not in file explorer (no screen lock, usually shows up even with screen off)
Odin cannot flash anything, so it's not in bootloader
Other Info:
It's obviously a Galaxy S7
It was originally a Sprint phone (G930P)
It now has Unlocked firmware (G930U)
It is also running engboot for root permissions
I have some previous experience with engboot with my other S7 and have had no problems after 2 years rooted
Any help at all is appreciated
Edit:I'm an actual idiot and didn't know about force reboot (power and vol. down for 10 sec.) and that worked :/
A week ago I rooted my note 20 ultra. Everything works really well. The only problem I have is the random restarts. Sometimes when I use my fingerprint unlock the phone just crashes into the boot screen and then boots back up to the home screen. Whenever the prompt comes back up to put in my pin, I put it in and the phone crashes again. This happens a few more times until it stops occurring and I am able to log in perfectly. I believe that the issue could be occurring due to a lack of memory, but I would like some second opinions. What do you guys think?
My Pixel 2 XL has an issue where the phone will boot and sometimes reboot randomly during the boot process. Other times, it successfully boots. When it does, all is well as long as the phone remains locked. Once the phone is unlocked however, it freezes after a few seconds and the reboots. When the phone finally unlocks without a reboot (seemingly random), it has no further restart issues and is good as long as it remains on (often weeks at a time).
I suspected it was an app causing the problem and tried booting into safe mode, but with the same result. Perhaps something that runs at startup is triggering the issue? The phone is quite old now and it has been dropped a fair number of times, perhaps it is a hardware problem, but it seems strange that the phone is fine as long as it can make it past whatever is happening at startup.
There are two things that I can visibly see happening at startup. The google assistant icon appears in the notification bar, followed by the voicemail icon.
Any ideas on this?
Samsung Note 10, SM-970F
Magisk Rooted
Android 10, N970FXXS6DTK8
It's my GF's, and she uses a pattern unlock along with fingerprint. No new apps were installed or settings changed that she recalls.
Began as phone locking immediately after correct pattern was entered, but using fingerprint would unlock correctly.
With this immediate locking, the phone will by itself turn off the screen then turn it back on for two seconds as though the power button was pressed, then turns the screen off again.
When entering incorrect pattern, it says incorrect pattern and does nothing else.
She tried restarting the phone, which disabled the fingerprint unlock feature until the phone is successfully unlocked once.
Phone still locks immediately after entering correct pattern, and now she can't unlock it using fingerprint.
Now unable to unlock phone.
EDIT: If I repeatedly enter the correct pattern, after a random number of tries it will go to the 'starting phone' screen, but then will either restart by itself or sit there until I restart the phone. It really is random, once it took 7 tries, another time 20 tries. The phone doesn't show up on my windows PC as a mounted device during any of this.
USB debugging was not enabled, so I don't believe I can run any ADB commands. She didn't backup her phone and our focus is at least to get the photos off the camera, at which point doing a factory reset would be acceptable.
I've tried:
Entering a lot of bad patterns, trying to get to an option of unlocking with the google account associated with the phone, but the option never comes up.
Removing the phone case, only external item on the phone now is the stock screen protector.
Starting into recovery, clearing cache, repairing apps.
Starting into safe mode.
Booting in and out of root.
Letting the battery discharge completely to do a hard power cycle.
But no luck. The phone still locks immediately after entering the correct pattern. I haven't tried taking the phone's stock screen protector off, but will probably do that in case there is something wrong with the proximity sensor.
This is the international two SIM version of the Note 10, the only Note 10 variant which was rootable. I haven't worked on the phone for at least a year since it was rooted and setup.
SEU or a hardware failure. Either way when this happens your only option is to backdoor in. If it was a SEU after resetting you're good to go. If hardware it will likely reoccur... Even with a hardware failure many times nothing happens if no lock is set, you still have access. Setting a lock password introduces added failure modes.
SEU's are very rare but they do happen, randomly and just one bit of data is flipped. Interesting they cause no hardware damage. Higher altitudes elevate the risk as does exposure to man made high energy particles. That's one reason why spacecraft have 3 or more redundant computers. Apollo fights have logged half dozen or more SEU's per flight.
I never screen lock my N10+'s, double tap on/off. This is one reason why. Same with PC bios, no password is ever set. Once bitten, twice shy as the user is always the most likely person to get locked out... as I learned the hard way
@blackhawk, I hear you on getting burned with device security. And for any electronic device, secured or not, backups and redundancy are the only reliable difference between your device being useful and useless. It's been hard not to say any 'I told you so' about this, since I was telling her both to use a pin instead of pattern and to let me setup a regular backup. I don't know that a pin would have been different, but I think it would have since the fingerprint was working before the restart.
Do you have any resources you could point me to on how to backdoor into an android with a password/encryption? I know you can unlock a device using ADB, but I believe you need USB debugging enabled first and I don't know how to make that happen without first unlocking the phone.
mc_squirrel said:
@blackhawk, I hear you on getting burned with device security. And for any electronic device, secured or not, backups and redundancy are the only reliable difference between your device being useful and useless. It's been hard not to say any 'I told you so' about this, since I was telling her both to use a pin instead of pattern and to let me setup a regular backup. I don't know that a pin would have been different, but I think it would have since the fingerprint was working before the restart.
Do you have any resources you could point me to on how to backdoor into an android with a password/encryption? I know you can unlock a device using ADB, but I believe you need USB debugging enabled first and I don't know how to make that happen without first unlocking the phone.
Click to expand...
Click to collapse
Samsung repair can do it. A local shop or yourself, maybe. If there's an associated Samsung or Google account, start there. I never had to do that but the information isn't hard to find. The data will likely be lost though.
Meh, it's a very rude surprise.