Been using the S8 Unlocked model SM-G950U1 (stock, not rooted) for the past 4 months without any major problems. A few weeks ago I decided to enable the Secure Boot feature, so that if the phone was powered off and back on, that it would require drawing the password pattern. Haven't had any problem, until tonight.
Since my phone hasn't been rebooted in about a week (which I like to do), I did a reboot, and drew the password pattern, the unlock icon is show with the green & blue circle around it, but then it just stays like this and never gets to the "android is starting, or phone is starting" screen.
I've gone into the boot menu and did a Clear Cache & Reboot, drew password pattern, and then let it sit for 30 min.
I also did a Safe Mode Boot, where it showed "Safe Mode" in the bottom left corner on the same screen where I draw the password pattern, but then it stays at the unlocking icon.
At this point I'm not sure what to do, as I really don't want to do a full factory reset in the boot menu, or do an ODIN wipe, and loose everything.
After trying to get it to properly boot for about 2 hours and trying different things, I ended up going into the boot menu and doing a factor reset. Then took several hours to get the phone all set back up again.
I had thought that when I backup the phone via Samsung Cloud, part of that is for Apps, and I thought it would be the apps and app data (similar to using Titanium Backup). But I guess not, as when I did the restore through Samsung Cloud, it only restores the app programs and not the data.
Related
I rooted my LG G2 vs980 (Verizon) many months ago. However I never actually performed any modifications. Don't ask haha.
Anyways, I wanted to unroot my phone, and being that I rooted it with ioroot, I was told to unroot it just by simply going into the settings in SuperSu and hitting Full clean uninstall. I did just that, however it stayed on the uninstalling screen forever, and NEVER WENT AWAY. It never finished the uninstalling process. I even left the phone doing the uninstalling process all night and never touched it. I had no interference with the uninstalling process.
When I realized it wasn't going to uninstall, I backed out, and did a factory reset on my phone, then restarted the uninstall process. Still the same.
This time when I tried using my phone:
1)My home button didn't work. When it was pressed, it would vibrate normally, but would not actually go to the home screen.
2) The little settings icon in the status bar, when dragged down, does not work. I have to hit the menu button and go into settings that way.
3) The lock screen does not work. I have a lock screen setup with a pattern. However the lock screen completely does not work, as if my phone isn't locking all the way. The screen will go black, and come back on with no lock screen.
4) My notifications completely do not work. My phone will sometimes make sound/vibrate like normal when receiving a notification, but my status bar will not show anything.
5) My computer won't even recognize my phone anymore either.
6) Volume buttons don't work.
7) So many other problems with the status bar.
Moral of the story, phone's screwed.
All help is greatly appreciated.
At this point, since there seems to be be so many issues, AND since you're already done a factory reset, I'd recommend just flash stock and start from the beginning again (which you've pretty much done already).
Alright, I don't think I'm the only one... 128GB black version, stock, no unlock.
Randomly restarts itself while sitting there, then sticks on the swirly image.
Have factory reset three times now. First reset, no longer tried to restore from backup (OnePlus). Second time, left it at default apps but with fingerprint enabled. Third time, default apps, no fingerprint/swipe. seemed to work ok. Installed my base apps (Whatsapp, etc), still okay. Enabled fingerprint and swipe... Boom...
Am I screwed and need to send this back?
C8st0rTr0y said:
Alright, I don't think I'm the only one... 128GB black version, stock, no unlock.
Randomly restarts itself while sitting there, then sticks on the swirly image.
Have factory reset three times now. First reset, no longer tried to restore from backup (OnePlus). Second time, left it at default apps but with fingerprint enabled. Third time, default apps, no fingerprint/swipe. seemed to work ok. Installed my base apps (Whatsapp, etc), still okay. Enabled fingerprint and swipe... Boom...
Am I screwed and need to send this back?
Click to expand...
Click to collapse
You could try using one of the toolkits to wipe and install a factory image to see if that works. More of a last resort option but it seems your nearly at that point.
tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits
okay I've got a moto Z-Force Droid Edition from Verizon. I did an update on the phone and now it's stuck in bootloop. It'll come to the screen that allows me to put in my password for starting Android and then it reboots to start Android and i get to see my background picture and then it reboots again back to the screen where it asks me for my password again like it's being turned on for the first time. I've got pictures and some notes from an app that I use in the phone that I need to get off of it. I do believe the phone came with encryption turned on and I never turned it off.my question is can I simply factory reset the phone and then use a third-party software from a computer to scan the phone and recover my photos and notes, or is the encryption going to prevent that?
I've never rooted or unlocked the bootloader, after updating to official oreo 8.1(via OTA), Lenovo startup screen is blocking the screen so I cannot access anything directly, like, the touch and everything is working fine but with the lenovo screen I just can't see where I'm touching, the phone starts up ok and I can hear when I getting messages and I can use Whatsapp web to write messages, I could rotate the phone and see half of the screen and the other half Lenovo logo still blocks, Is there anything I could do exept factory reset?
Hello,
Try to turn on screen rotation,
And turn the phone sideways and use split screen with the settings as the second app.
Uninstall any app that has access to system controls,like TeamViewer
rickyninpo said:
Hello,
Try to turn on screen rotation,
And turn the phone sideways and use split screen with the settings as the second app.
Uninstall any app that has access to system controls,like TeamViewer
Click to expand...
Click to collapse
I've fixed it after wipe cache in stock recovery.
But thanks anyway
Edit: and there we go again, same problem and not even a wipe cache is helping
.....
Thats how its looking like, this system popup shows something that i cant see
rickyninpo said:
Hello,
Try to turn on screen rotation,
And turn the phone sideways and use split screen with the settings as the second app.
Uninstall any app that has access to system controls,like TeamViewer
Click to expand...
Click to collapse
Done it and not worked
I am having the same issue: phone boots normally, then seems to hang on the Moto boot animation - except that the phone is fully booted, alive, accepts touch inputs and has network/signal, except nothing is rendered to the screen, only the frame of the Moto boot animation is displayed. This remains the case regardless of what occurs on the phone, e.g. the phone can receive a call, and will respond as expected, except the display remains fixed on the single frame from the Moto boot animation.
I have wiped cache partition multiple times to no avail.
Any ideas on what might be causing this?
Any ideas on how to solve this?
Worst case scenario, any ideas on how to pull data off the phone?
Thanks
zinkyzinkerson said:
I am having the same issue: phone boots normally, then seems to hang on the Moto boot animation - except that the phone is fully booted, alive, accepts touch inputs and has network/signal, except nothing is rendered to the screen, only the frame of the Moto boot animation is displayed. This remains the case regardless of what occurs on the phone, e.g. the phone can receive a call, and will respond as expected, except the display remains fixed on the single frame from the Moto boot animation.
I have wiped cache partition multiple times to no avail.
Any ideas on what might be causing this?
Any ideas on how to solve this?
Worst case scenario, any ideas on how to pull data off the phone?
Thanks
Click to expand...
Click to collapse
I've faced that issue a couple times, I don't know what is causing this but I think it's kind of some storage issue, and the workaround I've found is freeing up some storage space. You could try it and see if it works for you too!
I had same problem. TL;DR - Rebooted several times after wiping cache and resetting dpi to 400.
Full story:
I had recently encrypted the device and had about only ~300 MB left in my internal storage. Decided to wipe cache partition and went to shut down the device. Hit reboot instead of shutdown.
Decided to shut down after it boots up. But when it started, the motorola lenovo image was stuck.
I could hear the phone unlock and the notifications. Called the phone thinking the incoming call might display over the image but to no avail.
Google assistant could hear me and respond to commands. Opened apps with that.
Then tried to see if apps would respond to touch. Long pressed power button to bring up the power menu(Power off, Restart, Emergency), pressed the place right next to the power button because I remember the "Power off" option there. Booted into recover and cleared cache partition. Rebooted twice with the same result. Stuck at the moto image.
Read in the beginning of this thread that rotated screen seems to show half the display. So, tried to see of it works and it did. That was of no use to me as I didn't know what to do after that.
So decided to see if changing the dpi would make a difference. Used ADB and "adb shell wm density DPI" (replace DPI with your desired number. Default value is 480.) to change and rebooted. It seemed to fix it as I rebooted after the command and my display was back to normal.
Not going to change the value now as I don't want to mess with anything now. Maybe later, I will reset it to 480 and see if the issue appears again.
Manolingam said:
I had same problem. TL;DR - Rebooted several times after wiping cache and resetting dpi to 400.
Full story:
I had recently encrypted the device and had about only ~300 MB left in my internal storage. Decided to wipe cache partition and went to shut down the device. Hit reboot instead of shutdown.
Decided to shut down after it boots up. But when it started, the motorola lenovo image was stuck.
I could hear the phone unlock and the notifications. Called the phone thinking the incoming call might display over the image but to no avail.
Google assistant could hear me and respond to commands. Opened apps with that.
Then tried to see if apps would respond to touch. Long pressed power button to bring up the power menu(Power off, Restart, Emergency), pressed the place right next to the power button because I remember the "Power off" option there. Booted into recover and cleared cache partition. Rebooted twice with the same result. Stuck at the moto image.
Read in the beginning of this thread that rotated screen seems to show half the display. So, tried to see of it works and it did. That was of no use to me as I didn't know what to do after that.
So decided to see if changing the dpi would make a difference. Used ADB and "adb shell wm density DPI" (replace DPI with your desired number. Default value is 480.) to change and rebooted. It seemed to fix it as I rebooted after the command and my display was back to normal.
Not going to change the value now as I don't want to mess with anything now. Maybe later, I will reset it to 480 and see if the issue appears again.
Click to expand...
Click to collapse
I am also facing the same issue, I have tried cache wipe but it's not working. I can't access anything in mobile because of the logo. USB Debugging was already enabled but ADB commands are not working. Can you please share the steps how you have changed DPI.
Thank you
JaiSoni.87 said:
I am also facing the same issue, I have tried cache wipe but it's not working. I can't access anything in mobile because of the logo. USB Debugging was already enabled but ADB commands are not working. Can you please share the steps how you have changed DPI.
Thank you
Click to expand...
Click to collapse
Sorry for the late reply. Is this resolved?
Solution:- Clear some of your device's internal storage. Uninstall infrequently used apps & delete unnecessary data. Power off your phone & then power it on. It should get back to normal. Description:- While using my phone I got stuck on an application & had to restart the phone. During boot up it took longer than usual & at last got stuck at Lenovo logo. I tried restarting it several times again but in vain. I searched on the internet & tried their suggestions. Basically the phone is working in the back end. Only the screen is stuck at Lenovo logo. So I unlocked my phone by typing my PIN by guessing where the numbers would be. Then tried to turn on auto rotation using Google Assistant but since mobile data was off so it didn't work. Then I turned mobile data & auto rotation on by toggling the quick settings by guessing where they would be & trying again & again. Once turned on, hold your phone in landscape mode half of the screen will be visible if your home screen allows rotation, if not go to any app which supports auto rotation & then switch to landscape. Then using multi tab open settings in the second tab. Clear your internal storage. I cleared about 5-6 GB but 2 GB should be enough. After clearing your storage, power off your phone & then power it up. The phone was normal again.