Database Users

Note 3 now Useless > Error Message .....

My Note 3 is completely useless now ... !!! After charging, booted, get Error Message: "Unfortunately, the process android.process.acore has stopped." I clicked on ok, but get the same Error Message. Rebooted, same Error Message. Removed battery, rebooted, same Error Message. Can't do anything with the phone .....

vja4Him said:
My Note 3 is completely useless now ... !!! After charging, booted, get Error Message: "Unfortunately, the process android.process.acore has stopped." I clicked on ok, but get the same Error Message. Rebooted, same Error Message. Removed battery, rebooted, same Error Message. Can't do anything with the phone .....
Click to expand...
Click to collapse
Flash stock firmware using Odin . u can get the firmware packages from www.sammobile.com

Akhilendra Gadde said:
Flash stock firmware using Odin . u can get the firmware packages from www.sammobile.com
Click to expand...
Click to collapse
I called Samsung Tech Support. They told me to do a Reset, which I did. So far everything is good .... All of the apps that got erased are automatically downloading all over again, which is nice. Lost most of my Contacts and Camera Pics, and probably other data (private Journal).

vja4Him said:
I called Samsung Tech Support. They told me to do a Reset, which I did. So far everything is good .... All of the apps that got erased are automatically downloading all over again, which is nice. Lost most of my Contacts and Camera Pics, and probably other data (private Journal).
Click to expand...
Click to collapse
Nice to see your device is now working well.
But did u do the same steps again after doing a factory reset? Or using as it is?

Akhilendra Gadde said:
Nice to see your device is now working well.
But did u do the same steps again after doing a factory reset? Or using as it is?
Click to expand...
Click to collapse
I don't know if it was a factory reset ..... What are the "same steps"?

vja4Him said:
I don't know if it was a factory reset ..... What are the "same steps"?
Click to expand...
Click to collapse
When switch on your phone, push vol up+home+power button at the same time. Phone will enter stock recovery. In recovery you can select factory reset.
Sent from my SM-N9005 using XDA Premium 4 mobile app

vja4Him said:
My Note 3 is completely useless now ... !!! After charging, booted, get Error Message: "Unfortunately, the process android.process.acore has stopped." I clicked on ok, but get the same Error Message. Rebooted, same Error Message. Removed battery, rebooted, same Error Message. Can't do anything with the phone .....
Click to expand...
Click to collapse
If you had googled the error message you would have saved yourself some time. This used to happen to my HTC sensation XL and once with my note 3.
That process is your contacts syncing repeatedly, so just navigate to your application settings while cancelling the error message and force stop contacts and contacts sync, clear cache and you're done.

Most people don't know what to do when they get their device stuck in problems. Same was up with op. He didn't knew clearing cache would solve it . He was on the safe side by asking the tech ofiicials itself.
If he would go to recovery and would mess up somethings he would be in more trouble.
Anyways the issue is solved. :good:
I don't think thread discussion should still be open.
@op , if u want u may ask moderators to close this thread if u are done with.
Regards,
Akhilendra Gadde

