Hi all,
once my S5 mini boots up, it shows "System UI has stopped Working" and shows only my wallpaper. Power button is still working (i.e. shutdown menu appears), home button turns on display, anything else doesn't work.
Here is what I tried without success:
- remove SIM/SD
- go to airplane mode (possible from the menu when holding down power)
- Boot into "safe mode"
- Wipe cache in recovery mode
- use Kies (and Lite) to copy/reset (not working..)
- use Smart Switch to copy data to another phone
What seems to be the problem is the "Google App", according to various posts; e.g. [1, 2, ...]. But I cannot access settings and disable the app.
Is there any way to activate adb without being able to grant permissions from the phone and use it to remove the app? Any other ways to uninstall/reset this particular app?
Any other suggestions?
Thanks in advance!
yyy
Alright, it didn't leave me alone
I managed to get my files by flashing TWRP into recovery and getting contacts2.db (and everything else I needed) with adb pull.
Even wiping the Dalvik / ART Cache and the Cache from TWRP had no effect on the hangup. Even bute-deleting the searchbar-app didnt do nothing.
Godspeed to everyone with the same problem.
Related
So like many of you who were running the awesome LPV build for the past few months and just recently tried updating to official Lollipop (LRX21O) have likely run into issues on first boot (black screen with only a back button). In this state/issue the phone will respond to "OK Google" but nothing else. The pulldown shade will also be present but show nothing. The issue appears to be related to the lock screen. The following is how I fixed my issue, and I will be looking at this thread to try and update the OP as we pin down the EXACT issue, but I believe I have a fix:
NOTE: If you've already updated and are AT the black screen, I hope you have a backup to restore as you'll need to revert to change some settings. If not, you may find flashing the system.img or zip of your old build (LPV) allows you access to your phone again to access these settings.
1. Restore backup or revert if necessary so you can access settings BEFORE flashing LRX21O.
2. Settings-Security-Screen Lock Make sure you have one set other than swipe so you can perform the next step (we will change this back later)
3. Go to "Trust Agents" on the same screen (Security) and turn OFF SmartLock
4. Go back to screen lock, now select SWIPE (or none if present, but I don't believe it's an option on most)
5. (Optional) I chose to both enable USB debugging as well as going into SuperSU (if present) and setting it to grant all requests. I did not need this, however if you're having issues it may help your troubleshooting to have root adb access.
6. With your lock screen set to swipe and smart lock off, now try flashing LRX21O, followed by a custom kernel (or boot.img if you have it) and/or root in that order if you'd like.
7. Upon boot, it SHOULD have resolved the black-screen issue. I did still have the "non-working home button" issue that was quickly resolved by running the setup wizard again with the following command via adb:
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
When it asks about restoring backups or setting up as a new device, choose set up as new device. The "Restore" would simply re-download and restore apps that are already installed. "Set up as new device" simply tells setup to do nothing, which is fine, because all your data is already there
8. SDcard Fix (root required): If you have issues seeing SD card content, use these ADB commands below (credit to rootSU here
su
restorecon -FR /data/media/0
That's IT! You should be set. I love dirty flashing (I know everyone hates it because yes, it does cause a lot more chatter in the forums, but that's half the fun ) and problem solving. Everytime I see someone claiming they fixed a problem by factory resetting I'm thinking "...that's like saying you fixed your car by buying a new car". I hope I this makes other's lives a little easier
When I tried to go on my phone this morning, I started getting an error message. It said that 'Com.android.phone' had stopped working, and I cannot remove it as another one pops up every time I close it. Occasionally it changes to 'Settings has unfortunately stopped working', 'Dialer has unfortunately stopped working', etc. Along with this, it randomly restarts, and I cant fix it. It is not a rooted device, and clearing the Cache from the recovery menu did not work.
Any suggestions, as I really do not want to factory reset it?
Thanks, Rahim
Edit: Forgot to mention that it keeps saying preparing SIM card at the bottom
rahim07 said:
When I tried to go on my phone this morning, I started getting an error message. It said that 'Com.android.phone' had stopped working, and I cannot remove it as another one pops up every time I close it. Occasionally it changes to 'Settings has unfortunately stopped working', 'Dialer has unfortunately stopped working', etc. Along with this, it randomly restarts, and I cant fix it. It is not a rooted device, and clearing the Cache from the recovery menu did not work.
Any suggestions, as I really do not want to factory reset it?
Thanks, Rahim
Edit: Forgot to mention that it keeps saying preparing SIM card at the bottom
Click to expand...
Click to collapse
Try this:
- On the Home Screen of your phone, Press Menu
- Now Tap Settings
- Now Tap Applications
- Tap Manage Applications
- Now at the Top, Tap the All tab
- Now Navigate to and tap your equivalent of the phone app (may be called phone or dialer)
- Tap Clear Cache and Clear Data as available
- Now Turn Your Phone off, then back on.
OR:
2. Clear Cache and Data of the SIM Toolkit
Repeat the steps shown above. But this time, choose SIM toolkit from the list of apps under the All tab.
kativiti said:
Try this:
- On the Home Screen of your phone, Press Menu
- Now Tap Settings
- Now Tap Applications
- Tap Manage Applications
- Now at the Top, Tap the All tab
- Now Navigate to and tap your equivalent of the phone app (may be called phone or dialer)
- Tap Clear Cache and Clear Data as available
- Now Turn Your Phone off, then back on.
OR:
2. Clear Cache and Data of the SIM Toolkit
Repeat the steps shown above. But this time, choose SIM toolkit from the list of apps under the All tab.
Click to expand...
Click to collapse
Thanks for the reply, but I tried that previously and the 'Clear data' and 'Clear Cache' are blanked out for both of them so I can't press it
rahim07 said:
Thanks for the reply, but I tried that previously and the 'Clear data' and 'Clear Cache' are blanked out for both of them so I can't press it
Click to expand...
Click to collapse
make sure they are stopped.
"Force Stop" then try clear cache.
kativiti said:
make sure they are stopped.
"Force Stop" then try clear cache.
Click to expand...
Click to collapse
I can no longer get onto apps, so it seems I have no choice but to factory reset it
Do you know what could have caused this, so I can avoid it next time?
Thanks
Corrupt data maybe on a force shutdown. My phone was charging just now and decided to reboot and gave a error report but don't know the reason.
Some say google apps cache other dialer cache. Maybe someone else have a better ideia.
Use HTC backup. It backups everything...photos, definitions, emails, etc.
Hey folks,
since yesterday I have a serious problem with my Xperia Z3 compact D5803:
After waking up my phone from Stamina it just crashed.
Then it was stuck in a boot loop.
With TWRP I was able to (temporary) fix the boot loop:
- Advanced -> Fix Permission (also SElinux)
- Mount -> System
- Advanced -> File Manager -> Copy build.prop to /system
- Reboot: System
However the system was very laggy, running hot and had a high battery drainage (like 1 percent per minute). In OS Monitor I saw dhd_dpc had around 20% CPU usage (which is related to WiFi), so I disabled WiFi, which fixed these issues.
However after reactivating WiFi system crashed and again stuck in boot loop. And now I can't even fix the boot loop....
So what do the experts say:
a) Is this software or hardware related? (Notice: While the system was laggy, I was still able to download data via WiFi, so the antenna cannot be broken completely)
b) What can I try to fix the boot loop?
c) I guess last resort is factory reset. What else can I try before that?
Thanks!
Anyone?
Unless you say what you actually did to break the device, you're really not going to get much help. Once you own up to what you did to it, perhaps someone can figure out how to fix it.
If you've messed up the ROM, a factory reset isn't going to fix it. You'll need to reflash.
As discussed on IRC, I did nothing on the ROM or the system at all!
However apparently my try on fixing the boot loop, with copying a backup of the build.prop, did in fact broke the boot due to wrong permissions. I was able to fix this with a chmod 0644 on the build.prop.
Now the phone boots fine so far and isn't laggy anymore, however I have still problem with high battery drainage. The phone merely lasts one day...
Under battery usage it is just listing "Android system" as main appliance.
So I hope this is somehow software related and will go with a re-flash. Also then I can use this opportunity to update to 5.1.1 - at least something....
So I was messing around with the developer settings and turned on "Force RTL layout direction". This caused my phone to crash and for the error message to pop up "Unfortunately, system UI has stopped". I have tried rebooting multiple times and clearing the cache as some suggested but this doesn't seem to work. I was wondering if there are any other options instead of a factory reboot and if not, can I backup my phone from the recovery mode or using a USB connected to my laptop. Thanks!
see here:
PSA: Do not enable force RTL Layout in 5.1
http://forum.xda-developers.com/droid-turbo/general/psa-enable-force-rtl-layout-5-1-t3149244
on the last page is a solution that worked for someone, but most have to do a factory reset.
After installing N960FXXU6FTJ5 for my ITV Exynos version, I made a wipe cache as I usually do after a firmare upgrade but this time, in Recovery mode, I found a new option in the bottom of the list called "Repair apps".
Someone knows what does it do and how it work's?
joedellosso69 said:
After installing N960FXXU6FTJ5 for my ITV Exynos version, I made a wipe cache as I usually do after a firmare upgrade but this time, in Recovery mode, I found a new option in the bottom of the list called "Repair apps".
Someone knows what does it do and how it work's?
Click to expand...
Click to collapse
I answer myself :
I gave it a try....
....there's a reboot, the Samsung logo goes on normally for a while and after that it pops on the Optimizing Apps screen (two gears turnung plus the % of the apps optimized ) that you'll get everytime you update the OS.
When the process finishes, the phone gets on normally.
For what I've read around in Google, this process (Optimizing Apps) actually provisions the apps for the system by generating the Dalvik cache so that apps can run nicely (and quickly) with the current system. Personally I think it also makes a sort of defragmentation of all the apps .
So, when troubles occurs (lags, some types of app crashes) , with repair apps in recovery mode you can do a manuall re-optimize apps so the system will return snappie like it is after a firmware update..
On my s21+ repair apps also reset all my default services to Samsung apps. For instance, I had installed Gboard, Google Messaging, Phone etc and they all reverted to Samsungs version. Not a big deal since all I had to do was switch back to the Google apps when I opened each application.
FYI, I also did the clear system cache and repair apps and it made my fingerprint work consistently. I was having really inconsistent results with the reader before performing these recovery mode options.
proxybox said:
On my s21+ repair apps also reset all my default services to Samsung apps. For instance, I had installed Gboard, Google Messaging, Phone etc and they all reverted to Samsungs version. Not a big deal since all I had to do was switch back to the Google apps when I opened each application.
FYI, I also did the clear system cache and repair apps and it made my fingerprint work consistently. I was having really inconsistent results with the reader before performing these recovery mode options.
Click to expand...
Click to collapse
That would be safe mode i think