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.
Related
Android 2.3, 407band, DSC 7.0 rom, Go launcher (default), Zeam launcher (secondary)
Today while using an app called wallbase, I hit the home button while the app was setting a wall paper for me (normally I wait until it says wallpaper set). The home screen popped up but then Go launcher had a FC error (which it has never had since I've been using it). It had the option fc or wait I hit wait. Next my wall paper went black then my screen followed by two vibrations and a notification sound I never heard my device make.
I rebooted to the lock screen with a black background and no service on the screen. It was unresponsive to my touch and after about 10sec. it gave the same two vibrations and sound from before then shut the screen off. The power button did not turn on the display so I had to hold it down for about 20sec for it to reboot to dell logo. From there i went into nandroid and flashed severals roms loaded to the lock screen, rinse/repeat, to find the same result (simple streak, streakroid, older version of dsc).
I reset permissions, wiped cache and dalvik, calibrated screen. Want to avoid a factory reset because I don't have a backup.
Help guys? Mods please move to the appropriate forum.
If all fails and you don't have another alternative.
install the DSC v0.70 update, it shouldn't delete your 'data'.
I would backup your streak, better be safe than sorry.
So I tried letting it sit with the battery out for the night (6 hours) and booting it up this morning with the ac charger. It loads to the same lock screen (standard screen with black background and no service on screen) and all my start up apps loads, it even showed me a text notification. I did notice that the time was wrong though and never changed.
Any one have this issue before? What suggestions are there to combat this? The G.Note doesn't fit into my budget right now. May have to factory reset this and sell it as a last resort.
Help guys?
Outlook for this issue looks grim. Seem others with a similiar issue on different devices have had to factory reset or return it to manufacturer.
Before I do that, is there are any possible way for me to backup some of my app data?
Anyone know if Dell still helps with this device?
I use the app cadrebible often(its the only one I really care about) but it doesn't auto sync/backup and my last manual backup must be from Dec2011 - yea makes me want to cry.
I can load into fastboot, so is there a way I can uninstall a few apps I suspect are causing the issue? Move files from the phones to the sd card/computer?
factory reset. Mod feel free to close thread. -- yes im crying.
Did you try calibrating the touch screen?
I was playing NFS Underground on my Nexus 7 (Running Paul O'Briens MCR) and I have started having a weird problem with it.
I was playing away (at work) and someone came in the door, so I switched the screen off, after that it wouldn't respond to me pressing the power button to turn it back on. (I was using Gesture Control to hide the Nav Bar also)
So I held the Power Button to Hard Reset it, and it still wouldn't come back to life, so I thought I should plug it into the wall to give it a charge, then try again! When I picked it up 10 minutes later there was a weird vertical static on the screen (a bunch of white dots on black background), and again it wouldn't respond to any input.
From there I have tried to Wipe Dalvik & Cache and reboot (same happens), I tried to backup my ROM and flash a fresh one, the same thing happens in the middle of a backup.
I have managed to start it a few times (and it has now managed to process all the apps after the Dalvik wipe), but as soon as it boots, it just re-starts?
Anyone have any ideas how I can get it up and running again?
Also one thing I have noticed (this may be related to an updated Bootloader) whenever I plug my Tablet into the Wall, it turns on automatically! It definitely never used to do that!!
This is driving me mad!!!
Cheers
Stewart
EDIT - I seem to be able to put it in bootloader mode without it turning itself off!
Going to try flashing back to stock!
Quick question, can I pull a file from my SDCARD partition using my Mac while in bootloader?
Moral of the story, don't play games at work :/
But on a helpful note to you, yes you can pull a file.
If it doesn't boot, I'd get TWRP and the mount it whilst in recovery mode.
From there you can push/pull files
Earlier today, a few apps on my Nexus 7 have just started closing within one or two seconds of opening them.
Google Search Bar, Facebook and Catch Note all close within a couple of seconds after opening them. I have used them fairly frequently for the last few weeks with no problems. Other apps, such as Twitter, Chrome and some games all work fine.
I have turned my device on and off a couple of times, but the problem still persists. Any ideas?
The problem is still occurring for me.
Gmail, Calendar etc... all also closing within a second or two of opening. Is this a common problem?
Is your N7 all stock or do you have a custom rom?...custom kernel?
You really need to provide some information in order to get help.
I haven't seen it in the OP so: Reinstall them
Visa Declined said:
Is your N7 all stock or do you have a custom rom?...custom kernel?
You really need to provide some information in order to get help.
Click to expand...
Click to collapse
I haven't rooted my Nexus, or anything like that, it's all stock.
I just uninstalled Facebook, then downloaded it again. It seems to be working. Other apps still have the same problem. I assume that I have to do the same for all other apps - but is that even possible for apps such as Gmail, Calendar and the Search Bar?
Uninstalling and re-downloading hasn't worked as I had hoped.
It seems to have worked for Facebook. But I did the same for Catch Notes, and although it worked for a minute or so when setting it up, after creating a test note, it force-closed, I opened the app up again, and the old problem of closing within 2 seconds happened.
Other apps such as Gmail, I uninstalled, 'updated' again, and nothing changed, still closes immediately. There is no error message, it just returns to the home screen.
I thought that Task Killer might have been a problem, but I uninstalled that, restarted the Nexus, and the problem persists. Actually, when I turned off my Nexus, and tried to turn it back on, it was stuck on the 'coloured X' screen for a few minutes, I had to hold the power button down, and turn it on again. I'm starting to worry about my Nexus now.
Update:
A couple of other odd ones.
Google Drive doesn't even open. When clicking on the icon, the normal shading effect happens, but nothing else, no window even for a second.
Google Calendar opens, and just has a white screen, as if it is ready to load the calendar, but nothing loads. It doesn't close, just remains on the white screen, which can't be backed out of without pressing the home button.
Have you tried doing a cold-boot on the device? Maybe another app running in the background is causing conflicts. Where there any recent apps that you've downloaded?
Asus_USA said:
Have you tried doing a cold-boot on the device? Maybe another app running in the background is causing conflicts. Where there any recent apps that you've downloaded?
Click to expand...
Click to collapse
I have just followed the instructions for a 'cold-boot' and now my Nexus can't get beyond the 'X' screen...
I have held the power button down a number of times, and tried turning it on again - but the 'X' continues to be displayed for over 20 minutes.
Just managed to turn my device on - but the problem still exists.
I didn't download any new apps that seem to have caused this problem. Though I think an app might have force closed and the Nexus displayed an error message such as "android/Google system stopped working" (probably different) and my home screen went blank for a while. Everything reappeared though after a short while. It could have stemmed from that.
Sorry about another bump, but i'm wondering if anybody has any more ideas before I go for a factory reset?
Edit: Actually, I think that I have found the cause of the problem. I just opened a game (Let's Golf 3) that I was playing before the problem started and after a few seconds, a message popped up saying "Unfortunately, Launcher has stopped". When I press OK, it returns after a few seconds.
I pressed the sleep button, and my Nexus turned off. Now trying to turn it on again, having some problems getting past the 'X' screen again. If I finally get in, should I uninstall the game? Any other solutions to this problem?
If your N7 can boot up, go the isolate & identify routines - disable/uninstall or freeze the golf game - do a normal shutdown/restart.
If normal functionality is back, you've just found the source. Not a gamer myself except for Angry Birds ... , but from the Play Store description, it access & make changes to system & protocol, etc. as you should contact/email golf's tech support for resolution. Otherwise, take a look of any background running apps or widgets, newly added or updated.
Letitride said:
If your N7 can boot up, go the isolate & identify routines - disable/uninstall or freeze the golf game - do a normal shutdown/restart.
If normal functionality is back, you've just found the source. Not a gamer myself except for Angry Birds ... , but from the Play Store description, it access & make changes to system & protocol, etc. as you should contact/email golf's tech support for resolution. Otherwise, take a look of any background running apps or widgets, newly added or updated.
Click to expand...
Click to collapse
Thanks for the help.
I couldn't get my N7 to boot up, so I finally gave in and did a hard reset (by holding power + volume down, Recovery Mode, then wipe data etc...) but my N7 still won't boot up
I have wiped it twice, and rebooted it, yet it is constantly stuck on the 'X' screen. What on earth can I do?
Gawge said:
Thanks for the help.
I couldn't get my N7 to boot up, so I finally gave in and did a hard reset (by holding power + volume down, Recovery Mode, then wipe data etc...) but my N7 still won't boot up
I have wiped it twice, and rebooted it, yet it is constantly stuck on the 'X' screen. What on earth can I do?
Click to expand...
Click to collapse
I would flash the stock system image.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
I would flash the stock system image.
Click to expand...
Click to collapse
How would one do that?
My N7 isn't rooted or unlocked.
Gawge said:
How would one do that?
My N7 isn't rooted or unlocked.
Click to expand...
Click to collapse
You will need to download the factory image, unlock your bootloader, and flash it. There is a guide on this forum, it might be stickied.
Sent from my Nexus 7 using Tapatalk HD
I was hoping there was going to be a resolution to this other than a "flash to stock" suggestion... My Nexus started doing this exact same thing this past Sunday when it ran out of power completely and needed to be recharged. After it powered back up from charging the following apps quit working altogether or just started quitting once it appears they try to access data: Netflix, Currents, Zillow, Gmail, HBO Go, Press (though Google RSS Reader works), NVision, TegraZone and a couple others. I have done the reboot thing as well and almost had this thing brick again (stuck at X), but I managed to clear the data cache from the fastboot menu and it started up again. I'm now at the point where I'm troubleshooting individual apps but the clear data/cache, uninstall - reinstall process isn't working for any of the broken apps. This is now the 4th time I will be facing a 'flash to stock' situation as it appears that I've had every problem that leads to this 'fix'. I'll try a couple more things (mostly deleting and clearing everything) but I'm really frustrated with how many times I've had to flash this damn thing. sigh.
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
Hey guys, I have had my Note 4 for about 3 years now and it has never done me wrong. However, things have taken a turn for the worse... I started noticing a few days ago that it was slowing down on me, I mean, really slowing down. Big lag times when it comes to swiping to open the screen, or changing between apps, and the occasional self-shut down when the battery got down to about 15-20%. I had been putting off doing a self-update for a while, and when I finally had time to do one tonight, in hopes of cleaning it up, it is now lying on its death bed
I do not think the update ever finished (my phone is not rooted) but I was desperate enough to even do a factory reset and that has not fixed the issue.
Here are the symptoms:
As I go to boot the phone, I get past the Samsung Note logo and it looks like it is about to load properly, but then I get a popup that says "Unfortunately, the process com.android.phone has stopped" I hit ok and it keeps popping up again. I can't bypass it.. Then after I get passed that for a split second, another popup comes up that says "unfortunately system UI has stopped" It prevents me from getting to the home screen, in fact the screen behind it is black.
I have tried the following:
Clearing the cache partition from the recovery screen
I have done numerous hard restarts
I have gone through with a factory restart
That is where I have left off, and lost most hope, was with the factory restart. Now when I turn it on, I get past the logos and I can see in the background the page you would get as if it was a brand new phone (it says "Welcome! Preparing you device for first time use.." etc. But I can't do anything about it because I am still getting the same two popups that prevent me from doing absolutely everything!!!)
I have read about this happening and people seem to be able to fix this by accessing certain app setting and either resetting them, or clearing their cache. However, that is not an option for me because I can't get that far. I think something must have went wrong during the update...
Please help with any advice you can think of. I have been putting off rooting this phone pretty much because I was afraid of royally f****** it up, but at this point I am willing to try anything.
Thanks,
Eric
Hey guys, does anyone have any suggestions for my issue?? I am about to go out and buy a new phone, I have no idea what I can do to fix this. I have rooted it using Odin, but the popups are still occurring. I can't get the popups to stop, and they are preventing me from doing absolutely everything.
Is there anyway I can get it to go back to complete scratch? Again, I have done a factory reset, cleared the cache, rooted using Odin. I have done everything I can think of/what I have read I can do. I am willing to try anything at this point.
UPDATE: At this point my phone is on, and the only error message/popup I am getting is "Unfortunately, System UI has stopped." Behind that popup is a blank, black screen. The only option I have is to click ok, and the screen remains black.
Temporary solution that might work- Try logging in safe mode: Switch off the phone. Power it on and as soon as Samsung logo appears, release the power button and press and hold the volume down button. Release button when you see Safe Mode on the lower left corner of the screen. Try uninstalling all user apps in safe mode. To get back to the normal mode you can drag down from notification and disable safe mode.
You could also download the latest software for your model from samfirm and flash it via odin after factory reset. Could be a permanent solution.
why you just flash last frimware from sammobile,it will solve all your problems
SOLVED!!!
Alright guys, I was able to solve my problem, all thanks to this thread:
https://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3250864
I had already tried flashing a fresh stock rom, but to no prevail. I saw this thread and thought, hey why not give it a shot, and bingo! After downloading the .tar file for marshmellow and launching it through odin, she was good as new! So if anyone seems to have a problem with the system ui or the process phone.android popup, I suggest that thread.