Possible Problem: Android 4.4.2 KitKat - Worst Android Version Ever!
vja4Him said:
My Note 3 is completely useless now ... !!! After charging, booted, get Error Message: "Unfortunately, the process android.process.acore has stopped." I clicked on ok, but get the same Error Message. Rebooted, same Error Message. Removed battery, rebooted, same Error Message. Can't do anything with the phone .....
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Which Android-Version and BaseBand number has it got?
4.4.2 is Problematic and Buggy. And Also Deletes files
4.3 is Good.
The WRITE_EXTERNAL_STORAGE permission must only grant write access to the primary external storage on a device. Apps must not be allowed to write to secondary external storage devices, except in their package-specific directories as allowed by synthesized permissions. Restricting writes in this way ensures the system can clean up files (=delete them forever, without recovery chance because of that not-so-good MTP that repalced the much better MASS-STORAGE!) when applications are uninstalled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MUAHAHAHAHAHAAAAAHHHHHHHH!!!!!
((Multiple external Storage Devices>Text3)
Click to expand...
Click to collapse
Why does Google want that Android Deletes „Junk"-files?
If you take Pictures and Video Recordings with CameraMX for Example, then you uninstall CameraMX, then your Recordings would stay there at Andorid 4.3. But evil KitKat 4.4.2 Andriod would delete your files!
There would be a chance at Rooted Devices to recover with IsoBuster, the worldwieds best data recovery program, if your device is rooted. But with a locked bootloader, if you want to unlock it, there's something called „Factory-Data-Reset!“
PLEASE; Google!
Please remove this „data-junk-cleaner"!
Memories and CameraMX-Reocrdings or Whatever like Paint-Pro-Drawings (I Love Playing with Kids Mode!❤❤) aren't junk!
Is there a way to turn off this DataJunk-Removage that cleans more valueable data than junky data?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
Backup before doing a Factory-Reset!
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
There's a Difference between Factory-Reset and Factory-DATA-_Reset!
Factory Reset is Resetting Changes (not Physical damage) to the Fevice to the point where it was copletely unused.
Factory DATA Reset Wipes (Safe-Deletes) all User Data from Storage. No recovery chance anymore! TOO BAD!

AnDrOiD 4.4.2 is the most BOGUS AndrOId Version i've EVER SEEN in the version History List!

IS Private Mode NOT Working for you after Rooting? - Try This... - LOLLIPOP

Thread Updated - This Thread is now about Private Mode in LOLLIPOP
What is Private Mode?:
http://www.androidcentral.com/how-use-private-mode-samsung-galaxy-s5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OLD KITKAT REFERENCE/SOLUTION BELOW
Is Private Mode working after you rooted your Note 4?
If the answer is no... try this flashabe zip:
Private Mode Fix
I have already demonstrated that Private Mode can continue to work after rooting/tripped Knox:
See post #24...
http://forum.xda-developers.com/not...-configure-fingerprint-scanner-t2919478/page3
Please, post results here...

If i understand correctly, it wont work for stock rooted. U have to use an rom

I can confirm this works on DynamicKat 1.2, but the quick setting did not show up. I am still glad that private mode is working now. Thank you TEKHD!

It's working for me using an Xposed module called XSecureStorage

Confirming that this works on a stock rooted deodexed rom on the Sprint Note 4.
Thanks!

OK I may have figured out another piece of this puzzle. Maybe someone more knowledgeable than me can use it to get to the bottom of it. Some background:
I was running stock, rooted. I made two complete nandroids in TWRP. The first directly after rooting. The second after a few mods but before installing Xposed framework and Wanam Xposed. I knew Xposed might kill my Private mode and indeed it did!
Removing the XsecureStorage module did not fix it, nor did uninstalling Wanam and the Xposed framework, nor flashing the Private mode fix listed in this thread. Unfortunately neither did restoring the second nandroid and that really puzzled me since Private mode was working when I made that nandroid. I tried all these things more than once to be sure. It seemed like nothing would get back my Private mode which upset me since I had a file there I really wanted back!
Then I did a complete wipe and restored the first nandroid and finally Private mode was working! Unfortunately the file I wanted was only in the second nandroid. When I restored the second nandroid again (this time just system & data) Private mode stopped working so I figured it could be one of the mods I'd installed before making that second backup. Finally I traced it to the 4 way reboot mod which alters android.policy.jar. I believe quite a few mods alter this file.
So maybe Private mode locks up when that file is altered (though there may be other conditions which also breaks it). Anyway, my advice is make nandroids - lots of them! And beware! Like me you may install some mods and be sailing along with Private mode working, only to find that when you restore a nandroid, it no longer works because of something you installed. Why this should be the case I don't know.
Sorry for the long post but I hope it helps
someone who can test this further and figure it out!
Sent from my SM-N910T using XDA Free mobile app

Dumbo53 said:
OK I may have figured out another piece of this puzzle. Maybe someone more knowledgeable than me can use it to get to the bottom of it. Some background:
I was running stock, rooted. I made two complete nandroids in TWRP. The first directly after rooting. The second after a few mods but before installing Xposed framework and Wanam Xposed. I knew Xposed might kill my Private mode and indeed it did!
Removing the XsecureStorage module did not fix it, nor did uninstalling Wanam and the Xposed framework, nor flashing the Private mode fix listed in this thread. Unfortunately neither did restoring the second nandroid and that really puzzled me since Private mode was working when I made that nandroid. I tried all these things more than once to be sure. It seemed like nothing would get back my Private mode which upset me since I had a file there I really wanted back!
Then I did a complete wipe and restored the first nandroid and finally Private mode was working! Unfortunately the file I wanted was only in the second nandroid. When I restored the second nandroid again (this time just system & data) Private mode stopped working so I figured it could be one of the mods I'd installed before making that second backup. Finally I traced it to the 4 way reboot mod which alters android.policy.jar. I believe quite a few mods alter this file.
So maybe Private mode locks up when that file is altered (though there may be other conditions which also breaks it). Anyway, my advice is make nandroids - lots of them! And beware! Like me you may install some mods and be sailing along with Private mode working, only to find that when you restore a nandroid, it no longer works because of something you installed. Why this should be the case I don't know.
Sorry for the long post but I hope it helps
someone who can test this further and figure it out!
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I have been looking into this... I think it's actually the file:
system/framework/android.policy.odex
Flashable zip: (odex injection)
Can anyone with Jovy's ROM try this fix: (in order to verify if this fix makes Private Mode work with Jovy's ROM)
http://tek.serveftp.net/xda/Private_Mode_for_jovy_Fix_N4_tekhd.zip
If this works... All credit goes to you @Dumbo53
Quick Instructions...
1. Deactivate Xposed Framework
2. Reboot into recovery and flash file above...
3. Reboot... and see if Private Mode is working...

