**sorry for the thread title, it won't let me edit it. Was supposed to be "Help: android.process.acore error after Marshmallow update"**
Hi, I updated my HTC One M8 (stock ROM) to Android 6 via an OTA update sent to the phone.
The update went fine - no error messages. But after the final reboot, I am getting constant (and I mean constant, not every few seconds) errors that all processes are stopping. Particularly, after everything else has stopped, I get repeated messages about android.process.acore, android.process.media, and Sense Home unexpectedly stopping (I guess these are the ones that keep starting up and failing). By pressing "OK" or "close" on these messages, sometimes I can press something very quickly before another message pops up. In this ridiculous manner, I was able to do/find out the following:
- Pressing the home button shows me the white screen with "htc" written on it, like on phone startup, or sometimes a black screen
- Pressing the recent-apps button actually does show me the recent apps and I can click on them, though most of them just close right after I open them. Some of them work -- like I can receive phone calls (I just don't hear the phone ring, and I have to press the "talk" button in between pressing OK on error messages).
- I can get into the settings screen. In this way, I tried:
- Disabling one by one every app I could, including Google Services Framework and Google Play services which were giving repeated "stopped" error messages - but I still get the android.process.acore & Sense Home errors and no UI
- Clearing cache & data for all contact & calendar app I could find, and also for Google Services Framework and Google Play services and some others
- Going into Developer Options and viewing active services - I stopped all active and cached services and process I could, to no avail
I also tried booting into recovery mode and wiping the cache partition.
Nothing works!! Please can anyone help me save my phone without doing a factory reset? Unfortunately, since I started the Android update by accident (pressed "now" instead of "later"), I didn't backup anything beforehand... and while my contacts and calendars are always backed up, my apps & preferences & media files are not. I also tried connecting to a computer via USB, but while the computer recognizes the phone, I cannot actually access the files (I see it as a drive, but when I open it there are no files or folders, and the HTC sync SW does not recognize it) - so no possibility to back up the files in that way...
Thank you!!
Yael
Well true to form, it seems replacing the stock issued file manager , along with getting rid of the numerous setup wizards, has resulted in a dead/no-functioning home key. Yay. Joy. WOO-HOO .... :crying:
:silly:
So does anyone know which file i need to edit, to force the "proper" functioning of the home button?
What happens is the setup wizard for the phone actually seems to assign itself as a home launcher.
I found that out when i was checking to see if i could get around the wizard, and sure enough in settings/home
setup wizard appears in the listing as a home launcher launcher. I've managed to get rid of alot of the sony stuff not related to
the camera. I love the camera, it's so camera-y
Okay back on point here, Where is the file to correct the situation with the home button and what should be the correct setting?
alternately a build.prop adjust would do as well.
Thanks.
m
Also , has anyone been able to locate the japanese keyboard's apk on the international unlocked version?
Okay and here is the logcat blah when home key is hit,
Code:
I/WindowManager( 1557): [COLOR="Red"]Not starting activity because user setup is in progress[/COLOR]: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 }
EDIT- Sorted momentarily, the setup process includes the gapps wizard, whether you complete it or skip it, but you must complete it or skip it.
When i find the flag and/or file that says "Hey this is done" I will post the name of the file and/or flag.
My phone is a canvas a1 with android m on it ( version 6.0.1 ). I was plagued by lots of the "Google x has stopped working" today it became a nuisance as it popped up every 10 seconds, so according to a guy, I cleared the cache after booting into recovery mode and it took a good 5 minutes. After the wiping, I booted up and i get "starting apps" for some 10 second and then the boot logo. This cycle continues forever. And once I did manage to reach the lock screen but then it wouldn't load Home - "couldn't start home". Can anybody help me out of this mess?
Update : now it's showing "optimising app 46 of 95" but after it finishes, I get an empty screen and only the back and multitask button works and, I get an error when I click home - "couldn't start home".
Please help as, though I have another phone, this is very important to me and lots of my things depend on whether this works or not.
Also, I haven't done a reset yet as I thought it'd be good to ask here first.
ForcaBarca10 said:
My phone is a canvas a1 with android m on it ( version 6.0.1 ). I was plagued by lots of the "Google x has stopped working" today it became a nuisance as it popped up every 10 seconds, so according to a guy, I cleared the cache after booting into recovery mode and it took a good 5 minutes. After the wiping, I booted up and i get "starting apps" for some 10 second and then the boot logo. This cycle continues forever. And once I did manage to reach the lock screen but then it wouldn't load Home - "couldn't start home". Can anybody help me out of this mess?
Update : now it's showing "optimising app 46 of 95" but after it finishes, I get an empty screen and only the back and multitask button works and, I get an error when I click home - "couldn't start home".
Please help as, though I have another phone, this is very important to me and lots of my things depend on whether this works or not.
Also, I haven't done a reset yet as I thought it'd be good to ask here first.
Click to expand...
Click to collapse
If u have warranty then better go to care center or do flash ur mobile using sp flash tool and then u have to redownload the update for 6.0 and so on
ForcaBarca10 said:
My phone is a canvas a1 with android m on it ( version 6.0.1 ). I was plagued by lots of the "Google x has stopped working" today it became a nuisance as it popped up every 10 seconds, so according to a guy, I cleared the cache after booting into recovery mode and it took a good 5 minutes. After the wiping, I booted up and i get "starting apps" for some 10 second and then the boot logo. This cycle continues forever. And once I did manage to reach the lock screen but then it wouldn't load Home - "couldn't start home". Can anybody help me out of this mess?
Update : now it's showing "optimising app 46 of 95" but after it finishes, I get an empty screen and only the back and multitask button works and, I get an error when I click home - "couldn't start home".
Please help as, though I have another phone, this is very important to me and lots of my things depend on whether this works or not.
Also, I haven't done a reset yet as I thought it'd be good to ask here first.
Click to expand...
Click to collapse
Use SP Flash Tool !!! Something similar happened to my device (infinite bootloop) and I used SP Tool and now I am using my phone smoothly
Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
I couldn't fix the "Pixel is starting..." issue. Factory Flashing (after removing -w) QQ1A.191205.008 resulted resulted in being stuck at the "G" screen. I flashed the QQ1A.200105.002 factory image (again with -w removed) and was left in the same "Pixel is starting..." state.
Here is where things get interesting:
Over adb I launched the Settings app:
Code:
adb shell am start -a android.settings.SETTINGS
Next, I went into "Security," which prompted for my PIN, and then removed the screen lock. After doing this, I was able to get into /sdcard in the ADB shell, something that was not possible before.
Back in the settings app, I enabled USB File Transfer and copied all my files & photos off. I was also able to launch apps from within the apps list in Settings. This let me export settings/data from other apps that allowed it. :good:
So it seems that entering your PIN in the Settings app also unlocks the phone!
Thanks for describing this and how you ended up resolving it. I am seeing the same "Pixel is starting". Flashing the (March 2020) factory image didn't fix mine either.
I was able to get into Settings by pulling down the notification shade while the "Pixel is starting" message shows. I removed my fingerprints and PIN.
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
I've tried this:
Settings-->Apps & notifications-->App info--> {select any app and tried clicking on icon at top of screen} Nothing. Poked around a bit and tried various things but couldn't figure out how to launch an app from here. Thanks in advance.
docdl said:
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
Click to expand...
Click to collapse
There should be a "Open" shortcut just below the app icon to the left of "Uninstall" (or "Disable" if it is a built-in app).
_Ra1n_ said:
Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
Click to expand...
Click to collapse
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described. I'm also stock, rooted with Magisk, on the January update. I just found that I can get into adb, but I'm a loss of what do to from here. I can't believe toggling a system UI tuner setting could cause a catastrophic crash. How did you end up solving this? Were you able to flash the full factory image while preserving your data? I honestly have no idea what do to at the moment. I'm gonna have to use an older device and research this more after work.
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Ditamae said:
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described.
Click to expand...
Click to collapse
Interesting! Exact same order of events.
Ditamae said:
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Click to expand...
Click to collapse
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
_Ra1n_ said:
Interesting! Exact same order of events.
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
Click to expand...
Click to collapse
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
I did utilize the system UI tuner to disable my alarm icon from showing in the status bar, so I'm hoping I can perhaps find the file associated with the plugin specifically and rename that. Hmm. Only this is systemless... Might not be possible. This is my first rooted device without full read/write capabilities. Not sure how I feel about systemless.
Otherwise, other than time, the only bummer to all this is that I think I'm going to lose the Magisk module YouTube Vanced, as it's not longer supported.
Anyway, thanks very much for your help so far.
Ditamae said:
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
Click to expand...
Click to collapse
If your luck is as good as mine, you should be able to just plug in the device and enable file transfer (Settings > Connected Devices > USB > "Use USB For ... File Transfer."
Note that, as explained above, I had to remove my security PIN in settings before that worked, though.
_Ra1n_ said:
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
I was able to backup my data, and use Solid Explorer with root to search through system files. But, I don't see that directory. I see: data/data/com.android.systemui but no systemui.tuner. Any other idea where those systemui tuner files might be lurking? I'm an RN with a kindergartener home from school, and as much as I love tinkering with Android, now is not a good time.
_Ra1n_ said:
Interesting! Exact same order of events.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Ditamae said:
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Click to expand...
Click to collapse
Sorry for the slow reply. Unfortunately I'm mostly out of ideas.
I'd ask in the general Android Help subforum: https://forum.xda-developers.com/android/help
You'll likely get more eyes on the question (where does SystemUI Tuner store it's settings & how to reset them) and hopefully someone with better knowledge on Android settings/preferences can provide some incite.
Homeboy76 said:
Guide
Do #4 'keep data', then #9 to root.
Make sure you have the latest SDK platform-tools, there is a link in the guide.
Click to expand...
Click to collapse
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
_Ra1n_ said:
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
Click to expand...
Click to collapse
@Ditamae Rain is correct. I have edited my post.