I'm on firekat v4 not jovy's rom, but I lost my private mode along the way. I thought it was when I tripped knox rooting with the temporary recovery cf autoroot uses.
This fixed my issue.
Rocking private mode currently. Hadn't been able to use it since the day I started rooting and flashing.

I've been trying to install the Xposed module for secure storage. However it says waiting for download for over 20 minutes now. Any ideas on this because I'd really like to use this feature of my phone. Thanks.
Sent from my SM-N910T using XDA Premium HD app

Ok the server for Xposed was down last night. It is back up now. I installed the Xsecurestorage module and private mode is working.
So for those of you with the Xposed framework installed, that's probably the easier route over installing a flashable zip file.
Sent from my SM-N910T using XDA Premium HD app

not sure whats different but im on stock rooted and neither wanam nor xsecure fixed my private mode. IDK

Did you try the flashable zip in the op?

flash did not fix on stock rooted rom. No Xposed installed yet

i was going to try flashing that file but if you say it doesnt work...
When updating my phone yesterday via odin, i flashed the update...checked private mode. (it worked)
Flashed root file and checked private mode...(it worked) Told SuperSU to not disable Knox. Checked private mode again...(it worked)
Installed Xposed...checked private mode.(private mode failed). I have tried the xsecurestorage and wanam module and neither worked. S health works fine. Just not private mode. Was pretty excited about being able to use this. My only other option i suppose is to go with a deodex rom that stays closest to stock i guess.

Just used this trick again. Firekat v5.
I think I lost private mode when I tripped Knox with cf autoroot:
Nice to have it back. Although, I'm going to need a more exciting life before I need it.

This actually soft bricked my phone. Stock but rooted and stuck at the tmobile scree.

Just used this trick again. Infamous 2.3:

Working for me on Infamous 2.2
Sent from a mobius strip

Hey guys.
I started another threat but TEKHD requested i put this here as well. I found a method that worked for the 910f and worked for myself.
In data/system/secure_storage delete the personalpage folder
In data/system/users delete privatemode_edk_1000.
This got it working on my phone. Still using Xsecurstorage in xposed and haven't tested yet with it not on.
http://forum.xda-developers.com/note-4-tmobile/general/how-fixed-private-mode-t2985441

This Fix didn't work for me, but, the one mentioned by @avengethis1 at THIS POST worked for me on my T-Mobile Note 4 N910T with Stock ROM and TWRP Recovery

Success rooting SM-P900 Knox 0x0 (SuperSU)

I finally managed to root my SM-P900 without tripping knox and it survives a reboot. I'm running the OH2 Lollipop ROM and used the latest PC version of Kingoroot. This installs their own version of Superuser and I have been able to use Titanium Backup to remove Knox and other bloatware. I previously tried and failed with multiple Android versions of Kingroot and Kingoroot.
I'm not 100% happy having the Kingoroot software on my tablet (or my PC for that matter) as I'm unsure about privacy and security issues so I decided to try to install SuperSU instead and remove the Kingoroot files. First of all I tried running Flashfire but it said that the tablet wasn't rooted with the version of Superuser it requires. I then tried running Super Sume but it reported that the tablet wasn't rooted with Kingroot or Kingoroot. Next, I tried installing SuperSU from the app store but it got stuck at downloading the binaries so I removed it. Next, I installed the Kingoroot app and ran it - it reported that the tablet wasn't rooted (!) and when I ran it it then reported it had successfully rooted. I then ran Super Sume again and this time it ran but eventually hung and there was no sign of SuperSU having been installed. Next, I ran Flashfire and this time it obtained root and appeared to run successfully. I attempted to flash the stock OH2 ROM with it and inject Superuser but just ended up with a black screen and non-booting tablet. I then needed to re-flash the ROM with Odin and this obviously removed root.
So I think my next step will be to do a factory reset on my rooted and de-bloated tablet which will give me a sort of satisfactory outcome, i.e. a safe and secure ROM with no Knox or bloatware. But if anyone has any ideas about replacing the Kingoroot Superuser I'm all ears!
EDIT my next step is to try the manual method of running scripts here http://androidforums.com/threads/script-replace-kingoroot-with-supersu.919175/ but this was written for a different device running Kitkat so I'm not sure how it will go.

I've cracked it! The script method above didn't work. Here are the steps I took:
1. Factory reset tablet then allowed it to do an official update to OI1
2. Enabled USB debugging & installation of unknown apps
3. Ran the PC version of Kingoroot (not Kingroot)
4. Installed Titanium Backup then used it to uninstall all Knox software then rebooted
5. Installed & ran Kingroot 4.9 http://www.appsandroidapk.com/tools/kingroot/ and used it to root the tablet again
6. Installed & ran SuperSUme (paid-for app) which removed the Kingoroot and Kingroot SU apps and installed SuperSU
7. Updated SuperSU binaries and rebooted
Remember to turn off automatic updates otherwise your tablet's status will change from Official to Custom.
Screenshots attached!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hello on step 6 SuperSume doesn't seems to progress at all, while all the other steps seems to be fine, I'm using supersume 9.3.8, is it normal or is it like VERY long ?
PS : tried with the exact same versions you used, still the same, the progression bar increase a bit then got stuck at 10% Tried also to uninstall with SuperSu, instant crash...

Ok, I tried and it tripped Knox here...

Sorry about your Knox flag being tripped
It all worked smoothly when I did it on mine, Kingoroot did its stuff in a few minutes and SuperSUme took less than 2 minutes to finish. Not sure what happened with yours. Mine is still running well, rooted and Knox 0x0.

dwl99 said:
Sorry about your Knox flag being tripped
It all worked smoothly when I did it on mine, Kingoroot did its stuff in a few minutes and SuperSUme took less than 2 minutes to finish. Not sure what happened with yours. Mine is still running well, rooted and Knox 0x0.
Click to expand...
Click to collapse
Don't worry it's not under warranty anyway, I guess I left a knox soft before putting twrp and that might be the reason. Now I'm on cm12.1 and running fine. I'm pretty sure, the reseller would give me 100€ for that tablet anyway, so I better keep it for myself !

That explains it, any modded recovery will trip Knox no matter what you do. I still have stock recovery.
Sent from my SM-N9005 using Tapatalk

Im finally ready to root my tablet, Im tired of all of the lag I get and it seems as Samsung has let the 12.2 pro die.
Im running 5.02
Build: LRX22G.P900UEU1COL1
Kernel: 3.4.39-5574008
Knox: 2.3
USA version
Will this root method work without issue for me?

It should do
Sent from my SM-T700 using Tapatalk

I'm curious, will this method work just on P900 or all variances?

Cant erase FOTA via fastboot, update snuck through

Hey gang, I doubled checked and couldn't come up with an answer but somehow Android System Update got past my frozen FOTA & Update Center (few others) as well as having system updates unchecked in Dev Options. I haven't installed the update & would love to stay on 10D.
So I boot into fastboot, run the fastboot erase fota and get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As most can spot I'm definitely in fastboot as the fastboot getvar all and fastboot reboot function just fine. I tried defrosting the fota & others and that also didnt work.

Which phone do you have?

androiddiego said:
Which phone do you have?
Click to expand...
Click to collapse
Tmob,
I moved the Update.zip from Cache and the otacerts.zip from system/etc/security to my SD card and then went to settings/app [enable show system]/Update Center and cleared data and cache to remove the notification. I think I cleared the cache on Google Play Services as well the 1st time around but the notification came back on restart.
Side note: I had the update center frozen & it still was during clearing the data & cache. I've rebooted a few times and notification is still gone..hope it stays away. Still curious why the fast boot commands didnt work.

2muchspl said:
Tmob,
I moved the Update.zip from Cache and the otacerts.zip from system/etc/security to my SD card and then went to settings/app [enable show system]/Update Center and cleared data and cache to remove the notification. I think I cleared the cache on Google Play Services as well the 1st time around but the notification came back on restart.
Side note: I had the update center frozen & it still was during clearing the data & cache. I've rebooted a few times and notification is still gone..hope it stays away. Still curious why the fast boot commands didnt work.
Click to expand...
Click to collapse
I'm on tmo also.
Ok, here's what I did. It's the old Sammy trick. As you did, delete or move the update.zip file from /cache directory. You will have to unfreeze the update center to get the notification again.
I selected the update notification from notifications and then selected to install it. See the attached. It said rebooting. It won't reboot because the necessary file is gone. Wait 10 seconds and touch the recents home key and close the window. Done!
I rebooted the phone and no nag.
I'm on OvrDrive's 10j base now so it doesn't matter, but if you want to stay on 10d and stop the nags, this will work. Once the update fails, it won't try anymore.

androiddiego said:
I'm on tmo also.
Ok, here's what I did. It's the old Sammy trick. As you did, delete or move the update.zip file from /cache directory. You will have to unfreeze the update center to get the notification again.
I selected the update notification from notifications and then selected to install it. See the attached. It said rebooting. It won't reboot because the necessary file is gone. Wait 10 seconds and touch the recents home key and close the window. Done!
I rebooted the phone and no nag.
I'm on OvrDrive's 10j base now so it doesn't matter, but if you want to stay on 10d and stop the nags, this will work. Once the update fails, it won't try anymore.
Click to expand...
Click to collapse
These are great instructions, Im keepin them handy if my notification returns. How do you like OvrDrive's rom? I've traditionally stayed rooted stock but lately been curious about trying one out for a test drive.

2muchspl said:
These are great instructions, Im keepin them handy if my notification returns. How do you like OvrDrive's rom? I've traditionally stayed rooted stock but lately been curious about trying one out for a test drive.
Click to expand...
Click to collapse
I hope this worked for you. I was afraid to try this even though it used to work on all my sammy phones, but I bit the bullet and it worked. @OvrDriVE 's ROM is great. I do a lot of lurking watching what is going on with each rom and I feel that Ovrdrive has the best. That's not to say anything bad about the other guys. They are very involved and actually help people out in rom threads that aren't even theirs. We have a great group of folks here. With that said, OvrDrive's I believe has the least complications and he is very responsive. I believe he came from a Note 4 which is where I came from and his reputation on the Note 4 was excellent.

“Google keeps stopping” after Android Oreo update

I got a Nexus 6P and it received the Oreo update yesterday. After installing the update, there were few errors like "Gboard stopped working" etc., That happened only once and the device was working normally for few hours. Now suddenly, I keep getting "Google keeps stopping" in the launcher screen. When I close the popup, the launcher is reloaded and the popup appears again immediately. Phone is currently kind of unusable. Tried to open Settings, but that got closed as well.
Tried checking Play Store for the latest updates, but got none. Anyone else got this issue? Any idea if this can be resolved?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

emaillenin said:
I got a Nexus 6P and it received the Oreo update yesterday. After installing the update, there were few errors like "Gboard stopped working" etc., That happened only once and the device was working normally for few hours. Now suddenly, I keep getting "Google keeps stopping" in the launcher screen. When I close the popup, the launcher is reloaded and the popup appears again immediately. Phone is currently kind of unusable. Tried to open Settings, but that got closed as well. Tried checking Play Store for the latest updates, but got none. Anyone else got this issue? Any idea if this can be resolved?
Click to expand...
Click to collapse
Try wiping the cache partition from stock recovery. If you have TWRP (doesn't sound like it) wipe dalvik cache as well.

v12xke said:
Try wiping the cache partition from stock recovery. If you have TWRP (doesn't sound like it) wipe dalvik cache as well.
Click to expand...
Click to collapse
In the stock recovery, I see only these options:
Reboot bootloader - Restarts this recovery
Recovery mode - Boots up and then shows "No Command"
Power off
Barcodes - Shows barcodes of various things about the device.
Start - Starts the device normally, issue still exists
I don't see any option for wiping the cache partition.
I don't have TWRP installed, but will do if that is my last option.

Just figured out how to clear the cache partition from recovery mode. Just tried clearing the cache partition. But the issue still persists.

emaillenin said:
Just figured out how to clear the cache partition from recovery mode. Just tried clearing the cache partition. But the issue still persists.
Click to expand...
Click to collapse
It's kind of a long shot but you can go into settings>>apps and force close and wipe data from both Google App and Google Now Launcher, then restart the phone. If you are still seeing the error regularly then you download the full OTA (.019) and sideload it from recovery mode. You will not lose your data this way. If that sounds too daunting, you can also do a factory reset from recovery which will wipe your userdata, so be sure and back up your stuff before the factory reset.

It's kind of a long shot but you can go into settings>>apps and force close and wipe data from both Google App and Google Now Launcher, then restart the phone.
Click to expand...
Click to collapse
I can't do that, since I am not able to open Settings -> Apps. It gets closed as "Settings has stopped working"
If that sounds too daunting, you can also do a factory reset from recovery which will wipe your userdata, so be sure and back up your stuff before the factory reset.
Click to expand...
Click to collapse
Just did a factory reset. I didn't get the error for an hour. After setting up all my apps for half a day, the error came back. It is unfortunate that even stock Android has issues with Google's official app.

emaillenin said:
I can't do that, since I am not able to open Settings -> Apps. It gets closed as "Settings has stopped working"
Just did a factory reset. I didn't get the error for an hour. After setting up all my apps for half a day, the error came back. It is unfortunate that even stock Android has issues with Google's official app.
Click to expand...
Click to collapse
The problem is on your end. You will need to properly wipe your phone and reinstall Android. I would suggest you just go ahead and unlock your bootloader now, because unlocking at any point in the future will wipe the phone. After that is done, re-install Android 8.0. There are many tutorials on how to do this. It will not void any warranty you may have. It will give you more tools to work with in the future. Good luck.

emaillenin said:
I got a Nexus 6P and it received the Oreo update yesterday. After installing the update, there were few errors like "Gboard stopped working" etc., That happened only once and the device was working normally for few hours. Now suddenly, I keep getting "Google keeps stopping" in the launcher screen. When I close the popup, the launcher is reloaded and the popup appears again immediately. Phone is currently kind of unusable. Tried to open Settings, but that got closed as well.
Tried checking Play Store for the latest updates, but got none. Anyone else got this issue? Any idea if this can be resolved?
Click to expand...
Click to collapse
Try Nova launcher. It's working great. Best luck.

There is some critical error for the new android Oreo (for me is nexus 6p) which make a system crash on the desktop (google now launcher) and on settings (you can't open app list). It is can be created by any of your applications which you need to find. So only way to remove the app, in this case, it is to use a google play application or maybe some other launchers. For me, it was "6 Minute English". I find it via installing nova launcher and on the common app list, the application was shown without a logo, with green robot image instead.

Google keeps syopping after OREO update
I had the same problem with my Samsun Galaxy J7 after the update. I just unstalled the google from the apps. It went back to the previous version. Now the problem is solved